ClusterODM output ignores skip_report False

[and-viceversa]

I’m running my jobs through WebODM with ClusterODM as the target, all on Windows 10.

When the jobs complete, no report is generated. The skip_report parameter is not turned on in WebODM. The odm_report folder only contains a shots.geojson. The final log file doesn’t mention anything about skipping reports, but I seem to recall seeing a “No report generated” or similar message as split_merge jobs return to the main node.

Has anyone encountered this, or what am I doing wrong?

[smathermather]

Reports aren’t yet supported for split merge, I think.

[and-viceversa]

Thank you!