(Created page with "=== Synopsis === : ephemd <perturbers> <objects> <observers> [options] [command] === Description === : This is a simple, small and lightweight command-line driven ephemerides...") |
m |
||
Line 1: | Line 1: | ||
+ | __NOTOC__ | ||
=== Synopsis === | === Synopsis === | ||
: ephemd <perturbers> <objects> <observers> [options] [command] | : ephemd <perturbers> <objects> <observers> [options] [command] | ||
Line 46: | Line 47: | ||
: '''-j,''' '''--object-file''' <file> | : '''-j,''' '''--object-file''' <file> | ||
:: Pre-formatted orbital elements of small Solar System objects. See also README and the script ./scripts/prep-2-dat2in.sh in the ephemd source package for more details about the format. | :: Pre-formatted orbital elements of small Solar System objects. See also README and the script ./scripts/prep-2-dat2in.sh in the ephemd source package for more details about the format. | ||
− | + | ||
+ | === Leap seconds: === | ||
+ | |||
+ | : '''-l,''' '''--leap-file,''' '''--leap-seconds-file''' <file> | ||
+ | :: An IERS and IETF compilant version of data file describing the annoucements of leap seconds. One of such files can be https://www.ietf.org/timezones/data/leap-seconds.list. You may have to update this file regularly (once or twice per year). Predictions further than the last announced leap seconds are expected to have no insertions. Check the expire date of this file accordingly. | ||
+ | |||
=== Available commands: === | === Available commands: === | ||
Line 65: | Line 71: | ||
: ephem <name> <time> | : ephem <name> <time> | ||
− | :: Generates ephemerides for the object with <name> for the instance or interval defined by <time>. The <name> is taken from the input object file and by default (see `make prepare`) these are either the MPC designation numbers or the MPC temporal names. Official MPC names are not supported now. For instance, use `ephem 1234 ...` instead of `ephem Elyna ...`. The <time> is either a Julian Day instance or can have the format of <JD_start>:<step>:<JD_end> to generate a series of ephemerides. <JD_start>:<JD_end> is equivalent to <JD_start>:1.000:<JD_end>. | + | :: Generates ephemerides for the object with <name> for the instance or interval defined by <time>. The <name> is taken from the input object file and by default (see `make prepare`) these are either the MPC designation numbers or the MPC temporal names. Official MPC names are not supported now. For instance, use `ephem 1234 ...` instead of `ephem Elyna ...`. The <time> is either a Julian Day instance or can have the format of <JD_start>:<step>:<JD_end> to generate a series of ephemerides. <JD_start>:<JD_end> is equivalent to <JD_start>:1.000:<JD_end>. |
+ | |||
+ | : query <RA>,<DEC> <radius> <time> | ||
+ | :: Lists the objects with the respective ephemerides which has an apparent position within <radius> distance from the J2000 coordinate <RA>,<DEC>. <time> can either be an instance (in JDs) or an interval defined in the form of <JD_start>:<JD_end>. In the latter case, this command reports the JD when the object is (nearly) the closest to this point specified by <RA>,<DEC>. Currently, all of the angles (<RA>, <DEC> and <radius>) should be specified in degress. |