Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the meaning of phi_nominal in Mechanics.Rotational.PartialCompliantWithRelativeStates #615

Closed
modelica-trac-importer opened this issue Jan 14, 2017 · 3 comments
Assignees
Labels
bug Critical/severe issue L: Mechanics.Rotational Issue addresses Modelica.Mechanics.Rotational P: high High priority issue
Milestone

Comments

@modelica-trac-importer
Copy link

modelica-trac-importer commented Jan 14, 2017

Modified by dietmarw on 31 Oct 2011 08:39 UTC
The partial model Mechanics.Rotational.PartialCompliantWithRelativeStates has a parameter, phi_nominal, which is used to set phi_rel.nominal. The comment states that this is the "Nominal value of phi_rel (used for scaling)".

But phi_rel is an angle of rotation, which can range anywhere from -infinity to infinity. What is the purpose of scaling it at all? Even if the angles were kept within a single rotation, then the default nominal value of 1e-4 makes no sense, since the angle would typically range from -pi to pi.

This came up because a user set phi_nominal to zero. This makes sense from a physical point of view, but of course makes no sense for scaling purposes.


Reported by stefanv on 22 Sep 2011 15:31 UTC
The partial model Mechanics.Rotational.PartialCompliantWithRelativeStates has a parameter, phi_nominal, which is used to set phi_rel.nominal. The comment states that this is the "Nominal value of phi_rel (used for scaling)".

But phi_rel is an angle of rotation, which can range anywhere from -infinity to infinity. What is the purpose of scaling it at all? Even if the angles were kept within a single rotation, then the default nominal value of 1e-4 makes no sense, since the angle would typically range from -pi to pi.

This came up because a user set {{phi_nominal}}} to zero. This makes sense from a physical point of view, but of course makes no sense for scaling purposes.


Migrated-From: https://trac.modelica.org/Modelica/ticket/615

@modelica-trac-importer modelica-trac-importer added this to the MSL3.2.1 milestone Jan 14, 2017
@modelica-trac-importer modelica-trac-importer added bug Critical/severe issue L: Mechanics.Rotational Issue addresses Modelica.Mechanics.Rotational P: high High priority issue labels Jan 14, 2017
@modelica-trac-importer
Copy link
Author

Modified by dietmarw on 31 Oct 2011 08:39 UTC

@modelica-trac-importer
Copy link
Author

Comment by otter on 10 Dec 2012 15:11 UTC
Fixed in b8a1114:

A new chapter Modelica.Mechanics.Rotational.UsersGuide.StateSelection has been added to explain state selection in the Rotational library and the meaning of the phi_nominal parameter. Additionally, a guard was introduced to use a nominal value of 1, if phi_nominal < Modelica.Constants.eps to cope with a wrong user input of 0.

Please read the new chapter for a longer explanation. In short:

  • The default value of phi_nominal=1e-4 is defined for an elastic deformation of a drive train component that is in this order (like the SpringDamper element). A phi_nominal = 1 would most of the time switch off error control for this variable.
  • For other components, like the Clutch, a phi_nominal = 1 should be set. However, the default value of 1e-4 does not hurt in this case. The only effect is that the simulation might become a bit slower, since the required error tolerance is more stringent.

@modelica-trac-importer
Copy link
Author

Changelog removed by otter on 10 Dec 2012 15:11 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Critical/severe issue L: Mechanics.Rotational Issue addresses Modelica.Mechanics.Rotational P: high High priority issue
Projects
None yet
Development

No branches or pull requests

2 participants