Open albeanth opened 7 months ago
Additionally, rotatePins
is fixed to increments of 60 degree rotations, while rotate
is expected to be a flexible rotation. However, once assembly.rotate
boils down to blocks.rotate
, that flexible rotation angle needs to be in 60 degree increments
https://github.com/terrapower/armi/blob/7e1e16736b7082c2ce4892bb36243fb080c63a48/armi/reactor/blocks.py#L1839-L1844
There several rotation methods:
It looks like they all boil down to the two methods on
blocks.py
,rotate
androtatePins
. The docstring forrotatePins
suggests that calling it on it's own does not constitute rotation. https://github.com/terrapower/armi/blob/7e1e16736b7082c2ce4892bb36243fb080c63a48/armi/reactor/blocks.py#L1928-L1932That said, I think we should consider making
rotatePins
private and/or putting warnings in docstrings (on that method, assembly.rotatePins, and assemblyRotationAlgorithms.py::simpleAssemblyRotation) saying that it's an incomplete rotation.