Differences between revisions 6 and 8 (spanning 2 versions)
⇤ ← Revision 6 as of 2022-08-04 19:11:30 →
Size: 3988
Editor: AnchalguptaATligoDOTorg
Comment:
← Revision 8 as of 2022-08-04 19:14:34 → ⇥
Size: 3298
Editor: AnchalguptaATligoDOTorg
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
* See [[https://git.ligo.org/40m/scripts/-/blob/main/docker-compose.yml| docker-compose.yml]] for how the scripts are configured to run on optimus. ==== Configuration ====

See [[https://git.ligo.org/40m/scripts/-/blob/main/docker-compose.yml| docker-compose.yml]] for how the scripts are configured to run on optimus.
Line 66: Line 68:
The FSSSlow script was not properly documented and it was not working, so I had to use one that I knew worked from CTN. This scripts lives in ==== Stop a particular script ====
To stop a container (should be done if debugging the code on another computer):
Line 68: Line 71:
/opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/PIDLocker.py {{{
sudo docker stop <container_name>
}}}
Example for IMC autolocker:
{{{
sudo docker stop scripts_AL_MC_1
}}}
Line 70: Line 79:
and uses a configuration file

/opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/PIDConfigFSS.yml

The script runs all the time inside docker container which keeps it running. The heart-beat blinker shows if the script is active or not, but it only starts working when C1:IOO-MC_LOCK is 1 and C1:PSL-FSS_SLOWLOOP is 1. The second channel is a button on C1PSL_SLOW screen to engage autolocker. It has to be turned on for FSS to work.

 

docker instructions:

The following message is displayed on login in optimus:

-------------------------------------------------------------------------
This computer runs four services as of Feb 18, 2022 for 40m lab. To check
status of these services, type
> sudo docker ps
For restarting a particular service, type:
> sudo docker restart container_name
where container name can be found from ps command above.
Fimilarly, to check status of a service, type:
> sudo docker logs container_name		 ==== Start a particular script ====
To start the container from stoped state:
{{{
sudo docker start <container_name>
}}}
Example for IMC autolocker:
{{{
sudo docker start scripts_AL_MC_1
}}}

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

autolockMC.py

 /opt/rtcds/caltech/c1/Git/40m/scripts/MC/ 

ALConfigMC.yml

Keeps IMC locked.

scripts_AL_MC_1

autolockPMC.py

 /opt/rtcds/caltech/c1/Git/40m/scripts/PSL/PMC/ 

ALConfigPMC.yml

Keeps PMC locked.

scripts_AL_PMC_1

PIDLocker.py

 /opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/ 

PIDConfigFSS.yml

Adjusts Main laser temperature to keep PZT actuation around 0.

scripts_PID_FSS_Slow_1

Docker

Configuration

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

Stop a particular script

To stop a container (should be done if debugging the code on another computer): 

sudo docker stop <container_name>

Example for IMC autolocker: 

sudo docker stop scripts_AL_MC_1

Start a particular script

To start the container from stoped state: 

sudo docker start <container_name>

Example for IMC autolocker: 

sudo docker start scripts_AL_MC_1

Check IP address of running containers

To check the IP addresses of running containers: 

> sudo docker inspect -f '|| {{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}   ||   {{.Name}} ||' $(sudo docker ps -aq)

Computers_andScripts/AlwaysRunningScripts (last edited 2022-11-18 00:59:19 by AnchalguptaATligoDOTorg)