Use Case
It would be nice if a user who is visualizing a ReaDDy trajectory from one of the example models can access a persistent unique ID for a particle. Currently particle IDs change when they join and leave topologies.
Solution
Use the vertex.data field implemented by ReaDDy to save a unique ID for each particle when it is generated. This ID is never changed or reused for the course of the simulation and is read during analysis and used in .simulariu visualization files.
Acceptance Criteria
A particle that joins and leaves topologies in one of the ReaDDy example models can be followed continuously in the Simularium Viewer.
Use Case
It would be nice if a user who is visualizing a ReaDDy trajectory from one of the example models can access a persistent unique ID for a particle. Currently particle IDs change when they join and leave topologies.
Solution
Use the vertex.data field implemented by ReaDDy to save a unique ID for each particle when it is generated. This ID is never changed or reused for the course of the simulation and is read during analysis and used in .simulariu visualization files.
Acceptance Criteria
A particle that joins and leaves topologies in one of the ReaDDy example models can be followed continuously in the Simularium Viewer.