Serializable executable

[mathisrichter]

User story

As a user, I would like to be able to compile a network and reuse this compiled network in cases where the network doesn't change in between compilations or in cases that the network needs to be distributed and packaged with backend hardware. This would accelerate time to execution and enable use of compiled networks in embedded environments.

Conditions of satisfaction

• Compiling a network produces a compiled serializable executable
• When a network is already compiled, it will not be recompiled
• The compiled serializable executable can be executed on targeted hardware (GPU, NPU)
  The compiled executable can only be used with the same Run_Cfg as it was compiled for. Changing the backend/HW requires recompilation.
• Agreed on API to use serialization/storage and loading/deserialization for Lava networks
• In case of CProcs or µcoded neurons - feasible way to provide needed files/file paths (store files with executable?)

Acceptance tests

• A network is compiled twice in succession and is not recompiled on the second compilation
• A complied serializable executable is executed on two backends (GPU, NPU)
• Complied serializable executable with Py-, C and Nx procs is stored, loaded and executed
• Trying to execute a complied serializable executable with a different Run_Cfg gives meaningful error
• Network from optimization team and Oasis demo network is serializable