Programmer's reference

$\cal OYST\!ER\,$uses an external library ( containing C and FORTRAN objects. This library must be sharable in order for IDL to access it (via the call_external command). Aside from the $\cal OYST\!ER\,$specific code (written in C), this library contains five external libraries. These are:

After the standard installation procedure described above, manual re-compilation can be performed by going into the C source directory source/c, and editing Makefile. (Please note that the Makefile is the result of a concatenation of and Makefile.$<$uname$>$.in performed by the standard installation procedure.) Then run make clean and make to compile the library, which is named Copy this file into the sub-directory of the $\cal OYST\!ER\,$home directory corresponding to your operating system using the provided shell scripts release.Darwin or release.Linux. into the $\cal OYST\!ER\,$home directory. Please send a copy of the Makefile to the author if you had to modify it.

This procedure should work for LINUX and DARWIN. $\cal OYST\!ER\,$will detect your OS, and then know the path to the shared library and the binary JPL ephemeris file (which differs between MAC and PC based work stations), residing in directories linux and darwin under the main $\cal OYST\!ER\,$directory.

To recompile and install the IDL procedures, start up IDL (in the idl directory) with the command file, i.e. idl c, which will then compile the IDL code and save it into files oyster.cmb and oyster.cpr. The command file will then end the session. You should use $\cal OYST\!ER\,$first to recompile the crossindex subdirectory of the catalog directory, if the code and catalog data distribution tape was not specifically assembled for your architecture. (This is because the crossindex files are binary files in XDR format.) To recompile the crossindices, type get_crossindex,1. To exit the session, type quit.

Finally, it might be necessary to re-create the binary ephemeris file used by NOVAS. To do this, go into the jpl subdirectory and follow the instructions in README.1st.