Difference between revisions of "ICyPhy Webex Feb 4 2012"

From MurrayWiki
Jump to: navigation, search
Line 3: Line 3:
 
* [http://www.icyphy.org/icyphy/wiki/uploads/Main/NOzay-Feb4  Overview of the MuSyC challenge problem (Necmiye)]
 
* [http://www.icyphy.org/icyphy/wiki/uploads/Main/NOzay-Feb4  Overview of the MuSyC challenge problem (Necmiye)]
 
* [http://www.icyphy.org/icyphy/wiki/uploads/Main/PNuzzo-Feb4  Review of Berkeley modeling and design space exploration work (Pierluigi)] - limited access on iCyPhy wiki
 
* [http://www.icyphy.org/icyphy/wiki/uploads/Main/PNuzzo-Feb4  Review of Berkeley modeling and design space exploration work (Pierluigi)] - limited access on iCyPhy wiki
* [http://www.icyphy.org/icyphy/wiki/uploads/Main/MXu-Feb4 Review of Caltech correct-by-construction synthesis work (Mumu)]
+
* [https://www.cds.caltech.edu/~murray/wiki/images/2/20/MXu_ControlSynthesis_WebEx_4Feb13_iCyPhy.pdf Review of Caltech correct-by-construction synthesis work (Mumu)]
  
 
Possible directions for future work:
 
Possible directions for future work:

Revision as of 05:58, 5 February 2013

Presentations:

Possible directions for future work:

  1. Continuous-time synthesis
  2. Modelica like component models
  3. Identify parts of the design process where logic has to be designed by hand (so that we can try out synthesis).
  4. Sensor placement/sensor logic
  5. A unified language to capture multiple views (contract like specs in this language)
  6. Possible ways to integrate EPS domain specific language and LTL spec generator to other design tools (what that language can/should capture to be useful?)
  7. More interesting distributed control architectures:
    1. allowing controllers to share contactors
    2. allowing decisions to be made by voting
    3. mapping sensing and control points to controllers
    4. automatically finding local contracts for controllers

References: