-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add loadable agents to the backend #173
Comments
@clalancette I have a few questions with regards to the loadable agents. Let's catch up this week and summarise back here. |
Shared linking to Drake libraries (#365). |
Discussion about |
Remove non-loadable code from |
|
Looking good. Remaining work transferred to the final polish meta for M2: #378 |
We would like to have the ability to load in agents (more-or-less vehicles) dynamically at runtime into the simulation. The goal is to be able to have agents developed completely outside of delphyne, and then loaded into a scenario. The basic tasks here are:
Work Items
configure
is not being checkedconfigure
and fromAddLoadableModule
(skip till we have a need)~/.delphyne/plugins
, with override from environment variableDocumentation
configure
virtual method to describe design and usage considerations Loadable agents core #213Polish (see #346)
automotive_simulator.cc
to agents.setPlugin
constraintConfigure
time), so I think we have to have a two-step setup here.Integration
automotive_simulator.cc
(this may be somewhat difficult because most of the tests need to useAddPriusSimpleCar
, so we'd have to figure out how to deal with that)Demo Goal
Out of Scope
Dynamic reconfigure for scriptlet control will be left to a later milestone. Since it's a plugin framework with a fixed api, you can't just singly expose an api from this car, and yet another from another car. Likely some api with a generic key/value signature should help alleviate this situation.
Due to a limitation in ignition-common currently, implementations of the loadable vehicles have to derive from classes like:
AgentPluginDoubleBase
. In the future, it will be possible to templatize these, so the implementations can derive fromAgentPluginBase<T>
.The text was updated successfully, but these errors were encountered: