General information about the lab facility.

1. Changed sticky floor mats, because close to entrance the cleanroom, both sticky floor had a many died ants on top.
2. The light on top of the internet cable bridge is burned out.. I just saw this today but I am not sure if was like this before.
3. The ant bait traps seem very efficient and right now only a few ants are running around in the lab, most are dead in the bait traps, so probably in a day or two we can change those bait traps.

The replacement door for the HEPA garment cabinet arrived last week, and was installed on Thursday. However, it looks like there's a small gap between the door and where the hinge is attached to the cabinet frame. No screws were provided with the replacement door. If we want to perform any adjustments, we have to be very careful; the screws break very easily.

We moved Frosti into the cleanroom and debugged it to make sure everything was working. One of the DB25 pins broke off at the connector for element 1 so it needed to be recrimped. Element 6 short circuited but fixed with adjustment to the heater power pin position. We connected the power and sensor connectors to the power box and recalibrated the RTD sensors.

For this study, we looked at a simple case with an aLIGO-like test mass geometry (R=0.17m, H=0.2m) plus a barrel RH with 0.02m width at 0.03m from the AR surface with FEniCSx. The irradiance profiles are constant inside the width along the longitudinal direction, and zero outside the width. For the baseline non-astigmatic actuation with constant irradiance azimuthally. We have obtained roughly equal quadratic actuations along the x and y directions, as shown in figure. The total delivered power on the entire barrel is normalized to 1 W. The actuation on the curvature per power Delta S/Delta P in this non-astigmatic case thus is 0.835 uD/W.

For the astigmatic case however, the irradiance for the regions from one diagonal is increased by a given amount, compared to the non-astigmatic case, whereas for the other diagonal regions is decreased by the same amount (thus the total power is unchanged at 1 W). The HR deformation when the power is changed by 50%, for instance, is shown in picture, where the deformation along the x direction is larger than the y direction. The deformation in each direction however remains quadratic, with different curvature per powers for the x and y components, as shown in plot. The actuation on the curvature per power for an increasing amount of astigmatism is shown in plot. In terms of Zernike polynomials, the maximum amount of Z22 (astigmatism) for 1 W of total power is 2um while the remaining curvature content (Z20) is 6nm. This is shown in plot.

[Jon, Cao]

1. Re-routing of cables

We re-routed the connections between the turbo pump and its fan to the controller. Instead of going through the side of the server rack, they are now routed along the the cable tray and came down from the top of the server rack.

2. Planning for vacuum assembly re-configuration

• Move the entire RGA arm to the mirrored CF port, where the Up-to-Air valve is at
• Move the Up-to-Air valve to the calibrated leak port
• Move the calibrated Ar leak the main chamber full-range gauge port
• Move the full-range gauge to the RGA line port

3. First test pump-down

1. With all valves closed, we started scroll pump, pump line quickly got down to 6.08 mbar from atmospheric 1000 mbar (measured by Pirani gauge, channel 3 on controller )
2. We open Lesker angled valve and let the RGA arm pumped down, Pirani gauge read 6.3 mbar while the full-range guage on RGA line reads 4.9 mbar ( channel 1 on controller )
3. We open the pump line gate to expose the pump to the main volume, all gaugues readout immediate rise back up 1000 mbar. After 3 minutes, we started to see channel 3 slowly dropped down. A minute later channel 1 and 2 (main body) also dropped down. The slow pressure dropping speed and 6.3 mbar measured earlier got us suspected that there is some large leaks
4. We proceed to tighten all the ports as the vacuum is pumped down. In particular, we found that large feedthrough port still required a lot of tightening up
5. As we tighten up all the ports, after 40 minutes, the gauges are now
   • Channel 1 : RGA line full-range gauge: 2.55E-1 mbar
   • Channel 2 : Main chamber full-range gauge: 2.60E-1 mbar
   • Channel 3 : Pump line Pirani gauge: 2.94E-1 mbar
   Compare this to the scroll pump manual , Table 1, page 3, the ultimate pressure of the scroll pump is 2.5E-1 Torr (3.3E-1 mbar), we thus managed to achieve scroll pump ultimate pressure
