Forum

Author Topic: Error in Build point cloud  (Read 1031 times)

tjsckddhks

  • Newbie
  • *
  • Posts: 6
    • View Profile
Error in Build point cloud
« on: July 13, 2023, 04:29:08 AM »
Hello, 

Yesterday, there was no problem to handle the Metashape.
Today, It shows a error below with warning: Not enough memory.
I already restarted my computer, but I still get the same message.

2023-07-13 10:19:36 BuildPointCloud: quality = High, depth filtering = Mild, PM version, source data = Depth maps, point colors = 1
2023-07-13 10:19:36 Generating depth maps...
2023-07-13 10:19:36 Preparing 3 cameras info...
2023-07-13 10:19:36 cameras data loaded in 0.010388 s
2023-07-13 10:19:36 cameras graph built in 0.00019 s
2023-07-13 10:19:36 filtering neighbors with too low common points, threshold=50...
2023-07-13 10:19:36 avg neighbors before -> after filtering: 2 -> 0 (0% filtered out)
2023-07-13 10:19:36 limiting neighbors to 16 best...
2023-07-13 10:19:36 avg neighbors before -> after filtering: 2 -> 0 (0% filtered out)
2023-07-13 10:19:36 neighbors number min/1%/10%/median/90%/99%/max: 2, 2, 2, median=2, 2, 2, 2
2023-07-13 10:19:36 cameras info prepared in 0.011531 s
2023-07-13 10:19:36 saved cameras info in 0.009632
2023-07-13 10:19:36 Partitioning 3 cameras...
2023-07-13 10:19:36 number of mini clusters: 1
2023-07-13 10:19:36 1 groups: avg_ref=3 avg_neighb=0 total_io=100%
2023-07-13 10:19:36 max_ref=3 max_neighb=0 max_total=3
2023-07-13 10:19:36 cameras partitioned in 0.000114 s
2023-07-13 10:19:36 saved depth map partition in 0.002725 sec
2023-07-13 10:19:36 loaded cameras info in 0.000333
2023-07-13 10:19:36 loaded depth map partition in 1.7e-05 sec
2023-07-13 10:19:36 already partitioned (3<=50 ref cameras, 0<=200 neighb cameras)
2023-07-13 10:19:36 group 1/1: preparing 3 cameras images...
2023-07-13 10:19:36 tie points loaded in 0.00019 s
2023-07-13 10:19:36 Can't load OpenCL library
2023-07-13 10:19:36 Found 0 GPUs in 0.000643 sec (CUDA: 5e-06 sec, OpenCL: 0.000611 sec)
2023-07-13 10:19:36 Using device: CPU Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz (using 48/48)
2023-07-13 10:19:37 Finished processing in 0.646626 sec (exit code 0)
2023-07-13 10:19:37 Error: std::bad_alloc

How to fix this one?

Thanks