{"action":"created","issue":{"url":"https://api.github.com/repos/simonfuhrmann/mve/issues/428","repository_url":"https://api.github.com/repos/simonfuhrmann/mve","labels_url":"https://api.github.com/repos/simonfuhrmann/mve/issues/428/labels{/name}","comments_url":"https://api.github.com/repos/simonfuhrmann/mve/issues/428/comments","events_url":"https://api.github.com/repos/simonfuhrmann/mve/issues/428/events","html_url":"https://github.com/simonfuhrmann/mve/issues/428","id":323461337,"number":428,"title":"sfmrecon stuck at 159/434 views","user":{"login":"nitrotm","id":805632,"avatar_url":"https://avatars3.githubusercontent.com/u/805632?v=4","gravatar_id":"","url":"https://api.github.com/users/nitrotm","html_url":"https://github.com/nitrotm","followers_url":"https://api.github.com/users/nitrotm/followers","following_url":"https://api.github.com/users/nitrotm/following{/other_user}","gists_url":"https://api.github.com/users/nitrotm/gists{/gist_id}","starred_url":"https://api.github.com/users/nitrotm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nitrotm/subscriptions","organizations_url":"https://api.github.com/users/nitrotm/orgs","repos_url":"https://api.github.com/users/nitrotm/repos","events_url":"https://api.github.com/users/nitrotm/events{/privacy}","received_events_url":"https://api.github.com/users/nitrotm/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-05-16T04:02:49Z","updated_at":"2018-05-19T18:48:29Z","closed_at":null,"author_association":"NONE","body":"I am not sure what's the problem, but the sfm is repetitively stuck in one of my dataset (1 cpu at 100% for many days). It find features in views, start the matching and after a while gets stuck in the process.\r\n\r\nOn another similar dataset I didn't encounter this issue.\r\n\r\nI cleared the output and tried several times. The problem appears at a different view but is still there.\r\n\r\nThe last output is \"Camera X, focal length: 0.78788 -> 0.78788, distortion: 0.0000 0.0000\". According to the other steps in the process above, I assume it should be doing a full bundle adjustment which never finishes. If that's the case, could it be related to some stability condition in the algorithm which is never reached or something similar?\r\n\r\nHow can I diagnose the problem further?"},"comment":{"url":"https://api.github.com/repos/simonfuhrmann/mve/issues/comments/390424921","html_url":"https://github.com/simonfuhrmann/mve/issues/428#issuecomment-390424921","issue_url":"https://api.github.com/repos/simonfuhrmann/mve/issues/428","id":390424921,"user":{"login":"simonfuhrmann","id":1150723,"avatar_url":"https://avatars3.githubusercontent.com/u/1150723?v=4","gravatar_id":"","url":"https://api.github.com/users/simonfuhrmann","html_url":"https://github.com/simonfuhrmann","followers_url":"https://api.github.com/users/simonfuhrmann/followers","following_url":"https://api.github.com/users/simonfuhrmann/following{/other_user}","gists_url":"https://api.github.com/users/simonfuhrmann/gists{/gist_id}","starred_url":"https://api.github.com/users/simonfuhrmann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/simonfuhrmann/subscriptions","organizations_url":"https://api.github.com/users/simonfuhrmann/orgs","repos_url":"https://api.github.com/users/simonfuhrmann/repos","events_url":"https://api.github.com/users/simonfuhrmann/events{/privacy}","received_events_url":"https://api.github.com/users/simonfuhrmann/received_events","type":"User","site_admin":false},"created_at":"2018-05-19T18:48:29Z","updated_at":"2018-05-19T18:48:29Z","author_association":"OWNER","body":"Hi there,\r\n\r\nyou are correct with your concerns that these views may have impacted the accuracy, or correctness, of the bundle adjustment. It is very likely that they introduced a global bias during global optimization. Also,  you definitely won't benefit from these views in `dmrecon`, and it's not unlikely that they will cause some harm. It might not be that bad, but that's hard to say. In the worst case, it will introduce some spurious matches. In the best case, it just won't reconstruct any depth values for these views.\r\n\r\nThere is not really a good way to automatically identify the views that \"don't fit the scene\" because with the estimated parameters, it fits the scene well enough so that SfM decided to keep them. However, looking at your logs, you can see that the views where the focal length was thrown off, it introduces a rather large radial distortion term (in the order of +-5 or larger). If you look at the undistorted images in the directory structure for these views, you'll notice the problem. I think you can safely remove those, and maybe try to run SfM again without these views.\r\n\r\nI haven't seen your dataset, but usually, if you have a good coverage of photos in your scene and plenty of features, this should not happen. I'm wondering if there is a problem with how you captured the photos, or with the properties of your scene (reflective, etc.) that could cause these issues."}}
{"actor":{"display_login":"simonfuhrmann"}}