@@ -55,3 +55,57 @@ presented results and support with modeling challenges.
## Inventory Interface File
This work has developed a new inventory interface (`ii`) file format for exchanging nuclide inventory data with the MELCOR team. It is a heirarchical description of the inventory in one or more zones, at one or more time points. Currently the `ii` (pronounced aye-aye) data is emitted in standard [JSON](https://www.json.org/json-en.html) format so that one can read the files outside of SCALE. We currently use `ii.json` as the extension for these files. In the future we may provide an [HDF5](https://www.hdfgroup.org/solutions/hdf5/) version as well to save disk space--these would have the extension `.ii.h5`. We made the decision to package relevant nuclear data with the inventory in the `ii` format because typically downstream operations would like to calculate decay heat, mass, activity, and other derived quantities from the number of atoms/moles of each nuclide. Instead of providing number of moles, grams, and activity for each nuclide, we provide the molar mass (grams/mol) and decay constant (1/s) for each nuclide. Including nuclear data also aids us in nuclear data uncertainty studies where we would generate hundreds of `ii.json` files for each realization of the nuclear data. Each one of these realizations is the initial condition for a MELCOR severe accident analysis realization. Although the variation of the inventory in moles has the implicit effect of variations in nuclear data, the direct effect on decay heat and activity requires the perturbed recoverable energy from decay values and the decay constants. Additional details on the format are provided in this copy of the SCALE Quality Assurance (QA) case for this feature: [SCL-2020-003](supplemental/scl-2020-003_inventory-interface.md).
## Example of Processing the Inventory Interface File
An example script `supplemental/example_out.py` shows how to process the `ii.json`
file. It takes the file name and the label for the response. The `case(0)`
found time list [0.0, 259200.0, 13365490.0, 26471780.0, 39578068.0, 52684360.0, 65790648.0, 78896936.0, 92046424.0, 105195920.0, 118345408.0, 131494896.0, 144644384.0, 157793872.0] in SECONDS !
SYSTEM MASS
time(s) mass(g)
0.00000e+00 2.99799e+06
2.59200e+05 2.99799e+06
1.33655e+07 2.99799e+06
2.64718e+07 2.99799e+06
3.95781e+07 2.99799e+06
5.26844e+07 2.99799e+06
6.57906e+07 2.99799e+06
7.88969e+07 2.99799e+06
9.20464e+07 2.99799e+06
1.05196e+08 2.99799e+06
1.18345e+08 2.99799e+06
1.31495e+08 2.99799e+06
1.44644e+08 2.99799e+06
1.57794e+08 2.99799e+06
TARGET NUCLIDE Cs137
time(s) mass(g) activity(Ci)
0.00000e+00 1.00450e-14 1.37523e-12
2.59200e+05 9.02606e-04 1.23573e-01
1.33655e+07 4.63803e-02 6.34979e+00
2.64718e+07 9.14244e-02 1.25166e+01
3.95781e+07 1.36039e-01 1.86247e+01
5.26844e+07 1.80228e-01 2.46746e+01
6.57906e+07 2.23996e-01 3.06667e+01
7.88969e+07 2.67347e-01 3.66017e+01
9.20464e+07 3.10425e-01 4.24993e+01
1.05196e+08 3.53090e-01 4.83405e+01
1.18345e+08 3.95348e-01 5.41259e+01
1.31495e+08 4.37201e-01 5.98559e+01
1.44644e+08 4.78653e-01 6.55310e+01
1.57794e+08 5.19709e-01 7.11519e+01
```
The script can be modified to iterate through nuclides and output any desired