Robotics Systems Types

formally:
i cant do that right now as i am not at work

content:
1+2) a phoneme is not software dependant, see
http://www.phon.ucl.ac.uk/home/sampa/german.htm
http://en.wikipedia.org/wiki/Phoneme
The comment referring to mbrola is there as this seems to be some kind
of "standard" implementation known to everybody in that field.

3) you mean utterance.text? That field is a descriptor for the content.
For example you send an utterance with an audio file saying "my name is flobi"
you will have the associated phoneme list and a textual description (=.text)
One purpose is debugging (e.g. when looking at rsb lggger you can see what this binary blob represents)
The other one is that one might need the textual description to show it on a GUI while teh robot
is playing the audio file. Converting the phonemes back to text is not possible or lets say not easy:
example: Trotz=trOts / Schutz=SUts / hübsch = hYpS

ping

Simon? Any feedback here?

Simon?

ok, please use your suggested patch and include it into RST.
thanks!

There are TODOs in the patch. We cannot merge it until these are fixed / specified.

One last question. Is it necessary to make all members of Utterance required? E.g. including a SoundChunk sounds quite hard for some potential use cases of this type.

we can discuss that.

soundchunk: i could not imagine a use without this.
when you do not need the audio one would have a plain phonemelist.
What about introducing a PhonemeList (or whatever you would like to call it) datatype:

mesage PhonemeList{
    repeated Phoneme phonemes = 1;
}

And then including this in the Utterance?

I would vote for having the string description as required so that the users
are forced to fill this in. Otherwise they just skip that part and that makes debugging
quite hard. Another use of the description might be additional on screen text rendering in noisy environments.

Ok, so I propose that you add the annotation to Phoneme to generate the list type automatically.

For the description field: can we rephrase this as the "textual representation of the utterance" or something like transcription? So far we do not have debugging information in the data. But all use cases sound like this is basically the represented textual representation (screen rendering requires this).

Ok, so I propose that you add the annotation to Phoneme to generate the list type automatically.

how do i do that?

https://code.cor-lab.org/projects/rst/repository/revisions/5796a11a1d59abff23537526335229a3fd88a327/diff/

And how is the collection named afterwards?
or is there a documentation for that collection feature somewhere?

Not yet documented. It's quite new. The default name will be TypeCollection, but can be changed:
https://code.cor-lab.org/projects/rst/repository/revisions/a91af7f95f1db3bc53204fb92cb9a72e4464e319