You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PyNE tests fail if run with the newest version of OpenMC because of the current statepoint file is not compatible.
At a minimum this should include an update to the statepoint file. Ideally, something can be automated to prevent this happening in the future. For example, is it possible to build our tests of a statepoint file that ships with OpenMC? Or could we run OpenMC to generate a statepoint file as part of the tests?
The text was updated successfully, but these errors were encountered:
Unfortunately I don't see any statepoint files that ships with OpenMC. I did a quick search in the repository but it looks like any statepoint files openmc needs during it's tests are made during the running of the tests.
Perhaps best to run a small openmc simulation and make a statepoint file
Just to check I'm on the right page,
is this is the statepoint file that is not working?
Perhaps @zxkjack123 has the openMC input file that was used to generate the existing statepoint file so that we can update it and/or generate it in testing?
Otherwise someone can develop a new input file and change the tests to match the results generated from testing the newly generated statepoint file.
PyNE tests fail if run with the newest version of OpenMC because of the current statepoint file is not compatible.
At a minimum this should include an update to the statepoint file. Ideally, something can be automated to prevent this happening in the future. For example, is it possible to build our tests of a statepoint file that ships with OpenMC? Or could we run OpenMC to generate a statepoint file as part of the tests?
The text was updated successfully, but these errors were encountered: