Skip to content
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

OpenMC testing statepoint file has wrong version #1458

Open
gonuke opened this issue Aug 17, 2022 · 3 comments
Open

OpenMC testing statepoint file has wrong version #1458

gonuke opened this issue Aug 17, 2022 · 3 comments
Assignees

Comments

@gonuke
Copy link
Contributor

gonuke commented Aug 17, 2022

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?

@shimwell
Copy link
Contributor

shimwell commented Aug 17, 2022

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?

is this is the test command that is failing?

Does anyone know where the openmc script is that generated the statepoint used in the tests?

@gonuke
Copy link
Contributor Author

gonuke commented Aug 17, 2022

Those are the correct file and failure, respectively, although there are a few instances of that failure.

@gonuke
Copy link
Contributor Author

gonuke commented Aug 18, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants