Some Quick Timeline Basics		
			MDM  Ver 1.0  5-Sep-97

Edit the .tim files in /tsw/obs_dev/timeline on diapason
(you can edit on cheyenne, but diapason is recommended)

IDL> timeline, filename, date
IDL> timeline, '/tsw/obs_dev/timeline/tv_3days1.tim', '21-Jun-97 5:00'
IDL> timeline, auto=6, /z	;for tv_3days1.tim
				;/z makes the disk usage gif files
IDL> doc_library, 'timeline'	;to see the "auto" codes

IDL> .run web_seq
IDL> web_seq_do_timeline	;make timeline and .atim html

On Cheyenne, do the following to pull the /tsw/obs_dev
contents over and to update it's local /tsw tree
	% mirr_obs_dev
To check, do
	% ls -ltr /tsw/obs_dev/timeline
and check the file creation dates

A temporary method for copying the files to the FOT holding
area is
	% ~/mons/copy_time	# as user trace on cheyenne

Send mail to "trace_fotops@sag" announcing that the memory loads
and timeline inputs are ready.

------------------------------------------------------------
To make memory loads, a sample is
	IDL> topsdb, 'all_tv2.slst'
	IDL> topsdb, 'all_tv2.slst', aec='/tsw/dbase/tables/aec6.tab'

To reformat the DPS data on cheyenne (temporarily)
	IDL> .run go_ref_dps


------------------------------------------------------------
There is a need to be able to specify "sub-modules" for the
science timelines so that a series of instrument commands can
be specified.  I'd like to propose the following format which
is identical to the science plan file.


REL     +00:00:00       CMD  icsqreg (reg=$g1, val=9)
REL     +00:00:01       CMD  icsqreg (reg=$g2, val=7)
REL     +00:00:01       CMD  icsqreg (reg=$g3, val=12)
REL     +00:00:01       Start DPM.ift_speed1024

You can put any valid instrument command after the CMD
field.  The REL field says that it should be that many
hours:minutes:seconds after the previous command.  You
can have start sequence commands similar to the science
plan file.  I'd suggest naming conventions similar to
the sequences (first three characters are all caps, so
it's COM, or TDT, or DPM, ...).  The file extension should
be .utim to indicate a user timeline file.  There should
be no ABS time references within the the .utim file.

The science plan file would then have a reference of the
form

ABS	06:30:00	UTIM COM.GTI2_jitter_start

(although if the UTIM file in this case would be a single
command, I'd suggest a different mnemonic in the .TIM
file (like JSTART) which maps into the one CC command to
set the mode).

Comments/suggestions/questions are welcome.

Mons

PS: I don't know if the spacecraft ATS system will accept
a series of separate commands which all have the same 
time-stamp.  That is why I've always had a series of 
consecutive commands separated by at least 1 second.  I'll
need to check on that with the FOT/CMS team.