-
Notifications
You must be signed in to change notification settings - Fork 164
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
Add unit and displayUnit to signal input and output representing an angle #2488
Comments
I can understand the need for unit="rad", and I would also hope that we could derive that unit in more cases. However, it may be excessive to use displayUnit="deg" - when looking at polar representation I don't necessarily consider degrees a better choice. |
OK, to me this sounds like adding the angle unit "rad" is possible without getting the MSL backwards incompatible, right? The displayUnit shall not be included -- so this makes sense to me. I can create a pull request, if we agree to go for adding units to angle inputs and outputs. |
I agree with Hans, displayUnit might be overdone. |
But don't forget angular velocity ;-) |
I'm just working on the initially mentioned.
To be sure: We should go through the whole standard library a look for similar occurenes. |
To be sure: We should go through the whole standard library a look for similar occurenes. |
To be sure: We should go through the whole standard library a look for similar occurenes. |
There are a couple models in the MSL which provide an angle signal input or output. However, when simulating and displaying such angles, the displayUnit can often NOT be switched to "deg", since the output is just a RealOutput with no unit. Therefore, the angle signal input and output shall be equipped with
(unit="rad",displayUnit="deg")
.This issue applies to the following models (list may not yet be complete):
The text was updated successfully, but these errors were encountered: