[BUG] - Incorrect post-processing for Tiara-FC #465
Description
Describe the bug
The current implemented post-processing config files for the Tiara-FC benchmark don't produce a good comparison between results. The csv files produced, each corresponding to a single sub-run which defines the shielding material, the energy of the source, the shielding thickness, the offset and the fission cell used for the detector; have a single row of data.
As a result, the output plots do not provide a good comparison between results. For example, this is the produced atlas for the for the concrete shielding, 68 MeV source, and Th-232 detector sub-runs:
While results for various shielding thicknesses are available in different csvs, this is not reflected in the resulting atlas.
To Reproduce
Steps to reproduce the behavior:
- Produce raw results for Tiara-FC using JADE.
- Post-process those raw results also employing JADE.
Expected behavior
I would expect a similar output than for JADE v3, where the csv files produced contained all the shielding thicknesses for a specific shielding material, fission cell, offset and source energy. As a result, the output plots also reflected it:
Screenshots
Provided in previous sections.
Proposed solution
Even if not ideal, the proposed solution would be to create the csv files individually for each sub-run using the apply_to option in the raw config file for Tiara-FC. It would be very convenient to add a "Shielding thickness" column to each csv.
This would still produce csv files with a single row, but assigning them custom names and having added the "Shielding thickness" column would allow for all the different shielding thicknesses for a single shielding material, fission cell, offset and source energy configuration to be plotted together with JADE (having applied the necessary modifications to the atlas config file as well).