Dmg,
If I am running an optimization using Autooptimize using the new Tilt
parameters in the new panotools version, what is the parameter syntax in the
pto-file?
Cheers
/O
2009/9/11 Oskar Sander
>
>
> 2009/9/10 dmg
>
>>
>> to be honest, I am not sure how much they will help for a mosaic. The
2009/9/10 dmg
>
> to be honest, I am not sure how much they will help for a mosaic. The
> model for panos in libpano
> is still spherical. But it is a matter of trying.
>
> scale scales the tilt operations only. It actually scales the view
> point from which the photo was originally taken.
>
> --
Thanks Dev for your work.
BTW, this is now integrated into libpano HEAD.
On Thu, Sep 10, 2009 at 11:53 AM, dev g wrote:
> I committed my changes here:
> http://panotools.svn.sourceforge.net/viewvc/panotools/branches/libpano_gsoc2009_mosaic/
>
> On Wed, Sep 9, 2009 at 11:27 PM, Yuval Levy wrote
I committed my changes here:
http://panotools.svn.sourceforge.net/viewvc/panotools/branches/libpano_gsoc2009_mosaic/
On Wed, Sep 9, 2009 at 11:27 PM, Yuval Levy wrote:
>
> dmg wrote:
> >> Hello,
> >>
> >> I am confused. Would one not be able to continue development in the
> >> same branch that
Here are examples of the use:
This photo was not remapped:
But this one was:
http://turingmachine.org/~dmg/temp/floorInput.jpg
and this is the output, merged (difference mode):
http://turingmachine.org/~dmg/temp/merged.jpg
It was optimized using:
# specify variables that should be optimize
On Wed, Sep 9, 2009 at 23:03, D M German wrote:
> I have the inverse transformations done. they are described here:
>
> http://turingmachine.org/~dmg/temp/tiltEq.pdf
>
> I am struggling with the inverse ones. If anybody wants to help, I'll be
> grateful. This is the only roadblock to have an alph
> When assembling a "mosaic" camera position imagine subject beeing a plane
> Xs-Ys with Zs constant, and camera moved across a paralell plane X-Y
> (with Z=0). What would these parameter represent?
>
> * shearX,shearY = camera position in the camera plane, this would be
> different f
Nice work guys!
2009/9/9 D M German
>
>
> Now, the real question for hugin developers: can somebody create a
> branch of hugin that supports these new parameters during the
> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
>
>
>
So trying to mentally picture these parameters in
On Sep 9, 2009, at 10:56 PM, dmg wrote:
>
>> Hello,
>>
>> I am confused. Would one not be able to continue development in the
>> same branch that Dev made the initial changes in? Why is another
>> branch needed? I apologize if I am missing something obvious.
>>
>> Gerry
>
> are you talking
dmg wrote:
>> Hello,
>>
>> I am confused. Would one not be able to continue development in the
>> same branch that Dev made the initial changes in? Why is another
>> branch needed? I apologize if I am missing something obvious.
>>
>> Gerry
>
> are you talking libpano or hugin?
Dev never committ
> Hello,
>
> I am confused. Would one not be able to continue development in the
> same branch that Dev made the initial changes in? Why is another
> branch needed? I apologize if I am missing something obvious.
>
> Gerry
are you talking libpano or hugin?
-dmg
--~--~-~--~~-
On Sep 9, 2009, at 4:03 PM, D M German wrote:
>
>
>
> Now, the real question for hugin developers: can somebody create a
> branch of hugin that supports these new parameters during the
> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
>
>
> I haven't committed my code but wi
On Wed 09-Sep-2009 at 19:27 -0400, Yuval Levy wrote:
>dmg wrote:
>>> how does this interact with James' new layout (the "j" parameters in the
>>> .pto files) ?
>>
>> Is this read by libpano tools? I doubt it. In that case, not at all.
>
>should it be read by libpano tools?
The 'j' parameter is re
Remember that the PTO files are not compatible with libpano. One needs
to use the export feature in
hugin.
On Wed, Sep 9, 2009 at 4:27 PM, Yuval Levy wrote:
>
> dmg wrote:
>>> how does this interact with James' new layout (the "j" parameters in the
>>> .pto files) ?
>>
>> Is this read by libpano
dmg wrote:
>> how does this interact with James' new layout (the "j" parameters in the
>> .pto files) ?
>
> Is this read by libpano tools? I doubt it. In that case, not at all.
should it be read by libpano tools?
Yuv
--~--~-~--~~~---~--~~
You received this messa
On Wed, Sep 9, 2009 at 3:09 PM, Yuval Levy wrote:
>
> D M German wrote:
>> Now, the real question for hugin developers: can somebody create a
>> branch of hugin that supports these new parameters during the
>> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
>
> how does this inte
D M German wrote:
> Now, the real question for hugin developers: can somebody create a
> branch of hugin that supports these new parameters during the
> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
how does this interact with James' new layout (the "j" parameters in the
.pto
Thank you sooo much Dev and Daniel. I've been waiting for this for s long.
> From: d...@uvic.ca
> To: hugin-ptx@googlegroups.com
> To: panotools-de...@lists.sourceforge.net
> Subject: [hugin-ptx] Tilt transformation...
> Date: Wed, 9 Sep 2009 14:03:06 -0700
>
>
>
> (this code was brought
>
> and this is a photo of the same place taken:
>
> http://turingmachine.org/~dmg/temp/floorInput.jpg
sorry:
http://turingmachine.org/~dmg/temp/floor.jpg
And we should thank Dev and Google for this feature. I think it will go
a long way into making the nadir photos easier.
--
Daniel M. G
19 matches
Mail list logo
