Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Invalid camera reconstruction for symmetrical buildings #605

Open
Baasje85 opened this issue Aug 24, 2019 · 2 comments
Open

[bug] Invalid camera reconstruction for symmetrical buildings #605

Baasje85 opened this issue Aug 24, 2019 · 2 comments
Labels
bug for actual bugs (unsure? use type:question) do not close issue that should stay open (avoid automatically close because stale) feature request feature request from the community type:question

Comments

@Baasje85
Copy link

Baasje85 commented Aug 24, 2019

Describe the bug
We are trying to map a building which has many similarities, symmetrical if you want to keep it simple. One of the main problems we face is invalid camera reconstruction. As a clear example a screenshot. What happens is the left side tower of the church is reconstructed on the right side.

invalid-projection

To Reproduce
We can make a dataset of the project available.

Expected behavior
I understand it is sometimes impossible to differentiate between ambiguous images. This is fine, even in a human situation it is impossible to know without context. Still in this specific case images are available that clearly are zoomed and have left and right overlap. What I would like to say about a reconstruction: "Meshroom, this camera reconstruction is wrong." or ultimately: "Meshroom move and pan the camera, and attempt a local beam reconstruction for this single image."

Suggestions to improve the situation with settings are obviously also appreciated. Our minimum input track length was already increased. With Minimum Input Track Length to 6, and Min Observation For Triangulation to 4 the results look optically fine. I could now comment on the fact that this is still problematic for bigger projects. Absolute minims are; Minimum Input Track Length to 2 and Min Observation For Triangulation to 3 (a lower number results in mirroring of the building).

image

Desktop (please complete the following and other pertinent information):

  • Version 2019.2
@Baasje85 Baasje85 added the bug for actual bugs (unsure? use type:question) label Aug 24, 2019
@natowi natowi added feature request feature request from the community type:question labels Aug 25, 2019
@natowi
Copy link
Member

natowi commented Aug 25, 2019

differentiate between ambiguous images

You could try placing CCTAGs.

Still in this specific case images are available that clearly are zoomed and have left and right overlap. What I would like to say about a reconstruction: "Meshroom, this camera reconstruction is wrong."

@natowi natowi added the do not close issue that should stay open (avoid automatically close because stale) label Oct 27, 2019
@stale
Copy link

stale bot commented Feb 24, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale for issues that becomes stale (no solution) label Feb 24, 2020
@natowi natowi removed the stale for issues that becomes stale (no solution) label Feb 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug for actual bugs (unsure? use type:question) do not close issue that should stay open (avoid automatically close because stale) feature request feature request from the community type:question
Projects
None yet
Development

No branches or pull requests

2 participants