My project is "queued". Estimate of delay?

Is my project in line to be processed? I have not been stuck in “queued” in past attempts to process.



WebODM? Then purge the queue first and try again.

WebODM gets hung up processing for hours. I have deleted and started over several times. It’s only 680 pics, not a huge job. There is a BMP file saved before pics and another after. I included both files with pics. Is this normal?

depending on your settings and the machine specs 680 images can easily take hours especially if the process is using lots of virtual memory.

1 Like

Or days if using ultra settings!

I don’t understand the question… saved where, and by WebODM?

When you say ‘hung up’ is the CPU still being used?

BMP files saved with image files on CPU, then loaded by WebODM. I have used the PC for other work while WebODM processes. On other attempts, I have not used PC while WebODM processes. I have disabled sleep setting. The progress bar where “processing” is displayed shows 1/4" of green color. Progress icon is turning but does not advance.
[INFO] Initializing ODM 2.9.2 - Fri Oct 28 08:32:33 2022
[INFO] ==============
[INFO] 3d_tiles: False
[INFO] auto_boundary: True
[INFO] auto_boundary_distance: 0
[INFO] bg_removal: False
[INFO] boundary: {}
[INFO] build_overviews: False
[INFO] camera_lens: auto
[INFO] cameras: {}
[INFO] cog: True
[INFO] copy_to: None
[INFO] crop: 3
[INFO] debug: False
[INFO] dem_decimation: 1
[INFO] dem_euclidean_map: False
[INFO] dem_gapfill_steps: 3
[INFO] dem_resolution: 5
[INFO] depthmap_resolution: 640
[INFO] dsm: True
[INFO] dtm: False
[INFO] end_with: odm_postprocess
[INFO] fast_orthophoto: False
[INFO] feature_quality: high
[INFO] feature_type: sift
[INFO] force_gps: False
[INFO] gcp: None
[INFO] geo: None
[INFO] gps_accuracy: 10
[INFO] ignore_gsd: False
[INFO] matcher_neighbors: 0
[INFO] matcher_type: flann
[INFO] max_concurrency: 8
[INFO] merge: all
[INFO] mesh_octree_depth: 11
[INFO] mesh_size: 200000
[INFO] min_num_features: 10000
[INFO] name: e39d7e10-784f-4e16-a0ae-7144a698f29d
[INFO] no_gpu: False
[INFO] optimize_disk_space: False
[INFO] orthophoto_compression: DEFLATE
[INFO] orthophoto_cutline: False
[INFO] orthophoto_kmz: False
[INFO] orthophoto_no_tiled: False
[INFO] orthophoto_png: False
[INFO] orthophoto_resolution: 5
[INFO] pc_classify: False
[INFO] pc_copc: False
[INFO] pc_csv: False
[INFO] pc_ept: True
[INFO] pc_filter: 2.5
[INFO] pc_geometric: False
[INFO] pc_las: False
[INFO] pc_quality: medium
[INFO] pc_rectify: False
[INFO] pc_sample: 0
[INFO] pc_tile: False
[INFO] primary_band: auto
[INFO] project_path: C:\WebODM\resources\app\apps\NodeODM\data
[INFO] radiometric_calibration: none
[INFO] rerun: None

This is first portion of task output. Are there certain things in the task output I should look for?

Are the .bmp files part of your dataset- the images you want to process?
Are they in the folder with the rest of the images for the task?

Have you looked at the console to see what is happening? Set Task Output: ON

What are the most recent few lines of the log?

Use Task Manager to check for CPU and RAM usage.

What are your computer specifications?

Unless the task has failed, it is probably progressing ok.

Just for reference, my computer has been working on a task of 294 images for almost 36 hours.

1 Like