Key question: ¿Why is a some-days gap between a trajectory and the next one?I want 1 day gap trajectories!!!!!
To make it manageable, the user should have the possibility to apply conditions to the generated conics.
I.e. max dvt, max tof, max c3a, etc.
So when the user asks for 10k trajectories, will obtain 10k useful trajectories, and those which doesn't comply with the applied requirements, will be discarded.
The user can now load a huge mat file (over 15M nodes) and filter by dvt when converting it to table, reducing the dataset size to approx 4M nodes (aka table rows)
¿Why is a some-days gap between a trajectory and the next one?
I want 1 day gap trajectories!!!!!max dvt, max tof, max c3a
, etc.