-
-
Notifications
You must be signed in to change notification settings - Fork 173
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
Feature request - improve matches graph #54
Comments
I have good news for you: It's already a feature.
should do the trick. See also #14 |
I admit that it is not well documented, maybe we should include it in the stitching_tutorial |
Nice! I will take a look thanks a lot |
you can also explain what's range_width and what is its impact |
Setting it to 1 basically just means that that it only looks for matches in images directly to its left or right. 2 would mean 2 images left or right... All based on the order of the images passed into Stitcher.stitch() |
And another question, (idk if it's the right place) can the generated image be a spherical photo (in order to put it in a 360 visualizer)? |
at least there is a |
Hi @lukasalexanderweber, @Kalo0m Suppose that I have 5 images: "A, B, C, D, E" I know matches_graph as below:
As you suggestion I followed in tutorial I see that, maybe matches_graph is matches_graph_dot_file in Subset parameters ?
I saw in matches_graph have [label="Nm=68, Ni=19, C=0.669014"]. What is the master if I don't have label, Ni, C parameters? And if I use fastest function
as you summary, Can I put matches_graph for creating adjacent panorama as I expect? |
please use the discussions for questions |
Hi guys,
Firstly thank you all for you amazing work. I would like to have your thoughts on a new feature (afaik not available for now).
I have a list of ten images and I know the order of them, it would be nice to pass this order in order to override confidence_threshold and get the right graph. Of course it would be an option.
Example: I have 3 photos (A, B and C) and I know the exact order (B --> C --> A). instead of letting the package find the order and maybe be wrong (for example by rejecting A of the result graph), I could pass the graph below as an option to bypass the graph generation.
graph matches_graph{
"B" -- "C"
"C" -- "A"
}
Sorry if I'm not clear, I would like to contribute so what do you think ? Do you have any suggestions ?
The text was updated successfully, but these errors were encountered: