Differences between revisions 6 and 15 (spanning 9 versions)

Always Running Scripts

Contents

On Optimus through docker
Reverting back to systemd on megatron
1. MC autolocker
2. Disabling the services

1. 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	scripts_PID_FSS_Slow_1

On the computer megatron mounted at 1X4, following scripts are running as systemd services:

Name	Location	Arguments	Description	Service name
PIDLocker.py	`/opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/`	PIDConfigFSS.yml	Adjusts Main laser temperature to keep PZT actuation around 0.	FSSSlow.service

1.1. Configuration

See docker-compose.yml for how the scripts are configured to run on optimus.

1.2. 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

1.3. 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

1.4. 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.

1.5. 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

1.6. 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

1.7. 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

1.8. 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)

2. Reverting back to systemd on megatron

The setup on megatron is intact. All service files exist in same place and old scripts can be started in the old manner by doing following on megatron:

2.1. MC autolocker

Enable the service first and then restart it.

sudo systemctl enable MCautolocker
sudo systemctl restart MCautolocker

2.2. Disabling the services

For diabling these services to use optimus docker setup, do:

sudo systemctl stop MCautolocker
sudo systemctl disable MCautolocker

Note that one should stop docker containers on optimus before starting these systemd services to avoid conflicting scripts running together.

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

-  ⇤ ← Revision 6 as of 2022-08-04 19:11:30 → 
  Size: 3988
  Editor: AnchalguptaATligoDOTorg
  Comment:
+   ← Revision 15 as of 2022-11-18 00:59:19 → ⇥
  Size: 4238
  Editor: AnchalguptaATligoDOTorg
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
+#pragma section-numbers 2
-Line 2:
+Line 3:
+<<TableOfContents(4)>>
-Line 11:
+Line 12:
-|| [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/PMC/autolockPMC.py| autolockPMC.py]] || {{{ /opt/rtcds/caltech/c1/Git/40m/scripts/PSL/PMC/ }}} || [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/PMC/ALConfigPMC.yml|ALConfigPMC.yml]]|| Keeps PMC locked. || scripts_AL_PMC_1 ||
|| [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/FSS/PIDLocker.py| PIDLocker.py]] || {{{ /opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/ }}} || [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/FSS/PIDConfigFSS.yml|PIDConfigFSS.yml]]|| Adjusts Main laser temperature to keep PZT actuation around 0. || scripts_PID_FSS_Slow_1 ||
+|| [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/PMC/autolockPMC.py| autolockPMC.py]] || {{{ /opt/rtcds/caltech/c1/Git/40m/scripts/PSL/PMC/ }}} || [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/PMC/ALConfigPMC.yml|ALConfigPMC.yml]]|| Keeps PMC locked. || scripts_AL_PMC_1 ||scripts_PID_FSS_Slow_1 ||
 Line 14:
-=== Docker ===
+On the computer megatron mounted at 1X4, following scripts are running as systemd services:
 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.
+|| ''''' Name ''''' || '''''Location''''' || ''''' Arguments ''''' ||  ''''' Description ''''' || ''''' Service name    ''''' ||
|| [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/FSS/PIDLocker.py| PIDLocker.py]] || {{{ /opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/ }}} || [[https://git.ligo.org/40m/scripts/-/blob/main/PSL/FSS/PIDConfigFSS.yml|PIDConfigFSS.yml]]|| Adjusts Main laser temperature to keep PZT actuation around 0. || FSSSlow.service ||
-Line 18:
+Line 19:
-==== Start all scripts ====
+=== 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.

=== Start all scripts ===
-Line 30:
+Line 35:
-==== Stop all scripts ====
+=== Stop all scripts ===
-Line 37:
+Line 42:
-==== Checking status of scripts ====
+=== Checking status of scripts ===
-Line 55:
+Line 60:
-==== Restart a particular script ====
+=== Restart a particular script ===
-Line 66:
+Line 71:
-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 74:
-/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 82:
-and uses a configuration file
+=== 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
}}}
-Line 72:
+Line 92:
-/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

==== Check IP address of running containers ====
+=== Check IP address of running containers ===
 Line 97:
+== Reverting back to systemd on megatron ==

The setup on megatron is intact. All service files exist in same place and old scripts can be started in the old manner by doing following on megatron:

=== MC autolocker ===
Enable the service first and then restart it.
{{{
sudo systemctl enable MCautolocker
sudo systemctl restart MCautolocker
}}}

=== Disabling the services ===
For diabling these services to use optimus docker setup, do:
{{{
sudo systemctl stop MCautolocker
sudo systemctl disable MCautolocker
}}}
Note that one should stop docker containers on optimus before starting these systemd services to avoid conflicting scripts running together.