Open fabfabBesnard opened 2 years ago
Before commit : My initial comments on this issue were that not enough information was available to plantdb. That was wrong, as the files images.json generated provides the images that are matched by Colmap and not the images used by Colmap (which are the whole dataset). Then it was relatively easy to implement
Issue: some images are not "matched" during the ColMap process (which is quite upstream in the analysis pipeline). This can have strong effects in the quality of 3D reconstruction and in the precision of the measure. However, the pipeline does not necessarily fail in such cases, so that the final user may not be aware of this issue
Expected behavior: While exploring a dataset, the user should immediately see that some images are unmatched by Colmap
idea: information of matched/unmatched images should be printed in the dedicated Colmap folder during analysis. Viusalizaton task should then process this data
example of possible visual ouptut in plant-3d-explorer: in the carrousel (or in the main panel when images are open) color with a red filter the unmatched images