Panotoo...Variable(3)
π NAME π
Okay so bestie, welcome to Panotools::Script::Line::Variable β that's section 3 of the User Contributed Perl Documentation, and its whole entire job is Panotools optimisation variables. That's the assignment. That's the era. π
π¦ SYNOPSIS π¦
One or more parameters for optimisation form a 'v' line. Short, sweet, iconic. β¨
π DESCRIPTION π
Okay so before literally anything else, clock this: the 'v'-line must come after the 'i'-lines. Not before, not sandwiched, not "close enough." After. I don't make the rules, the parser does. π
'v'-line β after the'i'-lines. Periodt. π«Ά
Optimization variables are listed together with the image number, and that number starts at 0 β zero-indexed, main character energy, no cap. There can be several v-lines, so you're absolutely not limited to one. Go off. π₯
Here's the whole squad, exactly as the docs serve it:
y0 Optimize yaw in image 0
p1 Optimize pitch in image 1
r2 Optimize roll in image 2
v0 Optimize field of view in image 0
a2 Optimize lens correction parameter 'a' in image 2
b1
c1
d1
e1
g1
t1
X1 Optimize x-coordinate of image 1, only for PTStereo
Y2 Optimize y-coordinate of image 2, only for PTStereo
Z6 Optimize z-coordinate of image 6, only for PTStereo
TrX3 Optimise x-coordinate of image 3, mosaic/translation mode
TrY2 Optimise y-coordinate of image 2, mosaic/translation mode
TrZ1 Optimise z-coordinate of image 1, mosaic/translation mode
Tpp1 Optimise pitch of picture plane of image 1, mosaic/translation mode
Tpy1 Optimise yaw of picture plane of image 1, mosaic/translation mode
Little tour, because I love you: y0 is yaw, p1 is pitch, r2 is roll, v0 is field of view, and a2 is lens correction parameter 'a' β all with their image numbers. Then b1, c1, d1, e1, g1 and t1 justβ¦ show up with no description at all, and honestly? Respect. π
Then the special squads: X1, Y2 and Z6 are x/y/z-coordinates that are only for PTStereo, and the TrX3 / TrY2 / TrZ1 / Tpp1 / Tpy1 crew are all mosaic/translation mode only. iykyk. π
π photometric optimisation π
Additionally, photometric optimisation uses the same system β although heads up bestie, this is a secondary process and it is not simultaneous with geometric optimisation. So it's not doing both at once, okay? It's giving "after party, separate invite." π
Eev0 Optimise Exposure (Eev) for image 0
Er1 Optimise red multiplier for image 1
Eb1 Optimise blue multiplier for image 1
Ra0 Optimise EMoR camera response for image 0
Rb0 note usually all EMoR parameters are optimised at the same time
Rc0
Rd0
Re0
Va0 Optimise Vignetting 'Va' parameter for image 0, note usually only Vb, Vc, Vd are optimised
Vb0 Optimise Vignetting 'Vb' parameter for image 0
Vc0 Optimise Vignetting 'Vc' parameter for image 0
Vd0 Optimise Vignetting 'Vd' parameter for image 0
Vx1 Optimise Vignetting centre x-position for image 1
Vy1 Optimise Vignetting centre y-position for image 1
Not me pointing out the receipts in there: Rb0 carries a note that usually all EMoR parameters are optimised at the same time, and Va0 carries a note that usually only Vb, Vc, Vd are optimised. Read your notes, bestie, they're there for a reason. π
And the final boss rule: if a image has a parameter linked to another image, you only need to optimize the master. That's it. That's the whole thing. Slay. π
mwah π this lil page came from perl v5.42.0 and it's dated 2025-07-25, and yeah, the title gets truncated to Panotoo...Variable(3) because some things are simply too iconic to fit. bye bestie, go optimise something π¦πΈ
π¦ where this page comes from
- fedora 43: perl-Panotools-Script 0.29-20.fc43 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms