Agenda for the Meeting with Tim on April 15, 11AM - 1PM

1. Tim shows everyone the robot hardware.

2. Teams provide a laptop-based demonstration of the latest updates:

1. Monitor Team demos the latest in integrated UI, talking to packet generation stub.
2. Middleware + Mesh teams demo the latest in heartbeat-based operation.
3. We'll see if we can do some on-the-spot plug in of Tim's hardware.

3. Q/A session:

1. What exactly does Tim want for the final deliverable? How about the full git repo?
2. Based on today's demo, what would Tim like for the next release in 4 weeks?
3. Questions from Eric about Batman and heartbeat
4. Are there any features or pieces of information in the UI right now that should not be included? (Eg: latency, sig strength, etc...)

Minutes:

Points Noted by Tim During His Robot Presentation:

• He is running embedded QT; he'd rather not run X-Windows. Bottom line -- to run on the robots, we need to limit the amount of dependencies that our stuff needs, in particular dependencies on large libraries.
• For example, he asked if we using XML for config files? If so, se should limit the use of exotic XML libs.

Discussion Points during Monitor Demo 2:

• Use MAC address as the unique ID of the node -- NEED TO DO macaddrcmp instead of strcmp
• IP address may or may not be available
• Display shorter version of IP address on the UI
• Make the "standard" inactivity time
• Tim might be OK with throwing out latency. If it stays, we need a place to display latency other than in the parameter table. For example, it can go in the top right or top left corner of the display.
• Tim wants to see the bandwidth measured and display in some way. Put it in display with the latency value.]

Action Items:

So, Tim would definitely like to see a bandwidth test; he uses nuttcp, which takes parms for running a test. He suggests trying a 1 second test using the nuttcp API. He wants to run the bandwidth test along with ping and traceroute; he's not sure if it will produce meaningful results; THIS SHOULD HAPPEN IN FOUR WEEKS, OR SOONER.

He'd also like to see some scenarios of different network configs, posted on the wiki; MIDDLEWARE TEAM WILL WORK ON THIS.

We'll send Tim an email telling him what release we'd like to try -- HAPPENS IN TWO WEEKS

Homework for GUI team -- do some scenarios of use, in particular single-node vs two-configuration. In particular, he'd like to see it work, for starters in scenario form. If things are running, these scenarios can be generated by actually running the software; MONITOR TEAM WILL WORK ON THIS.