Forum

Author Topic: ... error reading pixel  (Read 2607 times)

JMR

  • Hero Member
  • *****
  • Posts: 502
    • View Profile
... error reading pixel
« on: January 13, 2023, 04:06:54 PM »
What can I do?

[...]
2023-01-13 13:55:52   2.83981/4~71% avg groups per camera
2023-01-13 13:55:52   146.25/206~70% avg cameras per group
2023-01-13 13:55:52   0% leaves avg camera intersects in group
2023-01-13 13:55:52   1% big leaves avg camera intersects in group
2023-01-13 13:55:52   29% of leaves are big
2023-01-13 13:55:52   100% of voxels in group are from big leaves
2023-01-13 13:55:52 saved 4 groups (0.03125 KB) for 344 leaves
2023-01-13 13:55:52 saved 2.28516 KB of affected cameras and 0.804688 KB of exclusive cameras for all leaves
2023-01-13 13:55:52 Scheduling octree 344 leaves hist initing in 4 groups (86 avg leaves per group)
2023-01-13 13:55:52 Initing hists in leaves group #1/4: [0; 60)...
2023-01-13 13:56:02 total cubes: 105221949 cubes, 1605.56 MB, 163.966 MB/s
2023-01-13 13:56:02 Data: 2408.34 MB hists + 0 MB codes, 117.297 MB pyramid
2023-01-13 13:56:02 Found 2 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2023-01-13 13:56:03 [GPU 1] Using device: NVIDIA GeForce GTX 1070 Ti, 19 compute units, free memory: 7104/8191 MB, compute capability 6.1
2023-01-13 13:56:03   driver/runtime CUDA: 12000/10010
2023-01-13 13:56:03   max work group size 1024
2023-01-13 13:56:03   max work item sizes [1024, 1024, 64]
2023-01-13 13:56:03 [GPU 2] Using device: NVIDIA GeForce GTX 1070 Ti, 19 compute units, free memory: 7197/8191 MB, compute capability 6.1
2023-01-13 13:56:03   driver/runtime CUDA: 12000/10010
2023-01-13 13:56:03   max work group size 1024
2023-01-13 13:56:03   max work item sizes [1024, 1024, 64]
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.

2023-01-13 13:56:09 [GPU 1] Exception
2023-01-13 13:56:09 [GPU 2] Exception
2023-01-13 13:56:09 Peak memory used: 8.44 GB at 2023-01-13 13:56:06
2023-01-13 13:56:09 deleting all temporary files...
2023-01-13 13:56:10 done in 0.734 s
2023-01-13 13:56:10 Finished processing in 2280.18 sec (exit code 0)
2023-01-13 13:56:10 Error: Can't decompress depth

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14849
    • View Profile
Re: ... error reading pixel
« Reply #1 on: January 13, 2023, 05:00:41 PM »
Hello JMR,

It seems that the depth maps data in the archive or the archive itself has been corrupted. Could happen during the depth maps generation procedure due to GPU driver or RAM issues, for example. Also it may happen if the project.files folder is stored on external or network with unstable connection to the processing machine.
Best regards,
Alexey Pasumansky,
Agisoft LLC

JMR

  • Hero Member
  • *****
  • Posts: 502
    • View Profile
Re: ... error reading pixel
« Reply #2 on: January 13, 2023, 06:58:19 PM »
Hi, Alexey, it happens consistently. New computer, 64gb ram. Sorage is ssd, Ryzen9, dual Gtx 1070ti, up to date Nvidia drivers... and occurs after depth maps are finished while mesh is being built. Will try same proj in my older computer.
regards

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14849
    • View Profile
Re: ... error reading pixel
« Reply #3 on: January 13, 2023, 07:30:10 PM »
Hello JMR,

I would suggest to run Memtest86+ on that computer, where you observe the problem. If any overclocking is applied, it may be also reasonable to disable it.

When running the same project processing on another machine, make sure to rebuild the depth maps, instead of re-using corrupted depth data.
Best regards,
Alexey Pasumansky,
Agisoft LLC