Wisc-HCI/CoFrame

FakeEvdData Further Specification Needed

Closed this issue · 3 comments

Frontend is currently faking some of EvD's data that will eventually be provided by the backend.

More of the node data (and structure) should be expressed in this file to act as a reference for component development.

Also add application level data, robot control server data, issues, and pending jobs.

  • waypoints
  • locations
  • regions
    • cube-region
    • sphere-region
  • machines
    • machine recipe
  • thing-types
  • things
  • trajectory
    • trace
      • trace-data-point
        • grade
  • program
    • skills
    • primitives

restructuring fake data to be a submodule.

  • arbitrary (our old data)
  • logical (new program with more coherent data)
  • template (template definitions for each node)
  • comm (submodule defining interacting with ROS nodes)
    • robot control server
    • data server
    • issue server