Full-Speed Simulator Meeting Notes

			      7 Jan 2015

For the next meeting:

* Diagrams of proposed synchronization designs: Rob, Rich, Hans
* Talk to Steve R and Yanwu.  Who else?  Talk to Dave and Brett? Rob
* Hans will prototype type some code for sychronization.
* Kent may take a look at the architecture (Rob to help).
* Audit the code; find all system time calls.  Consider redesigning the time
  object. (TimeP.h)  Rob, Rich (Hans?)

Be able to display ship's schedule and Resource allocations (hours)

After the next meeting:

* Develop candidate tasks based on the discussion: Rob, Rich
* Create a first-pass schedule; discuss: Rob

Notes from the 7th:

  Kent: Evaluate follow-on work ("If time permits" below) before proposal
        time.  Milestones to reflect proprosal process.

* Design Approach:
  Include incremental testing.

* If time permits:

     Hans:
     - Drifter tracking.
     - Cleaner way to set the start conditions in simulator.cfg.  
     - Simulator should read devices.cfg instead of reading a hardcoded list
       in Supervisor.cc.

     Rob:
     - DEM to Octree conversion code.  Develop a library of octree maps for
       our usual sites.
     - Use the fast simulator for regression testing.  Develop small suite
       (3-5) mission files that exercise as many aspects as possible of the
       flight code.  Include "lessons learned" situations.  Create a single
       script that automatically runs the simulations and evaulates the
       results, and returns with a pass/fail for each mission.

     Proposal Follow-On:
     - Water column modeling

     Both Rob and Hans will probably add to the "if time permits" list.


* Other Considerations:

  - Source code control:

    Branch in GIT if available, otherwise branch in CVS.

  - Small review with interested folks:

  Reviews:

  Have a PDR with interested parties: 
    Yanwu
    Steve Rock
    Hans