Support Website Contact Support Blog

[Desktop] [Pix4DmapperPro 4.2.15] DTM Generation on repeat?

Hi there,

I am currently processing a project with over 3000 images.

I am starting to get a bit concerned looking at the logs as ‘DTM Generation and Generate DTM Classification Mask’ seems to be stuck on loop. The Processing bar indicates that I am on stage 4/8 for DTM, Orthomosaic and Index and it hasn’t moved regardless of the curent task passing 100% over and over again. 

Can someone please help out

Below is the log output:

[2018.02.14 10:06:04][45%RAM][27%CPU][Processing]: Step3Running

[2018.02.14 10:06:20][45%RAM][47%CPU][Processing]: Substep Ortho load pcl started.

[2018.02.14 10:06:20][45%RAM][47%CPU][Processing]: Load point cloud

[2018.02.14 10:15:28][49%RAM][28%CPU][Processing]: Substep Ortho load pcl finished.

[2018.02.14 10:15:28][49%RAM][28%CPU][Processing]: Substep Ortho gridded dsm started.

[2018.02.14 10:15:28][49%RAM][28%CPU][Processing]: Point cloud gridding

[2018.02.14 10:43:58][49%RAM][27%CPU][Processing]: Substep Ortho gridded dsm finished.

[2018.02.14 10:43:58][49%RAM][27%CPU][Processing]: Substep Ortho dsm started.

[2018.02.14 10:43:58][49%RAM][27%CPU][Processing]: Generate DSM

[2018.02.14 12:06:48][52%RAM][17%CPU][Processing]: Substep Ortho dsm merge started.

[2018.02.14 12:06:48][52%RAM][17%CPU][Processing]: Merge DSM tiles

[2018.02.14 13:25:13][64%RAM][24%CPU][UI]: Processing Options clicked.

[2018.02.14 13:42:32][69%RAM][15%CPU][UI]: Processing Options clicked.

[2018.02.14 14:44:40][53%RAM][24%CPU][Processing]: Substep Ortho dsm merge finished.

[2018.02.14 14:44:40][53%RAM][24%CPU][Processing]: Substep Ortho dsm finished.

[2018.02.14 14:44:40][53%RAM][31%CPU][Processing]: Substep Ortho dtm started.

[2018.02.14 14:44:49][55%RAM][29%CPU][Processing]: Downsampling

[2018.02.15 08:02:47][57%RAM][15%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 08:02:56][59%RAM][52%CPU][Processing]: DTM generation

[2018.02.15 08:19:08][55%RAM][14%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 08:19:16][56%RAM][48%CPU][Processing]: DTM generation

[2018.02.15 08:36:15][55%RAM][100%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 08:36:23][56%RAM][43%CPU][Processing]: DTM generation

[2018.02.15 08:53:28][56%RAM][15%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 08:53:38][57%RAM][61%CPU][Processing]: DTM generation

[2018.02.15 09:10:08][60%RAM][100%CPU][UI]: Processing Options clicked.

[2018.02.15 09:10:20][55%RAM][100%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 09:10:30][56%RAM][56%CPU][Processing]: DTM generation

[2018.02.15 09:29:54][56%RAM][21%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 09:30:03][57%RAM][56%CPU][Processing]: DTM generation

[2018.02.15 09:49:45][57%RAM][26%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 09:49:53][58%RAM][56%CPU][Processing]: DTM generation

[2018.02.15 10:11:11][58%RAM][27%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 10:11:19][59%RAM][56%CPU][Processing]: DTM generation

[2018.02.15 10:32:05][55%RAM][20%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 10:32:15][56%RAM][71%CPU][Processing]: DTM generation

[2018.02.15 10:49:09][56%RAM][20%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 10:49:19][57%RAM][66%CPU][Processing]: DTM generation

[2018.02.15 11:14:57][57%RAM][21%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 11:15:06][58%RAM][61%CPU][Processing]: DTM generation

[2018.02.15 11:31:12][56%RAM][15%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 11:31:20][57%RAM][51%CPU][Processing]: DTM generation

[2018.02.15 11:48:32][56%RAM][11%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 11:48:40][57%RAM][51%CPU][Processing]: DTM generation

[2018.02.15 12:05:41][57%RAM][14%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 12:05:49][58%RAM][50%CPU][Processing]: DTM generation

[2018.02.15 12:26:11][57%RAM][24%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 12:26:20][58%RAM][59%CPU][Processing]: DTM generation

[2018.02.15 12:43:23][57%RAM][25%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 12:43:33][58%RAM][64%CPU][Processing]: DTM generation

[2018.02.15 13:01:39][57%RAM][11%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 13:01:50][58%RAM][62%CPU][Processing]: DTM generation

[2018.02.15 13:17:40][57%RAM][10%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 13:17:49][58%RAM][58%CPU][Processing]: DTM generation

[2018.02.15 13:34:14][57%RAM][14%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 13:34:22][58%RAM][51%CPU][Processing]: DTM generation

[2018.02.15 13:52:29][57%RAM][28%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 13:52:37][58%RAM][57%CPU][Processing]: DTM generation

[2018.02.15 14:11:57][57%RAM][20%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 14:12:05][58%RAM][57%CPU][Processing]: DTM generation

[2018.02.15 14:29:47][58%RAM][13%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 14:29:55][59%RAM][52%CPU][Processing]: DTM generation

[2018.02.15 14:47:44][57%RAM][10%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 14:47:53][58%RAM][56%CPU][Processing]: DTM generation

[2018.02.15 15:04:16][57%RAM][10%CPU][Processing]: Generate DTM Classification Mask

[2018.02.15 15:04:26][58%RAM][58%CPU][Processing]: DTM generation

Hi there,

I just realised that this step is repeating because Pix4D is logging the generation of each dtm tile as a line.

I had over 5000 files in my tile folder for the dsm so I can only assume I will have roughly the same number for my dtm.

Please close this thread. Thank you.