Jump to content

  •  

CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.

Photo

MegaStar comet issue

  • Please log in to reply
17 replies to this topic

#1 Tom Laskowski

Tom Laskowski

    Mariner 2

  • -----
  • topic starter
  • Posts: 223
  • Joined: 28 Apr 2008
  • Loc: South Bend, Indiana, USA

Posted 05 August 2014 - 06:52 PM

I just uploaded the latest comet elements for MegaStar from: http://www.minorplan...wareComets.html and am getting an error in trying to run the program. There appears to be a bug with the elements format. The error window keeps popping up showing the message: "Unable to compute coordinates. No convergence"

 

It happens on my Windows XP and Windows 7 computers. I'm running MegaStar version 5.0.14

 

Has anyone encountered this? Any ideas?

 

Thanks



#2 johnpd

johnpd

    Viking 1

  • -----
  • Posts: 636
  • Joined: 12 Apr 2008
  • Loc: Green Valley, AZ

Posted 06 August 2014 - 04:50 AM

Do you have an older file that you can compare to?

 

JohnD



#3 Tom Laskowski

Tom Laskowski

    Mariner 2

  • -----
  • topic starter
  • Posts: 223
  • Joined: 28 Apr 2008
  • Loc: South Bend, Indiana, USA

Posted 06 August 2014 - 07:29 AM

I did check against an older comet.txt file and the older one worked fine. I edited the new comet.txt file by deleting about the last half of the file and it also worked, so I suspect there is a "bad" comet element in there somewhere. I also tried manually adding a comet then I checked the txt file and it looked to be in the correct format. At this point I can probably just edit the file to have it contain only the comets I am interested in observing.



#4 Tom Laskowski

Tom Laskowski

    Mariner 2

  • -----
  • topic starter
  • Posts: 223
  • Joined: 28 Apr 2008
  • Loc: South Bend, Indiana, USA

Posted 07 August 2014 - 12:19 PM

Something is wrong with this element. I deleted this line from comet.txt and the program now seems to work fine.

 

SOHO                          P/2010 H3   2015 09  25.7864    0.046924   0.984813     24.8193     78.3744     23.9242   20.0    5.0    2000 MPC 70361



#5 johnpd

johnpd

    Viking 1

  • -----
  • Posts: 636
  • Joined: 12 Apr 2008
  • Loc: Green Valley, AZ

Posted 08 August 2014 - 12:10 AM

Something is wrong with this element. I deleted this line from comet.txt and the program now seems to work fine.

 

SOHO                          P/2010 H3   2015 09  25.7864    0.046924   0.984813     24.8193     78.3744     23.9242   20.0    5.0    2000 MPC 70361

That's strange. I looked at it in Hex with a text editor and could not see anything weird unless it was fixed before I downloaded it.

 

JohnD



#6 Retsub

Retsub

    Mariner 2

  • *****
  • Posts: 220
  • Joined: 08 Dec 2006
  • Loc: Houston,Tx.

Posted 12 August 2014 - 10:44 PM

Many thanks to Tom and JohnD for getting to the bottom of this problem.  I am not a strong user of Megastar but many of my friends are.  One friend had the same error when doing some comet work and he asked me.  I know for many others that Megastar may be a bit dated but it is still a solid work horse to use. A quick forward about your results and he is now happy as ever.  Thanks.    *BW*



#7 Alan French

Alan French

    Night Owl

  • *****
  • Posts: 4784
  • Joined: 28 Jan 2005
  • Loc: Upstate NY

Posted 01 January 2015 - 10:20 PM

I had problems tonight with a new comet file for Megastar. Deleting SOHO 2010/H3 from comet.txt still fixes the problem.

 

Clear skies, Alan



#8 calskywatcher

calskywatcher

    Lift Off

  • -----
  • Posts: 2
  • Joined: 17 Mar 2013
  • Loc: Southern California

Posted 23 August 2015 - 06:43 PM

I was happy to find this discussion as I encountered the same problem with the download I did today.  However, I am still getting the errors after deleting SOHO 2010 H3.   My guess is that a more recent listed comet has some unknown errors.  Based on the date of Alan's comment, I did a List/Locate Comets on every non-periodic comet in 2015 (actually back to C/2014 W9 PANSTARRS).  I also walk back the periodioc coments to 250P.  My assumption is that the problem comet would generate the message when I tried to locate.  However, I could not find another comet that could not be found.   Should anyone figure out the new problem elements, please post here!



#9 rmollise

rmollise

    ISS

  • *****
  • Posts: 20733
  • Joined: 06 Jul 2007

Posted 24 August 2015 - 09:21 AM

I've had various problems with Megastar on modern OSes, and I have finally, alas, thrown in the towel on the program I used to love so much. It's still on my hard drive, but maybe not for long. I've switched to using TheSky 6 Professional for planetarium software type tasks and am now only about five years behind the power curve. :lol:

#10 Tom Laskowski

Tom Laskowski

    Mariner 2

  • -----
  • topic starter
  • Posts: 223
  • Joined: 28 Apr 2008
  • Loc: South Bend, Indiana, USA

Posted 30 August 2015 - 10:25 PM

I just now delete all the SOHO elements and it seems to fix the problem.



#11 CCD-Freak

CCD-Freak

    Viking 1

  • *****
  • Posts: 778
  • Joined: 17 Jan 2008
  • Loc: Whitesboro,Texas

Posted 01 September 2015 - 09:05 PM

I just downloaded the latest ephemerides file and deleted the SOHO entry and my MegaStar 5 works fine now.

 

 

John

CCD-Freak

WD5IKX



#12 stevear

stevear

    Lift Off

  • -----
  • Posts: 6
  • Joined: 11 Feb 2017

Posted 12 February 2017 - 03:38 AM

Hi All,

 

Unfortunately this problem still exists. I downloaded the new comet data from MPC and installed in Megastar v5 yesterday the 11th February 2017. I still get the message  'unable to compute coordinates, no convergence', that is after deleting the SOHO 2010 faulty data line. I can only assume that one of the other cometary data lines is now faulty.

 

Does anyone know which is the line now causing the problem? Has anyone told the MPC about the problem with this data?

 

Any help much appreciated.

 

Thanks

 

Steve



#13 obrazell

obrazell

    Mariner 2

  • -----
  • Posts: 259
  • Joined: 03 Apr 2005
  • Loc: United Kingdom

Posted 12 February 2017 - 06:40 AM

I deleted all the SOHO comets and then it worked. Not sure which ones are problematic but there is obviously more than one. I suspect the algorithems in Megastar have an issue but I doubt that will ever be fixed.

 

Owen



#14 catalogman

catalogman

    Viking 1

  • *****
  • Posts: 816
  • Joined: 25 Nov 2014

Posted 12 February 2017 - 09:45 AM

Hi All,

 

Unfortunately this problem still exists. I downloaded the new comet data from MPC and installed in Megastar v5 yesterday the 11th February 2017. I still get the message  'unable to compute coordinates, no convergence', that is after deleting the SOHO 2010 faulty data line. I can only assume that one of the other cometary data lines is now faulty.

 

Does anyone know which is the line now causing the problem? Has anyone told the MPC about the problem with this data?

 

Any help much appreciated.

 

Thanks

 

Steve

 

The latest update of the elements gives the following data in Cartes du Ciel:

 

P/2010 H3

Date: 2017-02-12 14h25m04s UT

Magnitude: 27.4 (!)

Phase: 7 deg

Distance: 5.8685 AU

Solar distance: 5.1521 AU

Mean J2000.0 RA: 19h05m42.79s

Mean J2000.0 Dec: -29d47m45.7s

 

If other users get similar information from their programs, then the problem is with MegaStar

and the vendor should be notified of the error (not the MPC).

 

                                                                                                                   -- catalogman


Edited by catalogman, 13 February 2017 - 09:24 AM.


#15 obrazell

obrazell

    Mariner 2

  • -----
  • Posts: 259
  • Joined: 03 Apr 2005
  • Loc: United Kingdom

Posted 14 February 2017 - 02:14 PM

Megastar is not going to be fixed or updated whilst it is with Willmann-Bell.The last update was 2012. For interest for the OP I deleted SOHO 342P and it seemed to get rid of the convergence message.

 

Owen



#16 stevear

stevear

    Lift Off

  • -----
  • Posts: 6
  • Joined: 11 Feb 2017

Posted 15 February 2017 - 04:12 AM

Many thanks Owen, 

 

I deleted the one you mention above 342P and P/2010 H3 but still get the Unable to compute convergence message, there must be another one causing a problem in the current data set.

 

clear skies.

 

Steve



#17 obrazell

obrazell

    Mariner 2

  • -----
  • Posts: 259
  • Joined: 03 Apr 2005
  • Loc: United Kingdom

Posted 15 February 2017 - 12:06 PM

OK then delete all the SOHO comets.

 

Owen



#18 stevear

stevear

    Lift Off

  • -----
  • Posts: 6
  • Joined: 11 Feb 2017

Posted 15 February 2017 - 04:20 PM

It worked.

 

Thanks Owen




CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.


Recent Topics






Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics