Side note regarding robot_locked:
Curiously, VRX doesn't have this parameter in sandisland.launch, which the competition Docker runs. I think this might be a mistake that needs to be fixed in VRX too?
All the task launch files in VRX have robot_locked:=true by default, so I'm assuming the robot needs to be locked in the beginning.
All the VRX scoring plugins unlock the robot first, and print two red lines of not being able to unlock during the competition evaluation.
Does the robot need to be locked in the beginning? If so, vrx and vrx-docker need to be fixed too to use that parameter.
robot_lockedparameter tomarina.launchSide note regarding
robot_locked: Curiously, VRX doesn't have this parameter insandisland.launch, which the competition Docker runs. I think this might be a mistake that needs to be fixed in VRX too? All the task launch files in VRX haverobot_locked:=trueby default, so I'm assuming the robot needs to be locked in the beginning. All the VRX scoring plugins unlock the robot first, and print two red lines of not being able to unlock during the competition evaluation. Does the robot need to be locked in the beginning? If so,vrxandvrx-dockerneed to be fixed too to use that parameter.