I have an update for fastPTOptimizer and also for the Windows installer for Hugin++ that also installs the binaries for fastPTOptimizer. When there are weights for CPs other than 1, say a weight 'w', it should be exactly as if you had 'w' CPs with weight 1 at the same position. In the old version of fastPTOptimizer the reported error during the optimization wasn't correct. If e.g. all weights are 1000, the reported error should be the same as if all weights were 1 since the error is an average over all CP's errors. In the old version the error was too high if weights > 1 were used. I have corrected it.
[email protected] schrieb am Donnerstag, 1. Juli 2021 um 12:14:54 UTC+2: > Apologies, I was wrong about this. Sourceforge does support the usual > fork/pull-request workflow, with both mercurial and git. > > -- > Bruno > > On 28 June 2021 20:51:13 BST, Bruno Postle wrote: > > >This is an illustration of our creaking infrastructure. Sourceforge > >doesn't support the fork/pull-request/merge workflow that we have > >become used-to with github/bitbucket, so anyone wanting to work > >separately on Hugin needs to create a new repository or create a > >branch in the main repository. Florian, do you need access to work on > >this in a Hugin branch? > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/2ba6afce-aaa2-440f-9c97-fa1b7ef98b35n%40googlegroups.com.
