-
Notifications
You must be signed in to change notification settings - Fork 6
How to enter galactic coordinates? #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This can definitely be better addressed as I assumed that this would hardly ever be used, the current way to do it is a bit of a hack. It pops up in the error window if you enter an invalid coordinate format. To do this, you have to put "l=[Value for Galactic Longitude]" in the RA field and "b=[Value for Galactic Latitude]" in the DEC field. It converts this to hh:mm:ss in the background. |
Dougs original point is a good one. Is this a value that is currently being used? If so great, but slightly unexpected per the original requirements request.
Joe
… On Aug 4, 2017, at 1:24 PM, Doug Branton ***@***.***> wrote:
This can definitely be better addressed as I assimed that this would hardly ever be used, the current way to do it is a bit of a hack. It pops up in the error window if you enter an invalid coordinate format. To do this, you have to put "l=[Value for Galactic Longitude]" in the RA field and "b=[Value for Galactic Latitude]" in the DEC field. It converts this to hh:mm:ss in the background.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AL2u9mbYCOqaHdmMRTKmYj4nrAuO27reks5sU1PggaJpZM4Ot85m>.
|
Looks like we have our answer--will update documentation |
Documentation has been updated to cover entering galactic coordinates. |
Docs say we can--but how does it know? Because both are measured in degrees-minutes-seconds?
Answer may lie within "colon delineated RA & Dec broken in Telescope Control tab #8
"
The text was updated successfully, but these errors were encountered: