Select to view content in your preferred language

Ortho Mapping defaults to CPU processing

79
0
Friday
Labels (3)
motorcycleparking
New Contributor

When processing drone imagery, our system defaults to using the CPU for generating an Orthomosaic in the Ortho Product Wizard despite adjusting the environment to a parallel processing factor of 100% and the Processor Type to GPU (we have two on our machine, so we set the correct image processing GPU to ID 0).

This has never been a problem for us before the most recent update. The GPU we have is a NVIDIA T1000, which should have high enough processing capabilities, and has successfully created orthomosaics in the past. The CPU has been able to process imagery, but it takes about 4 times as long as the GPU.

0 Kudos
0 Replies