Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
1.9.3.10904
other
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
I’m having issues with using recorder-tui with Ouster’s custom lidar plugin on my host machine. I have successfully modified their plugin to record with 2 OS1-64 sensors simultaneously using the basic recorder tool. However, I need to get recorder-tui working. I will share the script, rig template, and the corresponding terminal output for when I use the script with recorder and for when I use recorder-tui.
Here is the slightly modified Ouster plugin script:
#!/bin/bash
if [ -z “$1” ]
then
echo “Usage: ./multi_record.sh REC_NAME”
echo " Where: "
echo " REC_NAME is the name of the recording, aka the folder where all sensor data is saved"
exit 1
fi
store the current script directory in a variable
SCRIPT_DIR=“$( cd “$( dirname “${BASH_SOURCE[0]}” )” &> /dev/null && pwd )”
DATA_DIR=“$( cd “${SCRIPT_DIR}/…/data” &> /dev/null && pwd )”
PLUGIN_DIR=“$( cd “${SCRIPT_DIR}/…/lib” &> /dev/null && pwd )”
ARCH=$( dpkg --print-architecture )
if [ “${ARCH}” = “amd64” ]; then
PLUGIN_FILE=“libouster_lidar_plugin_x86.so”
else
PLUGIN_FILE=“libouster_lidar_plugin_arm.so”
fi
PLUGIN_PATH=“${PLUGIN_DIR}/${PLUGIN_FILE}”
create a name for the folder to store all recordings in
REC_NAME=$1
create a session_id to use for recording and config filename
SENSOR1=os1_1
SENSOR2=os1_2
#SENSOR3=os2
This must be CUSTOM_EX, placeholder for now
SENSOR_TYPE=“CUSTOM_EX”
Set your host and sensor ip/hostname and ports here
SENSOR_ADDR=os1-99xxxxxxxxxx.local
SENSOR_ADDR2=os1-99xxxxxxxxxx.local
LOG_LEVEL=“WARN”
Lidar / imu ports
SENSOR_LIDAR_PORT=7502
SENSOR_IMU_PORT=7503
SENSOR_LIDAR_PORT2=7504
SENSOR_IMU_PORT2=7505
SENSOR_LIDAR_PORT3=7506
SENSOR_IMU_PORT3=7507
HOST_ADDR=xxx.xxx.xxx.xxx
Replace the parameters in the template file
cat ${SCRIPT_DIR}/ouster_multiLidar_rig_template.json
| sed ‘s||’“${SENSOR1}”‘|g’
| sed ‘s||’“${SENSOR2}”‘|g’
| sed ‘s|<SENSOR_TYPE>|’“${SENSOR_TYPE}”‘|g’
| sed ‘s|<LOG_LEVEL>|’“${LOG_LEVEL}”‘|g’
| sed ‘s|<SENSOR_ADDR>|’“${SENSOR_ADDR}”‘|g’
| sed ‘s|<SENSOR_ADDR2>|’“${SENSOR_ADDR2}”‘|g’
| sed ‘s|<HOST_ADDR>|’“${HOST_ADDR}”‘|g’
| sed ‘s|<PLUGIN_PATH>|’“${PLUGIN_PATH}”‘|g’
| sed ‘s|<DATA_DIR>|’“${DATA_DIR}”‘|g’
| sed ‘s|<LIDAR_PORT>|’“${SENSOR_LIDAR_PORT}”‘|g’
| sed ‘s|<IMU_PORT>|’“${SENSOR_IMU_PORT}”‘|g’
| sed ‘s|<LIDAR_PORT2>|’“${SENSOR_LIDAR_PORT2}”‘|g’
| sed ‘s|<IMU_PORT2>|’“${SENSOR_IMU_PORT2}”‘|g’
“${DATA_DIR}/${SENSOR1}_ouster_multiLidar_rig.json”
cat ${SCRIPT_DIR}/ouster_multiLidar_rig_template.json
| sed ‘s||’“${SENSOR1}”‘|g’
| sed ‘s||’“${SENSOR2}”‘|g’
| sed ‘s|<SENSOR_TYPE>|’“${SENSOR_TYPE}”‘|g’
| sed ‘s|<LOG_LEVEL>|’“${LOG_LEVEL}”‘|g’
| sed ‘s|<SENSOR_ADDR>|’“${SENSOR_ADDR}”‘|g’
| sed ‘s|<SENSOR_ADDR2>|’“${SENSOR_ADDR2}”‘|g’
| sed ‘s|<HOST_ADDR>|’“${HOST_ADDR}”‘|g’
| sed ‘s|<PLUGIN_PATH>|’“${PLUGIN_PATH}”‘|g’
| sed ‘s|<DATA_DIR>|’“${DATA_DIR}”‘|g’
| sed ‘s|<LIDAR_PORT>|’“${SENSOR_LIDAR_PORT}”‘|g’
| sed ‘s|<IMU_PORT>|’“${SENSOR_IMU_PORT}”‘|g’
| sed ‘s|<LIDAR_PORT2>|’“${SENSOR_LIDAR_PORT2}”‘|g’
| sed ‘s|<IMU_PORT2>|’“${SENSOR_IMU_PORT2}”‘|g’
“${DATA_DIR}/${SENSOR2}_ouster_multiLidar_rig.json” # Makes a copy for sensor2
Ensure the session directory exists
mkdir -p “${DATA_DIR}/${REC_NAME}”
#mkdir -p “${DATA_DIR}/${SESSION_ID2}”
DW_CMD=/usr/local/driveworks/tools/capture/recorder
${DW_CMD} “${DATA_DIR}/${SENSOR1}_ouster_multiLidar_rig.json”
recorder puts files in same directory as this script, so move them to REC_NAME directory
mv ${SCRIPT_DIR}/${SENSOR1}.* ${DATA_DIR}/${REC_NAME}
mv ${DATA_DIR}/${SENSOR1}.cfg ${DATA_DIR}/${REC_NAME}/${SENSOR1}.cfg
mv ${DATA_DIR}/${SENSOR1}_ouster_multiLidar_rig.json ${DATA_DIR}/${REC_NAME}/${SENSOR1}_ouster_multiLidar_rig.json
mv ${SCRIPT_DIR}/${SENSOR2}.* ${DATA_DIR}/${REC_NAME}
mv ${DATA_DIR}/${SENSOR2}.cfg ${DATA_DIR}/${REC_NAME}/${SENSOR2}.cfg
mv ${DATA_DIR}/${SENSOR2}_ouster_multiLidar_rig.json ${DATA_DIR}/${REC_NAME}/${SENSOR2}_ouster_multiLidar_rig.json
And here’s the corresponding rig template that gets populated using the script above:
{
“rig”: {
“sensors”: [
{
“name”: “”,
“nominalSensor2Rig_FLU”: {
“roll-pitch-yaw”: [
0.0,
0.0,
0.0
],
“t”: [
0.0,
0.0,
0.0
]
},
“parameter”: “device=<SENSOR_TYPE>,log_level=<LOG_LEVEL>,ip=<SENSOR_ADDR>,dip=<HOST_ADDR>,decoder-path=<PLUGIN_PATH>,data_dir=<DATA_DIR>,session_id=,lidar_port=<LIDAR_PORT>,imu_port=<IMU_PORT>”,
“properties”: null,
“protocol”: “lidar.custom”
},
{
“name”: “”,
“nominalSensor2Rig_FLU”: {
“roll-pitch-yaw”: [
0.0,
0.0,
0.0
],
“t”: [
0.0,
0.0,
0.0
]
},
“parameter”: “device=<SENSOR_TYPE>,log_level=<LOG_LEVEL>,ip=<SENSOR_ADDR2>,dip=<HOST_ADDR>,decoder-path=<PLUGIN_PATH>,data_dir=<DATA_DIR>,session_id=,lidar_port=<LIDAR_PORT2>,imu_port=<IMU_PORT2>”,
“properties”: null,
“protocol”: “lidar.custom”
}
],
“vehicle”: {
“valid”: true,
“value”: {
“COMMENT”: “steeringCoefficient is not validated”,
“axlebaseFront”: 1.582,
“axlebaseRear”: 1.575,
“bumperFront”: 0.912,
“bumperRear”: 1.109,
“centerOfMassToRearAxle”: 1.564,
“frontCorneringStiffness”: 30654.0,
“height”: 1.473,
“inertia”: 1780.8,
“length”: 4.872,
“mass”: 1779.4,
“rearCorneringStiffness”: 36407.0,
“steeringCoefficient”: 14.8,
“wheelDiameter”: 0.673,
“wheelbase”: 2.85,
“width”: 1.852,
“widthWithMirrors”: 2.121
}
}
},
“version”: 2
}
Using this script as is with the “recorder” tool, I get this terminal output and a total of 8 files are stored in the REC_NAME folder that I generate (2 .bin, 2 .bin.seek, 2 .cfg, and 2 rigs), which I can easily use with Ouster’s replay.sh script:
user@name:~/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin$ ./multi_record.sh Test31
[14-08-2024 09:18:12] Platform: Detected Generic x86 Platform
[14-08-2024 09:18:12] TimeSource: monotonic epoch time offset is 1723596207332754
[14-08-2024 09:18:12] Platform: currently selected GPU device discrete ID 0
[14-08-2024 09:18:12] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[14-08-2024 09:18:12] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin/data’: VirtualFileSystem: Failed to mount ‘/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin/data/resources.pak’
[14-08-2024 09:18:12] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/tools/capture/…/…/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/tools/capture/…/…/data/resources.pak’
[14-08-2024 09:18:12] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/data/resources.pak’
[14-08-2024 09:18:12] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/tools/capture/…/…/targets/x86_64-Linux/lib/libdw_base.so.5.10
[14-08-2024 09:18:12] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/x86_64-Linux/lib/libdw_base.so.5.10
[14-08-2024 09:18:12] SDK: No resources(.pak) mounted, some modules will not function properly
[14-08-2024 09:18:12] TimeSource: monotonic epoch time offset is 1723596207332754
[14-08-2024 09:18:12] Initialize DriveWorks SDK v5.10.87
[14-08-2024 09:18:12] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12
[14-08-2024 09:18:12] Rig overlay directory does not exist: /storage/driveworks/data/vehicle_cfg
[14-08-2024 09:18:12] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[14-08-2024 09:18:12] Rig: missing centerOfMassToFrontAxle parameter
[14-08-2024 09:18:12] RigConfiguration: rig file contains old 1d throttle and brake maps. Use rig version 6 with the new throttle and brake maps for a more accurate throttle map.
[14-08-2024 09:18:12] No valid data file found for os1_1 in parameter string: device=CUSTOM_EX,log_level=WARN,ip=os1-99xxxxxxxxxx.local,dip=xxx.xxx.xxx.xxx,decoder-path=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/lib/libouster_lidar_plugin_x86.so,data_dir=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data,session_id=os1_1,lidar_port=7502,imu_port=7503 (using configuration folder /home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data/)
[14-08-2024 09:18:12] No valid data file found for os1_2 in parameter string: device=CUSTOM_EX,log_level=WARN,ip=os1-99xxxxxxxxxx.local,dip=xxx.xxx.xxx.xxx,decoder-path=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/lib/libouster_lidar_plugin_x86.so,data_dir=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data,session_id=os1_2,lidar_port=7504,imu_port=7505 (using configuration folder /home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data/)
[14-08-2024 09:18:12] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[14-08-2024 09:18:12] Rig: missing centerOfMassToFrontAxle parameter
[14-08-2024 09:18:12] RigConfiguration: rig file contains old 1d throttle and brake maps. Use rig version 6 with the new throttle and brake maps for a more accurate throttle map.
sh: 1: cannot create /tmp/tegra_chip_id: Permission denied
[14-08-2024 09:18:12] SensorFactory::createTegraChipDeviceFiles(): Cannot create temporary file in 0x23
sh: 1: cannot create /tmp/tegra_chip_rev: Permission denied
[14-08-2024 09:18:12] SensorFactory::createTegraChipDeviceFiles(): Cannot create temporary file in 0
sh: 1: cannot create /tmp/tegra_cpu: Permission denied
[14-08-2024 09:18:12] SensorFactory::createTegraChipDeviceFiles(): Cannot create temporary file in 0
sh: 1: cannot create /tmp/tegra_platform: Permission denied
[14-08-2024 09:18:12] SensorFactory::createTegraChipDeviceFiles(): Cannot create temporary file in silicon
[14-08-2024 09:18:12] SensorFactory::createSensor() → lidar.custom, device=CUSTOM_EX,log_level=WARN,ip=os1-99xxxxxxxxxx.local,dip=xxx.xxx.xxx.xxx,decoder-path=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/lib/libouster_lidar_plugin_x86.so,data_dir=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data,session_id=os1_1,lidar_port=7502,imu_port=7503
[2024-08-14 09:18:12.801] [ouster::sensor] [info] initializing sensor: os1-99xxxxxxxxxx.local with lidar port/imu port: 7502/7503
[14-08-2024 09:18:16] SensorManager::setRTPriority() couldn’t set sensor thread prio
[14-08-2024 09:18:16] SensorManager::setRTPriority() couldn’t set sensor thread prio
Rig: os1_1_ouster_multiLidar_rig.json NewSink: /dev/null
Press s to start, just to see progress, q to quit.
s
Rig: os1_1_ouster_multiLidar_rig.json NewSink: .
Rig: os1_1_ouster_multiLidar_rig.json Sensor: os1_1 Bytes: 3689464
Rig: os1_1_ouster_multiLidar_rig.json Sensor: os1_2 Bytes: 887824
Rig: os1_1_ouster_multiLidar_rig.json EndOfSensorsInfo
q
rm: remove write-protected regular file ‘/tmp/tegra_chip_id’? ^Crm: remove write-protected regular file ‘/tmp/tegra_chip_rev’? ^Crm: remove write-protected regular file ‘/tmp/tegra_cpu’? ^Crm: remove write-protected regular file ‘/tmp/tegra_platform’? ^Cuser@name:~/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin$ ^C
user@name:~/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin$
Using the multi_record script for recorder-tui requires some slight changes:
recorder:
DW_CMD=/usr/local/driveworks/tools/capture/recorder
${DW_CMD} “${DATA_DIR}/${SENSOR1}_ouster_multiLidar_rig.json”
recorder-tui:
DW_CMD=/usr/local/driveworks/tools/capture/recorder-tui
sudo ${DW_CMD} “${DATA_DIR}/${SENSOR1}_ouster_multiLidar_rig.json”
Using the new script with recorder-tui, I now get this error message:
user@name:~/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin$ ./multi_record.sh Test29
[sudo] password for user:
running recorder-tui with arguments: Namespace(aes_key=None, aes_key_encrypted=None, backend=False, bbr=False, description=‘’, disable_encryption=True, enable_encryption=False, lane_id=None, log_dir_path=‘/tmp’, login_id=None, no_mount_check=False, no_sudo=False, non_interaction=False, remote_dw_path=‘’, rig=‘/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data/os1_1_ouster_multiLidar_rig.json’, route=None, rsa_key=‘/home/nvidia/.ssh/recorder-aiinfra.pem’, rsa_key_md5=None, skip_init_input=False, tag=‘NONE’)
[14-08-2024 09:17:20] SDK: No resources(.pak) mounted from ‘/usr/local/driveworks-5.10/data’. Please adjust path or some modules won’t function properly.
Copying rigs and setup code for local…
Platform setup for local…
os1_1_ouster_multiLidar_rig.json: Backend abruptly exited in waitForRecorderToStart
Cleanup started …
Waiting (timeout=30s) for child process 1/1 to exit cleanly…
Cleaning up sensor initializers …
Performing platform recorder cleanup, if found …
Errors detected during recording
First 100 lines of std error log:
/usr/local/driveworks-5.10/tools/capture/recorder-tui:1296: SyntaxWarning: “is” with a literal. Did you mean “==”?
if hostname is “local”:
/usr/local/driveworks-5.10/tools/capture/recorder-tui:1310: SyntaxWarning: “is not” with a literal. Did you mean “!=”?
if hostname is not “local”:
[14-08-2024 09:17:20] Platform: Detected Generic x86 Platform
[14-08-2024 09:17:20] TimeSource: monotonic epoch time offset is 1723596207332754
[14-08-2024 09:17:20] Platform: currently selected GPU device discrete ID 0
[14-08-2024 09:17:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘./resources’: VirtualFileSystem: Failed to mount ‘./resources/resources.pak’
[14-08-2024 09:17:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/tmp/recorder-43313/data’: VirtualFileSystem: Failed to mount ‘/tmp/recorder-43313/data/resources.pak’
[14-08-2024 09:17:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/tools/capture/…/…/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/tools/capture/…/…/data/resources.pak’
[14-08-2024 09:17:20] Context::mountResourceCandidateDataPath resource FAILED to mount from ‘/usr/local/driveworks-5.10/data’: VirtualFileSystem: Failed to mount ‘/usr/local/driveworks-5.10/data/resources.pak’
[14-08-2024 09:17:20] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/tools/capture/…/…/targets/x86_64-Linux/lib/libdw_base.so.5.10
[14-08-2024 09:17:20] Context::findResourcesPackageInPathWalk: Could not find ./resources/resources.pak in upto 7 parent directories from /usr/local/driveworks-5.10/targets/x86_64-Linux/lib/libdw_base.so.5.10
[14-08-2024 09:17:20] SDK: No resources(.pak) mounted, some modules will not function properly
[14-08-2024 09:17:21] TimeSource: monotonic epoch time offset is 1723596207332755
[14-08-2024 09:17:21] Initialize DriveWorks SDK v5.10.87
[14-08-2024 09:17:21] Release build with GNU 9.3.0 from buildbrain-branch-0-g9a5b4670e12
[14-08-2024 09:17:21] Rig overlay directory does not exist: /storage/driveworks/data/vehicle_cfg
[14-08-2024 09:17:21] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[14-08-2024 09:17:21] No valid data file found for os1_1 in parameter string: device=CUSTOM_EX,log_level=WARN,ip=os1-99xxxxxxxxxx.local,dip=xxx.xxx.xxx.xxx,decoder-path=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/lib/libouster_lidar_plugin_x86.so,data_dir=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data,session_id=os1_1,lidar_port=7502,imu_port=7503 (using configuration folder /tmp/recorder-43313/)
[14-08-2024 09:17:21] No valid data file found for os1_2 in parameter string: device=CUSTOM_EX,log_level=WARN,ip=os1-99xxxxxxxxxx.local,dip=xxx.xxx.xxx.xxx,decoder-path=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/lib/libouster_lidar_plugin_x86.so,data_dir=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data,session_id=os1_2,lidar_port=7504,imu_port=7505 (using configuration folder /tmp/recorder-43313/)
[14-08-2024 09:17:21] rig::DatabaseOverlayer: Failed to open a file ‘/tmp/car_vin’ - file likely does not exist - skipping overlay
[14-08-2024 09:17:21] SensorFactory::createSensor() → lidar.custom, device=CUSTOM_EX,log_level=WARN,ip=os1-99xxxxxxxxxx.local,dip=xxx.xxx.xxx.xxx,decoder-path=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/lib/libouster_lidar_plugin_x86.so,data_dir=/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data,session_id=os1_1,lidar_port=7502,imu_port=7503
Traceback (most recent call last):
File “/usr/local/driveworks-5.10/tools/capture/recorder-tui”, line 854, in
printMountsInfo(mntInfos, sensorsInfo, rig, rigmnt, usermnt)
File “/usr/local/driveworks-5.10/tools/capture/recorder-tui”, line 364, in printMountsInfo
storage = mnts if mnts else [infos[0][0]]
IndexError: list index out of range
First 100 lines of std out log:
running recorder-tui with arguments: Namespace(aes_key=None, aes_key_encrypted=None, backend=True, bbr=False, description=‘’, disable_encryption=True, enable_encryption=False, lane_id=None, log_dir_path=‘/tmp’, login_id=None, no_mount_check=False, no_sudo=False, non_interaction=False, remote_dw_path=‘’, rig=‘/tmp/recorder-43313/os1_1_ouster_multiLidar_rig.json’, route=None, rsa_key=‘/home/nvidia/.ssh/recorder-aiinfra.pem’, rsa_key_md5=None, skip_init_input=False, tag=‘NONE’)
Rig: os1_1_ouster_multiLidar_rig.json recorder-tui: started
[2024-08-14 09:17:21.078] [ouster::sensor] [info] initializing sensor: os1-99xxxxxxxxxx.local with lidar port/imu port: 7502/7503
Rig: os1_2_ouster_multiLidar_rig.json CurrentMount:
When reporting bugs, please attach full log and files /tmp/recorder-tui-43313/.log and /tmp/recorder-43313/.log
WARNING: Forcibly exited. Some data might have been lost!
WARNING: Use q to exit gracefully, next time.
mv: cannot stat ‘/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin/os1_1.': No such file or directory
mv: cannot stat ‘/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/data/os1_1.cfg’: No such file or directory
mv: cannot stat '/home/user/Downloads/ouster-driveworks-dist-5.10-x86-arm64/x86/bin/os1_2.’: No such file or directory
Summary
This attempt generates only 4 files, 2 .cfg files with locked permissions (probably due to sudo) and 2 rig files which get populated correctly. Considering that both output logs are similar, my suspicion lies with the following snippets from the recorder-tui output as it’s the only output that show up in red:
[14-08-2024 09:17:20] SDK: No resources(.pak) mounted from ‘/usr/local/driveworks-5.10/data’. Please adjust path or some modules won’t function properly.
This is particularly strange since recorder also mentions that it doesn’t have a resources.pak file to work with yet it works just fine.
Also, this line is worrisome:
os1_1_ouster_multiLidar_rig.json: Backend abruptly exited in waitForRecorderToStart
Any suggestions would be greatly appreciated!