-
Tim has found an issue with the meshtally refactor branch, it appears that when there are multiple meshes in the same input that have different multiplier cards then the result of the 2nd tally is inc…
-
Pull the non-geometry functions out of fluka_funcs and create a strictly MOAB class to provide support to extract the necessary information from the .h5m file to create input records.
This separate…
-
``` python
from pyne.mesh import Mesh
from pyne.material import Material
mat1 = Material({1001: 1.0})
mat2 = Material({2004: 1.0})
a = [[0, 1], [0, 1], [0, 1, 2]]
m = Mesh(structured=True, structure…
-
Currently test_cyl requires the user to add an argument 'cyl.h5m'. As this is a test program this is should not be the case. Update test_cyl.cpp so that the file it loads is automatically cyl.h5m.
-
Process the h5m created previsouly in the same manner to produce fluka compatable score information.
Using the exampe as before, processing the data should produce
*...+....1....+....2....+....3....+…
-
In the old version of MeshTally there are four functions that are used for implementing mpi/runtpe functionality in DAG-MCNP:
- get_tally_data
- get_error_data
- get_scratch_data
- zero_tally_data
Si…
-
Demonstrate and test that our method of giving groups the name of Fluka materials and compound is processed correctly.
- [x] Create model in Cubit with a range of group names including; valid fluka ma…
-
The code that attempts to identify the particle type/s in the MCNP wwinp file is incorrect. The wwinp file may contain weight windows for neutrons, photons, or both. In the wwinp file, the second …
bohmt updated
11 years ago
-
Develop routines to appropriately parse and thereby create appropriate handles to the FLUKA scoring routines, i.e. by parsing metadata found within the h5m created via Cubit group names
-
Any parts of dagmc_preproc that divide up the name of the group should be removed. Such that the only tags in the h5m file are identical to those in the cubit groups.