Open blairlyons opened 2 years ago
Some models do not have a consistent timestep, the engine and client should handle this when caching and sending data.
For a model with an inconsistent timestep, a client can still receive data for the correct frame in the trajectory.
Example model with inconsistent timestep https://simularium.allencell.org/viewer?trajUrl=https://aics-simularium-data.s3.us-east-2.amazonaws.com/trajectory/medyan_actin_only.simularium
A sample of the times in this trajectory:
0.00000e+00 1.00000e+00 2.00000e+00 3.05000e+00 4.10000e+00 5.15000e+00 6.20000e+00 7.25000e+00 8.25000e+00 9.25000e+00 1.02500e+01 1.12500e+01 1.22500e+01 1.32500e+01 1.42500e+01 1.52500e+01 1.62500e+01 1.72500e+01 1.82500e+01 1.92500e+01 2.02500e+01 2.12500e+01 2.22500e+01 2.32500e+01 2.42500e+01 2.52500e+01 2.62500e+01 2.72500e+01 2.82500e+01 2.92500e+01 3.02500e+01 3.12500e+01 3.23000e+01 3.33500e+01 3.44000e+01 3.54500e+01
Use Case
Some models do not have a consistent timestep, the engine and client should handle this when caching and sending data.
Acceptance Criteria
For a model with an inconsistent timestep, a client can still receive data for the correct frame in the trajectory.
Details
Example model with inconsistent timestep https://simularium.allencell.org/viewer?trajUrl=https://aics-simularium-data.s3.us-east-2.amazonaws.com/trajectory/medyan_actin_only.simularium
A sample of the times in this trajectory: