[hugin-ptx] Re: GSOC 2011 Student Introduction
Hi everybody! I have to apologize for not applying in GSOC 2011. I'm about to to graduate from my bachelor studies in the coming months. Therefore I couldn't make sure to have enough time for working intensively on another project. It was a great experience last year, so I'm looking forward to apply in the coming summers of code. Cheers, -- Flo -- 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] GSOC 2011 Student Introduction
Dear Hugin-Community! Congratulations for the successful GSOC application. Some of you might remember me from last year. I participated in GSOC 2010 and implemented the makefilelib [1] excellently mentored by Thomas Modes. Btw, I'm very happy to see my code in the current releases :) This semester I'm participating in rather intensive computer vision and computer graphics courses. When I followed the blueprint collection on the mailing list and launchpad I got interested in the vertical-line-horizon-detector blueprint [1]. It could give me the chance to use the courses content beyond examples and exercises. The blueprint says there exists already some work on that. Is it somewhere in the repo? Here is a little general introduction, mostly copied from last year's. My name is Florian Achleitner I'm from Austria and studying Telematics (a blend of computer science and electric engineering) at the Graz University of Technology. Currently I'm in the third year of my studies, before starting my studies I worked for four years as a developer in industry. My programming experience grew since I started writing programs on TI calculators in school probably 15 years ago. >From my work and university experience I'm familiar with C, C++, Python, Makefiles, Java, Shell Scripts.. (sorted by experience). I'm open-source enthusiast, exclusivly using Linux since years and administrating a linux web-file-mail-server. Since many years I'm interested in digital photography. My camera is a Konica Minolta Dimage Z5, which is no longer new or good unfortunately, but provides advanced capture modes. I don't have any special panorama equipment. [1] http://www.google-melange.com/gsoc/student_project/show/google/gsoc2010/hugin/t127230759674 [2] https://blueprints.launchpad.net/hugin/+spec/vertical-line-horizon-detector Regards -- Florian -- 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: New hugin-mac-2010.5.0-4854_d29b1d6da0e0 incl. Thoby projection, new cpfind and gsoc 2010 panorama projection
Hi everybody.
As I wrote it last summer, I can probably help you a little with the
makefilelib.
Generally it seams that the problem with echo and write() occurs when
executing the makefile with make, not during its creation with the
makefilelib.
On Fr, 2011-01-21 at 13:06 +0100, Rogier Wolff wrote:
> The error is explained in the write system call manual page:
>
>EBADF fd is not a valid file descriptor or is not open for writing.
>
> So standard output apparently isn't connected anywhere. (but as the
> error message DOES come through, the stderr IS!!!)
The three standard file descriptors are inherited from the parent so
they don't need to be set explicitly. So maybe it's done nowhere.
> > o Open a shell, change to the project directory, and use
> > "make -f .pto.mk"
> > to start the stitching
>
Does it work directly on a shell?
> It seems to be:
>
> src/hugin_base/makefilelib/test_util.cpp
>
> (which is unlogical because it isn't in any test-code anymore, and I
> think this is the actual code used, because I can't find any other
> pipe calls.
> Anyway, on first inspection I'd say that the code looks good. On
> the other hand, code like:
>
>
> if(dup2(fdmakein[0], 0) == -1 || dup2(fdmakeout[1], 1) == -1 ||
> dup2(fdmakeerr[1], 2) == -1) {
> std::cerr << "Failed to switch std stream" << std::endl;
> exit(-1);
> }
This was for development testing only and isn't built unless you
explicitly enable it with a cmake flags, and then isn't run unless you
start one of the dev-testers.
It connects the forked make process to the streams of the tester to
speed up the test, bypassing the creation of a makefile.
There is no connection to the problem you discuss here.
>
> should be rewritten as:
>
>stdinfd = dup2 (fdmakein[0], 0);
>if (stdinfd != 0) {
> // can't dup2 stdinfd...
>}
>...
The line above normally never fails .. so no need.
--
Flo
--
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 and the 10.10 'buntus
Hi everybody! On So, 2010-10-17 at 08:50 +0200, Kornel Benko wrote: > Am Sonntag 17 Oktober 2010 schrieb Yuval Levy: > > 2. dpkg was tolerant of this in the past. Now it throws an error if a > > folder does not exist / is not created properly. A well crafted deb > > package creates folders properly. > > This is to be corrected. > Lately I got a mail from Marijn Ros (mar...@mad.scientist.com). As it turned > out, the cmake 2.8.2 is broken, not dpkg. > The upcoming version 2.8.3 will be corrected. > In the deb-package there is a tar-file > data.tar.gz > which lacks the directory information. I never before have seen such a > tar-file. Certainly not created with tar-command. I think thats the point! I can confirm that on my ubuntu 10.10 (having the same problem). The tar file doesn't contain dirs. According to http://packages.ubuntu.com/ cmake was 2.8.0 in lucid and is now 2.8.2. I unpacked an inspected the data.tar.gz in a libpano deb file I built before upgrading on lucid. And it _does_ contain the dirs. > > Here is the proposed work-around for e.g. libpano13 for users having this > cmake version: > > #mkdir unpacked > #cd unpacked > #ar x ../libpano13.build/libpano13-2.9.17-Linux.deb > #mkdir untarred > #cd untarred > #tar zxvf ../data.tar.gz > #tar czf ../data.tar.gz . > #cd .. > #ar a ../libpano13-2.9.17-Linux.deb debian-binary control.tar.gz > data.tar.gz > ... I tried this with libpano. The tar file created by tar contains dirs and the repacked deb installs nicely. But ar a doesn't seem to be a valid operation. I used #ar r ../libpano13-2.9.17-Linux.deb debian-binary control.tar.gz data.tar.gz instead. > > Kornel -- Flo -- 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: Problem with installing hugin
On Mi, 2010-10-13 at 15:52 +0200, Kornel Benko wrote: > Am Mittwoch 13 Oktober 2010 schrieb Ehsan Esbati: > > Alright, maybe the wiki is not relevant to Maverick then? > > > > Wiki may be out of date, yes. You may be the first to find out what's going > wrong. > > Kornel I still have the same problem after upgrading to maverick. I tried to rebuild the packages from a long existing source tree, and was no longer able to install them. The error message is exactly the same as posted at the start of this thread. It seems there's some incompatibility with the generated packages and the maverick version of dpkg. I couldn't spend much time on that yet.. -- Flo -- 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] Problem with installing hugin
Hi! On Mo, 2010-10-11 at 18:06 -0500, Dale Beams wrote: > Begin by > > "dpkg -p enblend" > > Purge your old hugin installation first. > > Dale > > > > > > > > Date: Mon, 11 Oct 2010 15:48:01 -0700 > > Subject: [hugin-ptx] Problem with installing hugin > > From: sennai...@gmail.com > > To: hugin-ptx@googlegroups.com > > > > Hey peeps, > > > > First of all thanks to all the people who worked on the latest > > release, well done! > > > > I have been trying to build from source according to wiki > instructions > > on a fresh install of Ubuntu 10.10. Every thing goes smoothly until > I > > try to install the packages at which point I get this type of error > > (this is for enblend): > > > > sennai...@sennaista-desktop:~/src/enblend/enblend.build$ sudo dpkg > -- > > install enblend-4.1.1-Linux.deb > > (Reading database ... 175186 files and directories currently > > installed.) > > Preparing to replace enblend 4.0+dfsg-1ubuntu1 (using enblend-4.1.1- > > Linux.deb) ... > > Unpacking replacement enblend ... > > dpkg: error processing enblend-4.1.1-Linux.deb (--install): > > unable to create `/usr/local/share/man/man1/enblend.1.dpkg- > > new' (while processing `./usr/local/share/man/man1/enblend.1'): No > > such file or directory > > dpkg-deb: subprocess paste killed by signal (Broken pipe) > > Errors were encountered while processing: > > enblend-4.1.1-Linux.deb > > > > Libpano returns a similar error. Any idea what could be wrong? I have exactly the same problem since upgrading to ubuntu 10.10. But I didn't find out whats wrong yet. Anyways, purging does not help! -- Flo -- 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: [Ubuntu] libboost?
Hi! I just tried to build enblend again on my ubuntu 10.04 64bit, because I discovered that libboost-filesystem wasn't installed and therefore the substitution Chris mentionend was used. Here it works great. Install the packages from apt or synptic, both, including the -dev. That should be all. (libboost-filesystem1.40.0 libboost-filesystem1.40-dev) Remember to rerun cmake or configure after installing libraries! Otherwise it doesn't search for them again. Then rebuild, probably doing make clean first. Watch out for the lines mentioning libboost-filesystem. What do they say? I successfully tried cmake and autoconf. On 17.05.2010 21:31, Jake Kallman wrote: > From the install file in the zip. Also, I wanted to try setting the > DBoost_LIB_SUFFIX, but none of the libs seem to have a suffix (Unless > I'm looking in the wrong spot): On Linux, it normally just finds what is installed :) Did you use any additional libs? (the zip file). Good luck Flo -- 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] Exif Rotation Feature, vetting exercise
Hello everybody, this evening I tried to dive in and get an overview over the codebase to understand what needs to be done to implement the feature request [1], thats given as a vetting exercise. Honestly it was rather confusing. The directory structure below hugin/src is a little bit documented on the doxygen mainpage, but not up-to-date any more. I searched around a lot, but i believe I don't have a plan yet. What parts are in hugin_base and in hugin1? For Example there is an ImageCache class in hugin_base/huginapp/ImageCache and another one in hugin1/base_wx/ImageCache. While the latter is not used, i think. And there is the PT namespace, mentioned on the Mainpage.. I guess I lack the architectural overview .. ;) About the Exif Rotation: SrcPanoImage somehow encapsulates an image, and when one adds an Image in the GUI wxAddImagesCmd::execute creates an instance of SrcPanoImage and calls it's readEXIF(...) method. This huge method already reads Exif orientation tags and finally sets m_roll correctly. Although it doesn't do the trusted/not-trusted tag evaluation. What doesn't happen though is, that the image is correctly shown in the gui. Is that what should be done? By the way, i noticed that there are lots of SrcPanoImages constructed, even if only adding one photo. How does ImageCache work? And how is it related to SrcPanoImages? The Cache seems to store a map of names and entries that point to some special vigra:: types. Thanks for your help. Good night. Flo [1] http://sourceforge.net/tracker/?func=detail&aid=2974831&group_id=77506&atid=550444 -- 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 To unsubscribe from this group, send email to hugin-ptx+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[hugin-ptx] GSOC Introduction
Hi everybody, let me introduce myself to the hugin community as the first step to participate in development via gsoc. My name is Florian Achleitner I'm from Austria and studying Telematics (a blend of computer science and electric engineering) at the Graz University of Technology. Currently I'm in the second year of my studies, before starting my studies I worked for four years as a developer in industry. My programming experience grew since I started writing programs on TI calculators in school probably 15 years ago. From my work and university experience I'm familiar with C, C++, Python, Makefiles, Java, Shell Scripts.. (sorted by experience). I'm open-source enthusiast, exclusivly using Linux since years and administrating a linux web-file-mail-server. Until know I haven't made major contributions to open-source projects, except some bug reports and testing, but that should change soon ;) Since many years I'm interested in digital photography. My camera is a Konica Minolta Dimage Z5, which is no longer new or good unfortunately, but provides advanced capture modes. I don't have any special panorama equipment. I played with hugin and also commercial panorama tools before. Here are two examples: http://filestore.mg34.vc-graz.ac.at/pano/linz.jpg I created this one today with my newly built hugin, with autopano-sift control points. It's a view of Linz, an autrian town I visited this week. Freehand shot. http://filestore.mg34.vc-graz.ac.at/pano/eiffelpeakpanorama.jpg This one was shot last summer in the Canadian Rockies on the over 3000m high Eiffel Peak on a great trip through canada. (also stitched with hugin). Today I successfully checked out and built enblend, libpano, autopano-sift, and hugin, following the really good guide in the panotools wiki. I additionally buildt the hugin developer docs with doxygen to get some overview over the codebase. In the coming days I'll find some time to dive into the code and get a closer look. I'm targeting the topic "Make System and Detection of Panoramas", replacing the current panorama "build" process. Another interesting thing would be the improvement of the lens-database. The wiki says that there is still no system for updating the database. Maybe automatically calculate lens parameters from a testpicture, captured with the given lens? I must admit, that I don't know how the data is actually gained now. In the coming days I'll come up with ideas and a vetting-exercise patch.. cu Regards Flo -- 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 To unsubscribe from this group, send email to hugin-ptx+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
