Functions used for SCCS revision control
All station code is kept under SCCS revision control, and a number
of Unix scripts have been created to ease use of SCCS. These functions
are summarized below:
- putbck fileName area
- Places a fileName back under revision control.
The name of the file must be specified and the area
must be given the first time the file is placed under SCCS.
the Code which was written in Green Bank and has no use at
the VLBA.
Executing putbck without arguments causes the a help
message to be displayed.
- chkout fileName
- Checks out a fileName for editing from SCCS.
No other person may edit this file until
it is putbck.
The name of the file must be specified.
Executing chkout without arguments causes the a help
message to be displayed.
- retreive fileName [yymmdd]
- Retrieves a fileName from SCCS, but this
file can not be editted.
The name of the file must be specified, but the date
for which the file should be retrieved is optional.
Specifing a date allows examination of old version of the files.
Executing chkout without arguments causes the a help
message to be displayed.
- sccsinfo
- Displays summary information about all OVLBI files
currently checked out of SCCS.
Updating PHOBOS
Some of the Real-Time system (PHOBOS) input files are kept under
SCCS (ie ignore.cmd, anomaly.dat and monitorVsop.dat).
For SCCS changes to these files to take effect on PHOBOS, the files
must be placed on the PHOBOS real-time hard drive. To update PHOBOS,
use the Unix Script updatePhobos.
- updatePhobos fileName
- Copies fileName to the real-time hard drive.
The file is place in the directory /hd0/in.
Executing updatePhobos without arguments causes the
most recently edited file in the current directory to be
transfered to PHOBOS.
glangsto@nrao.edu, Last update: 2000 Sept 11