• View
• Edit
• History
• Print

ProgrammingTheSwarmWorkshop2015Agenda

(redirected from Main.ProgrammingTheSwarmWorkshopAgenda)

May 27-29, 2015, Berkeley.

Tentative Agenda. We expect the agenda to be very fluid, so this is just a guideline.

Important: Do the homework. In particular, install Ptolemy II. If you fail to do this, we will try to help starting at 8am Wednesday.

Notes from the Accessor Design Discussion are available.

Wednesday May 27:

Thursday May 28:

Friday May 29:

Common Exercise

1. Audio Accessor and Nashorn/Ptolemy II implementation. See Common Exercise Build An Audio Accessor.

Project suggestions:

1. 1. Find Node modules for audio capture and playback.
   2. Design a JavaScript module API for audio services (coordinate with common exercise outcome).
   3. Implement the JavaScript module using Node.
   4. Design AudioCapture, AudioPlayer, and ClipPlayer accessors (coordinate with common exercise outcome).
2. Kubi accessor (RESTful interface, so should work on everything)
   1. Figure out the Kubi API. According to Tim Huang <tim@revolverobotics.com>, something like http://new.kubi.me/api/1.0/move-kubi, with parameters like:
      1. hardware_id: 'XXXXXX',
      2. x: 0 <= x <= 1
      3. y: 0 <= y <= 1
3. Browser accessor with Nashorn implementation (boilerplate is checked in for Nashorn/Ptolemy II). A browser accessor accepts HTML and JavaScript input and uses a browser to provide a GUI to a swarmlet.
   1. Understand the boilerplate (which is very spare).
   2. Enhance its capabilities to, for example, plot audio signals from the common exercise in the browser.
4. TI SensorTag accessor with Nashorn and/or Node implementation (the SensorTag accessor on the website is not really what we want)
   1. Find Java and/or Node bluetooth interfaces.
   2. Design a JavaScript module API for bluetooth.
   3. Implement the JavaScript module using Nashorn and/or Node.
   4. Design SensorTag accessor.
5. ROS accessor with Nashorn and/or Node implementation
   1. Find or build Java and/or Node ROS interfaces.
   2. Design a JavaScript module API for ROS.
   3. Implement the JavaScript module using Nashorn and/or Node.
   4. Design ROS accessor.
6. Build an accessor to control a pan-tilt-zoom camera (we can provide one).
7. YourSensorOrActuator accessor with Nashorn and/or Node implementation
   1. Find or build suitable Java and/or Node interfaces.
   2. Design a JavaScript module API for this interface.
   3. Implement the JavaScript module using Nashorn and/or Node.
   4. Design SensorTag accessor.
8. ScriptedSignalProcessing accessor with Nashorn implementation.
   1. Get familiar with ptolemy.math.SignalProcessing class
   2. Design a JavaScript module API for some of the methods in this class.
   3. Implement the JavaScript module using Nashorn.
   4. Use the ScriptedAccessor of the previous project to demonstrate use of this module.
9. Help develop the AccessorJS platform.
   1. Implement and extend functionality to be more consistent with Ptolemy implementation.
   2. Work on the development of MoCs for this platform.
   3. Develop a browser-based front-end for Accessor editing.
   4. Get in contact with Chris Shaver shaver@eecs.berkeley.edu.
10. Leverage synchronous events in DE
    1. Build a paper-rock-scissors game with two sensors (e.g., WiiMote?)
    2. ...
11. Build new modules
    1. BLE
    2. GDP
    3. UDPSocket
    4. Url (support for reading and building URLs)
    5. ...
12. Get Vert.x Multicast working
13. Oort Smart Socket Accessor
14. TODOs and FIXMEs:
    • HttpClient module
      • http fails silently (response == null) [Marten]
    • Accessor interface
      • If exports.setup is changed, upon reload, it should remove ports that are not registered [?]
      • If the source of an accessor is local, then automatically reload if the file has changed [?]