Remove rmf_demos_panel (#235)

* Remove rmf_demos_panel

Signed-off-by: Luca Della Vedova <[email protected]>

* Readme for dashboard resources

Signed-off-by: Luca Della Vedova <[email protected]>

* Remove rmf_demos_dashboard_resources

Signed-off-by: Luca Della Vedova <[email protected]>

---------

Signed-off-by: Luca Della Vedova <[email protected]>
Co-authored-by: Yadu <[email protected]>

Author: luca-della-vedova

.github/workflows/build.yaml

@@ -14,10 +14,8 @@ jobs:
         rmf_demos
         rmf_demos_assets
         rmf_demos_bridges
-        rmf_demos_dashboard_resources
         rmf_demos_fleet_adapter
         rmf_demos_gz
         rmf_demos_maps
-        rmf_demos_panel
         rmf_demos_tasks
       dist-matrix: '[{"ros_distribution": "rolling", "ubuntu_distribution": "noble"}]'

README.md

@@ -54,29 +54,6 @@ By specifying `server_uri`, the fleetadapter will update `rmf-web` `api-server`
 * [Campus World](#Campus-World)
 * [Manufacturing & Logistics World](#Manufacturing-&-Logistics-World)
 
-**RMF Panel**
-![](../media/RMF_Panel.png?raw=true)
-
-Click this link: https://open-rmf.github.io/rmf-panel-js/
-
-> For a full-proof web application of Open-RMF, please refer to [rmf-web](https://github.com/open-rmf/rmf-web).
-
-The [RMF panel](https://github.com/open-rmf/rmf-panel-js) is a web based dashboard for interacting with rmf_demos. It allows users to send task requests to RMF and monitor the status of robots and submitted tasks. For more [details](rmf_demos_panel/README.md).
-
-There are two main modes of submitting tasks to Open-RMF via the Panel:
-
-1. Submit a Task: Used to submit a single task.
-2. Submit a List of Tasks: Used to submit a batch of tasks. A `.json` file containing a list of tasks may be loaded via the `Choose file` button. Some example files are found in `rmf_demos_panel/task_lists`.
-
-**LATEST UPDATE: Display Task States**
-
-`task_state_uptates` are now published via websocket. To display task states on `rmf-panel`, specify `server_uri:="ws://localhost:7878"` during ros2 launch. Example:
-```
-ros2 launch rmf_demos_gz office.launch.xml server_uri:="ws://localhost:7878"
-```
-
-This will let Open-RMF (websocket clients) to publish their states to port `7878`. In this case, rmf-panel's `api_simple_server` is the websocket server.
-
 ---
 
 ### Hotel World
@@ -98,15 +75,10 @@ ros2 launch rmf_demos_gz hotel.launch.xml
 ros2 launch rmf_demos_gz hotel.launch.xml
 ```
 
-Here, we will showcase 2 types of Tasks: **Loop** and **Clean**
-
-Open [RMF Panel](https://open-rmf.github.io/rmf-panel-js/) to submit clean or loop requests.
-To submit a **loop task**, select `Loop` from the `Select a request type` dropdown list. Choose desired start and end locations and click submit. Similarly for **Clean task**, select `Clean`, then choose the desired `cleaning zone` from the dropdown list.
-
-Or, dispatch robot via CLI
+Here, we will showcase 2 types of Tasks: **Loop** and **Clean**, you can dispatch them via CLI as follows:
 ```bash
-ros2 run rmf_demos_tasks dispatch_clean -cs clean_lobby --use_sim_time
 ros2 run rmf_demos_tasks dispatch_patrol -p restaurant  L3_master_suite -n 1 --use_sim_time
+ros2 run rmf_demos_tasks dispatch_clean -cs clean_lobby --use_sim_time
 ```
 
 Robots running Clean and Loop Task:
@@ -117,8 +89,6 @@ Robots running Clean and Loop Task:
 To submit a list of scheduled tasks via rmf web panel, load [hotel_tasks.json](https://github.com/open-rmf/rmf_demos/blob/main/rmf_demos_panel/task_lists/hotel_tasks.json),
 or paste the json list to the _Submit a List of Tasks_ section. Next, click on submit.
 
-> Tip: To speedup simulation on gazebo, user can run `gz physics -s 0.01` on a separate terminal after launching the world. Use with care!
-
 ---
 
 ### Office World
@@ -134,20 +104,17 @@ ros2 launch rmf_demos_gz office.launch.xml
 
 Now we will showcase 2 types of Tasks: **Delivery** and **Loop**
 
-To send task requests, open rmf_demos web panel: https://open-rmf.github.io/rmf-panel-js/
-
 ![](../media/delivery_request.gif?raw=true)
 
-To submit a **delivery task**, select `Delivery` from the `Select a request type` dropdown list. Next, select `coke` from the `Select delivery task` list. Choose an desired start time for task and click submit.
-
-Or, submit a task via CLI:
+You can request the robot to deliver a can of coke from `pantry` to `hardware_2` through the following:
 ```bash
-ros2 run rmf_demos_tasks dispatch_patrol -p coe lounge -n 3 --use_sim_time
 ros2 run rmf_demos_tasks dispatch_delivery -p pantry -ph coke_dispenser -d hardware_2 -dh coke_ingestor --use_sim_time
 ```
 
-To submit a **loop task**, select `Loop` from the `Select a request type` dropdown list. Choose desired start and end locations and click submit.
-To run a scenario with multiple task requests, load [office_tasks.json](https://github.com/open-rmf/rmf_demos/blob/main/rmf_demos_panel/task_lists/office_tasks.json) from `rmf_demos_panel/task_lists` in the `Submit a list of tasks` section. This should populate the preview window with a list of tasks. Click submit and watch the demonstration unfold.
+You can also request the robot to move back and forth between `coe` and `lounge` through the following:
+```bash
+ros2 run rmf_demos_tasks dispatch_patrol -p coe lounge -n 3 --use_sim_time
+```
 
 ![](../media/loop_request.gif)
 
@@ -170,9 +137,7 @@ source ~/rmf_ws/install/setup.bash
 ros2 launch rmf_demos_gz airport_terminal.launch.xml
 ```
 
-Open [RMF Panel](https://open-rmf.github.io/rmf-panel-js/). Load the [airport_terminal_tasks.json](https://github.com/open-rmf/rmf_demos/blob/main/rmf_demos_panel/task_lists/airport_terminal_tasks.json) list and click submit to begin a collection of loop, delivery and cleaning tasks.
-
-Or, submit `loop`, `delivery` or `clean` task via CLI:
+You can submit `loop`, `delivery` or `clean` task via CLI:
 ```bash
 ros2 run rmf_demos_tasks dispatch_patrol -p s07 n12 -n 3 --use_sim_time
 ros2 run rmf_demos_tasks dispatch_delivery -p mopcart_pickup -ph mopcart_dispenser -d spill -dh mopcart_collector --use_sim_time
@@ -198,8 +163,6 @@ ros2 launch rmf_demos_gz airport_terminal_caddy.launch.xml
 
 ![](../media/caddy.gif)
 
-> Tip: To speedup simulation on gazebo, user can run `gz physics -ps 0.01` on a separate terminal after launching the world. Use with care!
-
 ---
 
 ### Clinic World
@@ -216,9 +179,7 @@ source ~/rmf_ws/install/setup.bash
 ros2 launch rmf_demos_gz clinic.launch.xml
 ```
 
-Open [RMF Panel](https://open-rmf.github.io/rmf-panel-js/). Load the [clinic_tasks.json](https://github.com/open-rmf/rmf_demos/blob/main/rmf_demos_panel/task_lists/clinic_tasks.json) list and click submit to begin a collection of loop and delivery tasks.
-
-Or, submit a task via CLI:
+You can submit tasks via CLI:
 ```bash
 ros2 run rmf_demos_tasks dispatch_patrol -p L1_left_nurse_center L2_right_nurse_center -n 5 --use_sim_time
 ros2 run rmf_demos_tasks dispatch_patrol -p L2_north_counter L1_right_nurse_center -n 5 --use_sim_time

rmf_demos/launch/airport_terminal.launch.xml

@@ -9,7 +9,6 @@
     <arg name="use_sim_time" value="$(var use_sim_time)"/>
     <arg name="viz_config_file" value ="$(find-pkg-share rmf_demos)/include/airport_terminal/airport_terminal.rviz"/>
     <arg name="config_file" value="$(find-pkg-share rmf_demos_maps)/airport_terminal/airport_terminal.building.yaml"/>
-    <arg name="dashboard_config_file" value="$(find-pkg-share rmf_demos_dashboard_resources)/airport_terminal/dashboard_config.json"/>
   </include>
 
   <!-- TinyRobot fleet adapter -->

rmf_demos/launch/clinic.launch.xml

@@ -8,7 +8,6 @@
     <arg name="use_sim_time" value="true"/>
     <arg name="viz_config_file" value ="$(find-pkg-share rmf_demos)/include/clinic/clinic.rviz"/>
     <arg name="config_file" value="$(find-pkg-share rmf_demos_maps)/clinic/clinic.building.yaml"/>
-    <arg name="dashboard_config_file" value="$(find-pkg-share rmf_demos_dashboard_resources)/clinic/dashboard_config.json"/>
   </include>
 
   <!-- DeliveryRobot fleet adapter -->

rmf_demos/launch/common.launch.xml

@@ -5,11 +5,9 @@
   <arg name="use_sim_time" default="false" description="Use the /clock topic for time to sync with simulation"/>
   <arg name="viz_config_file" default="$(find-pkg-share rmf_visualization_schedule)/config/rmf.rviz"/>
   <arg name="config_file" description="Building description file required by rmf_building_map_tools"/>
-  <arg name="dashboard_config_file" default="" description="Path to dashboard config for web rmf panel file"/>
   <arg name="initial_map" default="L1" description="Initial map name for the visualizer"/>
   <arg name="headless" default="false" description="do not launch rviz; launch gazebo in headless mode"/>
   <arg name="bidding_time_window" description="Time window in seconds for task bidding process" default="2.0"/>
-  <arg name="use_rmf_panel" default="true" description="launch web and api server for rmf_demos_panel"/>
   <arg name="use_unique_hex_string_with_task_id" default="true" description="Appends a unique hex string to the task ID"/>
   <arg name="server_uri" default="" description="The URI of the api server to transmit state and task information."/>
 
@@ -63,12 +61,4 @@
       <param name="server_uri" value="$(var server_uri)"/>
     </node>
   </group>
-
-  <group if="$(var use_rmf_panel)">
-    <include file="$(find-pkg-share rmf_demos)/dashboard.launch.xml">
-      <arg name="use_sim_time" value="$(var use_sim_time)"/>
-      <arg name="dashboard_config_file" value ="$(var dashboard_config_file)"/>
-    </include>
-  </group>
-
 </launch>

rmf_demos/launch/dashboard.launch.xml

@@ -9,7 +9,6 @@
     <arg name="use_sim_time" value="$(var use_sim_time)"/>
     <arg name="viz_config_file" value ="$(find-pkg-share rmf_demos)/include/hotel/hotel.rviz"/>
     <arg name="config_file" value="$(find-pkg-share rmf_demos_maps)/hotel/hotel.building.yaml"/>
-    <arg name="dashboard_config_file" value="$(find-pkg-share rmf_demos_dashboard_resources)/hotel/dashboard_config.json"/>
   </include>
 
   <!-- Experimental Lift watchdog service launch, default disable -->

rmf_demos/launch/hotel.launch.xml

@@ -8,7 +8,6 @@
     <arg name="use_sim_time" value="$(var use_sim_time)"/>
     <arg name="viz_config_file" value ="$(find-pkg-share rmf_demos)/include/office/office.rviz"/>
     <arg name="config_file" value="$(find-pkg-share rmf_demos_maps)/office/office.building.yaml"/>
-    <arg name="dashboard_config_file" value="$(find-pkg-share rmf_demos_dashboard_resources)/office/dashboard_config.json"/>
   </include>
 
   <!-- TinyRobot fleet adapter -->

rmf_demos/launch/office.launch.xml

@@ -8,7 +8,6 @@
     <arg name="use_sim_time" value="$(var use_sim_time)"/>
     <arg name="viz_config_file" value ="$(find-pkg-share rmf_demos)/include/office/office.rviz"/>
     <arg name="config_file" value="$(find-pkg-share rmf_demos_maps)/office/office.building.yaml"/>
-    <arg name="dashboard_config_file" value="$(find-pkg-share rmf_demos_dashboard_resources)/office/dashboard_config.json"/>
   </include>
 
   <group>

rmf_demos/launch/office_mock_traffic_light.launch.xml

@@ -21,7 +21,6 @@
 
   <exec_depend>rmf_demos_assets</exec_depend>
   <exec_depend>rmf_demos_tasks</exec_depend>
-  <exec_depend>rmf_demos_panel</exec_depend>
   <exec_depend>rmf_demos_fleet_adapter</exec_depend>
   <exec_depend>rviz2</exec_depend>