Tony Alberti

@keckler you're exactly right with reference to #769 . It's the same problem. As @Nebbychadnezzar points out, the axial expansion changer definitely does not support this currently. When we were...

My working branch to address this issue. https://github.com/albeanth/armi/tree/processLoadUpdate

I think this is still an open issue. #735 was designed to address it, but opened up a hefty can of worms. It was decided to shelve that approach for...

Interesting idea! In theory that should work. I went into parameterCollections.py to check it out and came across this docstring mentioning that it might not be particularly safe to use...

@jakehader I noticed you changed the title to include the component type. This is an interesting addition! Consider - if a block has multiple components of the same type (e.g.,...

Looking into it.

> Component density differs if you create component through blueprints vs programmatically . I believe the issue you've identified here boils down to an inconsistency between the default behavior of...

> I would be curious to know how this problem relates to this docstring: @keckler has pointed this out as well in https://github.com/terrapower/armi/issues/770 and it feels related to #820 ....

A note to my future self of an instance where there is 0.0 inconsistency. https://github.com/terrapower/armi/blob/20ca6877c2e2221bc3e3521cf9e827cf2d4a4376/armi/reactor/reactors.py#L1692-L1696

I recently found that the operator object on the reactor, `r.o`, is not copied when deepcopy'ing a reactor. Which is interesting. So the following results in a `None`: ```python from...