[feature] Store OUTPUTS under a SCENARIO subfolder

Summary

Create a folder in OUPUTS that has the name of the scenario and in that folder find several folders with information on light, PV prod, crop prod, etc.

Current behavior

Outputs are manually saved and not standardized for each simulation.

Desired behavior

• Clearly define standard outputs of PASE simulations and automatically save them in a structured way.
• Store intermediate results in order to reuse as much as possible instead of re-running heavy computations (e.g. reuse de 3D scene, the raycasting output, etc. when applicable), aka lazy loading
• save inputs as well to ensure full consistency between simulation inputs and outputs.
• version tracking : store the git commit SHA and/or framework version in metadata

2 possible ways to do this :

Store in the file system in ad-hoc directories

Proposed structure :

pase/
└── OUTPUTS/
    ├── project A/
    │   ├── variant 1/
    │   │   ├── 1-inputs
    │   │   ├── 2-data
    │   │   ├── 3-interm. results
    │   │   └── 4-results
    │   └── variant 2/
    │       ├── 1-inputs
    │       ├── 2-data
    │       ├── 3-interm. results
    │       └── 4-results
    └── project B/
        ├── variant 1/
        │   ├── 1-inputs
        │   ├── 2-data
        │   ├── 3-interm. results
        │   └── 4-results
        └── variant 2/
            ├── 1-inputs
            ├── 2-data
            ├── 3-interm. results
            └── 4-results  

Link to edit the above : tree.nathanfriend.com

Database

If the diversity of different projects justifies it, build a reasonable-size SQLite database to store the data (inputs, data, outputs, etc.).

Sources

n/a

Linked features or branches

Issue #75 (closed)

#82

#124

Child item: #164