It's not necessarily an issue that the designer doesn't provide the connect command as an option in the list of camera commands but I just wanted to make this note. The execution code will only connect to the camera automatically if the rig yaml's camera config section includes the IP, the port, AND the path to the camera's config file. If any one of those are missing, the connection will not be made automatically, and the user has to connect manually using the connect command in the yaml file so they can provide the missing input. If we want to ensure those values are always in the rig file and not being provided in the experiment yaml, that's fine, but just wanted to make sure that requirement is known. Having the connect command available would also allow the user to connect manually and override the input values in the rig yaml if they wanted to, but that ability may not be needed.
It's not necessarily an issue that the designer doesn't provide the connect command as an option in the list of camera commands but I just wanted to make this note. The execution code will only connect to the camera automatically if the rig yaml's camera config section includes the IP, the port, AND the path to the camera's config file. If any one of those are missing, the connection will not be made automatically, and the user has to connect manually using the connect command in the yaml file so they can provide the missing input. If we want to ensure those values are always in the rig file and not being provided in the experiment yaml, that's fine, but just wanted to make sure that requirement is known. Having the connect command available would also allow the user to connect manually and override the input values in the rig yaml if they wanted to, but that ability may not be needed.