Output my own PTO file

[Jayhawk]

Hello,

I have developed some software to do some image manipulation. I am to
the point where I need to output my own PTO file. I have done some
looking around and haven't found a document which clearly states how
to do this (i.e., which parameters are which, required order,
assumptions, etc.). Could someone please point me to such a thing?

For instance, I have multiple images, each with their own sift feature
locations found, the process of finding matched sift features has been
completed, and now I need to output the sift features and found
matches to a PTO file so I can do further processing with Hugin tools.

Thank you for your time and assistance.
Chris

[Bruno Postle]

On Thu 11-Feb-2010 at 09:07 -0800, Jayhawk wrote:
>
>I have developed some software to do some image manipulation. I am to
>the point where I need to output my own PTO file. I have done some
>looking around and haven't found a document which clearly states how
>to do this (i.e., which parameters are which, required order,
>assumptions, etc.). Could someone please point me to such a thing?

The most up-to-date documentation is here, though this is a bit
terse: http://hugin.sourceforge.net/docs/nona/nona.txt

It is line-oriented, the first character of the line defines the
data type, and a series of key/attributes follows, each separated by
spaces. When image numbers are referenced, counting starts at '0'.

The order of lines is important, but the order of attributes within
the lines is not.

Every project needs one 'p-line' to define some attributes of the
'panorama' as a whole, and an 'i-line' for each input 'image'.

You need 'v-lines' to drive the optimiser and 'c-lines' define a
control point pair each. All other lines are not so interesting.

--
Bruno

[Jan Martin]

A crazy question:
Can one use a PTGui .pto file with hugin?
Or "translate" it into hugin project file?

--
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--
http://www.DIY-streetview.org

[Jayhawk]

Thanks, Bruno. I will dive into this and report back with any other
questions I may have. Your time and help are appreciated.
Chris

[Carl von Einem]

Although I don't know the difference between these two options, both
commands claim to open .pto, .ptp, .pts and .oto:
Menu File:
-> Open
-> Import project

Jan Martin schrieb am 11.02.10 22:05:

[Bruno Postle]

On Thu 11-Feb-2010 at 22:43 +0100, Carl von Einem wrote:

>Although I don't know the difference between these two options, both
>commands claim to open .pto, .ptp, .pts and .oto:
>Menu File:

> -> Open
> -> Import project

'Import project' is something Thomas added to the current trunk, you
can use it to merge another project with the current project. If
there are duplicate photos then only the control points are merged,
otherwise new photos just added to the list of images.

Maybe it should be called 'Merge', since 'Import' does imply opening
some alien file format.

--
Bruno

[Carl von Einem]

Thanks, I added your description to
<http://wiki.panotools.org/Hugin_Main_window#File>

And something like 'Merge with project...' is easier to understand than
importing...

Carl

Bruno Postle schrieb am 12.02.10 00:17:

[Lukáš Jirkovský]

Blender uses "append" for similar action (importing data from other
file to current scene).

[Nicolas Pelletier]

The file linked by Bruno references also the one from lib pano.

Here is a link

http://panotools.svn.sourceforge.net/viewvc/panotools/trunk/libpano/doc/Optimize.txt?view=markup

I'll come back with question about lens because I've yet been able to understand how hugin is able to have multiple lens number, but I don't see those in the pto.

nick

2010/2/12 Lukáš Jirkovský <l.jir...@gmail.com>

[Bruno Postle]

On Fri 12-Feb-2010 at 15:38 -0500, Nicolas Pelletier wrote:
>
> http://panotools.svn.sourceforge.net/viewvc/panotools/trunk/libpano/doc/Optimize.txt?view=markup

> I'll come back with question about lens because I've yet been able
> to understand how hugin is able to have multiple lens number, but
> I don't see those in the pto.

The lens numbers are implicit, Hugin derives them from shared image
parameters.

--
Bruno

[Nicolas Pelletier]

Thanks for the info

Can we therefore assume that the optimizer does the same?

As in if you have 10 images, but all "lens" parameters are equals in 3 distinct groups (i.e. 3 lens) then optimizing v3 e3 d3 will optimize those parameters for only the 3rd set of images sharing the same parameters, and keep them with the same value once optimized?

Thanks,

nick

--

[Bruno Postle]

On Sun 14-Feb-2010 at 15:27 -0500, Nicolas Pelletier wrote:
>
>As in if you have 10 images, but all "lens" parameters are equals in 3
>distinct groups (i.e. 3 lens) then optimizing v3 e3 d3 will optimize those
>parameters for only the 3rd set of images sharing the same parameters, and
>keep them with the same value once optimized?

Almost, the number always refers to an image number. The lens
number system (and the similar stack number in the trunk) is a
higher level abstraction presented by the Hugin GUI.

The optimiser and stitcher tools don't need it to do their job, they
link parameters between photos at the lower level of the '=3'
notation in the .pto files.

So b=3 in an i-line means "b-parameter is the same as image 3". b3
in a v-line tells the optimiser to "optimise b-parameter of image 3"
(and implicitely use the same value for other images that have b=3
in an i-line).

--
Bruno

[Nicolas Pelletier]

Excellent, I think that last explanation is what I was missing.

Thanks,

nick

--
Bruno