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
(process_with_single_worker pid=11508) read from disk
(process_with_single_worker pid=33896) read from disk
0%| | 0/1 [00:00<?, ?it/s]
0%| | 0/1 [00:00<?, ?it/s]
0%| | 0/1 [00:00<?, ?it/s]
(process_with_single_worker pid=17168) read from disk
0%| | 0/1 [00:00<?, ?it/s]
(process_with_single_worker pid=6860) read from disk
(process_with_single_worker pid=33896) scene0000_01: read frame 0/60
(process_with_single_worker pid=11508) scene0000_00: read frame 0/56
(process_with_single_worker pid=6860) scene0000_02: read frame 0/62
(process_with_single_worker pid=17168) scene0002_00: read frame 0/52
(process_with_single_worker pid=6860)
(process_with_single_worker pid=11508)
(process_with_single_worker pid=33896)
(process_with_single_worker pid=17168)
(process_with_single_worker pid=11508) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=11508) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=17168) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=17168) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=6860) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=6860) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=33896) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=33896) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=11508) *** SIGABRT received at time=1699517065 ***
(process_with_single_worker pid=11508) @ 00007FF8BEB268D3 (unknown) (unknown)
(process_with_single_worker pid=11508) @ 00007FF8BEB06A1C (unknown) (unknown)
(process_with_single_worker pid=11508) @ 00007FF8BEB25D2D (unknown) (unknown)
(process_with_single_worker pid=11508) @ 00007FF8BEB12515 (unknown) (unknown)
(process_with_single_worker pid=11508) [*** LOG ERROR #1 ***] [2023-11-09 16:04:25] [ray_log_sink] {wincolor_sink: write_to_file_ failed. GetLastError(): 6}
(process_with_single_worker pid=11508) Fatal Python error: Aborted
(process_with_single_worker pid=11508)
(process_with_single_worker pid=11508) Stack (most recent call first):
(process_with_single_worker pid=11508) File "<array_function internals>", line 200 in dot
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\fusion.py", line 353 in rigid_transform
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\fusion.py", line 370 in get_view_frustum
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\generate_gt.py", line 67 in save_tsdf_full
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\generate_gt.py", line 226 in process_with_single_worker
(process_with_single_worker pid=11508) File "C:\Users\Ruby\anaconda3\envs\deep_py39\lib\site-packages\ray_private\worker.py", line 772 in main_loop
(process_with_single_worker pid=11508) File "C:\Users\Ruby\anaconda3\envs\deep_py39\lib\site-packages\ray_private\workers\default_worker.py", line 226 in
what mean of this error? how to solve this problem?
The text was updated successfully, but these errors were encountered:
(process_with_single_worker pid=11508) read from disk
(process_with_single_worker pid=33896) read from disk
0%| | 0/1 [00:00<?, ?it/s]
0%| | 0/1 [00:00<?, ?it/s]
0%| | 0/1 [00:00<?, ?it/s]
(process_with_single_worker pid=17168) read from disk
0%| | 0/1 [00:00<?, ?it/s]
(process_with_single_worker pid=6860) read from disk
(process_with_single_worker pid=33896) scene0000_01: read frame 0/60
(process_with_single_worker pid=11508) scene0000_00: read frame 0/56
(process_with_single_worker pid=6860) scene0000_02: read frame 0/62
(process_with_single_worker pid=17168) scene0002_00: read frame 0/52
(process_with_single_worker pid=6860)
(process_with_single_worker pid=11508)
(process_with_single_worker pid=33896)
(process_with_single_worker pid=17168)
(process_with_single_worker pid=11508) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=11508) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=17168) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=17168) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=6860) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=6860) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=33896) OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
(process_with_single_worker pid=33896) OMP: Hint This means that multiple copies of the OpenMP runtime have been linked into the program. That is dangerous, since it can degrade performance or cause incorrect results. The best thing to do is to ensure that only a single OpenMP runtime is linked into the process, e.g. by avoiding static linking of the OpenMP runtime in any library. As an unsafe, unsupported, undocumented workaround you can set the environment variable KMP_DUPLICATE_LIB_OK=TRUE to allow the program to continue to execute, but that may cause crashes or silently produce incorrect results. For more information, please see http://www.intel.com/software/products/support/.
(process_with_single_worker pid=11508) *** SIGABRT received at time=1699517065 ***
(process_with_single_worker pid=11508) @ 00007FF8BEB268D3 (unknown) (unknown)
(process_with_single_worker pid=11508) @ 00007FF8BEB06A1C (unknown) (unknown)
(process_with_single_worker pid=11508) @ 00007FF8BEB25D2D (unknown) (unknown)
(process_with_single_worker pid=11508) @ 00007FF8BEB12515 (unknown) (unknown)
(process_with_single_worker pid=11508) [*** LOG ERROR #1 ***] [2023-11-09 16:04:25] [ray_log_sink] {wincolor_sink: write_to_file_ failed. GetLastError(): 6}
(process_with_single_worker pid=11508) Fatal Python error: Aborted
(process_with_single_worker pid=11508)
(process_with_single_worker pid=11508) Stack (most recent call first):
(process_with_single_worker pid=11508) File "<array_function internals>", line 200 in dot
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\fusion.py", line 353 in rigid_transform
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\fusion.py", line 370 in get_view_frustum
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\generate_gt.py", line 67 in save_tsdf_full
(process_with_single_worker pid=11508) File "C:\Users\Ruby\Desktop\NeuralRecon-master\tools\tsdf_fusion\generate_gt.py", line 226 in process_with_single_worker
(process_with_single_worker pid=11508) File "C:\Users\Ruby\anaconda3\envs\deep_py39\lib\site-packages\ray_private\worker.py", line 772 in main_loop
(process_with_single_worker pid=11508) File "C:\Users\Ruby\anaconda3\envs\deep_py39\lib\site-packages\ray_private\workers\default_worker.py", line 226 in
what mean of this error? how to solve this problem?
The text was updated successfully, but these errors were encountered: