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
x, y, _z=self.spatialLocator.getGlobalCoordinates()
x+=self.p.displacementX*100.0
y+=self.p.displacementY*100.0
return (
round(x, units.FLOAT_DIMENSION_DECIMALS),
round(y, units.FLOAT_DIMENSION_DECIMALS),
)
I can't find any use of this parameter in any repos that I have access to. I'm not even sure what it would mean for the rotation of a block to impact its location, assuming that orientation is about the centroid of the block.
Extremely low priority, but just pointing it out.
The text was updated successfully, but these errors were encountered:
I agree with Chris' assessment. This parameter looks like it should be removable from both methods.
It's possible that someone is passing unused values into one of those methods, positionally. But (a) unit tests would catch that, and (b) we'd want to know if people were trying to use this defunct parameter anyway.
If one specifies the
rotationDegreesCCW
parameter tocoords()
, it will either result in an error or do nothing with it:armi/armi/reactor/blocks.py
Lines 597 to 607 in 4f55d94
armi/armi/reactor/blocks.py
Lines 1620 to 1634 in 4f55d94
I can't find any use of this parameter in any repos that I have access to. I'm not even sure what it would mean for the rotation of a block to impact its location, assuming that orientation is about the centroid of the block.
Extremely low priority, but just pointing it out.
The text was updated successfully, but these errors were encountered: