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
Span out of #210 since this is one of the TODOs for cleaning up SDF export. Legacy traffic editor has a bit of a confusing support for dispensers and ingestors, specifically:
In all our demos we use a model (i.e. TeleportDispenser) that runs a plugin with a dispenser interface, this is what actually does the dispensing.
There is also a traffic editor property, called pickup_dispenser, that however seems to not be used, specifically this is a grep on my workspace:
rmf_traffic_editor: Just the GUI to populate it and the building_map_server to publish it as a parameter.
rmf_fleet_adapter / rmf_task_ros2, Actually referring to the pickup_dispenser field in the Delivery.msg message, not the vertex parameter.
rmf_fleet_adapter_python seems to just be bindings for the Delivery.msg.
Now the question is how do we port this to the site editor? There is a (currently unused) LocationTag for Workcells. It is technically possible to "just" import TeleportDispenser and TeleportIngestor models into a new LocationTag::Workcell location, but we should probably be more careful before locking into that data format / implementation, and make sure we can capture all the information we might need from a workcell.
Implementation Considerations
No response
Alternatives
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Before proceeding, is there an existing issue or discussion for this?
Description
Span out of #210 since this is one of the TODOs for cleaning up SDF export. Legacy traffic editor has a bit of a confusing support for dispensers and ingestors, specifically:
pickup_dispenser
, that however seems to not be used, specifically this is a grep on my workspace:It's made of the following sections:
rmf_traffic_editor
: Just the GUI to populate it and thebuilding_map_server
to publish it as a parameter.rmf_fleet_adapter
/rmf_task_ros2
, Actually referring to thepickup_dispenser
field in theDelivery.msg
message, not the vertex parameter.rmf_fleet_adapter_python
seems to just be bindings for the Delivery.msg.Now the question is how do we port this to the site editor? There is a (currently unused)
LocationTag
for Workcells. It is technically possible to "just" importTeleportDispenser
andTeleportIngestor
models into a newLocationTag::Workcell
location, but we should probably be more careful before locking into that data format / implementation, and make sure we can capture all the information we might need from a workcell.Implementation Considerations
No response
Alternatives
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: