Always Running Scripts
On Optimus through docker
On the computer optimus mounted at 1X4, following scripts run inside docker containers perpetually:
Name |
Location |
Arguments |
Description |
Docker container name |
/opt/rtcds/caltech/c1/Git/40m/scripts/MC/ |
Keeps IMC locked. |
scripts_AL_MC_1 |
||
/opt/rtcds/caltech/c1/Git/40m/scripts/PSL/PMC/ |
Keeps PMC locked. |
scripts_AL_PMC_1 |
||
/opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/ |
Adjusts Main laser temperature to keep PZT actuation around 0. |
scripts_PID_FSS_Slow_1 |
Docker
* See docker-compose.yml for how the scripts are configured to run on optimus.
Start all scripts
* To start all docker script containers, need to first start sot channel docker containers first. ssh to optimus:
> cd /opt/rtcds/caltech/c1/Git/40m/softchansmodbus > sudo docker-compose up -d
Then start all docker script containers using:
> cd /opt/rtcds/caltech/c1/Git/40m/scripts > sudo docker-compose up -d
Stop all scripts
To stop all the scripts on docker, cd to this directory and do:
> cd /opt/rtcds/caltech/c1/Git/40m/scripts > sudo docker-compose down
Checking status of scripts
Running services container names and statuses can be checked by:
> sudo docker ps
To check the logs of a particular script (whatever they priont out to stdout)
sudo docker logs <container_name>
Example for IMC autolocker:
sudo docker logs scripts_AL_MC_1
Add | tail -10 to see the last 10 lines in the logs.
Restart a particular script
If you made a change to a script or its configuration files, to get changes loaded, simply restart the container by:
sudo docker restart <container_name>
Example for IMC autolocker:
sudo docker restart scripts_AL_MC_1