[hugin-ptx] Re: hugin eats up to 12Gb of RAM and freezes system
Hi James, I haven't seen change yet, but can the warning (or maybe it already does) contain predicted output size and information what to do if this is not intentional ? For example: Warning output canvas size is 98x98 if this is not Your intention, use Sticher tab and set a different output image size then press Stich Now to create panorama. I guess it's not possible to calculate how much memory algorithm will use ? I agree that not everyone's intention is to scale down panorama, so information about size of canvas or better if possible the approximate memory that algorithm will use, would help to tune those parameters. For example I would be able to set slightly smaller canvas in Sticher Tab, but still larger than it is by default and be able to compute it in rational time without freezing my system and running out of both swap and ram. Maybe something checking available system memory and comparing it to what algorithm can use, would also be helpful. I would really like to make as precise as possible output picture, but in feasible time on my hardware and without blocking entire OS. Thanks for fixing this ! On Oct 12, 1:16 am, James Legg lankyle...@gmail.com wrote: On Sun, 2010-10-10 at 14:18 -0700, Mateusz wrote: I think, that it should not use entire memory 12Gb at once. The algorithm should be aware that there are machine limitations and should not allocate all possible memory even if the size of canvas is absurdity. For me the correct behaviour would be allocating less memory and freeing it when done, doing things at steps. This would help with large stitches, but I don't think all large stitches are intentional. For instance if I take a 360 degree equirectangular panorama then just change the projection to stereographic, Hugin sets the horizontal field of view to 359 degrees. Stereographic projection cannot contain 360 degrees, but I wouldn't want it to crop my image unexpectedly. Pressing Create panorama on the assistant tab now would try to make an image likely to be hundreds of gigapixels, where only the very middle has enough image data. But I wouldn't want Hugin to lose precession unexpectedly either. If I notice that it looks bad in the preview, and understand why, I might lower the field of view to contain only the bits I want. However, it could look reasonable in the preview and still make images over a gigapixel in size, where only the very middle has enough data. These size images are difficult to store, display, and print too. Also if this is not possible, then at least there should be a confirmation dialog, Do You really want to do that ... or You wanted this... and then choose. Anyway much better solution would be fixing algorithm then interface if possible. I added a warning for very large panoramas. I think fixing the interface includes making users aware of the practical limits of the projections, which is important to this issue. On Oct 10, 10:37 pm, Bruno Postle br...@postle.net wrote: It is a bug (because Hugin should stop you from doing this), but also the correct behaviour for what you are asking Hugin to do. The Assistant resets the pixel dimensions of the canvas to best fit the data. In particular it ensures that the canvas is big enough to represent all the detail without any part being downscaled. A 350° wide stereographic panorama probably really does need to be rendered with hundreds of gigapixels, otherwise the middle section has much less detail than the original photos - You really don't intend to lose information do you? -James -- 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] Re: hugin eats up to 12Gb of RAM and freezes system
On Tue, 2010-10-12 at 10:19 -0700, Mateusz wrote: Hi James, Thanks for the fix, but I still don't understand: How 3x 4288x2488 pixel images end up with 960 giga pixels which is 960 000 000 000 pixels image. For me making a square from those 3 images: 3x width and 3x height = 12864x7464 = 96 016 896 pixels. Aligning them should not take more space right ? In Your case its 9998 times more... Am I correct ? The mapping between image projections does not necessarily preserve area, and currently Hugin preserves the pixel density in the middle of the image. Very wide stereographic or rectilinear output projections, for example, will tend to put the detail in the middle, and the outside will get really stretched. If you preserve the original images' quality in the middle, the outside will be very enlarged, taking up much more space than the corresponding part of the input images. With a stereographic projection, as you approach 360 degrees the output size approaches infinity. With rectilinear projection, as you approach 180 degrees, the output size approaches infinity. Output projections such as fisheye and equirectangular can contain 360 degrees without requiring an infinitely big image to display all the input at full quality. If you move the horizontal field of view slider at the bottom of the fast preview with a rectilinear or stereographic output, you can see the middle gets squashed into a tiny part of the image as you near the limits of the projection. 960 gigapixels is possible for a full resolution really wide stereographic panorama, but I made up that figure by keeping to your 98x98 canvas size example from an earlier mail. -James -- 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] Re: hugin eats up to 12Gb of RAM and freezes system
On Sun, 2010-10-10 at 14:18 -0700, Mateusz wrote: I think, that it should not use entire memory 12Gb at once. The algorithm should be aware that there are machine limitations and should not allocate all possible memory even if the size of canvas is absurdity. For me the correct behaviour would be allocating less memory and freeing it when done, doing things at steps. This would help with large stitches, but I don't think all large stitches are intentional. For instance if I take a 360 degree equirectangular panorama then just change the projection to stereographic, Hugin sets the horizontal field of view to 359 degrees. Stereographic projection cannot contain 360 degrees, but I wouldn't want it to crop my image unexpectedly. Pressing Create panorama on the assistant tab now would try to make an image likely to be hundreds of gigapixels, where only the very middle has enough image data. But I wouldn't want Hugin to lose precession unexpectedly either. If I notice that it looks bad in the preview, and understand why, I might lower the field of view to contain only the bits I want. However, it could look reasonable in the preview and still make images over a gigapixel in size, where only the very middle has enough data. These size images are difficult to store, display, and print too. Also if this is not possible, then at least there should be a confirmation dialog, Do You really want to do that ... or You wanted this... and then choose. Anyway much better solution would be fixing algorithm then interface if possible. I added a warning for very large panoramas. I think fixing the interface includes making users aware of the practical limits of the projections, which is important to this issue. On Oct 10, 10:37 pm, Bruno Postle br...@postle.net wrote: It is a bug (because Hugin should stop you from doing this), but also the correct behaviour for what you are asking Hugin to do. The Assistant resets the pixel dimensions of the canvas to best fit the data. In particular it ensures that the canvas is big enough to represent all the detail without any part being downscaled. A 350° wide stereographic panorama probably really does need to be rendered with hundreds of gigapixels, otherwise the middle section has much less detail than the original photos - You really don't intend to lose information do you? -James -- 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: hugin eats up to 12Gb of RAM and freezes system
Sorry, This is not a projection I am trying to make. nona freezes my system with those three files. I also managed to make a linear assemble of my images, however when I turn projection in preview to stereographic and I move a bit ONLY image on axis (without moving those sliders at bottom and left) and then I try to make panorama it just eats all my swap and all RAM. For me this is bug of nona which is included in hugin package. I am attaching project file. http://groups.google.com/group/hugin-ptx/web/DSC0767-DSC0775-fail.pto My system is Debian (sid) ii hugin 2010.2.0+dfsg~rc2-1 ii hugin-data 2010.2.0+dfsg~rc2-1 ii hugin-tools 2010.2.0+dfsg~rc2-1 ii libpano13-1 2.9.14-3 ii libpano13-2 2.9.17+dfsg-2 ii libpano13-bin 2.9.17+dfsg-2 ii autopano-sift-c 2.5.0-0.1 ii enblend 4.0+dfsg-1 On Oct 9, 4:05 pm, Michal Bulik michal.bu...@free.fr wrote: Hi, I could assemble the 3 files in a few minutes with no manual tweaking and I've only 4 Gb of RAM (.pto file attached). Tymczasem, michal PS. My system is a Debian testing 64 bit with the following versions : ii autopano-sift-c 2.5.0-0.1 Automatically create control points for panorama image ii enblend 4.0+dfsg-1 image blending tool ii hugin 2010.0.0+dfsg-3+b1 GUI tools for Hugin Those are my files http://hugin-ptx.googlegroups.com/web/_DSC0767.JPG?gda=aQgrVT4yzV... http://hugin-ptx.googlegroups.com/web/_DSC0771.JPG?gda=qeE3qT4yzV... http://hugin-ptx.googlegroups.com/web/_DSC0775.JPG?gda=-s613D4yzV... On Oct 9, 12:12 pm, Bart van Andelbavanan...@gmail.com wrote: Your assumptions are wrong: it's not Hugin which is using up all your memory, it's either Nona, or more likely, Enblend. These are the external programs which are used by Hugin to create the warped images and to merge them together into a panorama. Hugin itself doesn't use that much memory with the amount of images you have fed into it. So unless it's a bug, I suspect you are trying to stitch the panorama at an enormous resolution. Please check the output size at the stitcher tab and report back. -- Bart DSC0767-DSC0775.pto 5KViewDownload -- 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: hugin eats up to 12Gb of RAM and freezes system
Mateusz mateusz.ka...@gmail.com wrote: Sorry, This is not a projection I am trying to make. nona freezes my system with those three files. I also managed to make a linear assemble of my images, however when I turn projection in preview to stereographic and I move a bit ONLY image on axis (without moving those sliders at bottom and left) and then I try to make panorama it just eats all my swap and all RAM. For me this is bug of nona which is included in hugin package. I am attaching project file. http://groups.google.com/group/hugin-ptx/web/DSC0767-DSC0775-fail.pto [...] When I open this pto file and use Stitch Now nona works without problem. I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. thanks cu andreas -- 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: hugin eats up to 12Gb of RAM and freezes system
1) Align those images 2) When I want to create panorama in a linear form it works 3) Go to preview GL 4) Go to projection and change it to Stereographic 5) Go to move tab 6) Make move the projection so it will create a half sphere. 7) Close preview window 8) Create panorama again in Assistant Tab This eats all memory with nona in both CPU or GPU variants. Hard reboot is needed. On Oct 10, 3:01 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: Mateusz mateusz.ka...@gmail.com wrote: Sorry, This is not a projection I am trying to make. nona freezes my system with those three files. I also managed to make a linear assemble of my images, however when I turn projection in preview to stereographic and I move a bit ONLY image on axis (without moving those sliders at bottom and left) and then I try to make panorama it just eats all my swap and all RAM. For me this is bug of nona which is included in hugin package. I am attaching project file. http://groups.google.com/group/hugin-ptx/web/DSC0767-DSC0775-fail.pto [...] When I open this pto file and use Stitch Now nona works without problem. I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. thanks cu andreas -- 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] Re: hugin eats up to 12Gb of RAM and freezes system
I'd start hugin from a command line. This might give some clue as to what's happening. Or use strace. This is of course if you can get to a term session on F4. I'd expect to have new *deb binaries sometime this afternoon. Ubuntu 10.04. Debian users have used them with success. An alternative is to try http://www.tatteredmoons.org/hugin/deb/ubuntu/10.04/20100915/20100915.html. Purge your other hugin debs b4 u do. I tried your three pics on my system, and they worked great. I haven't tried your procedure, but I'll try that later today. Dale Date: Sun, 10 Oct 2010 07:43:38 -0700 Subject: [hugin-ptx] Re: hugin eats up to 12Gb of RAM and freezes system From: mateusz.ka...@gmail.com To: hugin-ptx@googlegroups.com 1) Align those images 2) When I want to create panorama in a linear form it works 3) Go to preview GL 4) Go to projection and change it to Stereographic 5) Go to move tab 6) Make move the projection so it will create a half sphere. 7) Close preview window 8) Create panorama again in Assistant Tab This eats all memory with nona in both CPU or GPU variants. Hard reboot is needed. On Oct 10, 3:01 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: Mateusz mateusz.ka...@gmail.com wrote: Sorry, This is not a projection I am trying to make. nona freezes my system with those three files. I also managed to make a linear assemble of my images, however when I turn projection in preview to stereographic and I move a bit ONLY image on axis (without moving those sliders at bottom and left) and then I try to make panorama it just eats all my swap and all RAM. For me this is bug of nona which is included in hugin package. I am attaching project file. http://groups.google.com/group/hugin-ptx/web/DSC0767-DSC0775-fail.pto [...] When I open this pto file and use Stitch Now nona works without problem. I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. thanks cu andreas -- 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 -- 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: hugin eats up to 12Gb of RAM and freezes system
Mateusz mateusz.ka...@gmail.com wrote: On Oct 10, 3:01 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: [...] I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. 1) Align those images 2) When I want to create panorama in a linear form it works 3) Go to preview GL 4) Go to projection and change it to Stereographic 5) Go to move tab 6) Make move the projection so it will create a half sphere. 7) Close preview window 8) Create panorama again in Assistant Tab This eats all memory with nona in both CPU or GPU variants. Hard reboot is needed. Hello, Could you save the pto file after 7 (and post it)? At this point opening the saved project and running [Stitch Now] should immediately generate the error, shouldn't it? cu andreas PS: Please do not top-quote, thanks in advance. http://www.netmeister.org/news/learn2quote.html -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- 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: hugin eats up to 12Gb of RAM and freezes system
I already posted pto project file, which was ready to press Create panorama and freez system. Because of that I will post 6 screenshots of Hugin window with black font comments what I do in each window and how to reproduce system freez. Its 100% reproducible here on my system, but I cannot find out what is happening since all swap and all memory is taken and system becomes unresponsive. After 6) step I waited 7min and rebooted. Here are the steps http://groups.google.com/group/hugin-ptx/web/StepsToFreez.zip On Oct 10, 5:49 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: Mateusz mateusz.ka...@gmail.com wrote: On Oct 10, 3:01 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: [...] I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. 1) Align those images 2) When I want to create panorama in a linear form it works 3) Go to preview GL 4) Go to projection and change it to Stereographic 5) Go to move tab 6) Make move the projection so it will create a half sphere. 7) Close preview window 8) Create panorama again in Assistant Tab This eats all memory with nona in both CPU or GPU variants. Hard reboot is needed. Hello, Could you save the pto file after 7 (and post it)? At this point opening the saved project and running [Stitch Now] should immediately generate the error, shouldn't it? cu andreas PS: Please do not top-quote, thanks in advance.http://www.netmeister.org/news/learn2quote.html -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- 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: hugin eats up to 12Gb of RAM and freezes system
Because I could not open uploaded zip file. I am pasting a link http://www.kaduk.net/~mateusz/StepsToFreez.zip -- 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: hugin eats up to 12Gb of RAM and freezes system
Mateusz mateusz.ka...@gmail.com wrote: Because I could not open uploaded zip file. I am pasting a link http://www.kaduk.net/~mateusz/StepsToFreez.zip FWIW I get this instead of a crash: Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] nona -z PACKBITS -r ldr -m TIFF_m -o planet -i 0 /tmp/huginpto_1ZvYom ContractViolation: Precondition violation! BasicImage::lowerRight(): image must have non-zero size. (/tmp/HUGIN/hugin-2010.2.0/src/foreign/vigra/vigra/basicimage.hxx:868) caught exception: Precondition violation! BasicImage::lowerRight(): image must have non-zero size. (/tmp/HUGIN/hugin-2010.2.0/src/foreign/vigra/vigra/basicimage.hxx:868) make: *** [planet.tif] Fehler 1 After saving the pto I see that the canvas size in the stitcher tab ist set to an absurdely large value (595835x281497). Perhaps this another instance of http://sourceforge.net/tracker/?func=detailaid=2868139group_id=77506atid=550441 cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- 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: hugin eats up to 12Gb of RAM and freezes system
Hi, Could you try to replace step 8 by the following: 8a) Go to Stitcher tab 8b) Set Panorama Canvas Size to some sensible values 8c) Hit Stitch now! This will circumvent the behavior you have encountered where the panorama canvas size is somehow computed as an absurdly large value. By the way your PTO file looks quite normal: the p line indicates a width of 6160 and a height of 3617, which might indeed indicate that you have bumped into a bug since the program is clearly going nuts about size later on (see Andreas Metzler's reply). But the above steps will help you circumvent this erratic behavior. -- Bart On 10 okt, 16:43, Mateusz mateusz.ka...@gmail.com wrote: 1) Align those images 2) When I want to create panorama in a linear form it works 3) Go to preview GL 4) Go to projection and change it to Stereographic 5) Go to move tab 6) Make move the projection so it will create a half sphere. 7) Close preview window 8) Create panorama again in Assistant Tab This eats all memory with nona in both CPU or GPU variants. Hard reboot is needed. On Oct 10, 3:01 pm, Andreas Metzler ametz...@downhill.at.eu.org wrote: Mateusz mateusz.ka...@gmail.com wrote: Sorry, This is not a projection I am trying to make. nona freezes my system with those three files. I also managed to make a linear assemble of my images, however when I turn projection in preview to stereographic and I move a bit ONLY image on axis (without moving those sliders at bottom and left) and then I try to make panorama it just eats all my swap and all RAM. For me this is bug of nona which is included in hugin package. I am attaching project file. http://groups.google.com/group/hugin-ptx/web/DSC0767-DSC0775-fail.pto [...] When I open this pto file and use Stitch Now nona works without problem. I do not completely understand I move a bit ONLY image on axis. I tried this: open Fast Preview (OpenGL) switch to the Move/Drag Tab click into the image and pull a little bit to the left go back to hugin Stitcher tag. [Stitch Now]. No problem. thanks cu andreas -- 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: hugin eats up to 12Gb of RAM and freezes system
Worked ! From the Sitcher tab it works. Looks like that if I press Create Panorama from Assistant tab it sets canvas size to ridiculous number, but it works from Sitcher tab. By the way, the size of canvas was correct in Sticher tab. I also did not know that I have to press Stich Now in Sticher tab but not in assistant. So this a bug of Assistant which is not using correct canvas size. On Oct 10, 9:18 pm, Bart van Andel bavanan...@gmail.com wrote: Hi, Could you try to replace step 8 by the following: 8a) Go to Stitcher tab 8b) Set Panorama Canvas Size to some sensible values 8c) Hit Stitch now! This will circumvent the behavior you have encountered where the panorama canvas size is somehow computed as an absurdly large value. By the way your PTO file looks quite normal: the p line indicates a width of 6160 and a height of 3617, which might indeed indicate that you have bumped into a bug since the program is clearly going nuts about size later on (see Andreas Metzler's reply). But the above steps will help you circumvent this erratic behavior. -- Bart -- 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: hugin eats up to 12Gb of RAM and freezes system
Your assumptions are wrong: it's not Hugin which is using up all your memory, it's either Nona, or more likely, Enblend. These are the external programs which are used by Hugin to create the warped images and to merge them together into a panorama. Hugin itself doesn't use that much memory with the amount of images you have fed into it. So unless it's a bug, I suspect you are trying to stitch the panorama at an enormous resolution. Please check the output size at the stitcher tab and report back. -- Bart On 9 okt, 09:25, Mateusz mateusz.ka...@gmail.com wrote: Hi, I was trying to work with images directly from my camera. Each image is of size 10mb. Hugin resized them when loading (21 images). I selected only 6 for panorama. After Create Panorama with CPU my system total freezed and I had to do hard reboot, with GPU I managed to to some extend kill hugin and find out that it takes 4Gb of RAM and 8Gb of swap. I think algorithm should not load into memory all images at once, thats wrong for me. It should free the memory after working of selected pair of images, especially if the images are large. The time cost loading image from hard-disk and freeing memory is incomparable to how sever problem it triggers when all images are loaded at once. Please fix the algorithm or feed it with fewer pictures at once. -- 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: hugin eats up to 12Gb of RAM and freezes system
Those are my files http://hugin-ptx.googlegroups.com/web/_DSC0767.JPG?gda=aQgrVT4yzV5MYQFyh_jVVcQjFmpSvjl7rrWFUCuDDb7vgX3UNnuHVJy7a_elHKnW8yXGIgbjsKXVs-X7bdXZc5buSfmxgsc=EkeQFwsVQK4g7g3zxnQwFAylkaK7 http://hugin-ptx.googlegroups.com/web/_DSC0771.JPG?gda=qeE3qT4yzV5MYQFyh_jVVcQjFmpSvjl7rrWFUCuDDb7vgX3UNmYFUtjHaxcqtHD8E_4qu3DjsKXVs-X7bdXZc5buSfmxgsc=EkeQFwsVQK4g7g3zxnQwFAylkaK7 http://hugin-ptx.googlegroups.com/web/_DSC0775.JPG?gda=-s613D4yzV5MYQFyh_jVVcQjFmpSvjl7rrWFUCuDDb7vgX3UNs8MfElD77lKN8Kl9PCjDBzjsKXVs-X7bdXZc5buSfmxgsc=EkeQFwsVQK4g7g3zxnQwFAylkaK7 On Oct 9, 12:12 pm, Bart van Andel bavanan...@gmail.com wrote: Your assumptions are wrong: it's not Hugin which is using up all your memory, it's either Nona, or more likely, Enblend. These are the external programs which are used by Hugin to create the warped images and to merge them together into a panorama. Hugin itself doesn't use that much memory with the amount of images you have fed into it. So unless it's a bug, I suspect you are trying to stitch the panorama at an enormous resolution. Please check the output size at the stitcher tab and report back. -- Bart -- 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] Re: hugin eats up to 12Gb of RAM and freezes system
Hi, I could assemble the 3 files in a few minutes with no manual tweaking and I've only 4 Gb of RAM (.pto file attached). Tymczasem, michal PS. My system is a Debian testing 64 bit with the following versions : ii autopano-sift-c 2.5.0-0.1 Automatically create control points for panorama image ii enblend 4.0+dfsg-1 image blending tool ii hugin 2010.0.0+dfsg-3+b1 GUI tools for Hugin Those are my files http://hugin-ptx.googlegroups.com/web/_DSC0767.JPG?gda=aQgrVT4yzV5MYQFyh_jVVcQjFmpSvjl7rrWFUCuDDb7vgX3UNnuHVJy7a_elHKnW8yXGIgbjsKXVs-X7bdXZc5buSfmxgsc=EkeQFwsVQK4g7g3zxnQwFAylkaK7 http://hugin-ptx.googlegroups.com/web/_DSC0771.JPG?gda=qeE3qT4yzV5MYQFyh_jVVcQjFmpSvjl7rrWFUCuDDb7vgX3UNmYFUtjHaxcqtHD8E_4qu3DjsKXVs-X7bdXZc5buSfmxgsc=EkeQFwsVQK4g7g3zxnQwFAylkaK7 http://hugin-ptx.googlegroups.com/web/_DSC0775.JPG?gda=-s613D4yzV5MYQFyh_jVVcQjFmpSvjl7rrWFUCuDDb7vgX3UNs8MfElD77lKN8Kl9PCjDBzjsKXVs-X7bdXZc5buSfmxgsc=EkeQFwsVQK4g7g3zxnQwFAylkaK7 On Oct 9, 12:12 pm, Bart van Andelbavanan...@gmail.com wrote: Your assumptions are wrong: it's not Hugin which is using up all your memory, it's either Nona, or more likely, Enblend. These are the external programs which are used by Hugin to create the warped images and to merge them together into a panorama. Hugin itself doesn't use that much memory with the amount of images you have fed into it. So unless it's a bug, I suspect you are trying to stitch the panorama at an enormous resolution. Please check the output size at the stitcher tab and report back. -- Bart -- 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 project file #hugin_ptoversion 2 p f1 w6160 h3617 v182 E14.8243 R0 S581,5568,348,2721 nTIFF c:NONE r:CROP m g1 i0 f0 m2 p0.00784314 # image lines #-hugin cropFactor=1.45455 i w4288 h2848 f0 Eb1 Eev14.9315685007998 Er1 Ra-0.665527880191803 Rb0.359071016311646 Rc-1.43397319316864 Rd-0.903934240341187 Re-0.683444321155548 Va1 Vb-0.107150921994808 Vc-0.117877962424395 Vd0.0247569135737863 Vx0 Vy0 a0 b-0.0188061318960326 c0 d-7.60348510558273 e-279.212472606822 g0 p12.4122744413074 r0.0656634390457093 t0 v96.7981961251668 y-36.9928595503911 Vm5 u10 nDSC0767.JPG #-hugin cropFactor=1.45454549789429 i w4288 h2848 f0 Eb1 Eev14.7927698749044 Er1 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 a=0 b=0 c=0 d=0 e=0 g=0 p12.3739319288035 r-0.10449538042374 t=0 v=0 y-0.915787156276963 Vm5 u10 nDSC0771.JPG #-hugin cropFactor=1.45454549789429 i w4288 h2848 f0 Eb1 Eev14.8071830640234 Er1 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 a=0 b=0 c=0 d=0 e=0 g=0 p12.313038882 r0.0643678602636514 t=0 v=0 y36.0635063168891 Vm5 u10 nDSC0775.JPG # specify variables that should be optimized v p1 r1 y1 v p2 r2 y2 v # control points c n0 N1 x2931.766912 y1534.978561 X1641.876165 Y1536.687731 t0 c n0 N1 x2856.579698 y2187.032425 X1492.079903 Y2179.283476 t0 c n0 N1 x2552.695124 y2295.20267 X1150.508368 Y2347.445218 t0 c n0 N1 x2878.917416 y2223.83133 X1508.066766 Y2212.587075 t0 c n0 N1 x2693.346954 y2234.182749 X1316.982818 Y2255.559373 t0 c n0 N1 x2517.816563 y2436.97463 X1090.456683 Y2509.992907 t0 c n0 N1 x2679.969265 y2381.892015 X1283.937097 Y2411.399679 t0 c n0 N1 x3120.317985 y2577.710694 X1694.12936 Y2508.592655 t0 c n0 N1 x2870.618101 y2510.647868 X1467.349287 Y2501.460409 t0 c n0 N1 x2557.924166 y2390.474213 X1145.389904 Y2449.230152 t0 c n0 N1 x2637.19086 y2413.875142 X1233.240783 Y2454.498169 t0 c n0 N1 x3120.317985 y2577.710694 X1694.12936 Y2508.592655 t0 c n0 N1 x2747.907068 y2226.270937 X1376.546062 Y2235.725524 t0 c n0 N1 x2862.065417 y2148.632358 X1500.904333 Y2140.123034 t0 c n0 N1 x3115.578325 y1799.279297 X1777.476825 Y1781.769619 t0 c n0 N1 x2586.560814 y2196.213628 X1202.710424 Y2234.868987 t0 c n0 N1 x2777.649369 y2580.655781 X1365.425141 Y2594.344166 t0 c n0 N1 x2395.558928 y2206.907991 X970.249024 Y2282.403954 t0 c n0 N1 x2247.67898 y2504.652305 X734.419219 Y2665.095756 t0 c n0 N2 x3371.033264 y2284.693862 X245.473224 Y2385.413 t0 c n0 N2 x3381.235639 y2178.094745 X293.163345 Y2256.991691 t0 c n0 N2 x3657.386277 y2659.153953 X494.979454 Y2684.443427 t0 c n0 N2 x3436.747503 y1909.447254 X448.283787 Y1935.181504 t0 c n0 N2 x3359.200611 y1483.984465 X469.862846 Y1471.930217 t0 c n0 N2 x4013.250615 y2457.27277 X876.251931 Y2351.0696 t0 c n0 N2 x3630.179691 y1647.585766 X728.925023 Y1647.032458 t0 c n0 N2 x3634.974694
