Closed BasilioPV closed 1 year ago
Even if helpful in some models, IMO we shall not implement this. The reason especially is that this in principle changes a particular variable from being a parameter (parameter SI.Position r[3]
) to being an input (RealInput r_vect[3]
). Doing so, we should also accordingly change e.g. r
and rotation parameters in Mechanics.MultiBody.Parts.FixedRotation
or Mechanics.MultiBody.Parts.Fixed
. And so on in further models for (arbitrary) parameters.
So the rationale behind this change (incl. all known overhead) is not clearly declared and I don't believe we will be able to do so.
As far as I understand it can also be modeled with 3 translation position components (with exact=true) connected to 3 prismatic joints (I believe I have seen that used somewhere). I don't know whether that is an argument for adding it - or for not adding it.
BTW: The world
and import Modelica.SIunits.Conversions.to_unit1;
should just be removed as not needed.
@HansOlsson You are right, this can be modelled using other MSL components. Mi intention is to crerate a shortcut for use this funcionality. Thanks for point on the not needed lines!
I have created a simple Variable Translation component based on a translation with a vector[3] real input.
This component is very useful to place forces over a body that their application point changes over time. The 3D animation was disabled.
If this has interest to add to MSL, please indicate on the issue how can I help on this. Oterwise close the issue. Thanks!
Source code: