Re: [hugin-ptx] Hugin - Microscope images showing strong parallax when stitched
On Tue, Jul 24, 2012 at 3:31 PM, hercat grandrive...@gmail.com wrote: Hello, I am a new user using version 2011.4.0 I have 12 images taken with a microscope, all overlapping with the same magnification. As the sample is on a mechanical stage, Yaw, pitch and Z (focal length of the microscope) should all be constant. In the optimizer tab, I select custom parameters and set Yaw, Pitch, and Z to be unchecked. I also uncheck the image that will be in the center of the panorama so that the software will use it as the starting image. I have all images listed as separate lenses. I run the optimizer and save the settings. [snip] A bit offtopic, but if you're stitching microscopic images, you might be better off/faster if you use http://www.xuvtools.org/, as it's highly optimized for this task, while hugin is highly optimized for panoramic stitching... David -- 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] Hugin - Microscope images showing strong parallax when stitched
hercat The program automatically generates suitable control points when I tell it hercat to align. However, when I reach the fast panorama preview, the resulting hercat image shows strong parallax, and is much narrower on the right side, even hercat when I select Mosaic and Cylindrical projection. You have to use rectilinear projection. Don't ask me why or how, below is how I do this. Hugin works very well for stitching microscope images. No need for lens calibration in my experience. I follow the procedure for stitching flat scanned images at: http://hugin.sourceforge.net/tutorials/scans/en.shtml For examples, look at http://histoweb.co.za/ and http://gallery.chaos.co.za/index.php?/category/8 From my experiences, some notes: 1. The align function of the Assistant Tab sometimes work, sometimes not, so I do it by hand as explained in the tutorial. 2. It is not always necessary to do the New Lens step. Depending on your microscope and camera setup, this has already been set to different lenses or, does not make any difference. 3. On the Images tab, you can use the Create control points button. With multi-row captures, this is not always work 100%, but take care of most of it. 4. On the panorama preview screen, NEVER touch the Center button. 5. On the fast preview screen, stay away from the Move and Drag Tab. It is extremely easy to mess things up here. 6. One mayor hassle, and I should take invest some time and figure what I am doing wrong: On the Stitcher Tab, you have to click the Calculate field of view and Calculate optimal size button, and adjust Crop in the fast preview screen several times before it will give you the correct sized 1:1 output. 7. For large multi-row stitches, (for example http://histoweb.co.za/012/012img001.html) I find it useful to use the following steps: a. Load images and set HFOV(v) = 10 b. Stitcher tab select Projection = Rectilinear. c. Stitcher tab Field of view: Horisontal = 50 and Vertical = 50 d. Create control points. e. Do not do any alignment yet. f. Open the Preview Panorama window. g. Click None (Show none of the images). h. On the displayed images buttons, select the first two overlapping images. i. Go to the optimizer tab, and do custom optimize and described in the tutorial (Custom - r, v, d and e or Custom - r,X,Y,Z excluding anchor). Usually rvde works best. j. Accept results if low enough. k. Open the Preview Panorama window. l. Adjust the viewport. m. Add an additional image overlapping with the previous two images. n. Align again. Sometimes it is possible to add more than one image to the existing aligned set. Problems are usually encountered when you reach the end of the slide and go to the next row. Hope this help, and feel free to ask if you need more info. Groetnis Marius mailto:mlo...@medic.up.ac.za -- add some chaos to your life and put the world in order http://www.mapungubwe.co.za/ http://www.chaos.co.za/ skype: marius_loots Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig. Volledige besonderhede is by www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar. -- 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] Hugin 2012.0beta1 released
Hi Harry
It seems that I was a bit premature with my patch. The api-min/max
strings from the python scripts are compared to HUGIN_API_VERSION and
this is defined as ${V_MAJOR}.${V_MINOR}.${V_PATCH}. So in order to
actually work, the api-max would have to be set to 2012.0.0. Obviously,
the same should apply to api-min.
However, I don't like this. In my book, the patch version should not be
api relevant as it should serve for bug fixing, which should not
influence the API.
Therefore, I propose the following:
The current HUGIN_API_VERSION shall be redefined as
#define HUGIN_API_VERSION ${V_MAJOR}.${V_MINOR}
Unfortunately, this will influence the behavior of the warning message
regarding the possibly changed preferences upon upgrades, too. If this
is not desired, an additional
#define HUGIN_FULL_VERSION ${V_MAJOR}.${V_MINOR}.${V_PATCH}
could be defined and used instead.
As an alternative,
#define HUGIN_PYTHON_API_VERSION ${V_MAJOR}.${V_MINOR}
could be used for the python interface checks only.
Of course, at least the second solution is much more invasive and
probably exceeds the amount of changes tolerated for a beta version. It
could be applied to the trunk, though.
I can supply you with patches for all options. I tend towards the
HUGIN_PYTHON_API_VERSION, at least for the current release. What
solution do you prefer?
With kind regards
Stefan Peter
--
In theory there is no difference between theory and practice. In
practice there is.
--
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: Translators requested for Hugin 2012.0 release
Hi all, there is a first bug report about typos in the strings which should be translated. https://bugs.launchpad.net/hugin/+bug/1028387 Are there more typos? If you found one please report back. We will collect some typos and fix them in one rush to keep the annoyance for the translators as low as possible. Maybe also a native speaker could help us with some better words/ sentences for the proposals in the bug report. Thanks Thomas -- 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 2012.0beta1 released
Harry van der Wolf hvdw...@gmail.com wrote: [...] This tarball is equivalent to rev/changeset 774550436f28 in our Mercurial repository, where it is also tagged 2012.0beta1 Verify its SHA1SUM 8f9aa64b86f799283d302d702de4ecb16976f07a hugin-2012.0.0_beta1.tar.bz2 Uploaded to Debian/experimental, afaict there are no changes to the previous version in experimental except for translation and documentatuion updates. 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] Garbage output despite many control points
Hello, I tried to stitch 30 photos to create a 360° equirectangular (and then stereographic) panorama following this tutorial: https://secure.flickr.com/photos/jftphotography/505008136/in/set-72157600232700728/ I import my images and generate control points with autopano-sift-c. The problem is that not all images are connected, as seen from the Layout view, only about half of them are connected, the others are in the top-left corner and the output doesn't make any sense. https://lh5.googleusercontent.com/-MIhb_gh_4tQ/UBBF9r1icyI/Auo/57tgvgKOaVI/s1600/Screen+shot+2012-07-25+at+21.15.01.png https://lh6.googleusercontent.com/-wj03bDUYzWQ/UBBGaF6l8FI/Auw/i6mKnubEuBM/s1600/Screen+shot+2012-07-25+at+21.10.30.png -- 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] Garbage output despite many control points
I hardly use auto generated control points, but have heard that the new cpfind works much better than autopano-sift-c. It comes with newer versions of hugin. What version are you using? I would suggest that you create few well distributed control points in one horizontal line of images first, and also create some vertical and horizontal lines if possible, than optimize and then connect the rest of images. Sorry if something is said in the tutorial, flickr is blocked from where I am accessing internet now. Cheers, Carlos E G Carvalho (Cartola) http://cartola.org/360 http://panoforum.com.br/ http://gnugraf.org/ 2012/7/25 Martin G differe...@gmail.com Hello, I tried to stitch 30 photos to create a 360° equirectangular (and then stereographic) panorama following this tutorial: https://secure.flickr.com/photos/jftphotography/505008136/in/set-72157600232700728/ I import my images and generate control points with autopano-sift-c. The problem is that not all images are connected, as seen from the Layout view, only about half of them are connected, the others are in the top-left corner and the output doesn't make any sense. https://lh5.googleusercontent.com/-MIhb_gh_4tQ/UBBF9r1icyI/Auo/57tgvgKOaVI/s1600/Screen+shot+2012-07-25+at+21.15.01.png https://lh6.googleusercontent.com/-wj03bDUYzWQ/UBBGaF6l8FI/Auw/i6mKnubEuBM/s1600/Screen+shot+2012-07-25+at+21.10.30.png -- 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
Re: [hugin-ptx] Garbage output despite many control points
I'm using 2011.4.0 on OS X, I'll try with cpfind and your suggestions. -- 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] Homebrew panohead (novice approach)
Thomas Pryds píše v St 18. 07. 2012 v 19:43 +0200: Hi Sorry if this is off-topic (is it?) Recently, I spent some time doing a homebrew panohead. Being a total novice to this in particular and to building physical stuff in general, I thought I would share my experiences with you, so I did a detailed description of my progress: http://goo.gl/cLXCm Comments very welcome, both here and on the website. In your article there is mentioned the non-fitting nuts bolts for camera tripod. Note that the reason is not some American inch measure, but rather British Withworth thread - camera tripods usually use it. The difference to metric thread is not just size, but also the shape of the thread. http://en.wikipedia.org/wiki/Screw#Thread_standards It is possible to buy the screws and nuts with the Withworth thread in photographic shops or you can ask a locksmith in your neibourghood to make them for you. Regards, Milan -- http://milan-knizek.net -- 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] Garbage output despite many control points
With cpfind it's about the same. -- 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] Garbage output despite many control points
If you don`t want to make control points manually (I usually do, as I said) you can also try to make them automatically in parts. Go to the Image tab, select only part of the images (like those correspondent to one only horizontal line or those that were disconnected) and with them selected press the button to create the control points. You can also do that after the global point detection step. I also don't have good experience with optimization made automatically. I usually do a first step to one horizontal, in three steps, y,p,r / y,p,r,v / Eveything without translation. Anyway, I also know that many people do spherical in different ways. It is really usual necessary to try many alternatives to find the best way for you and in the middle try to understand the details. If you search for recipe or other words in the list history you will find many ways to do the same thing. Here is an examplehttps://groups.google.com/forum/?fromgroups#%21searchin/hugin-ptx/recipe/hugin-ptx/XFu5PRRfIIk/0QhYFoJIQ9IJ . For a spherical it is also very important that you have used a panoramic tripod head. Without it you will have much more trouble to solve. Cheers, Carlos E G Carvalho (Cartola) http://cartola.org/360 http://panoforum.com.br/ http://gnugraf.org/ 2012/7/25 Martin G differe...@gmail.com With cpfind it's about the same. -- 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
