Meeting Notes 2017 03 08 - LLNL-Collaboration/uiuc2016 GitHub Wiki

Attendees

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

Progress Review

• Change the data communication between the server and client so that only mesh updates are sent after the initial mesh state is sent.
  • Update the C++ websocket server so that it sends the whole mesh on its first send and then only the updated position list on each successive send (e.g. update the positions so that some subset of the points move each frame).
    • Updated the C++ server to send a different mesh after the initial send.
    • Planning to revise the code so that the mesh is updated by updating the data in-place and so that only the coordinates of the updated mesh are sent on successive updates (sent through Blueprint nodes).
  • Update the mesh viewer client so that it renders the entire mesh when it receives in on the first update from the server and then only renders vertex position changes for each successive update.
    • Unable to address this task for this week.
• Add support for sending and rendering field data.
  • Write a quick script that takes the "blueprint_mesh.json" file and adds a new per-element field that uses the value of the element's index in the elements array as its field value.
    • Unable to address this task for this week.
  • Update the C++ websocket server so that it sends updated field data on each update frame (e.g. by incrementing each field's value by 1).
    • Unable to address this task for this week.
  • Implement rendering of field data in the mesh viewer through a simple color map.
    • Unable to address this task for this week.

Upcoming Tasks

• Change the data communication between the server and client so that only mesh updates are sent after the initial mesh state is sent.
  • Update the C++ websocket server so that it sends the whole mesh on its first send and then only the updated position list on each successive send (e.g. update the positions so that some subset of the points move each frame).
  • Update the mesh viewer client so that it renders the entire mesh when it receives in on the first update from the server and then only renders vertex position changes for each successive update.
  • Revise the mesh viewer client code so that it recalculates the bounding box of the rendering view when new mesh positions are received from the server.
• Add support for sending and rendering field data.
  • Write a quick script that takes the "blueprint_mesh.json" file and adds a new per-element field that uses the value of the element's index in the elements array as its field value.
  • Update the C++ websocket server so that it sends updated field data on each update frame (e.g. by incrementing each field's value by 1).
  • Implement rendering of field data in the mesh viewer through a simple color map.