search

rosscooperman / betterspacecal

A (much) better version of myspacecal.com
http://spacecalnyc.com
3 stars 6 forks source link

Import Chandra Data #14

Open ronaldbradford opened 11 years ago

ronaldbradford commented 11 years ago

Awaiting technical feedback from Jon on RA/DEC data.

jonroberts commented 11 years ago

I've had a look at the Chandra page. They're not providing the RA and Dec of the source at all. However they are providing the RA and Dec of the guide star. This means that there's a star in the field of view that they're using as their reference point - it's going to be close enough that it's totally valid to use that as the RA, Dec passed in to the converter to push to the site.

Alternatively - and better - each observation in the Chandra data has a link to the proposal. It's the hyperlink under Obs ID. This has the exact Ra and Dec (for example http://cda.cfa.harvard.edu/chaser/startViewer.do?menuItem=sequenceSummary&obsid=15372). If we're willing to scrape down one more layer, this is the exact data.

Time - this is in kiloseconds. So multiply by 1000 to get the number of seconds. There was another telescope that had oddly short observing periods. Which was it?

Image - on each row there's a 'dss' link with a url that's an image of the quadrant of the sky to be observed. We should use this if we can't find an image.

jonroberts commented 11 years ago

Also CAL-ER entries can be ignored - they are calibration periods.

ronaldbradford commented 11 years ago

Ok, so looking at the link, it looks like it has all the data we need.

Target, Observation Id, RA, DEC, Date, Date + time *1000 secs

I can parse that.

Target NameObsIDRADECTime (ks)LTS Bin (week)Schedule DateSIGratingSI ModeConstraintsPreferencesTypeStatusObs. CycleGMBCG J178.26065+01.0405315372178.26001.040510.02013-Apr-22 Apr-22-2013--2:36PMACIS-INONETE_00458(none)(none)GTOscheduled14

Ronald

On Mon, Apr 22, 2013 at 12:21 PM, jonroberts notifications@github.comwrote:

I've had a look at the Chandra page. They're not providing the RA and Dec of the source at all. However they are providing the RA and Dec of the guide star. This means that there's a star in the field of view that they're using as their reference point - it's going to be close enough that it's totally valid to use that as the RA, Dec passed in to the converter to push to the site.

Alternatively - each observation in the Chandra data has a link to the proposal. It's the hyperlink under Obs ID. This has the exact Ra and Dec (for example http://cda.cfa.harvard.edu/chaser/startViewer.do?menuItem=sequenceSummary&obsid=15372). If we're willing to scrape down one more layer, this is the exact data.

Time - this is in kiloseconds. So multiply by 1000 to get the number of seconds. There was another telescope that had oddly short observing periods. Which was it?

Image - on each row there's a 'dss' link with a url that's an image of the quadrant of the sky to be observed. We should use this if we can't find an image.

— Reply to this email directly or view it on GitHubhttps://github.com/rosscooperman/betterspacecal/issues/14#issuecomment-16798388 .

ronaldbradford commented 11 years ago
  1. Get a summary list from http://cxc.harvard.edu/target_lists/stscheds/oldscheds.html
  2. Get related page from list entry (e.g. MAR2513A) http://cxc.harvard.edu/target_lists/stscheds/stschedMAR2513A.html
  3. Get a list of observation id's from page (e.g. 14991)
  4. Get data for observation at http://cxc.harvard.edu/cgi-bin/mp/mp_target.cgi?id=14991
jonroberts commented 11 years ago

Precisely - that should do the trick.