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

Removing user defined blueprints from snapshot runs #872

Merged
merged 9 commits into from
Sep 14, 2022

Conversation

albeanth
Copy link
Member

@albeanth albeanth commented Sep 8, 2022

Description

When doing a snapshots run, ARMI allows users to use both new settings and blueprints. This PR removes the ability to use new (potentially different) blueprints.

Effects:

  • Prevents users from unintentionally applying blueprints that are different than what is stored on the H5 database.
  • If the database was written with a different version of ARMI the db load may not work. This could occur if an overhaul is done to the database system (though doing such a task would likely break a slew of other things as well).

More relevant information can be found in #871. This PR will close #871 as well.


Checklist

  • This PR has only one purpose or idea.
  • Tests have been added/updated to verify that the new/changed code works.
  • The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
  • The documentation is still up-to-date in the doc folder.
  • The dependencies are still up-to-date in setup.py.

@albeanth
Copy link
Member Author

Note: Testing impacts on downstream projects. Reverting to draft.

@albeanth albeanth marked this pull request as draft September 12, 2022 15:09
- blueprints assemblies should be numbered 0 to len(assemDesigns). This should help guarantee that there are no name conflicts with blueprints assemblies and those in core.
- assertion now only counts core + sfp without blueprints assems.
- Not counting blueprints assems stems from this change here terrapower@77411cd
- There are some cases where a database may not have blueprints, so a user will need to provide them.
- However, for snapshot runs, we still do not allow user defined blueprints.
@albeanth albeanth marked this pull request as ready for review September 14, 2022 15:18
@albeanth albeanth changed the title Removing optional param "bp" from db load Removing user defined blueprints from snapshot runs Sep 14, 2022
# retrieve current count of assemblies to restore after
# creating blueprints assemblies. This is particularly useful for
# doing snapshot based runs with database loads where the
# assembly counter is likely not equal to 0.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add "To ensure that the assembly count is not a function of how many times load state/snapshots has been called"

@onufer onufer merged commit 1a24d7a into terrapower:main Sep 14, 2022
@albeanth albeanth deleted the dbLoadUpdate branch September 15, 2022 19:21
scottyak pushed a commit to scottyak/armi that referenced this pull request Oct 27, 2022
* Subsequent DB loads no longer cause the assembly count to increase (due to blueprints)
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.

Remove the ability for users to load separate blueprints in snapshots run
2 participants