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
Two issues for Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.ForceCurrentBehaviour and Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.ForceStrokeBehaviour:
I don't see why we have so short Interval (1e-4) for these two models in Resolve #4336 #4418
To me it seems 0.01 s would work as well, and if someone sets a very small Interval I expect that there is something relevant on that time-scale, and I don't know which signal. So, if there is something interesting on that time-scale, please enlighten me. (Note that Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.ArmatureStroke has a small Interval since it simulates for a short time and has interesting dynamics.)
The documentation is broken for those two models (and likely have been for quite some time) - it refers to flange_b for components that only have flange.
I just compared two simulations and yes 100 ms is ok.
We just have to take care of the reference results ...
I'll have a look at the broken links.
beutlich
changed the title
Modelica.Magnetic.FluxTubes examples - comment from 4418
Modelica.Magnetic.FluxTubes examples - comment from #4418
Jul 23, 2024
Two issues for Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.ForceCurrentBehaviour and Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.ForceStrokeBehaviour:
To me it seems 0.01 s would work as well, and if someone sets a very small Interval I expect that there is something relevant on that time-scale, and I don't know which signal. So, if there is something interesting on that time-scale, please enlighten me. (Note that Modelica.Magnetic.FluxTubes.Examples.MovingCoilActuator.ArmatureStroke has a small Interval since it simulates for a short time and has interesting dynamics.)
Originally posted by @HansOlsson in #4418 (review)
The text was updated successfully, but these errors were encountered: