Is your feature request related to a problem? Please describe.
At the moment, no metadata is available for JADE simulation outputs. JADE outputs should have some kind of metadata associated to them at least covering:
JADE version that produced them
the transport code version that produced them
the benchmark input version (since they will come from external repositories in the future)
When it was performed.
The libraries employed
This metadata should come partially from the metadata associated to the input retrieved from a git database (e.g., CONDERC, SINBAD, IAEA) possibly in a form also of json (e.g., the transport code version, the benchmark input version, further info or links, modifications ...).,
Describe the solution you'd like
The simplest implementation would be to add a .json file to the output folder containing all the necessary data. This could be read at post-processing time when a comparison is asked, in order to warn users about eventual differences. The topic is open for discussion though.
Is your feature request related to a problem? Please describe. At the moment, no metadata is available for JADE simulation outputs. JADE outputs should have some kind of metadata associated to them at least covering:
This metadata should come partially from the metadata associated to the input retrieved from a git database (e.g., CONDERC, SINBAD, IAEA) possibly in a form also of json (e.g., the transport code version, the benchmark input version, further info or links, modifications ...).,
Describe the solution you'd like The simplest implementation would be to add a .json file to the output folder containing all the necessary data. This could be read at post-processing time when a comparison is asked, in order to warn users about eventual differences. The topic is open for discussion though.