- start vio.sh in mrse package
- start md_start.sh inside scripts/simulation folder and wait for the object_tracker_simple get better
- inside vio.sh simulation tmux, go to the estimator with UWB in the name, start estimator with uwb
- start plotjugler rosrun plotjugler and import the xml file
- start in sequence by sufix, vio.sh simulation tmux
- watch in plotjugler
- start vio.sh in mrse package
- inside vio.sh simulation tmux, go to the estimator with UWB in the name, start estimator with uwb
- start plotjugler rosrun plotjugler and import the xml file
- start in sequence by sufix, vio.sh simulation tmux
- watch in plotjugler
- start vio.sh in mrse package
- inside vio.sh simulation tmux, go to the estimator with UWB in the name, start estimator with uwb
- start plotjugler
rosrun plotjugler plotjugler
and import the xml filecomparing_same_time.xml
- start the code
python cmds.py
- watch in plotjugler
- start vio.sh in mrse package
- inside vio.sh simulation tmux, go to the estimator and start it
- start plotjugler rosrun plotjugler and import the xml file
- start in sequence by sufix, vio.sh simulation tmux
- watch in plotjugler
-
I think that jiri uses the uvdar error in his favor, to create the lines that in the intersection is the UAV
-
how to implement if I dont have this kinda of information?
-
increase the number of drones and implement a triangulation ? and the UWB?
-
test the vio implementation
- implement all at the same time
- same path for all the drones
- code are running, good performance in spin test (python code)
- still some problems because of not showing in some moments (return nothing)
- verify the implementation if works like before (OK)
- create new branch on mrse and insert the code inside uvdar callback
x2x -to :0 -east
eval "$(ssh-agent -s)"
ssh-add /home/mrs/.ssh/lucasnn
rosnode list
rosnode kill ...
i3-msg workspace $(number 0 .. 9)
xwd -display :0 -root > output.xwd && convert output.xwd output.png
code $folder_name
xdg-open $file_name
pkill -f uvdar_uwb_state_estimator_workspace