/u/ecs/soc/info/long-term_schedule.info Tina usually sends the long-term schedule as an ASCII text file. It may occasionally be mislabeled or mis-named as a .doc file, try saving it first and look at it before asking her to resend. Save the attachment in /u/ecs/dsn_longterm/, USING THE NAMING CONVENTION of the file that's already there (e.g. longterm.w30-04 for weeks 30 through 04 [following year]). After saving the new one, DELETE the one that was already there. NOTE: Delete keyhole file if the longterm schedule is more up-to-date Run the steps that do a manual update of the graphical schedule, i.e. get_dsn_all and make_dsnplots. The get_dsn_all will overwrite the long-term schedule with any newer information fetched from the DSN ftp site. Tina usually sends out a separate schedule for upcoming keyholes, instead of just sending an updated longterm plan that covers the keyhole. What to do with it? Just as with longterm plans: put in the /u/ecs/dsn_longterm directory, name it e.g. keyhole.mar05 (the part after the dot can be anything...). I've made sure that a keyhole plan will overwrite anything wrong or outdated in an existing longterm plan. BUT that also means that if we get an updated longterm plan (covering the keyhole), the updates will be overwritten by the keyhole plan.... So, the keyhole plan will have to be deleted in that case. Note also that there should *never* be two different keyhole plans in the dsn_longterm directory... that would obliterate any regular longterm plan between the two.