Versions Compared

Old Version 2

changes.mady.by.user Timothy Ellsworth-Bowers

Saved on

compared with

New Version 3

changes.mady.by.user Timothy Ellsworth-Bowers

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 (either in email or via USB drive).  Regardless of the chosen method of submission, the formatting requirements are the same and the files .  Files must be in plain text and should be saved with the .eph file extension.

Tip
titleData Format

The 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.sss ±δd δm δs.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 the ephemeris:

For J2000 coordinates:   "FK5 J2000.0 2000.0"

For apparent coordinatescoordinates:  "APPT xxxxxxxxxxxxx" (Need this type to be generated by TCS to have a look.J20xx.xx 20xx.xx" where the 'x' must be replaced by the epoch of your observing night.  (e.g. the night of 31 October 2020 was J2020.83)

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
titleSample Data Format - FK5
2020 10 25 01 43 00 03 17 11.826 +36 35 33.10
2020 10 25 01 48 00 03 17 11.869 +36 35 31.13
2020 10 25 01 53 00 03 17 11.910 +36 35 29.15
FK5 J2000.0 2000.0
Info
titleSample Data Format - Apparent Coordinates
2020 10 25 01 43 00 03 17 11.826 +36 35 33.10
2020 10 25 01 48 00 03 17 11.869 +36 35 31.13
2020 10 25 01 53 00 03 17 11.910 +36 35 29.15
APPT J2020.83 2020.83

On Site Data Generation

You Instead of preparing your own ephemeris file, you may have your ephemeris data created from the JPL 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
titleRequired Information
  1. Target ID or name - the interface requires either the Horizons ID number of the record of interest or the name of the target.  If you plan to provide the name you will need to ensure correct formatting of the name (including white spaces e.g., "2014 RC" – note the space, without this no target will be found), you will need to inform the TO of the object type (asteroid, comet, satellite, etc...), and in the case of multiple records you will need to select the desired solution.
  2. UT Start and UT End - for these you will want a desired start and end time in hours and minutes as well as a date.
  3. Step size of the ephemeris file (typical is ~2 - 10 minutes unless the object is moving at high apparent speed).
Note

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.

...