Preamble. I find that sometimes when I launch Optimise for the first time on a new project it will run for a very long time. I think this has only started being a problem in the last year or so ... sorry I can't be more specific as to which version it started happening.
Usually I interrupt it and check control points by "human" removing the outliers and then start it again. However I assume that until Optimise has run for the first time the distance figures are not so helpful for finding those outliers. Sometimes if I am not in a rush I get on with other work and leave Hugin/Optimise running in the background. If it is the last job of the day I will leave it running overnight and it will usually have finished by breakfast time. Current Project Last weekend I left an optimise session running and so far it has clocked up more than 70 hours of processor time. Most of the time it is keeping one core 100% busy. Hugin is ocupying 500Mb of RAM and 1Gb of Virtual Memory. The running-commentary pop-up tells me that Optimise is on Strategy 2 and has completed 18 iterations. I THINK it takes longer for one iteration the longer it runs ... but that is just an impression I have not been systematic in recording its progress. The image set is 8 stacks of 3x bracked-exposures each image is a 70Mb 16-bit TIF. I am using Harry's recent build for the Mac (2011.5.0.5723) on a Mac Pro with a 2.8 Ghz Quad Core Xeon processor with 12Gb of RAM. So I don't think the problem is that it is short of processing power. Questions, Conclusions, Suggestions a) do other people notice this? Is it only on 16-bit TIFF files? Is it only on MacOS-X? b) would it be possible for Optimise to make some sort of check either initially or between iterations, perhaps something like: - if this is the first time it has been run on this project and there are extreme outliers amongst the control points stop after two or three iterations and suggest that the user removes the outlying control points. OR - At the end of an iteration if a control point distance is more than X (more than x% away from the average?) and hasn't changed more than y % in that iteration then start to ignore it c) As well as a "Cancel" button could the Optimise running-commentary pop-up offer an option "Stop after current Iteration" which would tidy up the processing and update the control point distances at the end of the current iteration rather than abandon the work done so far ... which is what I assume happens with "Cancel" -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
