FS#76689 - [meshroom] can't compute depth map as the required function is not installed by alice-vision

Attached to Project: Community Packages
Opened by Michael Prasthofer (mpr) - Monday, 28 November 2022, 15:54 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 04 January 2023, 23:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Thanks for adding meshroom to the community repository a few days ago. When testing it on the Monstree Image Dataset ( https://meshroom-manual.readthedocs.io/en/latest/first-steps/test/index.html ) meshroom stopped working at the DepthMap node with the error message `/bin/sh: line 1: aliceVision_depthMapEstimation: command not found`. On my system, after installing alice-vision the depth map related commands (aliceVision_depthMapEstimation and aliceVision_depthMapFiltering) don't seem to be installed. Without them meshroom cannot compute the full pipeline. I installed the packages with `sudo pacman -S meshroom` and made no changes to the installation.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 04 January 2023, 23:02 GMT
Reason for closing:  Fixed
Comment by Michael Prasthofer (mpr) - Monday, 28 November 2022, 16:12 GMT
The depth map step works if I install alice-vision-cuda instead of alice-vision (please add a comment/an optional dependency to the package description https://archlinux.org/packages/community/x86_64/meshroom/). However, now it fails at the texturing step with

/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = aliceVision::Voxel; _Alloc = std::allocator<aliceVision::Voxel>; reference = aliceVision::Voxel&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.

Also, the program crashes when trying to display features on images:

/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = QPointF; _Alloc = std::allocator<QPointF>; reference = QPointF&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted (core dumped)
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 29 November 2022, 18:49 GMT
The default meshroom reconstruction pipeline is not expected to work without CUDA. See this thread: https://github.com/alicevision/AliceVision/issues/439

I can reproduce the segfaulting problem. Could you produce a stacktrace for upstream and report an issue on their tracker?
Comment by Michael Prasthofer (mpr) - Tuesday, 29 November 2022, 19:04 GMT
Yes you're right, the default pipeline expects CUDA, so the default dependency of meshroom should be alice-vision-cuda. Currently it's alice-vision (no CUDA). I think it would make sense to change that dependency in https://archlinux.org/packages/community/x86_64/meshroom/.

Ok, glad it's not just on my computer :) I'll report an issue on their tracker.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 29 November 2022, 20:40 GMT
Sadly, that would prohibit us from allowing users to use the non-CUDA package if I don't wrangle the dependencies any other non-obvious way. I think alice-vision-cuda will have to stay the non-default alternative. However, I will add an optdep to meshroom to make this more obvious.
Comment by Michael Prasthofer (mpr) - Tuesday, 29 November 2022, 20:47 GMT
ok thanks
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 29 November 2022, 21:33 GMT
I think we should close this issue for now and perhaps track the other issue in another bug report where you can also link the upstream bug report? I think this particular original issue has been resolved. What do you think?
Comment by Michael Prasthofer (mpr) - Wednesday, 30 November 2022, 21:16 GMT
Yeah that sounds good, I'll try to get the report in sometime this week
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 07 December 2022, 07:32 GMT
Did you get around to report the bug upstream?
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 04 January 2023, 22:06 GMT
I believe I found and fixed the cause. Can you check rel-12?

Loading...