|
Size: 3051
Comment:
|
Size: 3051
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 32: | Line 32: |
| by '''op140m'''. | by '''op340m'''. |
This page describes, or has links to descriptions of, all scripts used at the 40m.
Find the Locking Scripts here.
Scripts that run all the time (usually):
Name of script |
Computer where it lives |
What it does |
Notes |
PSLWatch |
op340m |
Runs lockFSS, lockMZ, lockPMC when appropriate |
|
autolockMCmain40m |
op340m |
watches the MC. Runs mcup and mcdown |
|
FSSSlowServo |
op340m |
Watches C1:PSL-FAST_MON and servos C1:PSL-SLOW_DC |
|
blinky |
op340m |
monitors C1:PSL-AUTOLOCK_BEAT and C1:IOO-MC_AUTOLOCK_BEAT |
|
RGAlogger |
op440m |
gets data from RGA nightly |
Runs as a cron job |
autoburt |
op440m |
backs up EPICS control settings hourly |
Runs as a cron job |
rsync.backup |
fb40m |
backup minute trend files and /cvs/cds/caltech to the archive in Powell-Booth |
Runs as a cron job |
nodus |
Provides NDS access from off-site |
|
|
nodus |
Provides DAQ channel access from off-site |
|
|
others |
|
|
|
RGA logger
RGAlogger In $SCRIPTS/RGA, it polls the RGA for data and settings, and puts these into two files:
RGA-date.data
RGA-date.settings
both in the $SCRIPTS/RGA/logs directory. It also checks the file $SCRIPTS/RGA/alarms/RGAalarms.spec for limits on certain AMUs, and compares the current data to the limits. If the current partial pressure of a given AMU exceeds its specified limit, it puts that information into a file called RGA-date.alarms. Run as a cronjob every day at 12.05 am by op340m.
bobafett.pl
- Location: $SCRIPTS/starwars/
- Name: bobafett.pl
- Use: run without additional arguments
This script can be used to manually align a component (TM or TT-PZT stage) in the PIT and YAW using the keypad on the keyboard. It does exactly what the (1D) sliders do in the EPCIS screens, but you don't have to move the mouse around when swapping axis.
When started, the user will be presented with a menu with the choice of all the components of the 40m.
With the Num Lock 'ON', the up(8) and down(2) arrows will move the component in positive and negative PIT respectivily. While the left(4) and right(6) will move in positive and negative YAW, respectivily.
To change the step size, you use the (7) and (9) keys to increase and decrease, respectivily.
The change is written directly to the '_COMM' channel of the component.
When one of the PZT stages is chosen, the step size is automatically multiplied by 10k (which will be shown).
The script can be ended by pressing 'q'.