Open khaep opened 1 year ago
Thanks for testing!
The fre22_task_mapping
worlds needs dandelion models. These were not open-source and only distributed among the competitors of last years event. Therefore, you cannot build these. Probably this should be clarified in the readme somewhere.
The IndexError
only happens sometimes if I am correct. Rerunning ros2 run virtual_maize_field generate_world fre21_task_1_fast
should work.
Furthermore, there was an error in the ROS2 code for generating ros2 run virtual_maize_field generate_world fre21_task_3
. That should be solved when #46 is merged.
Thanks for the information.
Are you planning to merge #46 in foreseeable future to solve the error from ros2 run virtual_maize_field generate_world fre21_task_3
?
I will merge it now, however, the IndexError
still exists. If you encounter it, just rerun the generate_world
script.
Thanks for merging.
After pulling the changes, the AssertionError: Cannot find model nettle!
in fre21_task_3
was fixed as described above.
However, it would be nice to have a fix for the IndexError
. But you are right, running multiple times works so far.
I agree, however I could not find a quick fix yet. I'll leave this issue open till it's resolvd.
Hello all,
in relation to the bugfix mentioned here, I pulled the updates from the ros2 branch, built the package again with
colcon build
and test the other configs from the config folder.Thereby some other issues occured that indicate other bugs. The config files with the corresponding error messages are listed below.
------------------------------fre21_task_1------------------------------
Error message:
------------------------------fre21_task_1_fast------------------------------
Error message:
------------------------------fre21_task_3------------------------------
Error message:
Same error for fre21_task_3_fast.yaml and fre21_task_3_mini.yaml.
------------------------------fre22_task_mapping------------------------------
Error message:
Same error for fre22_task_mapping_fast.yaml and fre22_task_mapping_mini.yaml.
Can you please provide a bug fix or a hint how to solve this problem?
Kind regards