SoC 2010 ideas - Revision history

Bruno: /* Regression tests for pano13 */

2011-03-30T23:46:00Z

‎Regression tests for pano13

Bruno: /* Makefile system and Detection of panoramas */

2011-03-30T23:45:29Z

‎Makefile system and Detection of panoramas

Bruno: /* Colour */

2011-03-30T23:44:27Z

‎Colour

Bruno: /* Patent free control point generator */

2011-03-30T23:43:06Z

‎Patent free control point generator

Bruno: /* Threading for Hugin */

2011-03-30T23:42:15Z

‎Threading for Hugin

Bruno: /* Vetting exercise */

2010-03-30T22:46:44Z

‎Vetting exercise

Bruno: /* Vetting exercise */

2010-03-30T22:41:58Z

‎Vetting exercise

Dmgerman: /* Regression tests for pano13 */

2010-03-30T07:01:24Z

‎Regression tests for pano13

Dmgerman: /* Regression tests for pano13 */

2010-03-30T06:57:09Z

‎Regression tests for pano13

James Legg: /* Vetting exercise */

2010-03-26T13:55:26Z

‎Vetting exercise

← Older revision		Revision as of 23:46, 30 March 2011
Line 116:		Line 116:

	=== Regression tests for pano13 ===		=== Regression tests for pano13 ===
		+
		+	''note: this was completed in GSoC 2010''

	libpano13 is the panotools library containing panoramic math, if it was easier to test it might make life easier for those who want to hack it. A regression testing framework that can be configured for different related command-line tools would be even better.		libpano13 is the panotools library containing panoramic math, if it was easier to test it might make life easier for those who want to hack it. A regression testing framework that can be configured for different related command-line tools would be even better.

← Older revision		Revision as of 23:45, 30 March 2011
Line 96:		Line 96:

	=== Makefile system and Detection of panoramas ===		=== Makefile system and Detection of panoramas ===
		+
		+	''note: this was implemented in GSoC 2010 and is available in the current Hugin release''

	Hugin uses gnu ''make'' to drive stitching, this involves writing makefiles and executing ''make'' as a sub-process. We have two issues with this;		Hugin uses gnu ''make'' to drive stitching, this involves writing makefiles and executing ''make'' as a sub-process. We have two issues with this;

