Open kaarmu opened 8 months ago
@frankjjiang what do you think of this?
This is a good initiative! I like the proposal. Especially good to trim down the svea_sensors
launch files, since they are very very bloated with legacy arguments+parameters.
Some ideas of arguments to bubble up to the top level launch:
<?xml version="1.0"?>
<launch>
<!-- My Very Cool Experiment That Is Using AI, ML, Big Data, IoT, ... -->
<include file="$(find svea_core)/launch/svea.launch">
<arg name="is_outdoor" ... />
<arg name="map_file" ... />
<arg name="is_sim" ... />
<!-- other svea.launch arguments... -->
</include>
<node name="cool_node" pkg="awesome_project" type="cool_node.py">
<!-- experiment parameters... -->
</node>
</launch>
Similar cleaning should also be done for other related SVEA repos, e.g. svea_vision
.
It is time to do some spring-cleaning of the launch files again.
To resolve this issue, I would like to see two PRs for
svea_sensors
andsvea_core
. Currently, there are many outdated and redundant launch files insvea_sensors
. It would be good to streamline the things we are using and removing the things we are not using. Furthermore, to improve user experience it would be nice to have a main launch file insvea_core
, much like whatlocalize.launch
is forsvea_sensors
. This launch file, maybe we can call itsvea.launch
, should calllocalize.launch
,foxglove_bridge.launch
,serial_node
and more. IMO, the aim should be that for a typical experiment/demo there is only this:After the discussions we have had, I suggest that:
svea_sensors
PR, @Annika-wyt looks into said improvementssvea_core
PR, @sulthansf creates our firstsvea.launch
We should also think about abstraction levels, e.g. where things like
map_server
should be called (svea.launch
orlocalize.launch
?).