PT Observers (any anyone else who may be interested)-
MOP is now under a version control closely related to that of the rest
of the 'OP's. In practice, when observing under "normal" photometric
contidions, the observer should set up the current IOP on 'mth:
sdssmth ~% setup iop
This will setup a well tested, current version. Each version to be
used now has a tagged version number. It will be listed at startup,
for example:
IOP_VERSION=m2_0_0
It may be a good idea to record the version used in the log. I plan on
recording it there automatically pretty soon.
A tagged version will remain constant: IOP version m2_0_0 a year from
now will still be the same as it is today. If it is still on disk on
sdssmth, you can setup a version of IOP explicity:
sdssmth ~% setup iop m2_0_0
Note that, because of limitations on disk space on 'mth, only a few
non-current versions will be available. If you really want an older
version that is not installed, you can follow the instructions for
installing IOP from cvs found on the sdsshost web page:
http://sdsshost.apo.nmsu.edu/sdssProcedures/swInstall.html#iop
In these instructions, "tag_name" will be the version of IOP you want,
something of the same form as m2_0_0. (Versions of IOP beginning with
a "v" instead of an "m" are versions tagged for the 2.5m instruments,
and will not generally be good choices for running the PT. This may
change someday. The numbering scheme for MOP versions of IOP follow
the traditions of the IOP versions, with the exception of the "m"
replacing the "v".)
When the current version of IOP (that setup using only "setup iop" and
no further arguments) changes I will announce it by email to the
observers, and the versions corresponding to current, test, and old
should be recorded on the whiteboard in the control room.
In general, observers will not need to keep track of version numbers
of IOP for the PT. (This is not true of the IOP's for the 2.5m
instruments.) Instead, the observer can use the chain mechanism:
If there is a version in need of testing, this can be set up using the
"-t" (for test) option:
sdssmth ~% setup iop -t
I expect that in practice most MOP testing ("shaking") will be done
during non-photometric nights when I am at the observatory, and I will
tell the observer in person what I want tested and how. If for some
reason I want some shaking earlier, I will send email instructions to
the observers, who will then wait for the next suitable
(non-photometric) night and do the testing then.
If for some reason the current version fails in a circumstance where
the previous current version would not have, the observer will be able
to revert to the previus current version using the version declared
"old". To set up the old version, use the -o option:
sdssmth ~% setup iop -o
At present, I believe the old version points to an exact copy of the
current version. I did this for two reasons: first, no suitable truly
old version is on 'mth, and second, if I somehow goofed up the CVS and
didn't get the files installed as current that I thought I did, you
can get to the stable version we've been using for the past 3 months
or so in my usrdevel directory. In the future, the old version will be
a genuinely old stable version.
If there is ever a new, well tested version that for some reason is
not declared current, it will be declared as "new", and can be setup
as follows:
sdssmth ~% setup iop -n
I don't anticipate this happening very often, if ever. Lastly, for the
sake of completeness, if you ever want to set up my development
directory, it can be done using:
sdssmth ~% setup iop -d
This should only ever be done if I (or another MOP developer) is
sitting there at the same keyboard and instructs that this be done.
-Eric