Closed ClemensLinnhoff closed 1 year ago
Hi @jdsika and @ClemensLinnhoff .
Thanks for putting together this template model.
I've been checking this against a similar template I was making (in a private repo). So far I found this PR to be quite complete:
One thing I did not have time to check yet: I wanted to make a local build (on my PC) of the model template and the new esmini with traffic update input. However, I see this is already working on the pipeline.
Some potential improvements:
traffic_update.update.base.___
vs. traffic_update.internal_state.___
? Usually, you would use one OR the other: either the traffic agent has it's own dynamics and computes its new position/velocity to send to the simulator, OR, the traffic agent sends control inputs (e.g., throttle, steering, ...) and a block downstream uses this to compute position/velocity. Is this template expected to cover only the first case (as currently coded) or also the second one?Both of these improvements are more "nice to have", not "must have" for this PR to be completed.
Thank you for your review @nocll! I put some more explanation in the readme to describe, that the update output is used in this template. Generally there are several possibilities for traffic participants (e.g. also TrafficCommand) and we just wanted to give one example here.
For testing you are right, in the end it should be tested, if the trajectory given by the model is correct, but we would like to wait for an actual model in the sub-library, before we implement this.
Some files did not pass the configured checks!
Have any feedback or feature suggestions? Share it here.
Add a description
Take this checklist as orientation for yourself, if this PR is ready for Maintainer Review