Inconsitencies with Trackformat
robofish-io implements the track format. I have noticed some inconsitencies between the trackformat and its implementation here. There are 4 Options for each of these items:
A. change the robofish-io implementation.
B. plan a. by adding a TODO to robofish-io in some way.
C. change the track format.
D. is not actually an inconsitency.
List of inconsitencies:
- 3D World support missing from robofish-io
- According to the track format specification: When creating an entity, if no orientations are given, they should default to the orientation vector (0,1). This is not implemented in robofish-io
- The canonical categories for entities in robofish-io are ['fish', 'robot', 'obstacle'] but in the trackformat they are ['organism', 'robot', 'obstacle']
- For outlines of fish, we should define whether the shape has to be (n_timesteps, n_outline_points, 2) or (n_timesteps, 2, n_outline_points). This is actually more of missing definition in the trackformat