R2S Config/Step1 #25
R2S Config/Step1 #25
Conversation
| # unstructured mesh tally .h5m file. | ||
| meshtal: Mesh_with_Tally.h5m | ||
| # Tally number within the meshtal file containing the fluxes for activation. | ||
| tally_num: 2 |
There was a problem hiding this comment.
Is this relevant for an unstructured mesh? It doesn't seem like your script to convert from OpenMC to H5M preserves any tally number (which is fine if we don't actually need it).
There was a problem hiding this comment.
No, it's not relevant here--only data from one tally is written to h5m, so the same ALARA input file is printed regardless of which number is chosen here
| # mesh this tag must already exist within the file specified in <meshtal>. | ||
| flux_tag: FLUX_MESH | ||
| # Path to the DAGMC material-laden geometry file (.h5m). | ||
| geom: DAGMC_Geometry.h5m |
There was a problem hiding this comment.
Does this geometry have materials in it? Where is the script that does that?
There was a problem hiding this comment.
Yes, this is material laden. PyNE_Lib.py creates a PyNE material library which is then assigned to the DAG-MC geometry using the uwuw_preproc tool (done inside a terminal).
Co-authored-by: Paul Wilson <[email protected]>
Co-authored-by: Paul Wilson <[email protected]>
Co-authored-by: Paul Wilson <[email protected]>
|
I'd say that this is working in the sense that it is creating a photon source distribution (as in #26), but the source printed at each decay time (source_1.h5m & source_2.h5m) is the same, so this might be something to look into |
fixes #23