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
The setRoationRate function in pyADflow has a bug that prevents assigning specific rotation rates to individual blocks. Instead, the rate is applied to n cgns blocks starting form the first block number.
PR #323 potentially has fixes for this bug, however due to inactivity and incompleteness that PR has been closed.
Steps to reproduce issue
PR #323 identified this bug, but no tests or MWE was provided.
Current behavior
Currently ADflow applies the rotation rate the first n blocks instead of targeting specific blocks provided by the user.
Expected behavior
Rotation rates should be applied to specific blocks provided by the user.
The text was updated successfully, but these errors were encountered:
Description
The
setRoationRate
function inpyADflow
has a bug that prevents assigning specific rotation rates to individual blocks. Instead, the rate is applied ton
cgns blocks starting form the first block number.PR #323 potentially has fixes for this bug, however due to inactivity and incompleteness that PR has been closed.
Steps to reproduce issue
PR #323 identified this bug, but no tests or MWE was provided.
Current behavior
Currently ADflow applies the rotation rate the first
n
blocks instead of targeting specific blocks provided by the user.Expected behavior
Rotation rates should be applied to specific blocks provided by the user.
The text was updated successfully, but these errors were encountered: