Open john-science opened 1 month ago
@albeanth and I identified two places where the ARMI codebase does not support the new EOL time point being written to the database (added in PR 1090):
EOL
Database3.genTimeSteps()
https://github.com/terrapower/armi/blob/8b5163a8b61ebe704419d2d77067bfcf8018f328/armi/bookkeeping/db/database3.py#L612
Returns (cycle, node), but if the EOL is present in the DB, it just returns the last time node twice.
(cycle, node)
Database3.load()
cycle
node
https://github.com/terrapower/armi/blob/8b5163a8b61ebe704419d2d77067bfcf8018f328/armi/bookkeeping/db/database3.py#L702
Cross-referencing #1090 since it's related.
@albeanth and I identified two places where the ARMI codebase does not support the new
EOL
time point being written to the database (added in PR 1090):Database3.genTimeSteps()
:https://github.com/terrapower/armi/blob/8b5163a8b61ebe704419d2d77067bfcf8018f328/armi/bookkeeping/db/database3.py#L612
Returns
(cycle, node)
, but if theEOL
is present in the DB, it just returns the last time node twice.Database3.load()
takes incycle
andnode
as integers, thus not allowing us to load an EOL timestep:https://github.com/terrapower/armi/blob/8b5163a8b61ebe704419d2d77067bfcf8018f328/armi/bookkeeping/db/database3.py#L702