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
/opt/rtcds/caltech/c1/Git/40m/scripts/PSL/FSS/PIDLocker.py
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
In case, you have just rebooted the machine, to start these services do
following:
> cd /opt/rtcds/caltech/c1/Git/40m/softchansmodbus
> sudo docker-compose up -d
> cd /opt/rtcds/caltech/c1/Git/40m/scripts
> sudo docker-compose up -d
To stop the docker services completely, for example before a reboot, do
following:
> cd /opt/rtcds/caltech/c1/Git/40m/scripts
> sudo docker-compose down
> cd /opt/rtcds/caltech/c1/Git/40m/softchansmodbus
> sudo docker-compose down
This should remove all active containers from the computer.
To check IP address of running containers, type:
> sudo docker inspect -f '|| {{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}} || {{.Name}} ||' $(sudo docker ps -aq)
The softchansmodbus directory runs modbusEPICS docker image to host some
useful soft EPICS channels. The scripts directory runs pyep docker
image to run MC autolocker, PMC autolocker and FSS PID locker.
-------------------------------------------------------------------------
For checking log files of autolocker script, on optimus do:
sudo docker logs scritps_AL_MC_1
For checking log files of FSS PID loop, on optimus do:
sudo docker logs scripts_PID_
In the above commands, add < | tail -15> to just see the most recent 15 lines in the log file. change 15 to whatever number of lines you want to see from the end.
At any time, if you want to know how docker is running stuff, check out the /opt/rtcds/caltech/c1/Git/40m/scriptsdocker-compose.yml file for self-explanatory script usage.
I'll add some documentation on the wiki soon. That is indeed required and should have been done already.
Debugging scripts:
All scripts could be debugged by running them on rossa by directly using python command. You can stop the docker container on optimus using:
sudo docker stop container_name
and then run the file on rossa to check it's behavior. After debugging and fixing any issues, please commit the file to gitlab repo and go back to optimus and restart the docker container:
sudo docker restart container_name
I'll add this procedure to a wiki page as well.
Reverting back to systemd on megatron
The setup on megatron was not removed at all. All service files exist in same place and old scripts can be started in the old manner by doing following on megatron:
For FSSSlow:
sudo systemctl enable FSSSlow
sudo systemctl restart FSSSlow
For MC autolocker:
sudo systemctl enable MCautolocker
sudo systemctl restart MCautolocker
For diabling these services again, do:
sudo systemctl stop FSSSlow
sudo systemctl disable FSSSlow
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.
I have added above instructions on megatron motd. So on loging into megatron, these updated instructions would come.
If someone wants to fix the old scripts and use systemd for managing those scripts, please do so but I won't be able to help in debugging those old scripts. The shell scripts are very complicated and beyond my knowledge and python scripts are lacking documentation.
I'm happy to help debug or extend the functionality of the new scripts that live in the git directory. |