You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like they all boil down to the two methods on blocks.py, rotate and rotatePins. The docstring for rotatePins suggests that calling it on it's own does not constitute rotation.
Changing (x,y) positions of pins does NOT constitute rotation, because the indexing of pin
atom densities must be re-ordered. Re-order indexing of pin-level quantities, NOT (x,y)
locations of pins. Otherwise, subchannel input will be in wrong order.
That 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.
The text was updated successfully, but these errors were encountered:
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
There several rotation methods:
armi/armi/reactor/assemblies.py
Line 1215 in 7e1e167
armi/armi/reactor/assemblies.py
Line 312 in 7e1e167
armi/armi/reactor/blocks.py
Line 1827 in 7e1e167
armi/armi/reactor/blocks.py
Line 1902 in 7e1e167
armi/armi/physics/fuelCycle/assemblyRotationAlgorithms.py
Line 76 in 7e1e167
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.armi/armi/reactor/blocks.py
Lines 1928 to 1932 in 7e1e167
That 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.The text was updated successfully, but these errors were encountered: