Standards for representing series of other geometrical objects #112
felixchenier
started this conversation in
2. Development: Ideas, new features, doc, etc.
Replies: 1 comment
-
Probably we should look the other way. At the moment, the player assumes Nx4 series with ones on the 4th column are points, and Nx4x4 series are frames. I think this should stay the same, but as a fallback for a proper identification. If the TimeSeries' data_info has an entry of, for example, "Kind", then we could specify what we expect, and then use different expressions for this kind of object. For instance: "line" could be either
or
"plane" could be either:
or
"force_position":
"moment_position":
and even other constructs such as "point_cloud":
|
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
-
At the moment, we can express:
At some point, we may want to express more geometrical objects or constructs:
These representations should be compatible with linear operations so that get_local_coordinates() etc. still work on these constructs. If they are all consistent one with the other, it is also great.
I think a good way would be to represent all those would be Nx4x2 matrices that combine one vector and one point:
The only problem I see for now is that there is no way to identify what is what. Probably that this identification shouldn't be on the "data" level, but more on using some sort of metadata or manual identification by the user. This remains to be clarified.
If someone reads this and has ideas, I'm all open.
Beta Was this translation helpful? Give feedback.
All reactions