Open m3d opened 3 years ago
Je to divne, protoze podle logu hlasil pozice i mu chodilo echo pres radio (self echo):
python -m osgar.logger logs\aws\P2\ver78mdbread2p2\A\aws-ver78mdbread2p2-A600L.log --stream radio.breadcrumb
0:06:15.545838 32 [29.786302739039666, 3.570442651703712, 0.7107453829422778]
0:10:17.020574 32 [59.51430372506629, -0.33122404231637037, -0.5736284562513388]
0:14:20.114875 32 [88.90740964719565, 1.9813630680172913, -6.114361478664414]
0:18:10.696877 32 [117.4188990950508, 1.2783841867040777, -15.448032130770715]
0:21:37.756769 32 [146.457908742016, 0.9696952276401734, -22.993244741465414]
0:24:35.187797 32 [175.93844402698713, 2.862592383470917, -17.680553681864225]
python -m osgar.logger ogs\aws\P2\ver78mdbread2p2\A\aws-ver78mdbread2p2-A600L.log --stream breadcrumbs.location
0:06:15.527154 41 [29.786302739039666, 3.570442651703712, 0.7107453829422778]
0:10:16.841675 41 [59.51430372506629, -0.33122404231637037, -0.5736284562513388]
0:14:19.892094 41 [88.90740964719565, 1.9813630680172913, -6.114361478664414]
0:18:10.477450 41 [117.4188990950508, 1.2783841867040777, -15.448032130770715]
0:21:37.734803 41 [146.457908742016, 0.9696952276401734, -22.993244741465414]
0:24:35.165088 41 [175.93844402698713, 2.862592383470917, -17.680553681864225]
and the deploy was called:
python -m osgar.logger logs\aws\P2\ver78mdbread2p2\A\aws-ver78mdbread2p2-A600L.log --stream breadcrumbs.deploy
0:06:15.526878 40 []
0:10:16.841344 40 []
0:14:19.891791 40 []
0:18:10.476957 40 []
0:21:37.734385 40 []
0:24:35.164666 40 []
podle event logu vyhazoval pouze B, jedina zprava od A
65.340000000 INFO /cloudsim2osgar [cloudsim2osgar.py:117(main.__init__)] [topics: /clock, /rosout] freya 2 (with comms beacons)
i A byl spravne detekovany jako config2
I v ROS logu je info, ze vysila
101.284000000 INFO /A600L_proxy [/osgar-ws/src/osgar/subt/ros/proxy/ros_proxy_node.cc:585(receiveZmqThread)] [topics: /rosout, /A600L/cmd_vel, /statistics] BROADCAST RECEIVED {'breadcrumb': [29.786302739039666, 3.570442651703712, 0.7107453829422778]}
ale chybi hlaska:
100.432000000 INFO /A600L/ros_ign_bridge_breadcrumbs [/tmp/ros-ign-bridge-release/include/ros_ign_bridge/factory.hpp:137(Factory<ROS_T, IGN_T>::ros_callback)] [topics: /rosout] Passing message from ROS std_msgs/Empty to Ignition ignition.msgs.Empty (showing msg only once per type
kterou pozoruji v predeslem behu ... ignore, je to i v tomto behu:
101.280000000 INFO /A600L/ros_ign_bridge_breadcrumbs [/tmp/ros-ign-bridge-release/include/ros_ign_bridge/factory.hpp:137(Factory<ROS_T, IGN_T>::ros_callback)] [topics: /rosout] Passing message from ROS std_msgs/Empty to Ignition ignition.msgs.Empty (showing msg only once per type
Jaký stav analýzy? Mám tady taky na něco koukat?
jestli mame nejaky zpusob jak zjistit, ze service na deploy byl OK, tak mozna na to ... ale dalsi beh vypada OK (oba roboti vyhazuji). Take jsem napsal organizatorum, jestli se tam ted nemota komunikace s deploy, protoze to je ted temer soubezne.
po dohodÄ› jsme upravili výpisy v cloudsim2osgar tak, aby byla pÅ™ÃsluÅ¡ná informace v rosout logu
stejný problém se objevil u #22, kde jsem byl schopen problém dotrasovat až do cloudsimu, tj. tohle asi můžeme zavÅ™Ãt.
2x Freyja, s omezenim na vyhozeni po 30m a vzajemnou komunikaci. Limit 6 breadcrumbs per robot ... ale vypada to, ze to vubec nefunguje a vubec nic nevyhodil 👎