Robot movement language

[craigvear]

Expand the range of movement of the robot arm across a rage of response types:

Response types:

• [ ] continuous human data movement (from embodied musicking dataset)
• [ ] continuous movement from Nebula output stream (realtime x,y,z rather than block moves)
• [ ] Block moves to include inspiration points from Christian Wolff's "For 1, 2, 3 players" and Cardew's "Treatise"
• [ ] designing page size/ arm stretch parameters in config (e.g. where the edge of the page is)
• [ ] maintain the open functions so that new robot API's/ primitives can seamlessly slide in
• [ ] implement Z dimension as an optional response
• [ ] design an input format for data streams coming from affect/ gate module
• [ ] design a function that allows off the edge of page movement
• [ ] implement a sub-looper that can capture some large rhythmical gesture ( from random or dataset or stream, or all?) and repeat gesture with only a slight shift in an axis (duration 2-6 seconds ... this should be ordered by the affect/ gate module)
• [ ] When new robot arrives, implement rotating gripper to allow different coloured pens

[craigvear]

Adam. I'm going to start organising the gesture manger to align to 1 of the 5 modes and see what happens. It doesn't effect your task list, but you need to be aware of it.

[craigvear]

This was a pretty helpful library when I was building my own stuff for the Dobot. https://github.com/AlexGustafsson/dobot-python/tree/master/examples

[craigvear]

Adam - I'm going to close this, and open up task specific issues to complete.