Search results

• Geocpset
  ...geocpset''' should only used with projects which have assigned rough image positions. * Then assign rough positions to images with [[pto_var]]
  2 KB (304 words) - 22:22, 5 November 2015

• File:Lens rayfan.gif ...o<sub>1</sub>''' and '''o<sub>2</sub>''' are the distances from the object positions '''0<sub>1</sub>''' and '''0<sub>2</sub>''' to the principal plane '''P''' ...'i<sub>1</sub>''' and '''i<sub>2</sub>''' are the distances from the image positions '''I<sub>1</sub>''' and '''I<sub>2</sub>''' to the principal plane '''P'''' (869 × 401 (9 KB)) - 17:28, 2 August 2021

• File:Lens construct.gif ...o<sub>1</sub>''' and '''o<sub>2</sub>''' are the distances from the object positions '''0<sub>1</sub>''' and '''0<sub>2</sub>''' to the principal plane '''P''' ...'i<sub>1</sub>''' and '''i<sub>2</sub>''' are the distances from the image positions '''I<sub>1</sub>''' and '''I<sub>2</sub>''' to the principal plane '''P'''' (869 × 401 (7 KB)) - 17:29, 2 August 2021

• Talk:Hugin Camera and Lens tab
  It seemed like a good idea at the time. One or two of them were in awkward positions because there is no heading for the first few paragraphs in each page. Mayb
  369 bytes (67 words) - 11:33, 8 May 2007
• Hugin Optimizer tab
  === Positions (incremental, starting from anchor) === === Positions (y,p,r) ===
  10 KB (1,683 words) - 17:34, 5 March 2013
• Optimization
  positions relative to the background in successive shots. Clearly, The optimizer will never change the positions of the points in the
  6 KB (1,004 words) - 15:52, 16 April 2009
• Image positioning model
  {{Glossary|A mathematical model that accounts for the image positions in a panorama}} Relative image positions are usually obtained by [[control points]] in the [[optimization]] step of
  3 KB (530 words) - 10:38, 16 December 2012
• Hugin Preview window
  ...[[roll]] and [[pitch]] of the input images without changing their relative positions, levelling the panorama in the process. This normally produces good result ...al transform''' to rotate the input images without changing their relative positions - Effectively this rotates the entire panorama.
  6 KB (1,042 words) - 22:14, 26 October 2015
• Hugin Photos tab
  * Edit the positions of the images in the final panorama. ** Reset positions
  25 KB (3,993 words) - 21:54, 2 August 2017
• Panorama tools
  | ''[[PTOptimizer]]'' || Optimizes positions and sizes of images using control-point data. ...view interpolator. Given two images of the same scene taken from different positions, this tool creates views from any intermediate position.
  4 KB (620 words) - 10:03, 22 May 2011
• Pto gen
  * '''-l | --linkstacks''' When given links the image positions in stacks.
  2 KB (287 words) - 12:17, 10 April 2022
• User:James Legg
  ...hot, so don't count those!". There is a possibility of taking the intended positions as they are given and showing a fast preview so the user is aware their set Unlike the nona GPU branch, the shaders that remap positions should not be compiled for every image, as this would be slow during update
  6 KB (1,087 words) - 00:21, 5 April 2009
• PTStereo
  ...face set. In addition, world coordinates of all feature points and camera positions are calculated and can be used for measurements. o World coordinates of camera positions are individually settable or can be calculated.
  5 KB (751 words) - 10:04, 22 May 2011
• Hugin Parameters for Control Point Detectors dialog
  This setting works only if the rough positions of the images are defined in the project. It tries to link all overlapping ...does not run on the stacks. In this case you can use linking of the image positions on the [[Hugin Images tab]].
  5 KB (874 words) - 11:48, 27 January 2013
• Hugin Main window old gui
  The table in the middle also shows the positions in the final scene for each of the images. These positions are actually angles for [[roll]], [[pitch]] and [[yaw]].
  10 KB (1,560 words) - 14:45, 30 January 2013
• Align a stack of photos
  * Select "Positions (y,p,r)" and "Optimise now!" in the [[Hugin Photos tab|Photos tab]].
  2 KB (337 words) - 11:00, 7 February 2015
• Pano12
  * [[PTOptimizer]] Optimizes positions and sizes of images using [[control points|control point]] data.
  2 KB (319 words) - 18:54, 15 December 2007
• Align image stack
  # Optimize positions and lens parameters ...ng the remapping step the lens distortion and the corrections of the image positions is done in one processing step.
  5 KB (835 words) - 18:14, 9 April 2024
• Vig optimize
  For this to work, photos first have to be aligned with correct relative positions and lens parameters. Hugin will compare randomly selected groups of pixels
  2 KB (377 words) - 11:57, 27 January 2013
• Cpclean
  Do only whole panorama cp checking and use current image positions for calculation of distance errors (skip optimisation of whole panorama):
  3 KB (442 words) - 16:14, 22 May 2022

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)