Procedural Scheduling Follow Up: Extract Shared Processor Code into Shared Library

NASA-AMMOS / aerie

A software framework for modeling spacecraft.

https://nasa-ammos.github.io/aerie-docs/

MIT License

73 stars 19 forks source link

Procedural Scheduling Follow Up: Extract Shared Processor Code into Shared Library #1552

Open Mythicaeda opened 2 months ago

Mythicaeda commented 2 months ago

Related comment on PR

In the Procedural Scheduling PR, a lot of processing code was copied from the mission model processor. This shared code should be pulled out into a standalone library that both processors reference to avoid us having to maintain this code in two places.