Unable to read Statepoint File

[AnthonyB08]

Hi all,

I managed to run Cardinal, with open mc and Moose, with post-processing primarily accomplished by Moose. However, for me to fully understand the built-in normalization of Cardinal I am trying to open the StatePoint file with python API
(with openmc.StatePoint("statepoint.25.h5") as sp:) and I am returned with this error:

statepoint file has a version of 17.0 which is not consistent with the version expected by OpenMC, 18

What does the community propose I do to be able to read-in the statepoint file.

-Thanks,
Anthony Bowers

[aprilnovak]

Hmm, that's strange. Can you try running the OpenMC case in "standalone" mode to see if the same issue persists? We're not doing any calling/writing of statepoint files ourselves (e.g. OpenMC is handling all that).

cd <your case directory>
openmc
<try loading the statepoint file>

[lewisgross1296]

I'm not sure this is an environment variable issue but this is how my environment variables are set up for Cardinal and OpenMC

# Cardinal Environment 
# build without NEK
export ENABLE_NEK=false

# [REQUIRED] you must set the location of the root directory of the NekRS install;
# this will be the 'install' directory at the top level of the Cardinal repository.
# Be sure to adjust this to wherever you have cloned the Cardinal repository
export NEKRS_HOME=$HOME/cardinal/install

# [REQUIRED IF USING MOOSE CONDA ENV] you must set the location of the HYPRE
# libraries (so that a libHYPRE.so or something similar is located at
# HYPRE_DIR/lib). This is needed because NekRS uses the same HYPRE built with MOOSE
# export HYPRE_DIR=$CONDA_PREFIX

# [OPTIONAL] it's a good idea to explicitly note that you are using MPI compiler wrappers
export CC=mpicc
export CXX=mpicxx
export FC=mpif90

# [OPTIONAL] if running with OpenMC, you will need cross section data at runtime;
# you will need to set this variable to point to a 'cross_sections.xml' file.
# Be sure to adjust this to wherever you have cross section data.
export OPENMC_CROSS_SECTIONS=${HOME}/cross_sections/endfb71_hdf5/cross_sections.xml

# without setting HDF5_ROOT, the default is PETSc's HDF5, which is fine

# using multiple options causes multiple libraries to be built with different settings
export METHODS='opt oprof debug'

# current method to build
export METHOD='opt'

# set the OCCA Backend
export NEKRS_OCCA_MODE_DEFAULT=CPU

# set the PYTHONPATH
export PYTHONPATH=/home/lgross/cardinal/contrib/moose/python:$PYTHONPATH

export MOOSE_DIR=/home/lgross/cardinal/contrib/moose

# openmc
export OPENMC_ENDF_DATA=/home/lgross/endf-b-vii.1
# set the OPENMC_DIR when testing new features
export OPENMC_DIR=/home/lgross/openmc
# add openmc executable to path
export PATH=/home/lgross/openmc/build/bin:$PATH

This feels like more of an OpenMC issue than a Cardinal one. I just looked for this issue on the OpenMC discourse and it seems like you are not the only one with this problem. Maybe you could comment on this thread to see if someone at OpenMC has more helpful tips

[lewisgross1296]

Actually this thread seems to be the exact same error as you and Patrick gave an answer as what to do.

[aprilnovak]

@AnthonyB08 when was the last time you built Cardinal? Last week, I update the OpenMC submodule (it was previously pointing to a version from July, so there was a big gap there). Maybe if you do the following the version issue will be fixed?

cd cardinal
git pull upstream devel
./scripts/get-dependencies.sh
make -j8

[AnthonyB08]

@lewisgross1296 I am curious then, where is your sys path for import openmc?

@aprilnovak I am trying that now, will update ASAP.

[lewisgross1296]

Maybe this is what you were wondering?

lgross@ulam:~/openmc (s2patch) $ python
Python 3.10.5 (main, Jun 30 2022, 12:02:41) [GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print(sys.path)
['', '/home/lgross/cardinal/contrib/moose/python', '/home/lgross/openmc', '/home/lgross/.pyenv/versions/3.10.5/lib/python310.zip', '/home/lgross/.pyenv/versions/3.10.5/lib/python3.10', '/home/lgross/.pyenv/versions/3.10.5/lib/python3.10/lib-dynload', '/home/lgross/.pyenv/versions/3.10.5/lib/python3.10/site-packages']

Could be worth looking into pyenv for managing OpenMC's python API. April suggested this to me a while back.