Mach 30 #EngineeringSpeak Hangout Aug 29, 2013

Discussion Topic: 

Attending: J, Ethan, Chris, Jeremy

Start:  2205 EDT

End: 2315 EDT

Minutes:

• J - Chris, you want to show off Java version of Shepard App?
• J - What about networking issues?

• Jeremy - If you run both the server and client on localhost they use the loopback interface and there’s no config.
• Chris - Both processes seem to exit gracefully so you don’t have processes hanging around and locking access to the port.

• J - Still nervous about adding what is basically an unneeded networking layer to the code.
• Jeremy - Would prefer the Java app over Processing.

• J - Agreed

• J and Jeremy took opposing sides to argue for and against having the network features.

• Jeremy feels that some more technologically advanced teachers might set their laptops up so that multiple students can connect to collect and analyze data.
• J - But that takes away the hands-on experience that students would get. That keeps them from having the physical interaction with the test stand which teaches them things like safety and proper procedures.

• Chris - Would say that it’s not going to be used in a network fashion, so the utility of having the network layer may not be as useful.
• J - Three major concerns for the networking layer.

• Doesn’t fit the audience. Too much complexity.
• Encourages behavior that keeps students from operating the test stands themselves.

• Ethan - Second that.

• From a design simplicity standpoint, the network layer when we’re moving quickly towards a kit, is concerning.

• Chris - Supports taking the networking layer out, but leave in the functionality as a hidden way or an advanced setting.
• J - We need to have a more serious architecture discussion before we start adding a networking layer back in.

• Comm protocol needs to be independent of the device.
• “I’m a sensor that’s capable of collecting this data at this rate and I support the following commands.”
• Need to talk about security, especially over networks we don’t control.

• Chris - Believes the project can be architected so that we’ve got a good path to the future while not overly complicating things now.
• Chris - Any control of the test subject needs to be separated somewhat from the collection portion.

• J - May have to share the same network, but can be separate.
• J - Need hardware interlocks.
• Ethan - For NASA compatibility it’s a good practice to have safety interlocks.

• Chris - So are we ready to vote to move ahead with the Java app without networking?

• Jeremy - Do we have enough of the team here to make this decision?
• J - Greg and Aaron are two important voices that are missing.

• Chris - Jeremy, make sure you test the hardware with the Java software.

• Would wait for QA until the software is a little more fleshed out.

• ACTION - J will check with one of his contacts to see what kind of data reduction features we need.
• ACTION - We will need to check with CCSSC on what they need.
• J, Chris, and Jeremy all gave thumbs up on going with Java while removing networking. The three decided to send Greg and Aaron an email to ask for their feedback before lunch on Wednesday.