Difference between revisions of "ICyPhy Webex Feb 4 2012"

From Murray Wiki
Jump to navigationJump to search
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:


Presentations:
== Presentations: ==
* [http://www.icyphy.org/icyphy/wiki/uploads/Main/NOzay-Feb4 Overview of the MuSyC challenge problem (Necmiye)]
* [https://www.cds.caltech.edu/~murray/wiki/images/5/50/NOzay-3Feb13-ICyPhy.pdf 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: ==
# Continuous-time synthesis
# Continuous-time synthesis
# Modelica like component models
# Modelica like component models
# Identify parts of the design process where logic has to be designed by hand (so that we can try out synthesis).
# Identify parts of the design process where logic has to be designed by hand (so that we can try out synthesis).
# Sensor placement/sensor logic
# Sensor placement/sensor logic
# A unified language to capture multiple views (contract like specs in this language)
# A unified language to capture multiple views (design concerns) and/or abstraction levels (contract-like specs in this language)
# 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?)
# 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?)
# More interesting distributed control architectures:  
# More interesting distributed and/or hierarchical control architectures:  
## allowing controllers to share contactors
## allowing controllers to share contactors
## allowing decisions to be made by voting
## allowing decisions to be made by voting
## mapping sensing and control points to controllers
## mapping sensing and control points to controllers
## automatically finding local contracts for controllers
## automatically finding local contracts for controllers
## automatically explore distributed control architectures using contracts and possibly different specialized analysis and synthesis frameworks


References:
[http://www.icyphy.org/icyphy/wiki/Main/2013February5DesignDriverMeeting Corresponding iCyPhy wiki page (limited access)]
* J. Finn, M. Mazumdar, A. Sangiovanni-Vincentelli, [http://www.musyc.org/thms/distributed/EPSmodelingSysML_V_02.pdf  767 Electric Power System Modeling in SysML], MuSyC Public Report.
 
* Robert Rogersten, Huan Xu, Necmiye Ozay, Ufuk Topcu, and Richard M. Murray, [http://www.cds.caltech.edu/~murray/preprints/rog+13-hscc_s.pdf An Aircraft Electric Power Testbed for Validating Automatically Synthesized Reactive Control Protocols], Hybrid Systems: Computation and Control (HSCC) 2013.
[http://www.cds.caltech.edu/~murray/wiki/index.php/Distributed_Sense_and_Control_Systems Richard's MuSyC project page]
* Huan Xu, Necmiye Ozay and Richard M. Murray, [http://www.cds.caltech.edu/~murray/preprints/xom13-hscc_s.pdf A Domain-Specific Language for Reactive Control Protocols for Aircraft Electric Power Systems], working paper.
 
== References: ==
* [http://www.musyc.org/thms/distributed/EPSmodelingSysML_V_02.pdf  767 Electric Power System Modeling in SysML], J. Finn, M. Mazumdar, and A. Sangiovanni-Vincentelli. MuSyC Public Report 2011.
* [http://www.cds.caltech.edu/~murray/preprints/rog+13-hscc_s.pdf An Aircraft Electric Power Testbed for Validating Automatically Synthesized Reactive Control Protocols], Robert Rogersten, Huan Xu, Necmiye Ozay, Ufuk Topcu, and Richard M. Murray. Hybrid Systems: Computation and Control (HSCC) 2013.
* [http://www.cds.caltech.edu/~murray/preprints/xom13-hscc_s.pdf A Domain-Specific Language for Reactive Control Protocols for Aircraft Electric Power Systems], Huan Xu, Necmiye Ozay and Richard M. Murray, working paper.
* [http://www.cds.caltech.edu/~murray/papers/2012g_xtm12-cdc.html Reactive Protocols for Aircraft Electric Power Distribution], Huan Xu, Ufuk Topcu, and Richard M. Murray. 2012 Conference on Decision and Control (CDC).
* [http://www.cds.caltech.edu/~murray/papers/2012g_xtm12-cdc.html Reactive Protocols for Aircraft Electric Power Distribution], Huan Xu, Ufuk Topcu, and Richard M. Murray. 2012 Conference on Decision and Control (CDC).
* {{otm11-cdc}}
* {{otm11-cdc}}
* {{otwm11-iccps}}
* {{Won+11-hscc}}
* {{Won+11-hscc}}

Latest revision as of 21:40, 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 (design concerns) and/or abstraction levels (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 and/or hierarchical 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
    5. automatically explore distributed control architectures using contracts and possibly different specialized analysis and synthesis frameworks

Corresponding iCyPhy wiki page (limited access)

Richard's MuSyC project page

References: