[hugin-ptx] Hugin Version 2009.4.0.4597 strange error
I have a strange error when I try to preview a quite large project ... CacheEntry: 1last access: 5 8bit: 1 16bit: 1 float: 1 mask: 1 purged: 0 MB, memory used for images: 158 MB ContractViolation: Precondition violation! BasicImage::upperLeft(): image must have non-zero size. (/home/gerald/hugin/hugin-RC1/hugin-2009.4.0/src/foreign/vigra/vigra/ basicimage.hxx:857) ERROR: 22:09:19.794038 (/home/gerald/hugin/hugin-RC1/hugin-2009.4.0/ src/hugin1/hugin/PreviewPanel.cpp:489) updatePreview(): error during stitching: Precondition violation! BasicImage::upperLeft(): image must have non-zero size. (/home/gerald/hugin/hugin-RC1/hugin-2009.4.0/src/foreign/vigra/vigra/ basicimage.hxx:857) ContractViolation: Precondition violation! BasicImage::upperLeft(): image must have non-zero size. (/home/gerald/hugin/hugin-RC1/hugin-2009.4.0/src/foreign/vigra/vigra/ basicimage.hxx:857) ERROR: 22:09:21.944475 (/home/gerald/hugin/hugin-RC1/hugin-2009.4.0/ src/hugin1/hugin/PreviewPanel.cpp:489) updatePreview(): error during stitching: Precondition violation! BasicImage::upperLeft(): image must have non-zero size. (/home/gerald/hugin/hugin-RC1/hugin-2009.4.0/src/foreign/vigra/vigra/ basicimage.hxx:857) Processus arrêté On a AMD Phenom 6g of ram -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Unsteadiness problem about panomatic and Autopano-sift-C
I use panomatic and Autopano-sift-C (written below )to generate the init pto file using the same input images, The generated pto file sometimes is OK,but sometimes is disqualified panomatic --output Output.pto --fullscale --ncores 4 --sieve2width 5 --sieve2height 5 --sieve2size 2 leftImage.jpg rightImage.jpg (Autopano-sift-C --ransac on --refine-by-middle Output.pto leftImage.jpg rightImage.jpg) Sometimes part of the generated pto file is like: # input images: #-imgfile 640 480 leftImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d0 e0 v50 a0 b0 c0 #-imgfile 640 480 rightImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d=0 e=0 v=0 a=0 b=0 c=0 and this will fail when I use the autooptimiser or nona on this pto file And sometimes part of the generated pto file is like: # image lines #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a0 b-0.0404700058313363 c0 d0 e0 g0 p13.7544483408515 r1.49156376203419e-022 t0 v50 y-6 Vm5 u10 nleftImage.jpg #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a=0 b=0 c=0 d=0 e=0 g0 p17.1491715564502 r2.20989737925425e-012 t0 v=0 y5.03358945449259 Vm5 u10 nrightImage.jpg and this will be OK when I use the autooptimiser or nona on this pto file How to handle this problem? Thanks! Bob -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Unsteadiness problem about panomatic and Autopano-sift-C
Hi Bob, Which is generating the problem? Panomatic? Both? Can you add the output of the tool causing the problem? I know for a fact that Panomatic is memory thirsty; depending on if I'm running full scale images or not, I have to limit myself to 1 or 2 cores (i.e. 1 or 2 images loaded at the same time max). if I go over that, it will blow the 2 gig limit of a 32 bit process and the resulting pto will crash hugin. (this is itching me a lot lately). The test is simple, change ncores to 1 and retest, and then ncores to 4 and retest. in both cases, follow the memory usage of the process. Hope this helps! nick On Thu, Nov 12, 2009 at 11:10 PM, Bob boo...@gmail.com wrote: I use panomatic and Autopano-sift-C (written below )to generate the init pto file using the same input images, The generated pto file sometimes is OK,but sometimes is disqualified panomatic --output Output.pto --fullscale --ncores 4 --sieve2width 5 --sieve2height 5 --sieve2size 2 leftImage.jpg rightImage.jpg (Autopano-sift-C --ransac on --refine-by-middle Output.pto leftImage.jpg rightImage.jpg) Sometimes part of the generated pto file is like: # input images: #-imgfile 640 480 leftImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d0 e0 v50 a0 b0 c0 #-imgfile 640 480 rightImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d=0 e=0 v=0 a=0 b=0 c=0 and this will fail when I use the autooptimiser or nona on this pto file And sometimes part of the generated pto file is like: # image lines #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a0 b-0.0404700058313363 c0 d0 e0 g0 p13.7544483408515 r1.49156376203419e-022 t0 v50 y-6 Vm5 u10 nleftImage.jpg #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a=0 b=0 c=0 d=0 e=0 g0 p17.1491715564502 r2.20989737925425e-012 t0 v=0 y5.03358945449259 Vm5 u10 nrightImage.jpg and this will be OK when I use the autooptimiser or nona on this pto file How to handle this problem? Thanks! Bob -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Unsteadiness problem about panomatic and Autopano-sift-C
Thanks Nick, Both of panomatic and Autopano-sift-C exist the problem. I did as you said. and the generated pto is the same. # oto project file generated by Panomatic # input images: #-imgfile 640 480 leftImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d0 e0 v50 a0 b0 c0 #-imgfile 640 480 rightImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d=0 e=0 v=0 a=0 b=0 c=0 # Control points: c n0 N1 x256.556 y112.81 X132.59 Y147.572 # Control Point No 0: 1.0 c n0 N1 x256.025 y117.097 X131.863 Y151.566 # Control Point No 2: 1.0 And here is part of the running information: ... --- Find matches --- i0 i1 : Find Matches... i0 i1 : Found 50 matches. i0 i1 : RANSAC Filtering... i0 i1 : Removed 0 matches. 50 remaining. i0 i1 : Clustering matches... i0 i1 : Kept 27 matches. --- Write output --- Detection took 1.062 seconds. ... But this time when I use autooptimiser to process the generated pto file,it generated a correct pto file # hugin project file #hugin_ptoversion 2 p f0 w725 h725 v72 E0 R0 nTIFF_m c:NONE m g1 i0 f0 m2 p0.00784314 # image lines #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a0 b-0.038470283676702 c0 d0 e0 g0 p13.8033624433412 r-4.09392475350606e-016 t0 v50 y-6 Vm5 u10 nleftImage.jpg #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a=0 b=0 c=0 d=0 e=0 g0 p17.2018422504829 r-7.49134445880203e-015 t0 v=0 y5.03730259236181 Vm5 u10 nrightImage.jpg # specify variables that should be optimized v b0 v p1 r1 y1 v # control points c n0 N1 x256.556 y112.81 X132.59 Y147.572 t0 c n0 N1 x256.025 y117.097 X131.863 Y151.566 t0 ... Do I need to use autooptimiser everytime I used panomatic and Autopano- sift-C?? On 11月13日, 下午12时21分, Nicolas Pelletier nicolas.pellet...@gmail.com wrote: Hi Bob, Which is generating the problem? Panomatic? Both? Can you add the output of the tool causing the problem? I know for a fact that Panomatic is memory thirsty; depending on if I'm running full scale images or not, I have to limit myself to 1 or 2 cores (i.e. 1 or 2 images loaded at the same time max). if I go over that, it will blow the 2 gig limit of a 32 bit process and the resulting pto will crash hugin. (this is itching me a lot lately). The test is simple, change ncores to 1 and retest, and then ncores to 4 and retest. in both cases, follow the memory usage of the process. Hope this helps! nick On Thu, Nov 12, 2009 at 11:10 PM, Bob boo...@gmail.com wrote: I use panomatic and Autopano-sift-C (written below )to generate the init pto file using the same input images, The generated pto file sometimes is OK,but sometimes is disqualified panomatic --output Output.pto --fullscale --ncores 4 --sieve2width 5 --sieve2height 5 --sieve2size 2 leftImage.jpg rightImage.jpg (Autopano-sift-C --ransac on --refine-by-middle Output.pto leftImage.jpg rightImage.jpg) Sometimes part of the generated pto file is like: # input images: #-imgfile 640 480 leftImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d0 e0 v50 a0 b0 c0 #-imgfile 640 480 rightImage.jpg o f0 y+0.00 r+0.00 p+0.00 u20 d=0 e=0 v=0 a=0 b=0 c=0 and this will fail when I use the autooptimiser or nona on this pto file And sometimes part of the generated pto file is like: # image lines #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a0 b-0.0404700058313363 c0 d0 e0 g0 p13.7544483408515 r1.49156376203419e-022 t0 v50 y-6 Vm5 u10 nleftImage.jpg #-hugin cropFactor=1 i w640 h480 f0 Eb1 Eev0 Er1 Ra0 Rb0 Rc0 Rd0 Re0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 a=0 b=0 c=0 d=0 e=0 g0 p17.1491715564502 r2.20989737925425e-012 t0 v=0 y5.03358945449259 Vm5 u10 nrightImage.jpg and this will be OK when I use the autooptimiser or nona on this pto file How to handle this problem? Thanks! Bob -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.comhugin-ptx%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx- 隐藏被引用文字 - - 显示引用的文字 - -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Command lines to make a panorama
Thanks Bruno, HFOV is the horizontal angle of view (or Horizontal Field Of View) of the photo. This can often be calculated from the camera EXIF metadata, but some cameras don't write enough information to the photo, and some photo editing software discards EXIF data. How to calculate the HFOV? Can PanoTools or Hugin calculate ? I generate the init pto file using the Autopano-sift-C, but when I use autooptimiser to process the init pto file,I got the same error: HFOV of image leftImage.jpg invalid, trying to read EXIF tags Unable to read EXIF data from opened file:leftImage.jpg EXIF reading failed, please specify HFOV with -v Cheers! Bob On 11月11日, 上午4时58分, Bruno Postle brunopos...@googlemail.com wrote: 2009/11/10 Bob boo...@gmail.com Is there any more steps to get a more optimized panorama? panomatic --output Output.pto --fullscale --ncores 4 --sieve2width 5 --sieve2height 5 --sieve2size 2 leftImage.jpg rightImage.jpg (Autopano-sift-C --ransac on --refine-by-middle Output.pto leftImage.jpg rightImage.jpg) You could use ptomerge to combine control points from both panomatic and autopano-sift-c. You can use cpclean and/or celeste_standalone to remove 'bad' control points before optimisation. autooptimiser -o OutputOptim.pto -a -l -s Output.pto nona -o out -m TIFF_m OutputOptim.pto leftImage.jpg rightImage.jpg enblend -o finished.tif out.tif out0001.tif out0002.tif BTW,the autooptimiser sometimes failed and says: HFOV of image leftImage.jpg invalid, trying to read EXIF tags Unable to read EXIF data from opened file:leftImage.jpg EXIF reading failed, please specify HFOV with -v HFOV is the horizontal angle of view (or Horizontal Field Of View) of the photo. This can often be calculated from the camera EXIF metadata, but some cameras don't write enough information to the photo, and some photo editing software discards EXIF data. -- Bruno -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
