crp/OpenMC

mirror of https://github.com/openmc-dev/openmc.git synced 2026-07-25 04:25:29 -04:00

OpenMC Monte Carlo Code https://docs.openmc.org

computational-physics high-performance-computing monte-carlo-simulation neutron-transport neutronics nuclear-data nuclear-energy nuclear-engineering nuclear-fusion openmc particle-transport photon-transport radiation-transport

Find a file

Sterling Harper 0d7df88edd Finish moving score_general_mg to C++		2019-02-10 13:06:33 -05:00
cmake/Modules	Adding check for DAGMC_ROOT in environment as a hint.	2018-10-01 10:38:16 -05:00
docs	Merge branch 'develop' into cpp-material	2019-02-01 17:15:40 -06:00
examples	Remove weight correction method for resonance scattering, rename ARES -> RVS	2019-01-10 15:53:45 -06:00
include/openmc	Merge remote-tracking branch 'upstream/develop' into cpp_tallies	2019-02-09 13:27:12 -05:00
man/man1	Remove option to specify multipole library outside of cross_sections.xml	2018-11-12 13:35:29 -06:00
openmc	Use 0-based indexing for Tally.filters_ values	2019-02-05 18:42:56 -05:00
scripts	updated casl chain and the scripts	2018-12-04 10:44:16 -05:00
src	Finish moving score_general_mg to C++	2019-02-10 13:06:33 -05:00
tests	Merge remote-tracking branch 'upstream/develop' into cpp_tallies	2019-02-09 13:27:12 -05:00
tools/ci	Make sure numpy gets upgraded on Travis	2019-01-18 08:25:58 -06:00
vendor	Finish converting windowed multipole functions to C++	2019-01-02 13:55:08 -06:00
.gitignore	Adding VTK image format to ignore.	2018-10-07 19:36:20 -05:00
.gitmodules	Replace FoX with pugixml	2017-03-03 09:17:49 -06:00
.travis.yml	Try using xvfb as a service (to fix Travis CI failures)	2019-01-17 15:07:04 -06:00
CMakeLists.txt	Merge remote-tracking branch 'upstream/develop' into cpp_tallies	2019-02-05 14:05:15 -05:00
CODE_OF_CONDUCT.md	Clarify enforcement in code of conduct	2018-07-25 06:30:26 -05:00
CONTRIBUTING.md	Document governance model discussed at OpenMC developer's meeting	2018-08-03 13:01:45 -05:00
Dockerfile	Changes suggested by @liangjg	2018-11-13 10:52:53 -06:00
LICENSE	Add 'contributors' to copyright	2018-08-02 13:32:24 -05:00
MANIFEST.in	Use PEP 518 pyproject.toml file to manage build dependencies	2018-08-16 12:00:39 -05:00
pyproject.toml	Use PEP 518 pyproject.toml file to manage build dependencies	2018-08-16 12:00:39 -05:00
pytest.ini	Skip multipole-related tests if OPENMC_MULTIPOLE_LIBRARY is not set	2018-02-06 13:27:01 -05:00
README.md	change mit-crpg -> openmc-dev	2018-08-02 10:49:40 -05:00
schemas.xml	So begins the CMFD Fortran purge :D (~3.6K lines)	2018-11-24 00:13:37 -05:00
setup.py	Removing optional silo dependency.	2018-10-07 19:36:21 -05:00

README.md

OpenMC Monte Carlo Particle Transport Code

The OpenMC project aims to provide a fully-featured Monte Carlo particle transport code based on modern methods. It is a constructive solid geometry, continuous-energy transport code that uses HDF5 format cross sections. The project started under the Computational Reactor Physics Group at MIT.

Complete documentation on the usage of OpenMC is hosted on Read the Docs (both for the latest release and developmental version). If you are interested in the project or would like to help and contribute, please send a message to the OpenMC User's Group mailing list.

Installation

Detailed installation instructions can be found in the User's Guide.

Citing

If you use OpenMC in your research, please consider giving proper attribution by citing the following publication:

Paul K. Romano, Nicholas E. Horelik, Bryan R. Herman, Adam G. Nelson, Benoit Forget, and Kord Smith, "OpenMC: A State-of-the-Art Monte Carlo Code for Research and Development," Ann. Nucl. Energy, 82, 90--97 (2015).

Troubleshooting

If you run into problems compiling, installing, or running OpenMC, first check the Troubleshooting section in the User's Guide. If you are not able to find a solution to your problem there, please send a message to the User's Group mailing list.

Reporting Bugs

OpenMC is hosted on GitHub and all bugs are reported and tracked through the Issues feature on GitHub. However, GitHub Issues should not be used for common troubleshooting purposes. If you are having trouble installing the code or getting your model to run properly, you should first send a message to the User's Group mailing list. If it turns out your issue really is a bug in the code, an issue will then be created on GitHub. If you want to request that a feature be added to the code, you may create an Issue on github.

License

OpenMC is distributed under the MIT/X license.