New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Expand/enhance unstructured mesh capability #50

Open

1 of 4 tasks

erelson opened this issue Mar 14, 2013 · 0 comments

Labels

Contributor

erelson commented Mar 14, 2013

Derived from #3. Since the workflow is functional, the following can be classified as a set of related enhancements to the workflow.

mmGridGen/mmgrid.py #38

Ray tracing of tet mesh for material fractions
Combine mmgrid.py and tag_vox_center_mat.py into a single script for both structured and unstructured meshes

Additions to source.F90 to read MOAB mesh directly:

Enable parsing of r2s.cfg by source.F90
- Arbitrary input mesh names Pass arbitrary mesh file (.h5m, .vtk) to MCNP's source.F90 #41 (currently we default to source.h5m)
- Replace passing parameters via gammas with using tags instead Photon Source Sampling: Parameters when not using 'gammas' approach #45

Compiling DAGMCNP with iMesh API calls in Fortran #44, svalinn/DAGMC#48

Understand/implement changes to Makefile
- gfortran call definitely requires adding -fcray-pointer -I/filespace/groups/cnerg/opt/MOAB/opt-cubit-c12/include -liMesh -L/filespace/groups/cnerg/opt/MOAB/opt-nocgm/lib
- may also require -lstdc++ -lMOAB -lhdf5 -lnetcdf

The text was updated successfully, but these errors were encountered:

erelson mentioned this issue

Add unstructured mesh capability for R2S workflow #3

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment