Failing to process data

PIX4Dmapper PIX4Dmapper Questions/Troubleshooting
1

Hi,

I am having trouble processing a project. I am experiencing errors when going through steps 2 and 3. Is this an issue with not enough RAM in my machine? (I have 16GB)

Here’s the end part of the log:

…
Processing: Group group121, 2 cluster(s) processed, 87951044 points
Processing: Generating tiles
[Error]: Generating tiles failed!
[Error]: >>>Generating tiles<<< failed with error (failed to run a step!)!
[Error]: >>>Generating tiles<<< failed with error (failed to run a step!)!
[Error]: Processing group group121 failed!
[Error]: >>>Processing group group121<<< failed with error (failed to run a step!)!
[Error]: >>>Processing group group121<<< failed with error (failed to run a step!)!
[Error]: Dense Processing failed!
[Error]: >>>Dense Processing<<< failed with error (failed to run a step!)!
[Error]: >>>Dense Processing<<< failed with error (failed to run a step!)!
[Error]: Dense matching failed!
[Error]: >>>Dense matching<<< failed with error (failed to run a step!)!
[Error]: >>>Dense matching<<< failed with error (failed to run a step!)!
Processing: Substep Dense matching finished.
Processing: Step1Done
[UI]: Settings clicked.

2

Hi Joe4,

It could be due to insufficient RAM. However, for us to know for sure, we will need you to attach the full .log file to this posting. We’ll take a look once you post it.

3

Hi Mike, thanks - log file uploaded

Log file.txt (3.7 KB)

4

Hi Joe4,

We need the actual .log file that is generated by Mapper. You can find it in the project folder.

▸ The project log file (text file): …\project_name\project_name.log

5

187 Hood Rd.log (167.3 KB)

6

I don’t think this is a RAM issue. I never saw RAM utilization get above 85%, which is within the threshold of adequate RAM.

I see that you are using a P: drive. Is this an external or network drive? These can sometimes be slow and sometimes unstable. The data can bottleneck and cause the program to crash. If this is the case, can you move your project to your C: drive and try again?