search

openphotogrammetry / meshroomcl

MeshroomCL: An OpenCL implementation of photogrammetry with the Meshroom interface
Other
174 stars 8 forks source link

There is no node able to be processed error #45

Open wmolevelt opened 2 years ago

wmolevelt commented 2 years ago

Hi,

After several projects with around 100 images all finished with succes, though some needed a restart, but Meshroom was able to continue, I am now working on 800 images and when almost done with the MultiviewStereoCL pass the program crashed. When opening the project and restarting it comes with an error message: There is no node able to be processed. Since I am about 60 hours into all calculations I would like to know how to recover and continue processing. If any clarification is needed please ask.

Regards

revisionarian commented 2 years ago

Hi @wmolevelt, sorry that you are getting a crash after 60 hours (wow) of processing! Can you post or send the log file from the MultiviewStereoCL node? That will allow us to see at what stage of processing the crash is happening.

wmolevelt commented 2 years ago

log.txt if it helps I run Meshroom on Windows 10, AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx 2.10 GHz, with 12GB of RAM. From your answer I understand there is no way to recover and continue?

thanks for the quick reply!

HapHazard1 commented 2 years ago

I believe I am seeing the same error. In case additional logs will help:

============================================================================== Image undistortion

Undistorting image [1/2] Undistorting image [2/2] Writing reconstruction... Writing configuration... Writing scripts... Elapsed time: 0.052 [minutes] Reading workspace... Reading configuration... Configuration has 2 problems... Elapsed time: 0.006 [minutes] Reading workspace... Reading configuration... Configuration has 2 problems... Elapsed time: 0.006 [minutes]

StereoFusion::Options

max_image_size: 3200 min_num_pixels: 5 max_num_pixels: 10000 max_traversal_depth: 100 max_reproj_error: 2 max_depth_error: 0.01 max_normal_error: 10 check_num_images: 50 cache_size: 32

Reading workspace... Reading configuration... Fusing image [1/2] in 2.887s (6 points) Fusing image [2/2] in 0.756s (6 points) Number of fused points: 6 Elapsed time: 0.071 [minutes] Writing output: p:/Temp/3DScans/GnomeProject/MeshroomCache/MultiviewStereoCL/e068ef47995de7d486a3ec33bbafd7d51c55fa15\fused.ply Triangulating points... Triangulation has 6 using 6 points. Initializing ray tracer... Initializing graph optimization... Integrating image [1/2] in 0.000s Integrating image [2/2] in 0.000s Setting up optimization... Running graph-cut optimization... Extracting surface as min-cut... Creating surface mesh model... Check failure stack trace: @ 000007FED2795FCB public: void cdecl google::LogMessage::Flush(void) ptr64 @ 000007FED2794B29 public: cdecl google::LogMessageFatal::~LogMessageFatal(void) ptr64 @ 000000013F42D401 (unknown) @ 000000013F44CB2A (unknown) @ 000000013F44CFBC (unknown) @ 000000013F30F849 (unknown) @ 000000013F3017A6 (unknown) @ 000000013F3441BF (unknown) @ 000000013F85EAD4 (unknown) @ 00000000773B652D BaseThreadInitThunk @ 00000000775EC541 RtlUserThreadStart F0826 06:28:34.222056 6272 math.h:233] Check failed: !elems.empty()

wmolevelt commented 2 years ago

quick recap of how I proceeded afterwards. On the first try I had Meshroom resizing my images, on the second try I did so previously using Darktable. This seems to help a lot. Also I was much more strict on using other applications at the same time, in general only one next to Meshroom. Project is now completed, learned a lot, also that I still have a lot more to learn. Also helpful is to know that selecting the active process and on the right marking the log tab helps seeing if Meshroom is active.