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

Zones overhaul #943

Merged
merged 29 commits into from
Oct 26, 2022
Merged

Zones overhaul #943

merged 29 commits into from
Oct 26, 2022

Conversation

joshuavictorchen
Copy link
Contributor

@joshuavictorchen joshuavictorchen commented Oct 17, 2022

Description

Overhaul tooling in the reactor.zones module and remove application-specific zoning logic, which may be implemented as desired in downstream Interfaces.

This satisfies the main intent of #811. Enhancements may be added in the future.

Related issues:
#563
#800


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.

john-science and others added 25 commits August 3, 2022 13:37
…zones (#857)

Co-authored-by: Joshua Chen <jchen@terrapower.com>
* remove buildZones function (in favor of using Interface for zoning)
* remove log re: zone creation from reactors.py (buildZones function was removed in prior commit)
* remove reactors.buildZones; move zones.buildManualZones to reactors module
* add unit test coverage, fix Zones.getAllLocations bug, move tests for buildManualZones to test_reactors
* update ThirdCoreHexToFullCoreChanger.convert to adjust zones when growing to full core
@joshuavictorchen joshuavictorchen marked this pull request as ready for review October 17, 2022 22:19
@joshuavictorchen joshuavictorchen marked this pull request as draft October 17, 2022 22:19
@john-science
Copy link
Member

john-science commented Oct 18, 2022

TODO:

  • We need to bump the ARMI version number.
  • We need to mention this in the release docs
  • In a future PR??? we should add some docs on how to define Zones.

@john-science
Copy link
Member

@sombrereau @drewejohnson

We are moving the super custom zones logic out of ARMI, so ARMI only provides a way to define Zones.

I assume this is better for both of your reactor projects, but I just want to ask you.

@john-science john-science added enhancement New feature or request architecture Issues related to big picture system architecture labels Oct 22, 2022
@john-science john-science marked this pull request as ready for review October 22, 2022 15:22
Copy link
Member

@john-science john-science left a comment

Choose a reason for hiding this comment

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

@joshuavictorchen @opotowsky I think this is ready! Do you think the downstream repos are ready?

@joshuavictorchen
Copy link
Contributor Author

@joshuavictorchen @opotowsky I think this is ready! Do you think the downstream repos are ready?

Yep! Zoning board meeting has been scheduled for the downstream application/repos :)

@john-science john-science merged commit 47658eb into main Oct 26, 2022
@john-science john-science deleted the zones_overhaul branch October 26, 2022 17:09
scottyak pushed a commit to scottyak/armi that referenced this pull request Oct 27, 2022
Overhaul tooling in the reactor.zones module and remove application-specific zoning logic, which may be implemented as desired in downstream Interfaces.

This satisfies the main intent of terrapower#811. Enhancements may be added in the future.

Related issues:
terrapower#563
terrapower#800
@keckler keckler mentioned this pull request Oct 31, 2022
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Issues related to big picture system architecture enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants