BeamDyn initialization with non-zero initial azimuth produces strange results

[bjonkman]

See attached file for description of the problem.

BeamDyn_InitializationBug.pdf

[bjonkman]

@michaelasprague - Has there been any progress on this issue?

[michaelasprague]

@bjonkman , sorry, no. @rafaelmudafort is taking lead on this now; plan is to address this by exposing the problem in the testing harness and to then pursue the fix.

[andrew-platt]

In the CalcIC routine, the calculation of the translational velocity is incorrectly referenced. The root node position needs to be subtracted otherwise the distance used in the cross product is relative to the original root position, not the rotated root position. We (Envision) have a fix for this that we will give you.

BTW: the fix we have for this appears to help get a larger timestep.

[michaelasprague]

@andrew-platt, it would be great if this could be submitted as a pull request -- please let us know if there's another mechanism you'd prefer. Thanks!

[rafmudaf]

This issue was fixed in pull request #114