Skip to content
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

Provide RA/Dec of exposure #24

Open
pmelchior opened this issue Oct 14, 2013 · 5 comments
Open

Provide RA/Dec of exposure #24

pmelchior opened this issue Oct 14, 2013 · 5 comments
Assignees

Comments

@pmelchior
Copy link
Owner

Don't need WCS positions, but, say, center-chip location would be nice to have.
It would suffice to have that coordinate in the FITS header.

@ghost ghost assigned esheldon Oct 14, 2013
@pmelchior
Copy link
Owner Author

Do the new y1p1 data have the RA/Dec in the header?

@esheldon
Copy link
Collaborator

esheldon commented May 8, 2014

yes, but I'm not sure how accurate they are

This one looks wrong
RA = '00:00:00.000' / [HH:MM:SS] Target RA
DEC = '00:00:00.000' / [DD:MM:SS] Target DEC
TELRA = '00:00:00.068' / [HH:MM:SS] Telescope RA
TELDEC = '00:00:00.101' / [DD:MM:SS] Telescope DEC

This one looks OK
RA = '23:07:30.365' / [HH:MM:SS] Target RA
DEC = '00:04:24.326' / [DD:MM:SS] Target DEC
TELRA = '23:07:30.407' / [HH:MM:SS] Telescope RA
TELDEC = '00:04:24.398' / [DD:MM:SS] Telescope DEC
HA = '01:48:03.360' / [HH:MM:SS] Telescope hour angle

On 5/8/14, Peter Melchior notifications@github.com wrote:

Do the new y1p1 data have the RA/Dec in the header?


Reply to this email directly or view it on GitHub:
#24 (comment)

Erin Scott Sheldon
Brookhaven National Laboratory erin dot sheldon at gmail dot com

@esheldon
Copy link
Collaborator

esheldon commented May 8, 2014

(well maybe not wrong if it really was targeted at 0,0

@pmelchior
Copy link
Owner Author

I like the second better. The first is suspiciously close to zero...

Anyway, so I can pull them from the header now. Needs: a place to put them in the viewer.

@kadrlica
Copy link
Collaborator

Along the same lines, it might be useful to have the date the exposure was taken. I think DATE-OBS is the header keyword that you want:
DATE-OBS= '2013-09-01T05:32:05.089479' / UTC epoch
or possibly for the calendar date:
DTCALDAT= '2013-08-31 ' / calendar date from observing schedule

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants