-
Notifications
You must be signed in to change notification settings - Fork 128
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
Documentation Update Collection - Clarification Static vs Dynamic data #770
Comments
Here I will add some thoughts on different message parameters: osi_trafficsign.proto |
osi_trafficupdate.proto |
osi_trafficlight.proto |
osi_trafficcommand.proto and osi_trafficcommandupdate.proto |
Hm, I have some doubts about the current approach. As you mentioned in the pull request:
it is indeed not clear what label a variable should receive. For some variables like the ID or the version it might be clear that they're static, but things like obstacles, traffic lights, signs or even logical lanes might not necessarily be static. In general, I'm a bit unsure about the use-case here. Why do we actually need these labels? It would be good, if you could give me a better understanding about the problem we're trying to solve here. |
The topic was discussed in today's Performance/Packaging meeting:
|
Thanks, I got it. This could help for my problem. I wasn't aware of that. My problem for the understanding there was, that it is not referenced to the OSMP https://github.com/OpenSimulationInterface/osi-sensor-model-packaging repo, which specifies the "GroundTruthInit". In that regard, we can try to improve the documentation. |
In the PR #768, an update on static an dynamic data should be made.
Therefore the documentation on the data types will be updated.
This Issue will be the central collection of Q&A on the static or dynamic data description.
Please add questions, suggestions or answers to support this approach.
Currently used cocumentation notes:
The text was updated successfully, but these errors were encountered: