[hugin-ptx] Re: cpfind ransac mode

2011-01-22 Thread kfj
On 22 Jan., 22:20, Pablo d'Angelo wrote: > I have thus implemented a new RANSAC model that can make use of the > restrictions we have in panoramas, and also include prior information > about lens type, HFOV and distortion etc. Basically, it tries to > estimate roll,pitch and yaw for each image

[hugin-ptx] Re: Test case for cpfind

2011-01-22 Thread Pablo d'Angelo
Hi Yuv, Am 23.01.2011 04:33, schrieb Yuval Levy: > can somebody please check why Hugin/cpfind has difficulties with this set of > images from Michel Thoby? > > http://www.sendspace.com/file/vnek81 I tried the set with the following steps: With assistant: 1. load images, set 14 mm rectilinear

[hugin-ptx] Re: clustered hugin

2011-01-22 Thread Pablo d'Angelo
Hi Michael, Am 22.01.2011 12:20, schrieb michael.grant: Unless you do something like this, I can't see how hugin is going to be able to create a pano any greater than the available swap space. How difficult would it be to rework emblend to do something like the above? Enblend can use temporar

[hugin-ptx] Test case for cpfind

2011-01-22 Thread Yuval Levy
can somebody please check why Hugin/cpfind has difficulties with this set of images from Michel Thoby? http://www.sendspace.com/file/vnek81 thanks Yuv signature.asc Description: This is a digitally signed message part.

[hugin-ptx] Re: clustered hugin

2011-01-22 Thread Jimmy
On Jan 12, 9:28 pm, "michael.grant" wrote: > I used to work for Sun (but not on SGE).  I had a quick look at it. > We could create our own grid.  There's also things like BOINC, but > BOINC is a research grid.  BOINC is something you download and install > on your machine and it allows people to

[hugin-ptx] cpfind ransac mode

2011-01-22 Thread Pablo d'Angelo
Hi all, panomatic and thus cpfind use a RANSAC step for outlier removal. This used to be based on a homography, which works ok for non-wide angle images. It breaks for fisheye images, here a large error tolerance must be choosen, and this results in a rather weak outlier check for wide angle

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread kfj
On 22 Jan., 16:05, "T. Modes" wrote: > I finally found a solution to automatically create the preprocessed > file and input it into the swig process. So there is no need to fiddle > by hand with the preprocessing and there are not 2 version of the same > file which  needs to be in sync (commite

[hugin-ptx] Re: clustered hugin

2011-01-22 Thread Jeffrey Martin
This probably deserves another thread, but anyway, if I may ask, what is the state with Enblend, and are there any other plans to make another blender? I still use smartblend regularly, it's 5 years old, single core, 32-bit a dinosaur. but still superior in terms of blending to anything else

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread kfj
On 22 Jan., 16:05, "T. Modes" wrote: > I finally found a solution to automatically create the preprocessed > file and input it into the swig process. So there is no need to fiddle > by hand with the preprocessing and there are not 2 version of the same > file which  needs to be in sync (commite

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread T. Modes
I added also an installer for windows in CMake. The lines for unix are prepared by comment out because I don't know in which directories the files should go on unix. Thomas -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" gr

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread T. Modes
Hi Kay, > swigpyrun.h is input. It is included by hpi_classes.h which is in turn > included by hpi.cpp. This is why it is needed in the source tree. It's > needed in the making of the hpi object code which is then linked into > libhugin.so, but is irrelevant further down the road and does not > be

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread kfj
On 22 Jan., 11:16, "T. Modes" wrote: > > I've modified Thomas' CMakeList.txt code to generate swigpyrun.h in > > the source tree instead of the target tree, but I still haven't > > figured out how to have it made automatically initially - I can get > > only get it to be created if I explicitly

[hugin-ptx] Re: clustered hugin

2011-01-22 Thread michael.grant
By needing the emblend to be done all in one shot like this you loose the advantage of make here. Especially since if you stop the job at this point, you have to start the emblend all over again. Distributing the other pieces is a small job in comparison to the emblend which seems to take the most

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread T. Modes
Hi Kay, On 22 Jan., 10:08, kfj <_...@yahoo.com> wrote: > The new patch is now online at > > http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch48... > > This has the accessor code for class SrcPanoImage and some cosmetic > changes I commited a slightly modified version of your pat

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread kfj
On 21 Jan., 18:58, kfj <_...@yahoo.com> wrote: > I'll put a patch online today or tomorrow and post when I've done so. The new patch is now online at http://bazaar.launchpad.net/~kfj/+junk/script/view/head:/main/patch4878.gz This has the accessor code for class SrcPanoImage and some cosmetic

[hugin-ptx] Re: hugin plugin interface - developers please liaise

2011-01-22 Thread T. Modes
Hi Kay, >But you got it to run? On Windows? That would be good news indeed, >because there are so many Windows hugin users out there, and I was >secretly afraid of subtle differences in SWIG and Python that might >make my code useless there. Yes, it works. It has only a minor glitch. The output o