Re: [hugin-ptx] Hugin operation questions from a mostly-newby
On 9/8/14 7:01 PM, Bruno Postle wrote: Hello again, I've been doing some tests -- many with an alternate tool, so I'm back to learn more. First, the alternate tool I've been testing is the Gigapan Stitcher tool, and since I'm using a Gigapan panorama head it seemed like a natural -- except for my predilection for Linux and open-source that is. So the stitch that took Hugin 6 hours (and for which I hadn't found the proper means of setting the scope of the images), took Gigapan Stitcher 16 minutes. And that was with basically one button press: - Stitch The downside is that it too of course makes some errors, and I don't have the option to go in and tweak things. Well, I can tweak the colors, but I can't mask parts from particular images, and force the inclusion from others. I can't go in and tweak control points when it makes mistakes. So the two panoramas I've stitched with Gigapan stitch can be viewed at: - http://web.avl.indiana.edu/~shermanw/MST the second one is from 1547 images, but if you look to the left, you'll notice that that process went a little wonky. It's actually a cool effect -- love that ATT building. But for the Gateway Arch, it really could have done a much better job. The other downside of Gigapan stitch is that it can't handle hand-held shoots unless they rigidly take the same number of pictures in each column row. My first issue is that I'd like to find a way to constrain what images are compared in the control-point search. I've taken a range of panorams, and the largest are quite large -- over 1000 pictures. So I'd like to find a way to limit control point analysis to say the 8 neighboring pictures of any one picture. You can try different control point strategies in File - Preferences. The default CPFind detector tries to minimise the number of comparisons by assuming you have taken photos in rows. Alternatively if you can approximately arrange the photos using a template, there is a 'prealigned' detector that only compares photos that are nearby. Nice, glad to learn about that. One things makes my wonder -- after choosing Hugin CPFind (prealigned) and double-clicking on it, there is a setting window, and for Type, it has All images at once, and not Prealigned panorama. Is this a bug, or some orthogonal setting? Okay, so now onto a 210 image shoot (42x5) using a Gigapan robot. First, loading the images it put them horizontally, whereas they were shot vertically, so it has a typical striation pattern from a misalignment -- I know that at this stage that doesn't matter, but would be nice if I could provide Hugin with the basic layout of the images. Hugin will read any EXIF orientation data from the camera to try and get this right. If your photos don't have this data then you need to used the advanced/expert interface to set the 'roll' of the photos before alignment. Right, well that's not exactly what I meant. What I meant is that if I shoot pictures in columns -- say 5 pictures per column, and then import them into Hugin, it lays them out going left to right, not top to bottom, so they are in the wrong place. Of course I wouldn't know how to tell Hugin how many pictures per column, so I'd have to know that too. Anyway, that matters only once I figure out how to do the prealigned option. I then ran the 2. Align step. And this took over 6 hours to process. It was not fun waiting for that, and I dread what will happen when I get to my large image collections! I did notice that at times all the CPUs were going, and then other times just a single CPU. Also, I'd be interested to know exactly what Optimizing Variables were being optimized to get a sense for where it is in the process. Definitely you need to stop using the Assistant for such a big image set. The Assistant will optimise all sorts of lens parameters by default, whereas if you have already characterised your lens there is only any need to optimise roll, pitch and yaw for the photos. The optimiser is much quicker when optimising fewer parameters. Okay, good. And this is where my past experiences with Hugin may hinder me (or maybe not), but when I go to the Advanced layout, under Photos it has the name, and then columns for y, p r, whereas from the last I remember lots and lots of parameters for each image, which could be turned on and off for optimization. Aha, found a few more by switching to Expert mode. (I previously hadn't noticed a difference between Advanced and Expert.) Hmmm, but I don't see the buttons that I thought were there to tell the optimizer to skip certain values. Eventually, it produced a result, and the pictures are in the proper order. With one huge problem -- the pictures wrap around past 360 to about 400 degrees. In reality the shoot was about 270 degrees. The angle of view parameter for your _photos_ is too high. Normally the Assistant optimises this, but if your panorama doesn't cover much of the sphere surface
[hugin-ptx] Hugin operation questions from a mostly-newby
Hello again, Now that I have Hugin 2014.0.0_rc4 compiled and running, I've got a few questions for the list on usage. I'm doing my best to look on the web first for answers, but of course I may not stumble upon the nugget I need. Also, I've used Hugin before, but it's been a couple years, so consider me a half-newby. My first issue is that I'd like to find a way to constrain what images are compared in the control-point search. I've taken a range of panorams, and the largest are quite large -- over 1000 pictures. So I'd like to find a way to limit control point analysis to say the 8 neighboring pictures of any one picture. I figure that for an 801 image shot, that would save two orders of magnitude in control point searching (8 vs. 800). And in the meantime (ie. I've done a couple of experiments since typing the above), I now have a couple of *real* problems rather than the hypothesized problem above (which I still wonder about). Okay, so over the past couple days I've been experimenting with some image collections that I shot a few weeks ago. I started with a 21 image collection of a hand-held shoot, and then I did a 210 image collection shot with a Gigapan robot. In both cases, I'm using the Assistant mode, though I did venture into the control point views and some other tabs for experimenting. Also, I did tests with both enblend and multiblend as the blending tool. *** Small *** So the 21 image collection worked pre-well. I tried it first with multiblend, and no enfuse (because I hadn't compiled it yet), and that went pretty fast, and with reasonable results. It cut the head off of one person, but for a final rendering I'd go back and mask out the entire person anyway. That took just a few minutes to process. I then went back and ran with enblend/enfuse (selecting the Exposure fused from any arrangements option), and processing that took an hour or two (vs. about 10 minutes in the first attempt). I suppose most of that is in the exposure correction step, or maybe multiblend is really *that much faster* than enblend. With enblend, the guy has his head, but the flag gets oddly blended (whereas multiblend took the entire flag from one image, so it looks fine). *** Medium *** Okay, so now onto a 210 image shoot (42x5) using a Gigapan robot. First, loading the images it put them horizontally, whereas they were shot vertically, so it has a typical striation pattern from a misalignment -- I know that at this stage that doesn't matter, but would be nice if I could provide Hugin with the basic layout of the images. I then ran the 2. Align step. And this took over 6 hours to process. It was not fun waiting for that, and I dread what will happen when I get to my large image collections! I did notice that at times all the CPUs were going, and then other times just a single CPU. Also, I'd be interested to know exactly what Optimizing Variables were being optimized to get a sense for where it is in the process. Eventually, it produced a result, and the pictures are in the proper order. With one huge problem -- the pictures wrap around past 360 to about 400 degrees. In reality the shoot was about 270 degrees. I looked and looked for a way to correct this -- tried using the Field of View parameter under the Projection tab, and pressed the Fit button, but that just did some processing, then returned the horizontal FOV to 360, but shrunk the vertical FOV! But it left all the pictures where they were, so there is still about 40 degrees of overlap. I figured I might as well see what happens, so I began the 3. Create panorama process. Here, likely because I have overlapping pictures, it no longer has the Exposure corrected, low dynamic range option turned on (for some definition of option, because it seems to always be greyed out). This then forces me to choose one of the fusing options, so I chose exposure fused from stacks. The process began, but a short while later (5 minutes or so), it seg-faulted. Here's the end of the log file: processing IMG_7374-IMG_7584_stack_ldr_0073.tif... processing IMG_7374-IMG_7584_stack_ldr_0074.tif... processing IMG_7374-IMG_7584_stack_ldr_0075.tif... processing IMG_7374make: *** [IMG_7374-IMG_7584_fused.tif] Segmentation fault (core dumped) make: *** Deleting file `IMG_7374-IMG_7584_fused.tif' I looked at the stack_ldr pictures, and as I expected the two ends of the panoram are blended together. I also noticed that the list of exposure_layers temporary images was missing at least one in the sequence, so perhaps this could be related to the seq-fault. While typing this email I decided to select the other exposure option (Exposure fused from any arrangements), but since it's about 2:00am for me, I may not see then end of it before sending this email. (It's creating the exposure_layer intermediate images now.) Okay, it failed before I finished typing the email. But this time it complained: not enough
[hugin-ptx] Re: Difficulty compiling Hugin 2014.0.0_rc4 on Linux RHEL 6.4
Hello Terry, Kornel, Am Freitag, 5. September 2014 um 14:07:38, schrieb Terry Duell tdu...@iinet.net.au Hugin-2013.0.0 should be OK. The references you have seen to Hugin-2014.1.0 are to builds of the current development source (ie the default branch tip). He probably needs a newer version of exiv2. (google for e.g. exiv2-0.23.tar.gz, which I am using) Yes, in fact this turned out to be the case. After receiving Terry's suggestion I looked for and found the header files for exiv2, so I decided to give a new version of Exiv2 a shot, and that fixed it. I ended up using the latest version, which is 0.24. So I guess this could be considered a bug in the CMake specification in that it should be set to require a specific version of Exiv2. Of course, I don't know where the cutoff would be (something higher than 0.18, but at or lower than 0.23). Kornel Thank you both for your help, Bill -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/540B4CD9.6040901%40indiana.edu. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Difficulty compiling Hugin 2014.0.0_rc4 on Linux RHEL 6.4
Hello, I'm working on compiling Hugin on a Linux system running the RedHat enterprise version (RHEL) 6.4. I downloaded from SourceForge, using the 2014.0.0_rc4 tag, from which a zip file was created. I noticed in some of the forum messages a reference to 2014.1.0, but I did not see a tag for that, or other means to download it. I installed all the dependencies (except SWIG 2.0, so I disabled HSI for now), and began the compilation. It got to 26% which it came upon an error involving Exiv2. So before I cut and past the error, I'll point out that I installed version 0.18.2-2.1 of Exiv2 -- officially it's the RPM package: exiv2-devel.x86_64 0:0.18.2-2.1.el6 Also, I should note that I'm not necessarily trying to do anything extraordinary, (other than do a giga-pixel sized panoram from 1000 images or so), so if going back to version 2013.0.0 is adequate, I'll do that -- I think the latest version that I have installed is 2011.5.0 (or that's what the man page tells me), so I figured it was time to upgrade before doing another project -- it's been a while obviously. Okay, so here is the compiler error message produced: [ 26%] Building CXX object src/hugin_base/CMakeFiles/huginbase.dir/panodata/SrcPanoImage.cpp.o /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp: In member function 'bool HuginBase::SrcPanoImage::readEXIF()': /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp:318: error: cannot convert 'Exiv2::ExifData' to 'float' for argument '1' to 'Exiv2::URational Exiv2::exposureTime(float)' /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp:319: error: 'fNumber' is not a member of 'Exiv2' /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp:327: error: 'make' is not a member of 'Exiv2' /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp:328: error: 'model' is not a member of 'Exiv2' /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp:371: error: 'focalLength' is not a member of 'Exiv2' /opt/GFX/Hugin/hugin_2014.0.0_rc4/src/hugin_base/panodata/SrcPanoImage.cpp:411: error: 'subjectDistance' is not a member of 'Exiv2' make[2]: *** [src/hugin_base/CMakeFiles/huginbase.dir/panodata/SrcPanoImage.cpp.o] Error 1 make[1]: *** [src/hugin_base/CMakeFiles/huginbase.dir/all] Error 2 make: *** [all] Error 2 Thank you for your help, Bill -- Bill Sherman Sr. Technology Advisor Advanced Visualization Lab Pervasive Technology Inst Indiana University sherm...@indiana.edu -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group. To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/54092FDE.30006%40indiana.edu. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Big list of suggestions
Hello, So I have several little things that I noticed, and that I think would help my workflow in using Hugin. I offer these not as complaints, but as ways that will increase my desire to continue using Hugin for my panorama projects. As an FYI, I've tested on a Fedora 11 w/ Hugin 2010.4.0 and a Fedora 14 system w/ Hugin 2010.5.0 from 2/22/2011 mercurial snapshot. I'll do my best to categorize the list since and make it more readable. -- Image list tab: - Some of the screenshots for show thumbnails in the image list. I think this is good, but I don't see them in the versions I'm using. - The text entry boxes in the Image Orientation area (which btw might better be called the Image Position area since it covers both orientation and location) are too small -- especially for negative numbers (ie. can't see the entire number). - Place the larger view of the selected image less far to the right (right now I have to make the Hugin window nearly full-screen just to see the image). Two quick ways to do this would be to: - move the Create control points button to be aligned with the Settings and Points per Overlap widgets: - shorted the size of the settings pull-down options list Bug: the selected image view doesn't redraw when the window size is changed. - Is there an argument I can pass to CPFind to increase the gamma that it uses when doing a comparison? Actually, I guess it might not truly need this since it has the raw numbers, but I did a test where I increased the gamma in all my images, and CPFind did a better job of finding matching points, so it would seem that a gamma argument could have value. -- Control points tab: - I would like the ability to set a gamma value for the entire image in the comparison image views. Actually, this request is broader than control points, I'd like to see it in the mask view and even on the selected image view on the Image tab. - Can there be a button to cancel a control point creation operation? There is an Add button, of course, when working with control points, I don't know how to get rid of a new control point that I don't want other than to Add it and then immediately Delete it. - Is there (or can there be) a way to create control points only between the two images shown? - Can the colors of the control point markers also be placed in a new column on the left of the point list? -- Preview window: - I'd like a preference to set the background color of the preview window to be something other than black. When working with nighttime featureless images, it can be hard to find them with a black background. - the Scale value of the Layout tab doesn't get set properly when going to another tab and then returning to Layout. - the sliders on the main preview window seem to be counter-intuitive (at least I have a difficult time using them). Perhaps this is because I'm been testing with super-high-res panorams rather than high FOV images) -- I have to move both sliders way to the right and the top to zoom in sufficiently to see anything. - I would like to be able to move/resize the overall view under the Preview and Layout tabs with the mouse (ie. not with the sliders). - Preview window (2010.5.0 version): Bug: the image toggle boxes are only big enough to see one digit of the image number. - I can't raise the overall Panorama Preview window to be on top of the Overview window (when that window is torn off from the main window). - The grid checkbox on the Ovewview window controls the display of the grid in the primary preview window - I don't know how to adjust the scale of the images in the overview window (they seem too big in my project). - Selecting the Thoby projection from the pull-down menu in the Projection tab went off to do the calculations and three days later had not completed (yes, I didn't get back to my home computer for three days and found it still calculating). So, a way to interrupt/cancel this would be good -- as well as fixing what is probably a bug. --- Of course, those are mostly orthogonal to my original issue (which I haven't created a good solution yet) of doing an alignment based on the robotically generated positions of each image capture. But looking to when I'll be using Hugin more regularly, these issues will be most helpful. I hope that list isn't too overwhelming! Thanks, Bill -- Bill Sherman Sr. Technology Advisor Advanced Visualization Lab Pervasive Technology Inst Indiana University
