MeshTal Viewer is a Java based software which can read mesh tallies output formats of several neutron transport codes and display them graphically.
The bottom right blue bar shows the memory currently used by MeshTal Viewer and the maximum memory that can be used by the Java Virtual Machine (JVM), "628M of 2731M" means that MeshTal Viewer is currently using 628MiB and that the JVM won't used more than 2731MiB. A click on this bar triggers a garbage collection in order to have a more meaningfull view of the amount of memory really needed by the program.
"A" and "B" are two slots to load one or two mesh tallies files, if you want to display a single file you can use either of these.
Click the "..." button to browse and select your file.
Zipped files (ZIP with a single file or GZip) can be opened without uncompressing them first.
Note that you can load the same file in both slots in order to display combinations
Once a file has been loaded the "Display" area will list the available tallies and allow selecting the one that will be displayed.
The buttons "XForm A coord."/"XForm B coord." allows applying affine transforms to tallies coordinates (X/Y/Z, energies) and/or values. This feature could be used for example when comparing the mesh results between two models which were calculated with different origins.
Affine transforms of tallies coordinates and/or values
the right side table will show the transformation that will be applied.
Allows loading scatter values that will be displayed over the tallies data as colored dots.
Depending on the current view only some of these controls are available
4 views are available:
This is the main display area.
The current view can be saved as a PNG file by righ clicking in the view and selecting "Save as..."
To navigate in the 3D views:
"3D render" choices in the "2D Surf." view:
From left to right:
Only Cartesian mesh geometry is supported: keyword GEOM=xyz or GEOM=rec.
All output formats (keyword OUT) are supported: colum formats col and cf, series of 2D matrices formats ij, ik or jk.
Example MCNP FMESH input cards
c Flux Tally FMESH4:N GEOM=xyz ORIGIN=-90 -90 0 IMESH=90 IINTS=180 JMESH=90 JINTS=180 KMESH=200 KINTS=10 OUT=ij EMESH=0.625e-6 0.100 20 c Capture Tally FMESH14:N GEOM=xyz ORIGIN=-90 -90 0 IMESH=90 IINTS=180 JMESH=90 JINTS=180 KMESH=200 KINTS=10 OUT=ij EMESH=0.625e-6 0.100 20 FM14:N -1 0 -2 c Fission Tally FMESH24:N GEOM=xyz ORIGIN=-90 -90 0 IMESH=90 IINTS=180 JMESH=90 JINTS=180 KMESH=200 KINTS=10 OUT=ij EMESH=0.625e-6 0.100 20 FM24:N -1 0 -6 c Scattering Tally FMESH34:N GEOM=xyz ORIGIN=-90 -90 0 IMESH=90 IINTS=180 JMESH=90 JINTS=180 KMESH=200 KINTS=10 OUT=ij EMESH=0.625e-6 0.100 20 FM34:N -1 0 2
Note that while different tally numbers can be used in MCNP, F4,F14,F24,F34 will automatically be labelled as "Flux", "Capture", "Fission" and "Elastic Scattering" in MeshTal Viewer (this is the convention which is used in IDAT).
Example SERPENT mesh input cards
ene 1 1 1E-11 0.625E-6 1.00E-1 20 det 14 de 1 dx -80 80 160 dy -80 80 160 dz 0 250 10 det 24 de 1 dr -2 void dx -80 80 160 dy -80 80 160 dz 0 250 10 det 34 de 1 dr -6 void dx -80 80 160 dy -80 80 160 dz 0 250 10 det 44 de 1 dr -3 void dx -80 80 160 dy -80 80 160 dz 0 250 10
MeshTal Viewer requires the both the binary rmflux file and the input file (because mesh coordinates are not carried by the rmflux file).
The binary rmflux file and input are expected to be placed in the same folder and to follow this naming convention:
For example: rmflux.2d-zppr9 and 2d-zppr9.inp
You should open the rmflux binary file, MeshTal Viewer will then try to find the corresponding input file, if the input file is not found you will be prompted to select it
Last modified: 31 August 2019