Embedded Motion Control 2017 Group 5 Meetings Overview

From Control Systems Technology Group

(Difference between revisions)
Jump to: navigation, search
(Meeting 1 (12-5-2017))
Line 11: Line 11:
<li>Information flows need to be specified.
<li>Information flows need to be specified.
<li>Code the corridor challenge in pairs (Sjoerd & Bart, Rodrigo & Kagan, Angel & Torben).
<li>Code the corridor challenge in pairs (Sjoerd & Bart, Rodrigo & Kagan, Angel & Torben).
 +
 +
 +
== Meeting 3 (19-5-2017) ==
 +
Discussed corridor challenge progress.
 +
 +
<li>Focus on framework, easier to discuss if we are more specific.
 +
<li>Think carefully on what we need/want to test (some parameters) Simulation vs Real.
 +
<li>Code the corridor challenge separately, in pairs Sjoerd & Bart (world model) , Rodrigo & Kagan (Motion Controller), Angel & Torben (Action Manager).

Revision as of 11:58, 30 May 2017

Meeting 1 (12-5-2017)

Reviewed initial concept design with tutor.

  • Team needs to think more on software architecture (components, functions, flows).
  • Current architecture diagrams are not explicit enough.
  • Agreed to meet next week to discuss findings and prepare first presentation.

    Meeting 2 (16-5-2017)

    Discussed initial design and prepared presentation.

  • Presentation will be made.
  • Information flows need to be specified.
  • Code the corridor challenge in pairs (Sjoerd & Bart, Rodrigo & Kagan, Angel & Torben).

    Meeting 3 (19-5-2017)

    Discussed corridor challenge progress.

  • Focus on framework, easier to discuss if we are more specific.
  • Think carefully on what we need/want to test (some parameters) Simulation vs Real.
  • Code the corridor challenge separately, in pairs Sjoerd & Bart (world model) , Rodrigo & Kagan (Motion Controller), Angel & Torben (Action Manager).
  • Personal tools