Travis L.
Travis L.
Delta tracking will be useful for TRISO modeling. We've found that for an HTGR core, with random-TRISO, a roughly 6x runtime for OpenMC vs. Serpent.
This would be a nice feature! I've been guilty of trying to set `Material.color` more than once.
Partly addressed by PR #2826 (Material and Cell only, not Universe)
Here is where it is aliased: https://github.com/openmc-dev/openmc/blob/develop/src/reaction.cpp#L357-L376 Here is where the trigger scores are parsed: https://github.com/openmc-dev/openmc/blob/develop/src/tallies/tally.cpp#L707-L728 Tally trigger scores don't seem to be making the call to `reaction_type()` and thus...
Hey @kermitnuc You can use triple backticks (```) to make code appear correctly, like this: \```cmake configure_file("${l3d2vtk_output}" "${l3d2vtk_output}.unix" NEWLINE_STYLE LF) \``` So that it reads like: ```cmake configure_file("${l3d2vtk_output}" "${l3d2vtk_output}.unix" NEWLINE_STYLE...
``` MCNPTools Meshtal Bug MWE C C Cell cards c N M D Out In +11 -12 Imp 1 1 -10.713 -1 +11 -12 imp:n=1 $ Fuel 2 0 +1...
Oh duh. The auto-changelog can't update `main` because it's protected. I should have caught that.
If we go down the road of type enforcement, I'm in favor of just including [checkvalue.py](https://github.com/openmc-dev/openmc/blob/develop/openmc/checkvalue.py) from OpenMC, as is permitted by the license. I've been toying with the idea...
Started a discussion: https://openmc.discourse.group/t/spin-off-checkvalue/5242
A "fast-read, read-only" mode would be extremely useful.