Problem to switch from the Gitlab code to the Github code about uav_core HOT 1 CLOSED

Hey Pedro,

yes, we have the old stuff backed up, however, there is nothing "more" there than there it is here on Github. The Github repositories contain our Gitlab history. Actually, our last commit of the uav_core repo on Gitlab is e4e56c2, which you can find here on Github as well. I would recommend updating your code to work with the new version since it is more "future proof". It is unlikely that the pre-open-sourcing version from Gitlab will work with a fresh installation of your OS (outside dependencies such as Mavros often cause us troubles). I bet the automatic installation would not work now either. Moreover:

• we can't give you support for the old version,
• the open-source version is documented better (the old had hardly any documentation),
• the open-source version got a lot of problems and quirks figured out (we got a lot of time for it during the quarantine),
• the new open-source version got a lot of time invested in just to be easier to read and understand, thus, it is much easier to borrow code from it. It is not universal, there are still some botched pieces here, but much less than before.

There are some changes that happened during the open-sourcing era, that might influence normal people:

• the way how we send the desired trajectory to the system: the message type changed to this topic, service, the topic/service address is control_manager/trajectory_reference
• our paramLoader and other tools from mrs_lib slightly changed API, see https://github.com/ctu-mrs/mrs_lib

If you are lost with some particular stuff, don't hesitate to contact us here with the problem, we can suggest what to do. Also, feel free to check our own code for inspiration on how we do stuff in the new system.

Sincerely,
Tomas

from uav_core.