-
Notifications
You must be signed in to change notification settings - Fork 32
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
Hyperparameters in aerial scene #54
Comments
Hi, the multi-view nearest camera selection strategy may require choosing appropriate thresholds based on the actual scenario, as the default parameters may not always be suitable. You can check whether the strategy is appropriate by examining the final file "multi_view.json." |
I still had some questions that may needs your instruction, In the nearest cam selection stage: Here the nearest camera will take angle offset and distance offset into consideration: But the camera distance was an absolute distance between two camera centers. Due to the scale of different scenes. For example, when in indoor scenes, the camera might be much closer than in outdoor scenes. So I wonder if it would be better to use relative camera offsets. For example, divided the offset by the bounding box of the whole scene. Looking forward to your reply! |
Yes, if the entire scene size can be considered as the basis for adjustment, the parameters will be more universal. |
Hi, I noticed that your multi view nearest cam selection strategy was : select those cameras with angle between (0, 30) and distance between (0.01, 1.5) from the candidate cameras. Are these settings suitable for the large outdoor scenes? For example, My dataset is an aerial scene whose images are from a drone with 5 cameras shot from 5 different angles. And I also observed very small number of nearest cameras in my "mulit_view.json". Which means the multi-view loss can hardly work in my scene. Hope for your reply!
The text was updated successfully, but these errors were encountered: