How to create statepoints in HDF5

User Support
1

Hello All,

How would I get a statepoint to be written in HDF5 format rather than the binary one. I couldn’t find the docs for this. Thanks!

Be Well
Anthony

2

Hey Anthony,

Relevant information can be found in the documentation. If you have not yet installed HDF5, section 2.2.1 of the Installation guide will detail that. http://mit-crpg.github.io/openmc/usersguide/install.html

If you have installed it for the configuration you will be using (serial / parallel), section 2.2.3 explains how to enable it. If the directions are not clear enough, please explain what is confusing so that we may improve our documentation.

Best,
Derek Lax

3

Anthony,

Sorry if this posts twice, I got a send error the first time.

It has been a while since I have done this, but I think you just need to build OpenMC with HDF5 support and then when you have the statepoint tag in your settings.xml file it will automatically use HDF5 files. The instructions for building HDF5 for OpenMC are in the optional section of the installation instructions:

http://mit-crpg.github.io/openmc/usersguide/install.html

Those instructions were enough for me a while back to get things going. Hopefully this points you in the right direction. I am sure the lead devs can give better instructions.

Cheers,

4

Hey Anthony,

Relevant information can be found in the documentation. If you have not
yet installed HDF5, section 2.2.1 of the Installation guide will detail
that. http://mit-crpg.github.io/openmc/usersguide/install.html

Hi Matt, Derek,

Ahh thanks. I have more versions of HDF5 than I care to count :). I read
that page but thought that editing the makefile was bad form. It doesn't
play well with version control at all. Have you considered moving to CMake
or even autotools or similar Makefile generator?

As a quick fix you could change the lines:

HDF5 = no
HDF5_DIR = /opt/hdf5/1.8.11-$(COMPILER)

to use the ?= operator

HDF5 ?= no
HDF5_DIR ?= /opt/hdf5/1.8.11-$(COMPILER)

This would at least allow folks to define these variables in their env or
inline on the command line and they wouldn't have to edit the Makefile.
This should probably happen for all of the variables listed in section 2.2.3

Thanks!
Be Well
Anthony

5

Hey Anthony,

The develop branch of OpenMC currently is all CMake/CTest/CDash. We are just waiting for a couple more items to be finalized before we merge into the master branch.

-Bryan

6

Hi Bryan,

Sweet. That solves that problem.

Be Well
Anthony