¿Fallo constante en el procesamiento inmediatamente después del subpaso Calibración de Cámara?

Question

<\/HEAD>Hasta ahora, en mi prueba de D2M, solo he logrado completar un proyecto 2D. Desde entonces, consistentemente obtengo un Error de Excepción Desconocida que, según el registro, ocurre inmediatamente después (¿o durante?) del subpaso Calibración de Cámara durante la fase inicial de procesamiento. Sucede tanto si intento producir productos puramente 2D alrededor del 29% de finalización, como productos 3D, aunque el error de excepción parece ocurrir más tarde en el procesamiento de un intento puramente 3D al 80% de finalización. He intentado múltiples variaciones leves de opciones de procesamiento, principalmente ajustando la escala de imagen de puntos clave y el número objetivo de puntos clave, pero también con las opciones predeterminadas completas usadas en mi único intento exitoso de procesamiento (el primer conjunto de datos procesado). Aún no he intentado reprocesar un conjunto de datos idéntico a mi único intento exitoso para ver si el problema ocurre allí también, ya que ese conjunto de datos es bastante más grande y tomaría aproximadamente 5 horas o más para llegar al punto de fallo.<\/P> <\/P> Aquí está la sección relevante del registro: <\/P> 2019-03-30 00:56:20,513 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Calcular número de coincidencias.","overallProgress":"24","substep":"Georeferenciar el modelo"},"timestamp":"1553921780513"} 2019-03-30 00:56:20,746 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Subpaso Georeferenciar el modelo terminado.","overallProgress":"24","substep":"Georeferenciar el modelo"},"timestamp":"1553921780746"} 2019-03-30 00:56:20,750 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Subpaso Calibración de Cámara iniciado.","overallProgress":"29","substep":"Calibración de Cámara"},"timestamp":"1553921780748"} 2019-03-30 00:56:24,973 INFO - {"exit":{"code":"0","errorMessage":""},"status":{"currentStep":"initial","detailedMessage":"Subpaso Calibración de Cámara terminado.","overallProgress":"29","substep":"Calibración de Cámara"},"timestamp":"1553921784972"} 2019-03-30 00:56:25,099 INFO - {"exit":{"code":"1","errorMessage":"¡Excepción desconocida capturada durante el procesamiento inicial!"},"status":{"currentStep":"initial","detailedMessage":"Subpaso Calibración de Cámara terminado.","overallProgress":"29","substep":"Calibración de Cámara"},"timestamp":"1553921785099"} 2019-03-30 00:56:25,123 INFO - {"exit":{"code":"1","errorMessage":"¡Excepción desconocida capturada durante el procesamiento inicial!"},"status":{"currentStep":"initial","detailedMessage":"ProyectoCargado","overallProgress":"29","substep":"Calibración de Cámara"},"timestamp":"1553921785123"} 2019-03-30 00:56:25,150 INFO - {"exit":{"code":"1","errorMessage":"¡Excepción desconocida capturada durante el procesamiento inicial!"},"status":{"currentStep":"initial","detailedMessage":"Abortando ...","overallProgress":"29","substep":"Calibración de Cámara"},"timestamp":"1553921785150"} <\/P><\/BLOCKQUOTE> Cualquier ayuda es muy apreciada. Gracias --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