I'm definitely not going to have time for mentoring the summer of code this year.
This is a short list of features that are in Panotools::Script that I think ought to be moved into Hugin, maybe one of them could be the basis of a project: Adding GPano XMP tags to all equirectangular output. Google+ have released an open metadata spec to go with their panorama viewer, Hugin should write these to all equirectangular output. There is a bit of fiddly logic involved with partial and cropped panoramas, but this just needs to be copied from the pto2gpan tool. Adding this to the Hugin exiftool command would be no more than a days work. Reading white balance info from EXIF. match-n-shift initialises a pto project from a list of photos, it uses the nice exiftool code for reading white balance information and uses this to set the red and blue photometric parameters for each photo. Hugin uses the exiv2 library for reading metadata, so adding this feature to Hugin might involve copying this white balance feature from exiftool to exiv2. Morphing to fit. ptomorph implements two techniques for morphing the photos in a Hugin project so that they fit better when blended in enblend, they both use the ImageMagick -distort function. The one that uses the 'Shepards' option is deterministic and I think is suitable for implementing as a nona stitching switch. The 'Polynomial' option is more unpredictable, this feels like it really ought to be extra parameters that are part of the panotools model and that get optimised along with everything else - Though adding this complexity to Hugin isn't appealing. This idea has been floating around for a while: Merging nona with enblend/multiblend. Currently we remap each photo with nona, then enblend/enfuse splits these remapped images into multilevel pyramids, joins them into a single pyramid which is then reassembled into a final image. Another way of doing this would be to split the input photos into pyramids, then remap each directly into the final pyramid. This would have some advantages: less IO, since there are no intermediate files; much of each level of the pyramid is discarded anyway, as it is on the 'wrong' side of the seam, so we can avoid remapping this altogether; and I suspect doing it like this would avoid the nasty 'whorl' artefacts we get at the zenith/nadir (this assumption needs testing). The disadvantage is that is wouldn't be possible to optimise the seam position as we currently do with enblend. -- Bruno On 22 February 2013 02:09, Jim Watters <[email protected]> wrote: > Hugin and Panotools community, > > The Google Summer of Code 2013 is on. Where Google funds a student to work > on Free Software like Hugin for the summer. > http://google-opensource.blogspot.ca/2013/02/flip-bits-not-burgers-google-summer-of.html > http://www.google-melange.com/gsoc/homepage/google/gsoc2013 > > Hugin and Panotools has participated in the past but not last year. > Our 2011 involvement started here. http://wiki.panotools.org/GSOC_2011 > > If we want to do the Google Summer of Code, we need some volunteers to > mentor the students. > > What developers are interested in mentoring students? > Who is interested in taking leadership of Hugins and Panotools involvement > this year? > What new ideas do you have that a student could implement? > Ideas from 2011 http://wiki.panotools.org/GSOC_2011_Ideas > https://blueprints.launchpad.net/hugin -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
