Closed Mythicaeda closed 3 weeks ago
@duranb demo'ed progress on this in today's Sprint Demos meeting and we had some discussion/ideas come out of that:
sim_id
field from the JSON format since it's not really being usedmodel_id
from format and force the user to associate a model at import time - rather than matching to the same model ID and potentially using the wront model@dandelany , I'm not sure I'm adding this comment in the right place. I heard talk of switching from using durations instead of end times. I vote to support both. One activity could have a start time and duration. Another could have a start time and end time. Another could have all three, but they need to agree.
In addition, I would like to have the option to specify times as timestamps or offsets from the plan start and be able to mix them. I'd also like timestamps supported for DOY and MM-DD, again allowing a mix. I'd also like fractions of seconds to be optional (with any number of digits up to some limit, which I expect is 6 for aerie) along with time zone specifiers like "Z," "PST," "+7:00," and "-07:00." I guess I could live with restrictions on time zones, but I expect it wouldn't be much harder to support.
A few notes based on discussing ^these points with Brad yesterday:
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
https://github.com/NASA-AMMOS/aerie/issues/1318
Describe the feature request
Allow users to download and upload plans in a similar manner to what is provided in the aerie-cli. Specifically:
See slack thread for more context and details: https://jpl.slack.com/archives/CJ07FGRPH/p1718137212295689