6. Turn on turbo pump : Change turbo pump controller from REMOTE to FRONT PANEL mode by pressing both "COUNTERS" and "MEASURE" buttons at the same time, select "MODE=FRONT"
7. Shorting interlock pin: since we do not have an interlock signal for the controller, use the provided DB-9 connector that has pin 3 and 8 shorted and connect this to the P1 IN connection at the rear of the controller (see attachment 1 )
8. Press "START" on the controller to start the turbo pump
9. The pressure readout from the gauges quickly dropped down. After 3 minutes, the Pirani range is maxed out at 0.5E-3 mbar. After 20 minutes, we recorded the following values:
   • Channel 1 : RGA line full-range gauge: 1.50E-5 mbar
   • Channel 2 : Main chamber full-range gauge: 1.89E-5 mbar
   • Channel 3 : Pump line Pirani gauge: 5.0E-4 mbar
   This is Medium vacuum , we want to further reduce this by 2 orders of magnitude. However, we can run RGA test + helium leak test at this pressure
10. Turn off turbo pump, wait for 10 minutes, turn off scroll pump, open Up-to-Air valve, all pressure gauges indicated pressure returned back to atmospheric pressure

3. To-do actions

• Run RGA test to get information about contamination status of vacuum
• Implement suggested changes in section 2
• Check and modify suspected poor connection: Pirani gauge on pump line. A gap can be seen between connection. There's no good way to tighten it with the screw. Maybe use threaded pin + hex bolt?
• Controller communications

1. I was able to plot the final result with the data to the heater. I attached below the "3Combined_HighTemp_Gaussian_Plot." in this plot we can see better behavior on the Gaussian compared to the plot in ELOG 169, I was using the same data but with a different approach. On the ELOG 169, we have the center point isolated data and this new plot is the temperature more than 70 C isolated because we have a very good heater temperature distinguish do background. For the all data I got I was using a power current of 0.20A. To get the data I waited for 30 minutes until the heater became stable and after that, I started to take snaps, I took more than one snap for each one different 6 positions on the screen, and We can see the positions on ELOG 167.
2. Also I attached the calibration plot ("calibration_plot") between the measurements with the FLIR camera and thermocouple and we can see looks good if we compare the final plot.
3. For better analyses I attached a plot of the calibration line on the Gaussian plot.
4. To do: I will finish the final report.

Upon finishing the FROSTI assembly last week, we ran into some electrical issues. An electrical short was found between two of the d-sub pins (2 and 8). It appears that the pins were somehow coming into contact with the aluminum surrounding them. This was causing the power supply to trip. The issue was seemingly fixed by adjusting the positioning of the cabling leading out of the reflector. When handling the device in the future, please make sure to keep the wiring as undisturbed as possible. The setup is rather fragile, and moving the cabling around could potentially reintroduce a short like this.

Cleaned and baked the Cal Tech FROSTI legs and showed Luke the procedure on how to clean parts.

Below is the procedure we will follow to assemble the FROSTI prototype.

1. Install SS guide rods and bottom Macor spacers in bottom reflector
2. Install AlN elements on top of bottom Macor spacers
3. Install upper Macor spacers on top of AlN elements
4. Feed unterminated power and RTD leads through slots in upper reflector
5. Install upper reflector, using guide rods to slowly lower into position
6. Install vented SS bolts for reflectors; Macor bolts for heater elements
7. Remove SS guide rods
8. Bundle power and sensing cable with PEEK cable ties and SS cable mounts
9. Terminate power and sensing cable bundles with PEEK DB25M connectors

FROSTI assembly was completed today. The RTD and power wires were terminated at the DB-25 connectors and the legs were put on. It is currently placed in front of the stand-in test mass (~5 cm away). The FLIR has also been moved back to it's nominal position. As of now, it appears there are some shorts within the power cabling. This will be a focus of tomorrow's work.

FROSTI assembly began today. After a final set of RGA scans were taken, the vacuum chamber was vented and the reflectors were removed. The chamber was then resealed and pumped down again. 

Today we completed the installation of the Macor hardware and heater elements between the two reflector halves. Tomorrow we will route, bundle, and terminate the power and sensor cables. 

• Used the closest point possible for the reflector in front of the FLIR camera.
• 11:32 am : Turned on the electronic device (current on) for started taking data.
• 11:50 am: Started checking the temperature and the parameters.
• 12:04 pm: Started taking snap after waited for 30 minutes with the current on. Parameters: Current: 0.13A , Volt: 1.8V and Temperature: 51.4 C.
• Note: This snap is in the most close point possible, after that I should be change the reflector position and also the optical focus distance in the FLIR camera.
We can see, in the photo attached below, thought in this closest position the cable connect to reflector is a bit problem to take a good snap also the have issues to keep very uniform triangles (temperature) in the reflector.
• To do: I'll change the position on the light inside to see if the problem it is in the focal point inside the reflector (mirror).

• We changed the FLIR Focus Distance for around 0.55 m.
• Note: The old focus distance was 1.3 m.

• We tested this new focus distances and looks good. I attached a snap below.
Parameters: 0.1 A , 1.5 V and 38.4 C.

• Today we change the distance between the FLIR camera and reflector (3D-Mask with mirrors and light). Now the distance is 0.2032 m.
• Note: This distance is just for take a snap most close possible but we need move again for a little far way because in this distance we can't move up and down the reflector for have data to compare.

Initial tests
• 10:30 am : Started trying take some test with the new position/configuration between the 3D reflector-mask and the FLIR camera.
• 10:41 am : Started running the python code and take a snap. Parameters: 0.10 A, 1.4 V.
• 10:50 am : Started take the snap.It is possible see the triangles, this is a good thing. Negative thing: The middle/center point for the light maybe would be some problems for the future measurements. Parameters: 0.10A, 1.4 V and 41 C.
• 11:00 am : Started working to better align the entire structure. And double-check the distance between the 3D reflector-mask and the FLIR camera, following the instructions in Cassidy's Final FLIR Project Report.
• 11:10 am : Difficult point: I tried to attach the complete FLIR camera to the table, but I had a problem to secure the four screws to the table, the distance is not completely compatible with the table stand. Yesterday I just put two screws in the diagonal position, it works fine, but it's not the correct position to work.
• 12:00 am : Note: Two triangles take more long time to come back a not (low) irradiation position (east and south point).
• 2:00 pm : Started running the python code again.
• Parameters: 0.13 A 1.8 V.
• 2:30 pm: Started take snap. Parameters: 0.13 A, 1.8 V and 49.1 C
• 3:00 pm: Note: This time every triangles was able to come back a low irradiation position.

Test without the black wall.
General test:.
• 11:15 am : Started running the code. Parameters: 0.11 A, 1.9V and focus distance around 0.55m.
• 11:28 am : Started snapping the screen. Parameters: 0.12 A, 1.8V and 44.1 C .
First trying:
• 01:18 pm : Started testing and collection data. Parameters: 0.09 A, 1.4V. Reference position: (0,0).
• 01:28 pm : Started snapping the screen. Parameters: 0.10 A, 1.5V and 37.9 C. Reference position: (0,0).
Second trying:
• 01:34 pm : Started testing and collection data. Parameters: 0.08 A, 1.4V. Reference position: (0,-0.10).
• 01:44 pm : Started snapping the screen. Parameters: 0.09 A, 1.7V and 35.8 C. Reference position: (0,-0.10).
Third trying:
• 01:50 pm : Started testing and collection data. Parameters: 0.08 A, 1.3V. Reference position: (0,-0.05).
• 02:00 pm : Started snapping the screen. Parameters: 0.09 A, 1.4V and 35.4 C. Reference position: (0,-0.05).
Fourth trying:
• 02:04 pm : Started testing and collection data. Parameters: 0.09 A, 1.3V. Reference position: (0,0.05).
• 02:14 pm : Started snapping the screen. Parameters: 0.11 A, 1.6V and 41.7 C. Reference position: (0,0.05).

Note: So today i tried collecting data for every possible position in Y (height) way for starting analyses and compares the triangles shapes. I realize maybe we get a problem because i keep the same time in every try but the final temperature and the parameters change every time, so i will try do a better system to keep the parameters equal, maybe i can wait the reflector be back to a normal temperature after every test or keep the system on all the time and just change the reflector position. I pretty sure this was the problem.

Test without the black wall.

Note: So today i collected data for some positions in axis Y (height) for starting analyses and compares the triangles shapes. I tried keep the same parameters every time.

First position:
• 01:20 pm : Started testing and collection data. Parameters: 0.10 A, 1.6V. Reference position: (0,0.05).
• 01:30 pm : Started snapping the screen. Parameters: 0.10 A, 1.6V and 37.7 C. Reference position: (0,0.05).
Second position:
• 01:34 pm : Started testing and collection data. Parameters: 0.10 A, 1.6V Reference position: (0,0).
• 01:44 pm : Started snapping the screen. Parameters: 0.10 A, 1.6V and 40.6 C. Reference position: (0,0).
Third position:
• 01:50 pm : Started testing and collection data. Parameters: 0.10 A, 1.6V. Reference position: (0,-0.05).
• 02:00 pm : Started snapping the screen. Parameters: 0.10 A, 1.6V and 39.1C. Reference position: (0,-0.05).
Fourth position:
• 02:03 pm : Started testing and collection data. Parameters: 0.10 A, 1.6V. Reference position: (0,-0.10).
• 02:13 pm : Started snapping the screen. Parameters: 0.10 A, 1.6V and 39.6 C. Reference position: (0,-0.10).

Reinstalling the mask and Reconfiguration FLIR position.
• Today i change the aluminum foil inside the 3D mask. After some tries i was able to have a better shape for the triangles.
• I reinstalled the connections (the light with the thermometer point). Also i checked for the focal point inside the reflector, looks fine.
• I did a reconfiguration for the initial tests, without the black wall. I moved the FLIR camera and the Reflector-Mask for other position on the table.
To do:
• Start the test with the power current on.
• I need figure out a better position for the light cables because in front of the mask isn't a good position for us do measurement.

Cao suggested using the project without the reflector and mask because in this case we probably got good images around the screen. So I started this yesterday and today I started to get some data to see the stabilization position and check how the parameters fluctuated. I was looking and taking snaps for an hour and a half. I'll repeat this one more time to make sure we have enough data to do analysis.

To do: The next step is to start collecting data by moving the camera FLIR and covering all six positions on the screen (2x3). Also Aiden is on hand to help and is going to make a new 3D print bridge to have good heater support.

I attached a image for the new configuration below and a snap data.

• The new mask for the reflector.
• 1:40 pm: Started reconfiguration on the FLIR camera project. Changed the old bridge for the new mask-bridge.
• 2:00 pm: Started figure out the best way to cutting the aluminum foil with the new mask. Unfortunately, I had been some problems for cutting the perfect shape triangles with the mask because the size inside the triangle is different (smaller) than cutter/knife, so is not able to do the cut with precious and carefully then maybe I need other tool for this job. Also I tried use the scissor, didn't work. However, just for the initial testing I worked with the not perfect triangles shape.
• 2:49 pm: Started installing/attaching the light in the mask.
• 3:21 pm: Finished installing the light in the mask-bridge.
• 3:22 pm: Started testing the current and voltage in the new mask-bridge for make sure the light cable is working well.
• 3:25 pm: Started measurement the resistance with multimeter.
• 3:29 pm: The measurement looks fine. The multimeter show us 14.1 Ω;
• 3:38 pm: Started putting the reflector( with the mask attached) in front of the black wall.
• 3:44 pm: Started roll the testing with the python code to observer the behavior with this new mask. Parameters: 0.14 A and 1.9 V.
• 4:00 pm: Started snapping. Parameters: 0.13 A and 1.9 V. Final Temperature: 42.7 C.
• 4:02 pm: Started trying again with more current. Parameters: 0.16 A and 2.2 V.
• 4:36 pm: Started snapping. Parameters: 0.16 A and 2.2 V. Final Temperature: 50.3 C.
• 4:55 pm: For now, we can't see the triangles in the snap so i need do some changes.

