Aerie/FPrime Compiler Integration

[dandelany]

Follow-up to Part 1: https://github.com/NASA-AMMOS/aerie/issues/1529

In addition to generating FPrime text sequences, we also want to be able to compile them into FPrime binary sequences within Aerie, using the extension(?) architecture we're developing.

• FPrime Container: Create a Flask-based container to wrap FPrime's software package, which can receive FPrime (string) sequences and command dictionaries and generate FPrime binary files.
• Aerie Extension Integration for Compilation: Utilize Aerie extensions to connect to the FPrime Flask server and compile the FPrime Sequence
• Display Compiled Data: Display results of sequence compilation in the Aerie UI
  • Ability to view compilation status & download compiled files
  • View any complilation errors
  • Any way to preview compiled sequence before downloading? similar to how we do with string sequences? Roundtrip test?
  • Do we store compiled data (in DB or file) or is compilation a transient process?

[ewferg]

We have discussed compiled product storage a bit in some seq2 discussions and our decision is to support compiled product storage. Exactly how they should viewed/available for download in the UI is still up for debate, but essentially we want mission users who do not have a separate mission data store to be able to use Aerie is a simple stand in.