Warning |
---|
The file format will be changing slightly when we update the TCS to v1.8 in the near future. Stay tuned for more details. (posted - 2020 Feb 13) |
Tracking/Pointing Data for ephemeris targets can be made available at DCT LDT in several ways:
- You may submit a data file prior to your arrival at the site,
- You may bring your data to the site on a thumb drive,
- You may have your TO generate the data on your behalf.
Data Submission
Whether you chose to submit you data file prior to your arrival via email or bring your data with you, the target information will be submitted by your TO. Please check with them Ephemeris tracking is done by the Telescope Control System (TCS), and so any data file the observer chooses to prepare in advance will need to be given to your TO to load into TCS. Please check with your TO at the beginning of the night that your data is available to them (note; it will likely be your TO that uploads the data if you bring a thumb drive so please have it available for them). Regardless them (either in email or via USB drive). Regardless of the chosen method of submission submission, the formatting requirements are the same and the files should be saved with the .eph file extension.
Tip | ||
---|---|---|
| ||
The date 12 data columns are: Year, Month, Day, Hour, Minute, Seconds, RA (hours min sec), and Dec(deg min sec), with the following format: yyyy mm dd hh mm ss αh αm αs.sssss ±δd δm δs.s |
Info | ||
---|---|---|
| ||
2014 09 27 09 40 00 20 56 58.82 -19 55 39.4 2014 09 27 09 42 00 22 56 58.78 -19 55 39.4 |
Warning |
---|
The files should contain nothing except those columns: no column headers, and no meta data. For this reason, you should inform your TO of the Reference Frame for the data. Our system assumes Apparent coordinates, but the frame type can be set by the TO each time a new target is selected. |
On Site Data Generation
ss Note: All dates / times are UT. |
***From "Telescope Control System External Interface Definitions" (Sec 3.3.5.1): The first line of the ephemeris file contains the name of the object and the frame of reference in which the positions are specified. The frames of reference supported are the same as those supported with the target command. The target name must be provided; if missing, the frame is assumed to be J2000.0.
Note |
---|
The final line of the ephemeris file may include the reference frame for ephemeris: For J2000 coordinates: "FK5 J2000.0 2000.0" For apparent coordinates: "APPT xxxxxxxxxxxxx" (Need this type to be generated by TCS to have a look.) Note: If this line is not included, you need to inform your TO of the reference frame. In the absence of specification, TCS will assume ________. |
Info | ||
---|---|---|
| ||
2020 10 25 01 43 00 03 17 11.826 +36 35 33.10 |
On Site Data Generation
...
You may have your ephemeris data created from the Horizons database by your TO during your observing run. In all cases it is highly recommended that this process be completed before you are on sky for the night. The box below lists the information that you will need on hand to generate these data.
Tip | ||
---|---|---|
| ||
|
Note |
---|
Data generated in this way are generated in Apparent Coordinates, thus Ephemerides generated from the TCS / Horizons interface may be done in either FK5/J2000 or Apparent Coordinates. If you select Apparent, the apparent RA and Dec is what will appear in your image headers. Similarly the epoch will be reported as the current decimal year. Selecting FK5 will yield the J2000.0 RA and Dec populating the FITS headers. |
Detailed notes on the data generation process maybe found here.