GCVS finding, other issues

Bill J Gray Feb 14, 2007

John Greaves wrote:

"...There's an easy answer to that one, Roger ol' lad, it's called V435
Vul not being in Namelist 78...

;)

It were in namelist 77."

Yes, but the Name List 77 _and_ 78 stars (and all previous Name List
stars) are in 'iii.dat'. Still puzzling this out.

So far, there appear to be (at least) three issues with the new update:

(1) When you shut Guide down (or select a non-ASCOM scope), it doesn't
disconnect itself from ASCOM. Should be an easy fix.

(2) It's not finding new variables as it ought. As I wrote, still
puzzling.

(3) Lists of satellite passes aren't working. Still puzzling.

(And a fourth issue, not related to the update: as Julian Parks
points out, the GCVS display needs work.)

Also, a point some have asked me about: Guide can now make use of
ASCOM, but it does not _insist_ upon it. If you want to, you can
still control your LX-200, Celestron, etc. scopes "the old-fashioned
way".

I'd recommend controlling your scope via ASCOM in three cases. First,
you may have a scope not already supported by Guide. It'll control all
Meade and Celestron scopes, plus many others, but there are at least
a few for which ASCOM is a must.

Second, ASCOM lets multiple programs share a scope.

Third, you may find that for some bizarre reason, Guide isn't able
to communicate with your scope. This is very unlikely to happen, but
if it does, it's nice to have ASCOM available as a workaround.

If your scope already works with Guide, and you don't run other
software that hooks into a telescope, ignore ASCOM; it won't do much
for you. Otherwise, I think you'll find it useful.

-- Bill