Bug 378279 - Comet ephemeris 41P in wrong position
Summary: Comet ephemeris 41P in wrong position
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-30 13:50 UTC by VTVL
Modified: 2017-09-19 06:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
screenshot of KStars showing predicted and actual positions (157.76 KB, image/png)
2017-03-30 13:50 UTC, VTVL
Details

Note You need to log in before you can comment on or make changes to this bug.
Description VTVL 2017-03-30 13:50:42 UTC
Created attachment 104818 [details]
screenshot of KStars showing predicted and actual positions

On 25 March 2017 with a fresh download of comet ephemeris data an actual search for comet 41P revealed that the predicted position was about 2 degrees from the actual position as determined by a LX90 GoTo telescope with frequent synchronisation on nearby starts.  A different planetarium software gave a much more accurate position.  See the attached screen shot.
Comment 1 Jasem Mutlaq 2017-08-29 07:23:30 UTC
Please check with KStars 2.8.2
Comment 2 VTVL 2017-08-29 10:51:08 UTC
Hi Jasem,

I checked to see what 2.8.2 shows as the position of comet 41P on the
night of 2-04-2017 from the site in Germany.     It now appears to be
much more correct.   Just how correct will depend on my next observation
session when I can observe another comet.

regards,

John


On 29/08/17 09:23, Jasem Mutlaq wrote:
> https://bugs.kde.org/show_bug.cgi?id=378279
>
> --- Comment #1 from Jasem Mutlaq <mutlaqja@ikarustech.com> ---
> Please check with KStars 2.8.2
>
Comment 3 VTVL 2017-08-29 11:20:21 UTC
KStars 2.8.2 now shows the comet 41P on the night that it was observed in the more correct position.  Just how correct will depend on my next observation
session when I can observe another comet.
Comment 4 Jasem Mutlaq 2017-09-19 06:49:37 UTC
This should be completely fixed in 2.8.3. Reopen bug if you encounter the issue again.