Helping "incremental" optimization
Bug #816850 reported by
Frederic Da Vitoria
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Hugin |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
One of the optimization methods is: triggering each optimization option in turn and accepting the results if the new optimization iteration are better than those of the previous iteration. The only problem here is that you need to remember the results of the previous iteration in order to be able to compare! It would be nice if Hugin displayed the results of the previous iteration too when asking of we want to apply the changes.
To post a comment you must log in.
not very useful: the results you want to compare are visual (with undo/redo) and not the numbers. A lower RMS is not automatically associated with a better outcome.