@@ Line 86: / Line 86: @@
 * Display of images in tabs and preview is not colour managed, integrate [http://www.littlecms.com/ lcms] and access system  monitor colour profiles
-* Hugin has a good backend for adjusting white-balance. Add a GUI grey picker and/or tools to adjust colour temperatures manually on a subset of photos to be able to do stuff like this: http://www.flickr.com/photos/sbprzd/4196026736/
+* <del>Hugin has a good backend for adjusting white-balance. Add a GUI grey picker and/or tools to adjust colour temperatures manually on a subset of photos to be able to do stuff like this: http://www.flickr.com/photos/sbprzd/4196026736/</del> ''already added to recent hugin''
 * [[EXIF]] metadata contains information on colour balance (WBRedLevel, WBGreenLevel & WBBlueLevel) which should be used to initialise the red/blue colour balance parameters in Hugin - Currently Hugin does something very similar for EV.
 * [[Chromatic aberration|tca]] correction in [[nona]] with support in GUI and .pto format, possible simple GUI to run [[tca_correct]]

← Older revision		Revision as of 23:43, 30 March 2011
Line 58:		Line 58:

	=== Patent free control point generator ===		=== Patent free control point generator ===
		+
		+	''note: the patent free control point generator is complete and is now part of Hugin as [[cpfind]]''

	We now have a patent free control point generator with libpanomatic, but this needs some integration:		We now have a patent free control point generator with libpanomatic, but this needs some integration:

← Older revision		Revision as of 23:42, 30 March 2011
Line 43:		Line 43:

	===Threading for Hugin===		===Threading for Hugin===
		+
		+	''note: this has now been implemented in Hugin so this is not available as a SoC project''
		+
	Hugin currently becomes unresponsive while it loads images. It would be better to keep the interface responsive during image loading and scaling images in another thread. Also, something like [http://sourceforge.net/tracker/?func=detail&aid=2872111&group_id=77506&atid=550443 this patch], which loads images when Hugin is otherwise idle, would be better in a background thread.		Hugin currently becomes unresponsive while it loads images. It would be better to keep the interface responsive during image loading and scaling images in another thread. Also, something like [http://sourceforge.net/tracker/?func=detail&aid=2872111&group_id=77506&atid=550443 this patch], which loads images when Hugin is otherwise idle, would be better in a background thread.

@@ Line 88: / Line 88: @@
 ==== Vetting exercise ====
-Add support for reading EXIF colour-balance metadata, see [https://sourceforge.net/tracker/?func=detail&aid=2974841&group_id=77506&atid=550444 feature request #2974841 on the Hugin tracker]
+Add support for reading [[EXIF]] colour-balance metadata, see [https://sourceforge.net/tracker/?func=detail&aid=2974841&group_id=77506&atid=550444 feature request #2974841 on the Hugin tracker]. Note that implementing the entire request in the tracker is probably too big a task, alternatively you can do something simpler with colour balance such as add a button to the [[Hugin Camera and Lens tab]] that increases the red levels in all selected images by 10% and decreases blue by 10%.
 === Makefile system and Detection of panoramas ===

@@ Line 106: / Line 106: @@
 ==== Vetting exercise ====
-Modify Hugin to read and use EXIF Rotation tags in photos [http://sourceforge.net/tracker/?func=detail&aid=2974831&group_id=77506&atid=550444 feature request #2974831 on the Hugin tracker]
+Modify Hugin to <del>read and use</del> ignore [[EXIF]] Rotation tags in photos that have a pixel width smaller than the height (i.e. images that have been rotated in an image editor). <del>[http://sourceforge.net/tracker/?func=detail&aid=2974831&group_id=77506&atid=550444 feature request #2974831 on the Hugin tracker]</del>
 === Regression tests for pano13 ===

@@ Line 126: / Line 126: @@
 The main priority is to implement regression testing of PToptimizer and of the projections (input and output).
-This project requires scripting skills (we are open to either using Python or Perl) and motivation to create tests sets.
+This project requires scripting skills (we are open to either using Python or Perl), knowledge of C
 Images will be provided by the maintainers of libpano, and some might be created by the student.

← Older revision		Revision as of 06:57, 30 March 2010
Line 111:		Line 111:

	libpano13 is the panotools library containing panoramic math, if it was easier to test it might make life easier for those who want to hack it. A regression testing framework that can be configured for different related command-line tools would be even better.		libpano13 is the panotools library containing panoramic math, if it was easier to test it might make life easier for those who want to hack it. A regression testing framework that can be configured for different related command-line tools would be even better.
		+
		+	Libpano is responsible for doing the image transformations required to project photos to any given output panorama. It is also responsible for the optimization step of Hugin (and PToptimizer).
		+
		+	libpano is a relatively mature and stable library, but its development has been slowed by the lack of regression testing. Currently there are only two sets of tests (tests directory of the libpano module of panotools).
		+
		+	This project consists in the creation of:
		+
		+	1. Infrastructure to test the main functionality of libpano as used by hugin (perhaps at the function level).
		+
		+	2. Infrastructure to test the command line applications in libpano (PTmender, PTroller, PTtiff2psd, etc).
		+
		+	3. Create sets of tests.
		+
		+	The main priority is to implement regression testing of PToptimizer and of the projections (input and output).
		+
		+	This project requires scripting skills (we are open to either using Python or Perl) and motivation to create tests sets.
		+	Images will be provided by the maintainers of libpano, and some might be created by the student.

	=== Your own project ===		=== Your own project ===

@@ Line 50: / Line 50: @@
 ==== Vetting exercise ====
-Start a thread that pops up a window every ten seconds showing a
+When Hugin starts, start another thread that pops up a window every ten seconds showing a
 message. Extra bonus: the message should show relevant information
 (e.g. the number of processor cores, a thread id).