• Subscribe

    Subscribe to This Week In Panospace by eMail.
    Subscribe in a reader
  • License

    Creative Commons License
    This work is © 2008-2012
    by Yuval Levy
    and licensed under a
    Creative Commons License.
  • Entries

    February 2009
    M T W T F S S
    « Jan   Mar »
     1
    2345678
    9101112131415
    16171819202122
    232425262728  
  • Archives

A ToDo List For Google Summer of Code 2009 Student Applicants


MascotteWhile we’re gearing up to apply to Google Summer of Code 2009 as mentoring organization, here are ideas for students who want to prepare their application.

1. Meet The Community

Join the community early. Understand the people, the users, the developers. How do they interact? What is currently a hot topic in the community? Where is development focused? What are the itches to scratch?

This is the time to take the software for a spin. If you have a digital camera, shoot a few images. If not ask in the community for input. Follow the tutorials, get a feel for the user experience.

2. Learn the Tools of the Trade

Hugin is multi-platform and chances are that it builds and runs on your current computing platform. However on some platforms it is easier than on others. Whatever platform you choose, now is the time to make sure that you have all the necessary tools to access the repositories (Subversion and CVS) and to build the code. Your starting point is here. This is the time to take the software apart and rebuild it. You want to make sure you can build Hugin on your computer, and you want your potential mentors to know on which platform you are.

3. Submit A Patch

To ascertain proficiency of the tools and of the code base, we require all applicants to provide at least one relevant patch. It does not have to be complex or big. Just show that you can compile the code base, make modifications to it and compile it again.  If it is also useful, that’s a bonus. No matter if you fix a bug or add a new feature, what we want to see is proficiency of the tools and the codebase; and your working style. The bug tracker is full of opportunities for bug fixes. If you want to go fancy, there are plenty of feature requests tracked as well.

The earliest you submit a patch and make yourself known in the community, the more chances you will have to leave a good impression, establish your reputation, position yourself on the starting grid. It is always time to submit a patch. Below are a few ideas for small patches:

Autoformat

Hugin currently starts by default in 360°x180° equirectangular mode. This is comprehensive enough to fit all projects, but not adapted to them. An adaptive autoformat would trigger Hugin’s FoV calculation every time an image is added or changes position. Based on the calculated FoV, output format is selected. For narrower FoV it would be equirectangular and for wider FoV equirectilinear. A preference checkbox enables and disables this behavior.

Default Optimizer Preset

Currently in the Optimizer tab the user can chose between a few pre-defined optimization strategies. The default is always Positions (incremental, starting from anchor). Add a preference setting to determine which one to use. Extra bonus: add in the preferences tab a way to customize / add to the list.

Default Exposure Optimizer Preset

Same as above, but on the Exposure tab for Photometri Optimization.

Control Points Tab Usability

The widgets on the Control Point tab can use a bit of attention. Group the arrows so that the mouse can move quickly from one to the other and back. Optimize the widgets order so that moving forward and backward from these controls with the TAB / SHIFT+TAB keys is fast as well (only one keystroke apart). The drop-down list of photos seems to be buggy in Windows and work in Linux. Is this a wxWidgets bug or is it a Hugin bug? Is there a way around it?

4. Watch This Space

I mean this space. This is where Google will publish the list of accepted mentoring organizations, and this is where you will apply between March 23 19:00 UTC and April 3 19:00 UTC. You still have a few weeks to prepare, but don’t miss it!

4 Responses

  1. About that optimizer preset: another nice thing would be to have some defined ordner in which a few optimzation runs can be executed, e.g. position, position and view, position view barrel and in the end all. this way one usually doesnt get caught in local minima …

  2. When experimenting with Optimizer parameters, it would be a nice feature if you could have an ‘undo’ possibility. As long as you do not add any control-points, it would be even better if you could use a history of optimizations to compare the results (I use this very often with developing sql-query’s in an oracle-tool sql-developer). Both are useful in finding the best Photometric Optimization settings.

  3. I hope you’ll find people to optimize this great application ;-)

  4. […] where to follow? Take a look at this ToDo List for GSoC […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s