Google Summer of Code 2012 - Revision history

Alexwolf: /* Satellite and ring shadows on parent planets */

2012-04-03T10:10:42Z

Satellite and ring shadows on parent planets

Alexwolf at 10:09, 3 April 2012

2012-04-03T10:09:48Z

Fabien at 09:51, 3 April 2012

2012-04-03T09:51:34Z

Alexwolf at 18:27, 29 March 2012

2012-03-29T18:27:09Z

Alexwolf at 16:17, 29 March 2012

2012-03-29T16:17:10Z

Silverfields1: /* Irregular Solar System bodies */

2012-03-19T20:15:21Z

Irregular Solar System bodies

Silverfields1: /* Satellite and ring shadows on parent planets */

2012-03-19T20:15:04Z

Satellite and ring shadows on parent planets

Daggerstab at 19:35, 19 March 2012

2012-03-19T19:35:52Z

Daggerstab: /* Meteor shower calendar */

2012-03-19T19:14:04Z

Meteor shower calendar

Daggerstab: /* Meteor shower calendar */ these people will be paid to do this, won't they?

2012-03-19T19:10:29Z

Meteor shower calendar: these people will be paid to do this, won't they?

@@ Line 65: / Line 65: @@
 '''Knowledge Prerequisite:''' OpenGL
-'''Mentors:''' [https://launchpad.net/~alexwolf Alexander Wolf], [https://launchpad.net/~treaves Timothy Reaves]
+'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]
 ===Irregular Solar System bodies===

@@ Line 21: / Line 21: @@
 '''Knowledge Prerequisite:''' OpenGL, Geometry, Astronomy.
-'''Mentor:''' [https://launchpad.net/~treaves Timothy Reaves]
+'''Mentor:''' [https://launchpad.net/~xalioth Fabien Chéreau]
 ===Meteor shower calendar ===

← Older revision		Revision as of 09:51, 3 April 2012
Line 13:		Line 13:
	*All of this should prepare you to write a good proposal.		*All of this should prepare you to write a good proposal.

−	~~Please don't just submit a re-write of the task description here (some people actually did that last year). We are not that stupid, and plagiarism is a bad habit to learn this early in your career.~~

	==Ideas/projects==		==Ideas/projects==

← Older revision		Revision as of 18:27, 29 March 2012
Line 1:		Line 1:
	Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).		Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).
		+
		+	'''We propose [[GSoC_Application_Form_Template\|this template for students application form]] for GSoC 2012.'''

	==Common requirements==		==Common requirements==

← Older revision		Revision as of 16:17, 29 March 2012
Line 1:		Line 1:
	Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).		Ideas for the [http://www.google-melange.com/gsoc/homepage/google/gsoc2012 GSoC 2012] (Google Summer of Code 2012).
−
−	~~'''For students applications we have a Google Docs [https://docs.google.com/spreadsheet/viewform?formkey=dDFpYUJZbm5tWVQ3TmNQVWc3c3Vpb2c6MQ#gid=0 form]. Please fill in what you can.'''~~

	==Common requirements==		==Common requirements==

@@ Line 71: / Line 71: @@
 '''Brief explanation:''' At the moment, all Solar System bodies are rendered as spheroids. This is fine for all planets and large satellites, but unrealistic for all asteroids and some smaller moons (such as Phobos, etc.). Realistic rendering of asteroids requires the rendering of a simple 3D model, either in some accepted open 3D model format (e.g. COLLADA?) or in a simple format developed for Stellarium. Rough shape data for about 20+ asteroids can be found somewhere on NASA's websites. Working on this project should start with finding it and deciding which format to use.
-The implementation should be done having in mind that not all computers running Stellarium can use OpenGL shaders and other OpenGL2 features. It should either provide a fall-back mechanism in case they are not available, or it should be implemented in a way that doesn't use them. If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.
+If the implementation causes visible performance degradation on weaker systems, there should be an option for to turn the feature off.  Many such features are enable/disabled via preferences.
 '''Knowledge Prerequisite:''' OpenGL

@@ Line 5: / Line 5: @@
 ==Common requirements==
 All of these tasks require knowledge of '''C/C++''', as Stellarium is written in it, and some knowledge of the [http://qt.nokia.com/products/ '''Qt framework'''] (or willingness to learn the basics very quickly), because Stellarium relies heavily on it, especially for its GUI.
 ==Ideas/projects==

@@ Line 24: / Line 24: @@
 Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011]) or the [http://www.ta3.sk/IAUC22DB/MDC2007/ Meteor Data Center]. Attribution and/or copyright issues should be cleared before using the data!
 In all cases, the feature should meet the following requirements:
 *It should display a list of the meteor showers in the catalog
 **It should allow individual showers to be enabled/disabled
-**It should allow individual showers to be triggered on a whim. (Perhaps by jumping to the day of the peak?)
+**It should allow individual showers to be triggered on a whim. (Perhaps by jumping to the day of the peak? By setting radiant/ZHR, for example for demonstrations of historic showers?)
 *It should allow the user to toggle a marker showing the radiant(s). (Note that the radiants are not exactly point objects.)
 *It should model the drift of the radiant across the sky over time.
 *It should model the increasing/decreasing ZHR of each shower over time.
 '''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.

@@ Line 19: / Line 19: @@
 '''Brief explanation:''' At the moment, Stellarium can show meteors, but they are simply decorative - they appear at random points at a rate set by the user. The existing code of the MeteorMgr class can be used as a base for a plug-in that shows more or less scientifically accurate meteor showers. They are not random - the meteors appear to "stream" from a single point in the celestial sphere, the radiant.
-This feature can take several forms:
+The data behind the rendering can be organized in two different forms:
-* Weak form: Allows the user to define a meteor shower and/or pick it from a list, and then to turn it on and off on a whim.
+* Strong form: Keeps a meteor shower catalogue in JSON format as with the other kinds of objects tracked by Stellarium, and shows only what should be in the sky for the given date. The catalogue should contain information about the radiant and the annual changes in the zenith hourly rate (as meteor showers typically have a peak and are active some time before and after that; a distribution function can do).
-* Strong form: Keeps a meteor shower catalogue in JSON format as with the other kinds of objects tracked by Stellarium, and shows only what should be in the sky for the given date. The catalogue should contain information about the radiant and the annual changes in the zenith hourly rate (as meteor showers typically have a peak and are active some time before and after that; a normal distribution function can do).
 * Very strong form: Use a professional model for predicting meteor showers, based on the orbits of the clouds of space particles that cause them.
-Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011])
+Data about visual meteor showers can be found on the website of the [http://www.imo.net International Meteor Organization] (e.g. [http://www.imo.net/calendar/2011 calendar for 2011]) or the [http://www.ta3.sk/IAUC22DB/MDC2007/ Meteor Data Center]. Attribution and/or copyright issues should be cleared before using the data!
-The implementation should allow the user to toggle a marker showing the radiant.
+In all cases, the feature should meet the following requirements:
 '''Knowledge Prerequisite:''' OpenGL, Geometry, Basic Astronomy.