-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
[Meta] Work order for remaining PRs/Issues for OpenMC support #163
Comments
Hi, @yardasol I just wanted to ask that can we use OpenMC as depletion code now or still have to wait for release of 0.5.0.? Secondly will it be possible for you to add an example in examples folder for using OpenMC ad depletion code. Thanks |
@khurrumsaleem OpenMC support will be available once 0.5.0 is released. An example case will be included in the release |
Thanks @yardasol |
@khurrumsaleem There will most likely be a prerelease once item 5 is finished. This is to have a reference-able version for my Master's thesis. The rest of the features will be competed after the thesis is submitted. |
@khurrumsaleem There is a pre-release of v0.5.0 that should be have fully functional OpenMC support. Please check it out and let me know what you think! |
All of these are done! |
depcode.py
and related files #162DepcodeSerpent.get_nuc_name()
fails with MCNP-style metastable nuc-codes. #171mpiexec
flags when executing depletion codes via SaltProc #173DepcodeOpenMC
methods for starting simulation and writing/reading input files #133Simulation
class and related code, [Bug]: Use of "isotope" instead of "nuclide" in code, comments, and docs #120, [Bug]: PEP 257 enforcment #93, Feature: ReorderDepcode
functions and make appropriate functions private #180The text was updated successfully, but these errors were encountered: