MontePy




MontePy is the most user-friendly Python library for reading, editing, and writing MCNP input files.
Installing
Simply run:
pip install montepy
For more complicated setups
see the Installing section in the user guide.
User Documentation
MontePy has a website documenting how to work with MCNP in python with MontePy.
The website contains a user's guide for getting started,
a developer's guide covering the design and approach of MontePy,
instructions for contributing,
and the Python API documentation.
Features
Here is a quick example showing multiple tasks in MontePy:
import montepy
problem = montepy.read_input("tests/inputs/test.imcnp")
importances = {1: 0.005,
2: 0.1,
3: 1.0,
99: 1.235
}
for cell_num, importance in importances.items():
problem.cells[cell_num].importance.photon = importance
universe = montepy.Universe(123)
problem.universes.append(universe)
universe.claim(problem.cells[1:5])
problem.cells[99].fill.universe = universe
for surface in problem.surfaces:
surface.number += 1000
problem.write_problem("foo_update.imcnp")
For more examples see the getting started guide.
Use Cases
Here are some possible use cases for MontePy:
- Automated updating of an MCNP input file, or MCNP deck, for reactor reconfiguration, fuel shuffling, etc.
- Parameterizing an MCNP input file to check for explore the parametric space of your MCNP modeling problem
- Updating an MCNP model with the results from another code, such as depletion results from ORIGEN.
- To convert an MCNP model to another Monte Carlo code like OpenMC, SERPENT, etc.
Limitations
Here a few of the known bugs and limitations:
- Cannot handle vertical input mode.
- Does not support editing tallies in a user-friendly way.
- Does not support editing source definition in a user-friendly way.
- Cannot parse all valid material definitions. There is a known bug (#182) that MontePy can only parse materials where all
keyword-value pairs show up after the nuclide definitions. For example:
M1 1001.80c 1.0 plib=80p
can be parsed.
M1 plib=80p 1001.80c 1.0
cannot be parsed; despite it being a valid input.
Current Development Priorities
Here are the rough development priorities for adding new features to MontePy:
- Improve performance for the intial loading of models.
- Implement support for tallies.
- Implement support for source definitions.
If you have a specific feature priority that you would be willing to collaborate on you can open an issue or email us at mgale@montepy.org.
Alternatives
There are some python packages that offer some of the same features as MontePy,
but don't offer the same level of robustness, ease of installation, and user friendliness.
Many of the competitors do not offer the robustness that MontePy does because,
they do not utilize context-free parsing (as of 2024).
These packages are:
The only other libraries that do utilize context-free parsing that we are aware of are:
MontePy differs from MCNPy by being:
- On PyPI and conda-forge, and able to be installed via
pip
or conda
- Only requiring a Python interpreter and not a Java virtual machine
- Allowing contributions from anyone with a public GitHub account
MontePy differs from mckit by being:
- Thoroughly documented
- Object-oriented
For only writing, or templating an input file there are also some great tools out there.
These packages don't provide the same functionality as MontePy inherently,
but could be the right tool for the job depending on the user's needs.
Another honorable mention that doesn't replicate the features of MontePy,
but could be a great supplement to MontePy for defining materials, performing activations, etc.
is PyNE --- the Nuclear Engineering Toolkit.
Bugs, Requests and Development
So MontePy doesn't do what you want?
Add an issue here with the "feature request" tag.
The system is very modular and you should be able to develop it pretty quickly.
Read the developer's guide for more details.
If you have any questions feel free to ask @micahgale.
Citation
You can cite MontePy as:
Gale et al., (2025). MontePy: a Python library for reading, editing, and writing MCNP input files. Journal of Open Source Software, 10(108), 7951, https://doi.org/10.21105/joss.07951
Finally: make objects, not regexes!