Hugin should include control point errors in pto files

Bug #679855 reported by Brent Townshend
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hugin
Triaged
Wishlist
Unassigned

Bug Description

It would be nice if hugin and autooptimiser would include 'C' lines that give the control point errors after optimization. It is useful information to have in postprocessing to determine which control points to prune by other software and shouldn't make a difference to other programs since PTOptimizer already does this.

It would also be useful in that when hugin reloads a PTO file, it would have all the distances already available.

Revision history for this message
Brent Townshend (bst) wrote :

Logged In: YES
user_id=1934048
Originator: YES

Actually, what I meant was not the 'C' lines, but the control point comments that include the RMS error.

Revision history for this message
vossman77 (vossman77-users) wrote :

Logged In: YES
user_id=855267
Originator: NO

I second this, I had over 4000 control points. How I am supposed to go through and find the dozen bad points that are screwing up my optimization.

Revision history for this message
vossman77 (vossman77-users) wrote :

Logged In: YES
user_id=855267
Originator: NO

Actually, I found the "Control Point table". Just what I was looking for...

Revision history for this message
rew (r-e-wolff) wrote :

I agree, Saving the control point accuracy can benefit some automatic processing.

Changed in hugin:
importance: Undecided → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.