hugin-devs team mailing list archive

[tmodes <1856351@xxxxxxxxxxxxxxxxxx>]

The photometric optimizer chooses by default 200 (random) points per
image for the optimization of the photometric parameters. Using every
pixel would be to computationally intensive. So for each invocation of
the photometric optimizer different points are used and therefore
different absolute errors result.

PS: This number can be tuned in the preferences.

** Changed in: hugin
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1856351

Title:
  Consecutive photometric optimizer runs produce different results

Status in Hugin:
  Invalid

Bug description:
  The report uses the same data with the same data import instructions
  as bug #1856336.

  Input data and evidence can be found in
  https://cloud.mail.ru/public/3Xz6/4wnVcSp1c web folder.

  Input .NEF files were imported the usual way. Then control points were
  found automatically - see 'photometric_optimizer_report_1.png' file
  for details in the above web folder.

  Then geometric optimizer was run - see
  'photometric_optimizer_report_1.png' file for details in the above web
  folder.

  Then photometric optimizer was run 6 times (i.e. Optimize ->
  Photometrics - choose "Low dynamic range", click "Calculate").

  Screenshot was taken after each run - see
  'photometric_optimizer_report_1.png' ..
  'photometric_optimizer_report_6.png' files in the above web folder. As
  one can see from screenshots the reported values are 8.46, 7.52, 8.50,
  11.37, 7.63, 10.92.

  Since nothing was changed between the runs I expect the same data to
  be reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1856351/+subscriptions