Skip to content

Warn when ACE average heating numbers are written as zeros - #27

Open
jon-proximafusion wants to merge 1 commit into
llnl:masterfrom
shimwell:warn-on-zero-ace-heating
Open

Warn when ACE average heating numbers are written as zeros#27
jon-proximafusion wants to merge 1 commit into
llnl:masterfrom
shimwell:warn-on-zero-ace-heating

Conversation

@jon-proximafusion

@jon-proximafusion jon-proximafusion commented Jul 31, 2026

Copy link
Copy Markdown

gndsToACE.py fills the ESZ average heating (KERMA) column with zeros unconditionally, and the value is never recomputed elsewhere. Codes that read heating from that column get a valid ACE file in which heating is zero at every energy, so a heating tally silently returns zero instead of failing.

This doesn't calculate the heating numbers (that needs a HEATR equivalent). It just makes the gap visible: a warnings.warn where the zeros are written, plus an entry in the module's existing Issues: docstring. Generated ACE files are numerically unchanged.

warnings.warn rather than the module's printMessage(verbose > 0, ...) helper, since gating on verbose would leave the default path silent. Happy to switch that, or to raise instead, if you'd prefer.

The ESZ block's average heating (KERMA) column is unconditionally
filled with zeros, and is not recomputed elsewhere. Codes that read
heating from this column therefore get a valid ACE file in which
heating is silently zero everywhere.

Emit a warning at the point the zeros are written, and record the
limitation in the module's existing "Issues" docstring. The numeric
content of the generated ACE file is unchanged.

Co-authored-by: shimwell <mail@jshimwell.com>
Co-authored-by: jon-proximafusion <jon@proximafusion.com>
@jon-proximafusion
jon-proximafusion force-pushed the warn-on-zero-ace-heating branch from 85d0d0d to de786d4 Compare July 31, 2026 13:46
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

Successfully merging this pull request may close these issues.

2 participants