IndependentOperator claims that using an empty MicroXS object allows a decay-only step. It appears that trying to handle only decay, without any associated openmc.Model object, results in an error saying that no heat was found from the OpenMC output.
[openmc.deplete] t=0.0 s, dt=1.0 s, source=0.0
No energy reported from OpenMC tallies. Do your HDF5 files have heating data?
Well that's exactly what I expect! No transport-induced heat production, and pure decay. IndependentOperator suggests this is allowable use of it, to quote the documentation:
Note that passing an empty :class:`~openmc.deplete.MicroXS` instance to the
``micro_xs`` argument allows a decay-only calculation to be run.
If I am not using this class correctly, the documentation should be improved.
Bug Description
IndependentOperator
claims that using an emptyMicroXS
object allows a decay-only step. It appears that trying to handle only decay, without any associatedopenmc.Model
object, results in an error saying that no heat was found from the OpenMC output.Well that's exactly what I expect! No transport-induced heat production, and pure decay.
IndependentOperator
suggests this is allowable use of it, to quote the documentation:If I am not using this class correctly, the documentation should be improved.
Steps to Reproduce
Here's an MWE that produces the error:
I would hope to see the decay progeny of U239 appear here.
Environment
On the latest commit 2974d53b3c07dc1a822f2b31ecd27b6553cbd458. Ubuntu. Nuclear data libraries are visible in the MWE.