Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing assembly number issue in DB Load #615

Merged
merged 16 commits into from Apr 19, 2022

Conversation

john-science
Copy link
Member

@john-science john-science commented Apr 5, 2022

Description

It appears there has been a bug in our DB load for several years now. Essentially, when reading from certain (though not all) H5 databases, the assembly number can start off in a bad state. This is not immediately obvious, but if you try to do something serious with the resultant Reactor/Core objects, you immediately find the problem. In this case, trying to use growToFullCore() immediately after the load() raises the problem.

NOTE: Relatedly, it turns out Block.makeUnique() was unused. So I removed it. Thanks @ntouran !


Checklist

  • The code is understandable and maintainable to people beyond the author.
  • Tests have been added/updated to verify that the new or changed code works.
  • There is no commented out code in this PR.
  • The commit message follows good practices.
  • All docstrings are still up-to-date with these changes.

If user exposed functionality was added/changed:

  • Documentation added/updated in the doc folder.

@john-science john-science added the bug Something is wrong: Highest Priority label Apr 5, 2022
@john-science
Copy link
Member Author

@jasonbmeng @jeffbaylor

Just FYI, the PR to fix growToFullCore() is up. It turns out to be a problem in the database load().

@john-science john-science linked an issue Apr 5, 2022 that may be closed by this pull request
@john-science john-science merged commit 8140a89 into terrapower:master Apr 19, 2022
@john-science john-science deleted the fix_growToFullCore branch April 19, 2022 03:16
drewj-usnctech added a commit to drewj-usnctech/armi that referenced this pull request Apr 20, 2022
…efine-system-builders

* terrapower/master: (24 commits)
  Update docstring formatting in `getPotentialParentFromSettingValue` (terrapower#627)
  Removing inherited docstrings from Docs (terrapower#628)
  Removing bare "import armi" statements (terrapower#626)
  Fixing assembly number issue in DB Load (terrapower#615)
  Making the app version more available (terrapower#624)
  Adding MPI tests to code coverage (terrapower#625)
  Removing support for XML Settings files (terrapower#612)
  Minor language cleanup in new standards and practices. (terrapower#610)
  remove extraneous `mpicov` arg from tox.ini envlist (terrapower#604)
  Swap flux param (terrapower#605)
  Fixing _fluxSwapParam for NumPy arrays (terrapower#607)
  Unshaped component (terrapower#600)
  Fixing docstring (terrapower#601)
  Adding options to settings report (terrapower#598)
  Adding coding standards and practices to Docs (terrapower#597)
  Removing defunct code from HistoryTrackerInterface (terrapower#594)
  Fix to a bug where an ARMI application could not call (terrapower#593)
  Tracking ARMI Requirements (terrapower#590)
  Remove PyYaml Dependency (terrapower#586)
  Filling out code coverage for entry points (terrapower#587)
  ...
scottyak pushed a commit to scottyak/armi that referenced this pull request Oct 27, 2022
It appears there has been a bug in our DB load for several years now. Essentially, when reading from certain (though not all) H5 databases, the assembly number can start off in a bad state. This is not immediately obvious, but if you try to do something serious with the resultant Reactor/Core objects, you immediately find the problem. In this case, trying to use growToFullCore() immediately after the load() raises the problem.

NOTE: Relatedly, it turns out Block.makeUnique() was unused. So I removed it. Thanks @ntouran !
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is wrong: Highest Priority
Projects
None yet
Development

Successfully merging this pull request may close these issues.

r.core.growToFullCore() error when loading from database
2 participants