My comments, questions and enhancements

[thp]

>I've noticed this tendency myself.
>
Glad, that I'm not the only one, who encountered this issue.

>In the meantime, I would suggest that Hugin realize that there are
>disastrous results from optimization sometimes, and not even offer the
>user a chance to "Apply" those changes to the current project.  
>
Sounds good to me.

>If it could record a disaster/singularity flag in the pano or opts, then the
>Druid could try to explain how the user can get better results.
>
Then I only have the problem left, that the druid never has any proposal 
for me at the moment. Whenever I open the preview window the druid tells 
me that everything is OK with my pano.

>
>On Mon, 2003-11-10 at 16:47, Bruno Postle wrote:
>  
>
>>On Mon 10-Nov-2003 at 04:16:23 +0100, thp wrote:
>>    
>>
>>>(5) Bug? Whenever I optimive view (v) I get a nearly perfect image with 
>>>sensational deviation values far below 0! But this is the result of the 
>>>optimized focal length of 1000mm. Any ideas?
>>>      
>>>
>>PTOptimizer uses a process of trial-and-error to find the correct
>>parameters for FOV (field-of-view), roll, pitch, yaw, a, b, c, d & e.
>>
>>Sometimes is decides that it can fit all the images together
>>perfectly by making the FOV incredibly small - This isn't very
>>helpful.
>>
>>Basically, you have to be careful; you should already have a close
>>approximation of FOV and image position (roll, pitch & yaw) before
>>you optimise FOV.
>>    
>>