• To do:
  1. Change the FLIR camera position for the other side on the table.
  2. Start the test without the black wall.
  3. Try a better tool to cut the triangles inside the 3D-mask.

FLIR project updates- Initial tests

• 10:00: Starting test in position 2 cm to the black wall.
• Parameters : 0,305 A, 05,5 V and the temperature inside the mirrors 141,8°C.
• 10:23 Finished this first tried and take snap. The image is attached below.
• The name for the picture for this tried is “AcquisitionImage(Apr-19-2023_10 23)”.

• 10:37. Starting test in another position now 3 cm distance to the black wall ( this is more close than the original position.)
• Parameters : 0,348 A, 05,5 V and the temperature inside the mirrors 160,3°C.
• 10:57 Finished this second tried and take a snap. The image is attached below.
• The name for the picture for this tried is “AcquisitionImage(Apr-19-2023_10 57)”.

• 11:03 Starting test another position 1.3 cm distance to black wall.
• Parameters : 0,347 A, 05,5 V and the temperature inside the mirrors 158,7°C.
• 11:18 Finished this second tried and take a snap. The image is attached below.
• The name for the picture for this tried is “AcquisitionImage(Apr-19-2023_11 18)”.

The next step should be fix the problem with the shape (aluminum foil lid).

• I was able to work on the python code to do analysis on the FLIR-Reflector data.
• I could plot images of total area (Tyler help me on that) with csv file and also could have isolation area for triangles. I have attached examples below. Just for now the images are of different data, so there are some differences in the shapes.
• I'm working on getting a complete analysis code to work with the different positions of the triangles and to be able to do out the statistical analysis.
• Also we keeping have problem to get good data if when we move the camera or the reflector on horizontal or vertical position. I am working a some ideas for that.

Below is the dark noise spectrum of the Red Pitaya, which was measured over the course of a weekend. Additionally, I have successfully measured a signal from the photodetectors with the FROSTI as the IR source, so it seems there shouldn't be any worry of these particular detectors not being feasible for the RIN measurement.

The new FLIR A70 infrared camera has arrived. Tyler and I unpacked it in the lab yesterday. In less than an hour, we succeeded in powering it on and connecting it to the lab network. We have assigned it the static IP address 192.168.1.6.

Online Configuration Portal

The FLIR camera can be configured, as well as stream live data, through a web browser interface. It can be accessed from any workstation on the lab network by navigating in the browser to http://192.168.1.6. The login credentials are stored here (log in with your LIGO.ORG credentials).

Next Steps

The next step is to install FLIR's Python API for controlling and reading out the camera on chimay. The API comes with demo codes which we can use to test the basic connectivity and which will serve as a reference for developing our own Python interface over the summer.

Summary

I have installed the requisite software on chimay for interfacing the FLIR A70 camera in Python. There are two packages required from FLIR:

• Spinnaker SDK, which provides the low-level camera drivers and a C/C++ API.
• PySpin, a wrapper of the Spinnaker library which provides the Python API.

These installations did not work out-of-the-box for Debian 11 (only Ubuntu is officially supported). I had to make several modifications which are documented below for future reference.

This setup has not yet been tested with the camera connected to chimay.

Documentation and Demo Codes

The PySpin package comes with a number of Python demo codes and a complete API reference. These can be found on chimay at the following locations.

• Example codes: /opt/spinnaker/python/Examples/Python3/
• Python API reference manual: /opt/spinnaker/python/docs/PySpinDoc.pdf

Installing Spinnaker SDK

Below were the steps required to install Spinnaker on chimay (Debian 11).

1. Download the Spinnaker binaries (AMD64 architecture) and copy the tarball to, e.g., /home/controls on chimay.
   
   
2. Unpack the tarball contents and enter the new directory:
   $ tar -xf spinnaker-2.6.0.160-Ubuntu20.04-amd64-pkg.tar.gz
$ cd spinnaker-2.6.0.160-amd64
   
   
3. Next, install the dependencies (on chimay, these were all already installed):
   $ sudo apt-get install libavcodec58 libavformat58 \
libswscale5 libswresample3 libavutil56 libusb-1.0-0 \
libpcre2-16-0 libdouble-conversion3 libxcb-xinput0 \
libxcb-xinerama0
 
4. There is one additional dependency, qt5-default, which is obsolete in Debian and no longer available via the package manager (that is, its functionality was absorbed into other Qt packages). I was able to find a workaround based on these instructions.
   
   
   1. Install all the dependencies of qt5-default:
      $ sudo apt-get install qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools
 
   2. Manually remove the qt5-default dependency from the Spinnaker package.
      
      Unpack the spinview-qt_2.6.0.160_amd64.deb package:
      $ mkdir tmp
$ cd tmp
$ ar -x ../spinview-qt_2.6.0.160_amd64.deb
$ tar xf control.tar.xz

Open the file control in a text editor and delete the qt5-default dependency from the Depends list.
      
      Then repackage the contents:
      $ tar cfJ control.tar.xz control
$ ar rcs ../spinview-qt_2.6.0.160_amd64.deb debian-binary control.tar.xz data.tar.xz
$ cd ..
$ rm -rf tmp

This overwrites the original package with a version no longer containing the qt5-default dependency.
      
      
5. Now proceed with running the install script:
   $ sudo sh install_spinnaker.sh

This will install the Spinnaker library at /opt/spinnaker. Spinnaker also provides a standalone GUI application, SpinView, which can be executed from the terminal (from any directory) via the command spinview.

Installing PySpin

The main challenge with installing PySpin was that it is currently only supported for Python <=3.8. The system installation on Debian 11 is Python 3.9 and 3.8 is not available within the package manager. Following these instructions, I manually installed a second version of Python (3.8) on chimay, in a way that should not interfere with the system installation.

The Python 3.8 executable is in the system path and can be run only via the command python3.8. It is not symlinked to python or to python3. Those remain linked to the preexisting Python 3.9.

After installing Python 3.8, I proceeded with the installation as follows:

1. Download the PySpin package (x86_64 architecture) and copy the tarball to, e.g., /home/controls on chimay.
   
   
2. Unpack the tarball contents and into a new directory:
   $ mkdir python
$ mv spinnaker_python-2.6.0.160-Ubuntu20.04-cp38-cp38-linux_x86_64.tar.gz python
$ tar xf spinnaker_python-2.6.0.160-Ubuntu20.04-cp38-cp38-linux_x86_64.tar.gz


3. Move the new directory into the Spinnaker installation directory:
   $ sudo mv python /opt/spinnaker
$ cd /opt/spinnaker/python
 
4. Install the dependencies:
   $ sudo python3.8 -m pip install --upgrade numpy matplotlib
   
   
5. Finally, install PySpin itself:
   $ sudo python3.8 -m pip install spinnaker_python-2.6.0.160-cp38-cp38-linux_x86_64.whl

If this succeeded, you should now be able to enter import the package PySpin as

$ python3.8
>>> import PySpin

without error.

Today I tested the Spinnaker/PySpin software installations (detailed in ELOG #4) with the FLIR camera connected to chimay. It works!

Example codes

I was able to run several of the PySpin example codes. In particular, there is one which connects to the camera and streams live data to a pop-up Matplotlib window that looks very useful. It is called AcquireAndDisplay.py.

When running these, it is important to keep in mind that PySpin requires Python 3.8, which is not the default system version on chimay. So to run AcquireAndDisplay.py, for example, you must explicitly call the correct version of Python:

$ python3.8 AcquireAndDisplay.py

The standard python and python3 aliases are still linked to the system version (3.9), so calling these will result in a PySpin import error.

Git repository

I have set up a git repo for our FLIR camera control code. I have populated it with an Examples directory which contains the PySpin Reference Manual as well as all the example codes (see the README). There is a local copy of this repo on chimay at /home/controls/FLIR.

Other FLIR streaming software

In addition to the PySpin demos, there are several fully developed applications provided by FLIR. While we do not plan to use these long term, they may be very useful for debugging and cross-validation of our Python interface during development:

• Browser interface: From any web browser on the local lab network, navigate to http://192.168.1.6 and log in (credentials here). This interface supports live data streaming as well as full control of the camera settings.
  
  
• SpinView: A standalone application provided as part of the Spinnaker SDK. It supports streaming live camera data as well as saving images and videos. It can be launched from the terminal on chimay via the command: $ spinview
  
  
• Research Studio: This is FLIR's proprietary software, for which we have a one-year license. It can be launched from the terminal on chimay via the command: $ FLIRResearchStudio

Permanent cabling

Since everything appears to be working, I ran a permanent Cat 6 cable from the lab switch to the camera's power+I/O adapter. The adapter is plugged into a UPS-protected power strip overhanging the optical table, as pictured below. To prevent the adapter from unplugging itself under its own weight, I attached a zip tie around the adapter to hold it securely in place.

• 08:59 am: Turned on the electronic device (current on) for started taking data.
• 09:37 am: Tried understanding the error in the focal point. I realized the pillars was in the wrong place and because of that we got problems to keep the reflector in the correct position to FLIR focus.
• 09:58 am: Started checking the temperature and the parameters.Changed the pillars to the original position (0.5645m) just for checking with the problem was the pillar in the wrong place.
• 10:06 am: Changed the reflector to point (0.3282m) and now in the correct position for the pillars. Started take snap and collecting data. I moved up and down the reflector for got data to compare later.
• 10:37 am: Used the closest point possible for the reflector in front of the FLIR camera with the correct spot for the pillars.(0.2032m)
• 11:00 am: Started taking snap after kept the current on for a few hours. Parameters: Current: 0.10A , Volt: 1.3V and Temperature: 41.9 C.
• I attached below the snap in the most close point possible, now i can see a better photo and I think a fixed the problem about the focal point in the reflector for have more uniformity between the triangles, isn't perfect yet but now is just some adjustments. Furthermore after that I should be change the reflector position and also the optical focus distance in the FLIR camera and try use the black wall.

Today I change the distance between the FLIR camera and reflector (3D-Mask with mirrors and light). Now the distance is 0.3282 m.

• Note: In this distance is possible move up and down the reflector and take data to compare.
• The focal point inside the reflector keeping like little problem, every time I tried adjust this I got some triangles is not with "perfect emission" (looks like different than the others). Also if I move up or down the focal point inside the reflector have some issues as well.Therefore I am working on that.

Jon, Cao

In effort to try to reduce the noise level inside the cleanroom, we have dialed all four HEPA fan-filter units (FFUs) down from HIGH to MEDIUM speed. These dials can only be accessed from inside the cleanroom, by bringing in the large ladder and opening adjacent ceiling tiles.

We tested three configurations, in each case with all the FFUs on either HIGH (initial state), MEDIUM, or LOW. We measured the ambient noise in each configuration.

Going from HIGH to MEDIUM yields the largest improvement, reducing the ambient sound intensity by 6 dB (i.e., by a factor of 4, corresponding to a ~35% reduction in perceived volume).

An additional 3 dB of noise reduction can be achieved by further reducing the fan speeds to LOW. However, even after allowing some extended settling time (few hours), we found the particle counts to be fluctuating right at the threshold zone for ISO Class 5. Thus we dialed the fan speeds back up to MEDIUM with the expectation that this will be sufficient for Class 5 performance.

The cleanroom now needs to be recertified with a fresh round of five-zone particle count measurements.

[Jon, Tyler, Shane, Luis]

On Wednesday we completed the migration of the electronics workshop from 1119 to the large new workbenches in 1129. The two workstations pictured closest to the front of the room are for electronics assembly and testing, while the two in the rear will house LIGO CDS workstations. We moved all of the tools, cabling, and soldering and test equipment from 1119 to this new location. We also moved the large tool chest to 1129, as pictured, and moved the smaller tool chest to 1119 in its place.

The electronics workbench is ready for use. 

A quick update on the effective emissivity analysis for the CIT FROSTI testing:

I was able to (roughly) match the OPD data to a referenced COMSOL model, with an applied power of 12.6 W (as seen below). However, when changing the emissivity of the ETM in COMSOL, the dT profiles do not seem to change much. I am not sure as to why this is the case at the moment, and will continue to look further.

Additionally attached are the current RIN measurements of the FROSTI prototype. Shown is the PSDs of both channels, in reference to their individual backgrounds.

This is to optimize the FROSTI heating profile for ETM, by minimizing the residual RMSE of the HR surface deformation after the beam size weighted curvature is removed by the current RH. The parameters of the profile being explored are the location, width, and total power for the Gaussian Annulus. As shown in the attached series of plots, the optimal location is 9.9 cm, with a width of 7.7 cm, and a total FROSTI power of 12.7 W (for 1 W of Gaussian beam absorption). The residual RMSE is 1.2 nm. About 0.5% of the FROSTI power is lost at the edges of the TM.

For comparison, without FROSTI, the residual RMSE after the beam size weighted curvature removed by the current RH is 44.5 nm. When the width of the Annulus is set to be 3 cm however, the residual RMS is 3.1 nm, with much smaller FROSTI power needed at 4.7 W, and less power loss at 0.02%.

• Today I was able to plot a graph for the isolation point on the center of the heater. I got data from six different positions on the screen (I shifted the all coordinates). I extracted the data for the center point and plot the Gaussian with this extracted data for temperature. I attached the all plots below
• Also I took a snap using the black wall and with the heater at 120.1 C (0.30 A) try to have less noise but we can see this is not very good. At this temperature, we have noise on the top and I don't understand why because the heater is not in this location. I attached a snap below.

• Today I got more data to plot the Gaussian. So I took more snaps in each position for the six different spots than we be using to have a better calibration of the FLIR collected data. I attached the new plot below. Also, I did the same plot for each region as on the Elog 167 but I have more than 20 pics because I was using a big number of data so I just attached one example below.

To access the Elog, click here.

• Also I think we have some real (non-ideal) heat diffusion by the screen and not noise like Dr. Richardson suggested. I was testing today and we can see the first pic before the start heater source turns on, the second pic is at 120.2 C (0.31A) with the heater on and the last pic is after the heater source cooled back down to room temperature. Just in the second pic, we have a strong spot on the top, so it looks like a non-ideal diffusion.

[Pamella]

Updates: Problems with the emission intensity and python code.
• Yesterday I was working on get data from FLIR reflector but unfortunately we got some problems:

1. I realized than if I move the reflector a to left or right the screen doesn't get data very well(I attached a photo below). This is a problem because our idea is have the same type of emission every part on screen. Tyler and I worked to tried fix that but don't had success.
2. Dr. Richardson gave me the idea to move the FLIR camera to left or right (The same happens if I move up and down) and keep the refletor on the same position every time but unfortunately we got the same problem, the screen doesn't get data very well(I attached a photo below). Now I am working to tried fix that.

• Also I was able to work on the code to isolate the triangle shape for analyzes, I attached the image for that below.

Update: I was able to put the FROSTI power controller on the lab network. It is connected to the switch in the top of the rack and is assigned a static IP address of 192.168.1.12 and an NDS hostname of relay1.

The controller can be remotely accessed through an SSH command line interface as well as an HTML webpage, which can be opened from any web browser on the lab network by navigating to the above IP address (the login credentials are the same as for the workstation computers).

There is also an unofficial Python package for interfacing with the controller: dlipower. We will investigate using this package to interface the controller with soft EPICS channels hosted on the CyMAC. This will allow us to create a custom MEDM screen for controlling the FROSTI heater elements.

Edit: The login credentials were set up to be the same as for the CDS workstations.

The timing chassis used for the cymac has been shut off due to an unknown issue causing its supplied current to fluctuate. All real-time models will be suspended until a solution is found.