On 19 Mai, 20:51, Marie-Noëlle Augendre <
mnaugen...@gmail.com> wrote:
> 2012/5/19 kfj <_...@
yahoo.com>
> > I'd be cautious with that claim; I'd say the best
> > calibtation results are still to be had from a 360X180 with lots of
> > overlap, even if you have to do a few dozen shots for it - you'd do
> > that with the widest-angle setting you have and you can use these
> > images as a reference later on when you use longer lens settings and
> > can only manage a section of the full 360X180. Or. alternatively, you
> > can walk the path of the straight lines.
>
> What do you mean by 360x180?
I mean a full spherical 360 by 180 degrees panorama. Covering the
whole sphere allows you to precisely measure the field of view, and if
the images overlap well, say by 50 percent, and you have created lots
of control points by using the appropriate cpfind parameters (I
recommend using cpfind with these parameters for the purpose: --
fullscale --sieve2size 5 -o %o %s), just optimizing the lot will give
you good lens distortion parameters to work with. Then you have a
reference to 'pin' the longer lens images to - you can just put them
into the same project. But all of this has to be done in a proper
panorama setup, with a well set-up panorama head. Freehand panoramas
won't really do for calibration.
Anyway, it's all in the various tutorials, just browse for a technique
you like. Using lines is fine as well, but keep in mind that if you
want to work from lines you need lots of control points well
distributed over the whole image. Linefind is quite a new tool, and it
may just not work for you. If necessary, you'll have to add manual
line control points, which isn't too hard.
> > In the optimizer tab, switch to user-defined parameters. Uncheck
> > everything apart from the values you want, probably you will want
> > v,a,b, and c - only for the TIFF made from the RAW image, while the
> > other image, which you claim to be correct, should have these set to
> > the correct fov for v and zero for a,b, and c. Then optimize.
>
> I ended up doing just this. I got a set of a-b-c parameters for 7 different
> focals, but the result is not so nice; I don't know whether the problem is
> with Hugin, or with the other programs using the LensFun database.
I can't judge that either, but again I ask you to make sure you really
have many, and well-distributed control points. If you work from
lines, a few dozen isn't too much, and if you work with point control
points in panoramas, something like a hundred per image pair is a good
idea. You may also consider not to do a,b and c (like, you could try
omit c or just optimze for b by itself for a start and this may
already be quite good). And mabe you have to include lateral shift (d
and e) to get things right.
And if you work from a panorama, try and find something which has rich
content all around, like an ornate building from the inside.
Calibration sounds straightforward in theory, but it is quite an
involved process and may take you some time to get right, and there
isn't even a guaranty your results will be as good as you'd wish them
to be. It's definitely a fair amount of work for a zoom lens. Stick
with it, and don't hesitate to come back for more help.
What system are you on?
Kay