[Jon, Pooyan, Tyler]

A few computer machine changes have been made. 

• Logrus moved from 1119 to 1129. It is up and running with the same IP address as before. 
• A new Windows machine (host name: spica, IP:192.168.1.14) is installed in the 1119 server rack. It is connected to the RGA scanner with the serial port and is specifically used for that purpose. 
  • Update: The machine was off on 6/25, although it was left on 6/24. We think that it might have been because of Windows' default setting to suspend/hibernate the machine after idleness. To resolve this, I used  "powercfg /change" command to set all the following parameters equal to zero. The machine is still running on 6/26. 

    monitor-timeout-ac
    monitor-timeout-dc
    disk-timeout-ac
    disk-timeout-dc
    standby-timeout-ac
    standby-timeout-dc
    hibernate-timeout-ac
    hibernate-timeout-dc

• A new Debian machine (hostname: megatron, IP:192.168.1.16) is installed in the 1129 server rack. This machine is intended to be used for FEA/simulation work. A new 2TB WD Green SSD is used as its main disk drive. 

   At the moment, “controls” is the only user, and there are no apps/libraries installed on the machine.

  • Update: Jon installed LIGO cds-workstation tools and MiniConda on 6/26. 
  • Update: Pooyan and Liu set the following conda environments:
    • Env named “finesse” with Python 3.12.3 and Finesse version 3.0a24 installed. Finesse was installed via the source code. The subdirectory “/home/controls/packages” is used to store the package sourcecodes.
    • Env named “fenicsx” with the same version of Python and Finesse as the previous env, with the latest version of FEniCSx (0.8) and the test-mass-thermal-state installed.  

Set-up of the first CDS workstation for 1129, ws3, is complete and the machine is ready for use. The login credentials are the same as the other lab machines.

All that now remains is to install a permanent cable tray for running the new Ethernet cables between the electronics rack and bench (they are currently dangling from the suspended lights).

Today I installed the second desktop workstation in 1129. The new machine is an Intel NUC13ANHi5, with a 12-Core Intel i5-1340P CPU, 32GB DDR4 RAM, and a 1TB SSD.

I loaded it with a fresh installation of Debian 12 and installed the LIGO CDS workstation (control room) tools. It is assigned the hostname ws4 and and the static IP address 192.168.1.19 on the local lab network. Like the other CDS workstations, there is just one user account accessible with the usual credentials.

The machine is fully set up and ready for use.

One ongoing work is to make all lab machines automatically backed-up on Scribe on a daily basis. The updates should be boatable and stored for some time (potentially a few weeks) on Scribe. Making whole disk images has already been tried for some of the machines with no problems. (e.g., Cymac and WorkStations)

The same thing can not be done with Chimay though, as it currently has one huge RAID-controlled volume that stores all the information (OS, home directories, and NDS-downloaded data). Creating daily full disk images of such a system is not practical. 

Here is the plan we came up with to overcome this issue:

1. Create one full disk image of Chimay and store it on Scribe (it was already done)
2. Move the nds-downloaded raw data temporarily to Scribe and remove it from Chimay
3. Make another full disk image of Chimay
4. Burn this image to a single disk and boot chimay with it

5. Restore the rest of Chimay disks and move the NDS data back

    

On the weekend (Sat and Sun 9/7-8) I tried to execute these steps. There wasn't enough free space left on Scribe to move all the NDS data to it, so I stored part of this data temporarily on WS4. Then I also checked storage-consuming directories and, in one case, removed some non-important stored files. As there was no free space left on Scribe to execute step no. 3, I initiated storing the image on WS3. Unfortunately, a couple of different trials of the image-creation process failed as there was not enough free space on WS3 to accommodate Chiamy image as well. I was not able to reduce the image size such that it can be stored on WS3. 

These are the options left for us to get this work done. 

1. Distribute the NDS files between different machines to make enough free space on Scribe for the image and then follow the previous plan
2. Shrink the Chimay drive size, create the image and then follow the previous plan
3. Temporarily transfer some services to Megatrone (Network gateway, Wiki, elog) and recreate chimay and its services from scratch

Port 80 is kept closed by default. This might be causing the certbot auto-renewal cronjob to fail. Therefore we must renew the certificate manually.

Step 1: Open port 80. (This is needed as the certificate renewal process runs some tests which requires client communication over port 80)

Step 2: Run the following command

sudo certbot certonly --force-renew -d richardsonlab.ucr.edu

Step 3: Confirm the certificate was renewed by running the following command

sudo certbot certificates

Cross-linking instructions: How to run a Jupyter notebook in your custom Conda environment

1. Turn off the RGA filament and disconnect it.

2. Record the pressure and then close the angle valve and gate valve on the RGA line to isolate it from the system.

3. Turn off the backing and turbo pump and let the turbo pump spin to a stop by slowly leaking the chamber. The slower the safer.

4.Slowly open the vents on the chamber and the turbo pump. Making sure not to raise the pressure too fast.

5. Once done venting the chamber, open the lid by removing the bolts and prying the lid open with a long flat head screw driver.

6. Removed previous parts and placed them into clean bags. Place new parts inside of the chamber and group them together close to the center.

7. Place the lid back onto the chamber and tighten the bolts in a circular pattern until tightened all the way with the wrench.

8. Make sure all vents are closed and turn the backing pump back on.

9. The turbo pump can be turned back on when the pressure reaches e-1 torr.

10. Wait until the chamber reaches a pressure of e-6 torr before opening the angle and gate valve on the RGA line. After the RGA line is open and the pressure is still below e-6 torr, the RGA filament can be turned on and a leak test of the lid should be performed.

11. After the leak test shows no leaks, proceed with starting the low temp bake.

Below are a basic diagram of what the RTD measurement circuit logically looks like and an example schematic of the actual wiring. The schematic wiring will be placed internally into a chassis, connected to the RTDs via DB25 cable.

The custom front and rear panels for the RTD readout chassis arrived last Friday. I installed them in the chassis frame to check their fit. They fit very well, so all that now remains is to complete the internal wiring and test the connections.

The chassis panel designs are archived to LIGO-D2300452 and LIGO-D2300453.

Below is the current state of the RTD readout chassis wiring. Initial continuity tests seem good, will run through one more time to confirm.

I performed another continuity test on the RTD chassis wiring, and everything seems to be set up correctly. The chassis should be ready for installation.

Below is the proposed schematic for FROSTI optical testing, chosen so enough space is allotted for prototype assembly.

Steps to be taken include:

1. Reconstruct FLIR staging apparatus
2. Move test mass stand-in to cleanroom
3. Mark FLIR camera position on cleanroom optical table at correct distance
4. Run ethernet cable into cleanroom
5. Move FLIR aside to allow for more assembly space
6. Upon assembly completion, reposition FLIR onto optical table again

Tentative plan is to begin setup early next week.

Group Meeting slides for Non-deterministic Heater Response.