Konstante Verarbeitungsfehler unmittelbar nach dem Unterabschnitt Kamera-Kalibrierung?

Question

<\/HEAD>Bis jetzt habe ich in meinem Versuch mit D2M nur ein 2D-Projekt erfolgreich abgeschlossen. Seitdem erhalte ich konsequent einen Unbekannten Ausnahmefehler, der laut Protokoll unmittelbar nach (oder während?) des Unterabschnitts Kamera-Kalibrierung in der Anfangsverarbeitungsphase auftritt. Dies geschieht sowohl bei dem Versuch, rein 2D-Produkte bei etwa 29 % Fertigstellungsgrad zu erzeugen, als auch bei 3D-Produkten, obwohl der Ausnahmefehler bei einem reinen 3D-Produktversuch später im Verarbeitungsprozess bei 80 % Fertigstellung aufzutreten scheint. Ich habe mehrere leichte Variationen der Verarbeitungsoptionen ausprobiert, hauptsächlich die Skalierung der Keypoint-Bildgebung und die Zielanzahl der Keypoints angepasst, aber auch mit den vollständigen Standardoptionen, wie sie bei meinem einzigen erfolgreichen Verarbeitungsversuch (dem ersten verarbeiteten Datensatz) verwendet wurden. Ich habe noch nicht versucht, einen identischen Datensatz wie bei meinem erfolgreichen Verarbeitungsversuch erneut zu verarbeiten, um zu sehen, ob das Problem dort ebenfalls auftritt, da dieser Datensatz deutlich größer ist und es ungefähr 5 Stunden dauern würde, bis der Fehlerpunkt erreicht ist.<\/P> <\/P> Hier ist der relevante Abschnitt aus dem Protokoll: <\/P> 2019-03-30 00:56:20,513 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Berechne Anzahl der Übereinstimmungen.","overallProgress":"24","substep":"Georeference the model"},"timestamp":"1553921780513"} 2019-03-30 00:56:20,746 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Unterabschnitt Georeference the model abgeschlossen.","overallProgress":"24","substep":"Georeference the model"},"timestamp":"1553921780746"} 2019-03-30 00:56:20,750 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Unterabschnitt Kamera-Kalibrierung gestartet.","overallProgress":"29","substep":"Camera calibration"},"timestamp":"1553921780748"} 2019-03-30 00:56:24,973 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Unterabschnitt Kamera-Kalibrierung abgeschlossen.","overallProgress":"29","substep":"Camera calibration"},"timestamp":"1553921784972"} 2019-03-30 00:56:25,099 INFO - {"exit":{"code":"1","errorMessage":"Unbekannte Ausnahme während der Anfangsverarbeitung abgefangen!"},"status":{"currentStep":"initial","detailedMessage":"Unterabschnitt Kamera-Kalibrierung abgeschlossen.","overallProgress":"29","substep":"Camera calibration"},"timestamp":"1553921785099"} 2019-03-30 00:56:25,123 INFO - {"exit":{"code":"1","errorMessage":"Unbekannte Ausnahme während der Anfangsverarbeitung abgefangen!"},"status":{"currentStep":"initial","detailedMessage":"ProjectLoaded","overallProgress":"29","substep":"Camera calibration"},"timestamp":"1553921785123"} 2019-03-30 00:56:25,150 INFO - {"exit":{"code":"1","errorMessage":"Unbekannte Ausnahme während der Anfangsverarbeitung abgefangen!"},"status":{"currentStep":"initial","detailedMessage":"Abbruch ...","overallProgress":"29","substep":"Camera calibration"},"timestamp":"1553921785150"} <\/P><\/BLOCKQUOTE> Jede Hilfe wird sehr geschätzt. Danke --Jason<\/P><\/BODY><\/HTML>

JamesStewart-Moore1 · Answer

Were you able to resolve the issue?

JasonKovacs · Answer

Thanks for the tips Miki!

In regards to file storage, my laptop (not ideal; a proper workstation is in the works) has around 100 GB left. The successfully processed project folder is roughly 15.7 GB in size. So unless D2M is using around 80 GB of temp disk storage in it's processing, I should be OK.

All other applications are turned off to maximize CPU and RAM availability for D2M, including Chrome and usually internet all together. I also verify that most everything that can be turned off is so, prior to attempting to process.

The area in the attached screencapture is indeed a mostly flat, grass field. Some relief along it's northern edge, but not much, less than 3 meters total elevation gain from highest spot in the field to lowest. I will attempt a processing run using "Calibration Method: Alternative" as you suggested and see what happens.

All of the GCP have been manually linked to 7-10 photos each. As for their recorded location accuracy.... no idea. I utilized Collector with a sub-meter Bad Elf GPS unit. For quick points, accuracy is usually observed as +/- 4 m. I set it up to record an average over 30 seconds, which generally brings the accuracy error down significantly, according to our GIS person, although I do not know the magnitude. We did have a weird error where the elevations for all GCP came back as 0.0 m; I was able to calculate a ground surface elevation for each GCP from an ESRI DEM online service, however.

The individual images aren't blurry, but zooming in on the GCPs does show some loss of resolution. If I'm manually linking GCPs in photos, dropping an X myself to indicate the center of each target, is D2M still attempting to calculate where the crosshairs should be? It seems redundant and unnecessary if this is the case, but if so, I can see the program having issues deciding where exactly the center of the GCP is.

As to whether D2M is using each of the eleven GCPs .... How would one find that out for certain?

Thanks again,

Jason

MikiYAMAMOTO · Answer

Hello Jason,

I wonder...

- if you locate images and project in your local drive.

- if you have enough free spaces in your storage which the project located.

- if you have run other big applications at same time (CPU).

I cannot explain well at this moment why the project once processed successfully fails other time but some conditions would be different all the time and the differences may cause some issues even though you use same PC to process.

Regarding the answer 3) posted on 2019/04/08 15:19,  I wonder (if you use a dataset of field like above) ...

- if you have processed with using "Calibration Method: Alternative" ("Use Geometry Verified Matching" under "Matching Strategy" will be checked-on automatically btw) that is optimized for dataset captured flat and homogenous areas such a grass field. (related to an error appearance of "Camera Optimization" under "Quality Check" in Processing Report).

- if all GCPs are used in the process. If the accuracy of GCPs is low or images that linked with GCPs are blurred, it sometimes fail to verify using GCPs  (related to an error appearance of "Georeferencing" under "Quality Check" in Processing Report).

Hope these tips would be helpful,

Good luck!

Miki