Replies: 1 comment
-
Thanks for your input. I like the idea, so I hope to be able (with my PR) to find a format where we later could add dimensions/ratios like above if needed/wanted. At the moment there seems to be some mixed opinions on whether it is useful or not. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello @COVESA community,
I have recently encountered this project as we are working on verification and validation tooling for connected and autonomous systems. Having a well-defined specification for everything is very important for our goals. Therefore, we have the issue of physical quantities that frequently come up in our tooling when representing signals. So, we have thought about the issue quite a bit and wondered if there is a similar issue for the VSS project as well.
In the following, I would like to share some ideas to discuss whether this discussion is in the scope of VSS. I have to say that there are several approaches when it comes to representing physical quantities but here we take an SI-based approach to represent dimensions, units, and quantities. The SI defines 7 base dimensions such as
length
,mass
, andtime
and other domains are derived from these dimensions such asfrequency
andspeed
. Assume we havedomains.yml
as follows:Then we can define units with a
domain
and aratio
. You may guess that theratio
has been inspired by thestd::chrono
library to represent different time units. I think this works well for the general case. Here is an example snippet ofunits.yml
under this approach:These ideas have been implemented as our prototype C++ library of
scalr
here. However, note that there are a few other issues in this discussion, not adequately discussed or handled such asI found out this is related to #669
Beta Was this translation helpful? Give feedback.
All reactions