You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start converting ...
Traceback (most recent call last):
File "tools/create_data.py", line 327, in <module>
waymo_data_prep(
File "tools/create_data.py", line 204, in waymo_data_prep
converter.convert()
File "/mnt/0c39e9c4-f324-420d-a1e9-f20a41d147a8/personal_repos/LoopX/mmdetection3d/tools/dataset_converters/waymo_converter.py", line 112, in convert
mmengine.track_parallel_progress(self.convert_one, range(len(self)),
File "/home/s95huang/anaconda3/envs/openmmlab/lib/python3.8/site-packages/mmengine/utils/progressbar.py", line 191, in track_parallel_progress
pool = init_pool(nproc, initializer, initargs)
File "/home/s95huang/anaconda3/envs/openmmlab/lib/python3.8/site-packages/mmengine/utils/progressbar.py", line 133, in init_pool
return Pool(process_num)
File "/home/s95huang/anaconda3/envs/openmmlab/lib/python3.8/multiprocessing/context.py", line 119, in Pool
return Pool(processes, initializer, initargs, maxtasksperchild,
File "/home/s95huang/anaconda3/envs/openmmlab/lib/python3.8/multiprocessing/pool.py", line 205, in __init__
raise ValueError("Number of processes must be at least 1")
ValueError: Number of processes must be at least 1
with worker set to 1/8/10/16 on this i7-13700 or 16/32 on AMD threadripper 2950 using mmdetection3d v1.1, 1.3 and main dev-1.x,
The waymo-kitti conversion got stuck at
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] 150/150, 0.0 task/s, elapsed: 4830s, ETA: 0s
Finished ...
Start converting ...
completed: 0, elapsed: 0s
Finished ...
created txt files indicating what to collect in ['training', 'validation', 'testing', 'testing_3d_camera_only_detection']
Generate info. this may take several minutes.
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] 158081/158081, 75.6 task/s, elapsed: 2090s, ETA: 0s
[ ] 0/158081, elapsed: 0s, ETA:
for days and the system monitor indicates there is no disk read/write with very low CPU usage.
It appears the code is stuck when working on
mmengine.dump
Additional information
If needed,
the waymo dataset is v 1.4.1
waymo toolkit is 2.6, 1.4.9
I also tried the solution in #2371 and #2705 and the error is still there.
This solution #2364 won't work as GPU error out of memory.
I am currentyly testing the conversion in AWS and hope it might work~
The text was updated successfully, but these errors were encountered:
I used AWS EC2 G5 instance with 32 CPU etc.
The same problem occurs and the SSH connection is dropped after 10 min due to no activity.
I changed limit to 10 hours and the monitoring shows very low usage for 10 hr.
Prerequisite
Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
main branch https://github.com/open-mmlab/mmdetection3d
Environment
sys.platform: linux
Python: 3.8.18 | packaged by conda-forge | (default, Oct 10 2023, 15:44:36) [GCC 12.3.0]
CUDA available: True
numpy_random_seed: 2147483648
GPU 0: NVIDIA GeForce RTX 3090
CUDA_HOME: /usr/local/cuda-11.4
NVCC: Cuda compilation tools, release 11.4, V11.4.152
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
PyTorch: 1.12.0+cu116
PyTorch compiling details: PyTorch built with:
TorchVision: 0.13.0+cu116
OpenCV: 4.5.5
MMEngine: 0.9.0
MMDetection: 3.0.0
MMDetection3D: 1.1.0+4ff1361
spconv2.0: True
Reproduces the problem - code sample
'''
python tools/create_data.py waymo --root-path ./data/waymo/ --out-dir ./data/waymo/ --workers 0 --extra-tag waymo
'''
Reproduces the problem - command or script
'''
python tools/create_data.py waymo --root-path ./data/waymo/ --out-dir ./data/waymo/ --workers 0 --extra-tag waymo
'''
Reproduces the problem - error message
With --workers 0, I have
with worker set to 1/8/10/16 on this i7-13700 or 16/32 on AMD threadripper 2950 using mmdetection3d v1.1, 1.3 and main dev-1.x,
The waymo-kitti conversion got stuck at
for days and the system monitor indicates there is no disk read/write with very low CPU usage.
It appears the code is stuck when working on
Additional information
If needed,
the waymo dataset is v 1.4.1
waymo toolkit is 2.6, 1.4.9
I also tried the solution in #2371 and #2705 and the error is still there.
This solution #2364 won't work as GPU error out of memory.
I am currentyly testing the conversion in AWS and hope it might work~
The text was updated successfully, but these errors were encountered: