Meeting Notes 2017 02 22 - LLNL-Collaboration/uiuc2016 GitHub Wiki

Attendees

  • Joe
  • Ming
  • Kenny
  • Huck
  • Xingrui
  • Tong

Progress Review

  • Huck: Continue implementing a websocket in the mesh viewer that receives Blueprint mesh data, working through issues with backend communication (issue #11).
    • Fixed the remaining issues with the websocket implementation on the PHP stand-in server.
    • Finished and tested the initial implementation of the websocket reading and rendering implementation in the mesh viewer.
  • Xingrui/Tong: Continue implementing a websocket server that sends Blueprint mesh data repeatedly, using the LLNL instructions as a guide (issue #12).
    • Fixed up the issues with the Blueprint mesh reading functionality.
  • All: Integrate the websocket server with the mesh viewer and display a mesh sent from the server to the mesh viewer in real time.
    • Unable to link the back-end Conduit server to the mesh viewer client due to missing functionality in the server implementation.

Upcoming Tasks

  • All: Integrate the websocket server with the mesh viewer and display a mesh sent from the server to the mesh viewer in real time.
    • Mock up a detailed view of the components/data flow for the mesh viewer websocket test using Powerpoint or a similar application (something similar to the diagram in issue 4).
    • Finalize the implementation of the C++ websocket server that sends Blueprint mesh data continuously over a websocket (issue #12).
    • Add an option to the C++ websocket server executable that allows the path to the Blueprint JSON file to be specified.
    • Verify that the entire workflow properly functions by hooking up the mesh viewer to receive mesh data from the C++ websocket server.