Agenda for the Meeting with Tim on May 27 11AM - 1PM

1. Tim discusses deployment issues, runs Meshkit on laptop, other topics ...

2. Nathaniel and Jon overview in-the-field test plan.

3. Teams show latest developments:

a. Monitor: no-physics feature, MAC address as node ID    
b. Middleware: bigger and better test fixture; traceroute working    
c. Mesh: trace route data, Jon's setup scripts      

4. Q/A session:

 a. Any particular requirements for the final deliverable, in addition to
    [[Admin.Milestones.Deployment Phase 3 Functional Requirements]]
 b. Anything in particular for maintenance documentation?    

Minutes:

1. Tim did not understand what the bson versus json issues were. This was cleared up with further explanation.

2. Replace logo on Github wiki home page with an index that is linked to each major component of the project.

3. For each component, provide the following information:

   1. How to build

   2. How to install

   3. How to run

   4. A design discussion

4. Remove all unnecessary files from the repository, most particularly the binaries.

   1. Merge all branches into master.

   2. Remove the build directory entirely, or describe clearly what is in it.

5. Some details for the field tests to be performed in two weeks:

   1. The tests labeled "Initial Convergence" and "Convergence" should be re-named "Routing Performance", to avoid

   2. Julie suggest an additional field test to simulate robot power loss. This test is performed with a stop watch, to simulate the "robot rounds corner" problem.

6. In Monitor UI:

   1. Allow the table size to expand when the outer window is expanded.

   2. Label nodes with last octet of the IP address.

   3. A route must be selectable by clicking on source and destination nodes in the display.

7. In the final field tests, do traceroute, ping, and bandwidth test between nodes.