Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
The results of the ReconstructionSystem usually fail, and registration result is not ideal #1264
I try to turn off multithreading by using
I did some testing, and then found something interested, I hope you can help me to ensure it.
the command recommend in official tutorial like this:
python run_system.py config/tutorial.json --make --register --refine --integrate
Obviously, we can roughly divide it into two categories, fragment generation and registration.
① python run_system.py config/tutorial.json --make ② python run_system.py config/tutorial.json --register --refine --integrate
After using ① to generate the fragments, we keep the fragments folder unchanged, no matter how many times the ② command is used, the result is almost the same every time.
But once we regenerate the fragments using command ①, the result may be different.
Interesting, can you check if there is any corrupted fragment in your failure reconstruction? You may use this tool to visualize the fragments:
Also, do you have OpenCV installed? There will be an indicator telling you whether ORB+5pt is used in making fragments depending on the existence of OpenCV.
yes, opencv is installed by conda.
I also use the visualize_fragments.py to show the ply file, but it seems to just open all the .ply files in the fragments folder, and use open3d to visualize them. All ply files can be visualized very well.
And what is the meaning of corrupted fragment? A damaged ply file that cannot be opened?
I agree with your opinion, I also think that because of the registration failed, the final result is not good.
So I don't know what I should do, improve the precision of the registration or optimize the make fragments section.