You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are many situations where we need to start more than one instance of an "app". Currently we do this for most drivers, but I also like to consider doing it for things like the wind_estimator or ekf2.
One idea would be giving ModuleBase some concept of instance. You'd use the same entrypoint, but an additional command line option would select the particular instance, likely default to the 1st instance when not specified. This instance number could then correspond to the particular parameters it uses, orb topics subscribed to and orb multi publish instance. Related parameter issue. #8821
Yet another option could be generating separate entry points for each. Something like...
ekf2 start
ekf2_2 start
We could then start using ModuleBase on all of the drivers.
Ideas for how we could approach this scalably?
The text was updated successfully, but these errors were encountered:
There are many situations where we need to start more than one instance of an "app". Currently we do this for most drivers, but I also like to consider doing it for things like the wind_estimator or ekf2.
One idea would be giving ModuleBase some concept of instance. You'd use the same entrypoint, but an additional command line option would select the particular instance, likely default to the 1st instance when not specified. This instance number could then correspond to the particular parameters it uses, orb topics subscribed to and orb multi publish instance. Related parameter issue. #8821
Yet another option could be generating separate entry points for each. Something like...
We could then start using ModuleBase on all of the drivers.
Ideas for how we could approach this scalably?
The text was updated successfully, but these errors were encountered: