adrienmaillard
adrienmaillard
Should we keep all design stuff in the [discussion](https://github.com/NASA-AMMOS/aerie/discussions/1451?sort=new) instead of this ticket ? I have added impl notes/questions there instead of here.
This is indeed a bug and has already been fixed by @jmdelfa in his upcoming PR about anchors for scheduling, we've verified that with some tests. Mentioning #663 for reference....
Assigned @jmdelfa as he fixes this in his PR.
This is blocked because part of an ongoing prototyping for dependency modeling in #1364.
@dandelany I think we can close this PR.
Some prototyping happening on branch https://github.com/NASA-AMMOS/aerie/tree/1364-dependency-framework
For the FooActivity activity type ```java @EffectModel public void run(final Mission mission) { final var data = mission.data; final var complexData = mission.complexData; complexData.beginImaging(ImagerMode.HI_RES, 60); if (y.equals("test")) { data.rate.add(x); }...
Note: the temporal arguments are mainly to get the ability to build activities from a behavior definition only (without user-defined `run()` method).
@jmdelfa and I discussed and did not find that this was in the scope for the MVP of #1073. This is attached to provide a declarative behavior of the activities,...
Matt, I have not rewritten your part of the history. I think there is some stuff to squash, let me know what you want to do.