Northern Taurid radiant information version 0.14.3

Bug #1600254 reported by Alexander Wolf
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stellarium
Fix Released
Low
Unassigned
0.14
Fix Released
Low
Alexander Wolf

Bug Description

Anonymous report on SF: https://sourceforge.net/p/stellarium/discussion/278769/thread/0942dc37/

Just a very minor observation. In Version 0.14.3 the information regarding the parent body of the Northern Taurids is incorrect. It states that C/1917 F1 (Mellish) is the parent comet, when it should be the same as the Southern Taurids, namely 2P/Encke.

Of course, it is probably more accurate to say that both Encke and the Taurids are part of the Taurid complex, as it is strongly suspected that Encke and the Taurid meteors are remnants of a hierarchal break up of a larger progenitor some time in the distant past. However, I think it is sufficient to associate the Taurid meteor showers with Encke for the purposes of stellarium.

And a suggestion for a distant future version of Stellarium. It would be icing on the cake if you could include the nodal precession of meteor streams with time. Currently precession of the equinoxes moves the radiant in time, but the nodal precession would shift its radiant with respect to the background stars and time. A mammoth task, and one to possibly consider when all the more important stuff gets done first. Heres hoping to see a Version 1.X.X implimented. Keep up the good work.

Changed in stellarium:
milestone: none → 0.15.0
importance: Undecided → Low
tags: added: meteors plugin solar-system
Revision history for this message
Alexander Wolf (alexwolf) wrote :

First point (parent body is 2P/Encke) has been confirmed and fixed in revision 8527.

Changed in stellarium:
status: New → In Progress
Changed in stellarium:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.