-
Notifications
You must be signed in to change notification settings - Fork 91
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
Force plotAssemblyTypes to always use instantiated assemblies, and al… #2030
Force plotAssemblyTypes to always use instantiated assemblies, and al… #2030
Conversation
I am relatively sure that this is working now. I tested it with a simply dummy case, however I am unable to test it with my big model due to some dependency conflicts. I think it is ready for your eyes @john-science |
Love it!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it
…rrapower/armi into fix_plots_block_heights_again
Let me know what you think of that plan. |
Ah! No, I didn't notice that. I just assumed this was pointed at Thanks! |
This is meant to improve #1998 by allowing the specification of hot versus cold heights in the plots. Additionally, a couple clean ups are implemented:
plotAssemblyTypes()
so that it always operates based on instantiated assemblies. Allowing users to pass in blueprints was making things really messy, and provided absolutely no benefit because blueprints already containAssembly
objects in the first place throughblueprints.assemblies.values()
.plotAssemblyTypes()
method signature is changed. That signature is/was pretty ridiculous anyways, so I feel justified in changing it. I updated all calls to that method that I could find.I would not expect that there are many downstream calls to this
plotAssemblyTypes()
method. Checking all the projects that I have access to, I found it used in exactly one place (one of my own internal repos).