Trajectory plots are usually made once a year, and represent the planned Cassini trajectories for the
upcoming year. The Trajectory Plots text file in the reference folder
has some information about generating trajectory plots. There have been some updates to the procedure since
the file was written:
- You can use the getEphemData.py file in the reference folder to create the ephemeris files in
step 2. It is faster than using a web browser to view and download the data.
- All times in the 091005_EventsTable_091207.xls file in step 3 have been extracted to the file
times_list.txt in the reference folder. You still need to create the cassini_orbits.txt file and
follow the instructions for generating tilt values.
- Use this bash one-liner to convert the .ps files to pdf files in step 4, assuming you are in the
directory containing the .ps files:
for f in $(ls *.ps); do pstopdf ${f}; done
- File sharing is not enabled on the space server, called the Cassini server in step 5. Scott can
help with transferring the files to the server and modifying the trajectories.html file on the
server
- Since the UIowa ephemeris data are updated occasionally you should generate trajectory plots for
the past few years when making new plots. Generating the plots is fairly quick.
The
Website Script Maintenance text file in the reference folder has some
information about tasks needed to keep the automated processing working. There have been some updates
to the procedure since the file was written:
- You can use the getEphemData.py file in the reference folder to create the ephemeris files in
step 2. It is faster than using a web browser to view and download the data.
- APL sometimes updates the version of the data files (currently at v38). Updates to data files from
years ago can cause the 20DayAuto processing to bog down, so 20DayAuto now downloads all new files from
APL but only processes new files for the current year and the prior year. If APL generates newer
versions you can use a text editor to compare the new and prior versions of a few files to see if
the changes will affect our IDL programs.
- The kill_20DayAuto.py task is now run one hour before 20DayAuto runs in order to kill 20DayAuto if it
is still running after 23 hours.