I set up the new Windows 10 laptop (pictured below), which arrived yesterday. This laptop is intended to be used for running lightweight Windows-only programs, such as the Thorlabs beam profiler software or the SRS RGA client. However, none of that software is installed yet.

Configuration details

As usual, the computer is configured with one shared account (username: controls) and the standard password. Note that it is connected to the campus wifi (UCR-SECURE).

If a connection to the lab's local network is required, then the laptop must be connected by an Ethernet cable to the switch in the top of the server rack.

1. Macor spacer (drawing: LIGO_Redesign_Macor_Spacer_Drawing_v4.pdf attached below), quantities: 40
   • No defects, damages observed
   • Parts are free from grease/ machining fluid
   • Wall thickness of 1 mm appear to provide sufficient stiffness to part
   • Images of parts: Macor_spacer_0.jpg, Macor_spacer_1.jpg
2. Macor 5-40 UNC screw (drawing: LIGO_Redesign_Macor_Screw_Drawing_v6.pdf attached below), quantities: 20
   • One screw broke, location of break: should edge between head and shaft (see image Macor_screw_5.jpg )
   • All other screws look ok, no damage observed, clean surface overall
   • Images: Macor_screw_0.jpg , Macor_screw_4.jpg

We have tested the heater to find emissivity, mounted the heater system to the optical table, and have taken irradiance maps of the heater projected onto the screen.

The heater's emissivity was determined by using a thermocouple in conjunction with the FLIR's temperature calibration. To attach the thermocouple to the heater initially, I used Kapton tape and ran both the wires of the heater and the thermocouple through the heater bridge. This allowed for the heater to rest on an optical post and be observed without anyone directly holding it, but there were some measurement issues. The thermocouple had a very wide range of temperatures it was reading, which may have been due to intermittent contact or a short between the two legs of the thermocouple. To solve this and make the temperature measurements more stable, we pried apart the two ends of the thermocouple (to ensure there was no short) and put tape on either side, leaving the end connection bare. This was then taped to the heater, and the thermocouple was much more stable. We also used a K-type thermocouple that has an adhesive tape on it already, which assisted with the intermittent contact as well. With the thermocouple measuring the temperature of the heater, we could point the FLIR directly at the heater and calibrate the emissivity until the FLIR and the thermocouple agreed. Cassidy's emissivity calculator was also used, as I could input a temperature and observe what the emissivity of an area was based on that temperature. We found the emissivity of the heater to be 0.57.

As a note, when observing the heater with the FLIR, it appeared that there was a hot spot in the center, where the Kapton tape sat. Because the Kapton has a different emissivity than the 304 stainless steel of the heater, the FLIR will read it as having a different temperature than it actually does. When using the FLIR in the future, be sure to ascertain whether there is a temperature difference somewhere or if there may be different emissivities.

Additionally, the first heater that I used was taken to a very high temperature and oxidized. The emissivity of this oxidized heater is not known, but could be good information for knowing how oxidation affects these heaters specifically.

To mount the heater system in front of the screen, I used 1/2'' optical posts and the mount I designed using COMSOL's CAD program. The heater was originally 2.5 inches away from the screen, and has since been moved back by an additional two inches so that we could observe the heater side of the screen with the FLIR. We wanted to see what temperature the heater side of the screen was when irradiated by the heater, and how that compared to the camera side of the screen. When the heater ran at 1.12 W of input power, the heater side of the screen had a max temperature of around 29.7 C, and the camera side of the screen read at about 29.5 C. This means that there is very little thermal loss between the two sides of the screen, and any insulation that the screen's adhesive may have is largely negligible. Additionally, the camera was placed at an angle and undetermined distance for these tests, confirming that the temperature measurements compensate well/don’t depend on changes in angle or distance between the camera and the screen. However, there was spots on the back of the screen that the camera was measuring as hot spots where there shouldn’t have been any. I have included an example below. It would be useful to run a test where the camera is directly on the back of the screen without the heater to characterize the screen and see if the hot spots are physically present on the screen or if this is an artifice of the camera because of something like angle of viewing.

Taking irradiance maps of the screen was straightforward. After checking that the emissivity of the screen is 0.99 by viewing it at room temperature, we monitored the max temperature while slowing increasing the wattage the heater was running at. There is not a large change until the heater is at around 95 C, at which point the screen began to rise in temperature from 27 C to 28 C. We took measurements of this while the heater was 2.5 and 4.5 inches away from the screen. The irradiance map has a very symmetrical and circular shape, but does not have the ring pattern that we expected. There may be a few reasons for this: there could be some conduction between the two sides of the screen that is causing the pattern to spread further, the heater setup may not be as ideal as it was modeled to be, or there could be a different, unknown issue.

TO DO:

- It would be useful to run a test of the camera in multiple different positions to ensure our conclusion that the camera’s measurements don’t depend on angle or distance (or that these factors are well accounted for in the current temperature calculations) is correct.

- Measure the back of the screen straight on to identify bright spots and possible reasons as to their appearance.

- Recalibrate camera to ensure it is still correct after testing in multiple positions.

- Take another irradiance map of the screen at a higher input power, as well as moving the heater close/further away to try and replicate the COMSOL irradiance maps. It would be useful to also redo the COMSOL modeling at lower powers and variable distances.

Pictures included of full table setup, the heater mount, the heater with Kapton tape attaching the thermocouple as well as FLIR's measured irradiance map.

There were no issues with the physical replacement of the post, except that the fork clamp on the post needs to be on one of the perpendicular, not diagonal, axes in order to be secure. I chose the front axis (towards the screen) as before in order to easily access the alignment knobs.

To align, I followed the same process as last time except for a more purposeful original rough alignment. For alignment purposes, the visual camera was used. For the first rough alignment, I pulled the camera as far back as possible on the x axis (with the z axis roughly centered), then moved the entire stage setup back until I could just see both the top and bottom edge of the screen. Then, I set the z-axis to an extreme in order to use the edge of the screen to align the rotational and y-axis pieces for the fine alignment.

For the fine alignment, starting with the z and x axis at extremes, I began by aligning the rotational axis. To do this, I used the gaps between the top of the screen and the camera window on the far left and right of the image. When these gaps were equal I knew the rotation was adequately set. Then, I set the y-axis so that the pattern was centered. If the gaps were no longer even, I redid the rotation alignment and ditto with the y axis until both were set. This resulted in a rotation of about two degrees and a y axis at just under 3.5.

To set the z and x axis, I centered the z-axis using the top and bottom of the screen, which should both be visible if the rough alignment was done correctly. Then, I adjusted the x axis by pushing it forward until the top and bottom of the screen were just out of the frame. As with the rotational and y-axis, I iteratively fine tuned the x and z axis until both the image was centered in the z axis and only the screen was in view. This resulted in a z-axis value of just over 5.5 and an x axis value of nearly 1.75.

Pictures are included of all alignment knobs and the new post/stage setup!

Screen Setup

The screen was set up by clamping it between two rectangular posts on each side. First, two posts were set up with 22 in. between them (thus allowing the screen to span a total distance of up to 24 in. when clamped down). To best stabilize the screen and to allow for it to be "pulled" taut by exploiting the give in the L-bracket, the L-bracket was bolted on the outside of the post, along the same axis as the screen itself.

On first attempt, the screen was too thin to be fully clamped between the posts. In order to have it fit snugly, sections of heat shrink tubing was used as a shim at the points where the posts were clamped together. The tubing was slid into the track of one optical post at the desired points. In order to accommodate the shim, the two posts had to be held together, ideally clamped, with the screen and shim in place. Then, the post clamps could be slid into the tracks of the post, moved to the optimal location, and tightened down. This required at least three people: two to tighten one side while the third holds up the screen on the other side. The screen was placed ~1/8" from the edge of the posts and flush with the top.

Camera Stage Setup

Once the screen was in place, the camera stage was set up by placing the XY-Translational with Rotation stage on four 3" optical posts. Then, the z-axis stage was placed in the center of that, with another 3" optical post on top, which was then topped with the camera. This was set and clamped down ~22.5" from the screen. This was about 1" closer than expected based on our theoretical models.

Fine Alignment

We used the visible camera to fine align the screen and to test the setup. Notably, the visible camera is placed below the infrared and thus requires a calibration in order to ensure the two are aligned on the computer image. This can be set by hand using the FLIR proprietary software (FLIR CamWeb) and adjusting the "MSX alignment". The image mode "Thermal MSX" allows both the visible and IR camera to be displayed at once and the difference in their positioning can be seen. We found an offset of ~0.5m to be nearly accurate (note: using this method, although you can get more accurate than this, the displayed value only has one significant figure).

In order to align the camera, we first used the exposed top edge to judge whether the camera was appropriately centered on the screen. We set the rotation as close as possible to being in line by eye, then adjusted the y-axis until the gap on both corners was a similar size, thus indicating that the rotation and y-position were correctly set. Rotationally, the camera required only a refinement of -1/2 degree. The y-axis is set at 1.25. Then, the camera was pulled as far from the screen as possible using the x-axis to allow the screen to be easily centered using the z-axis. Once the outlined test mass was centered, the x-axis was used to bring the camera close until the screen just barely filled the field of view. The x-axis is at 2.25. The z axis is set to it full dynamic range at 10. Unfortunately, the camera is still slightly too tall for the screen, likely requiring the purchase of a new optical post about 0.5in shorter the current one. This interchange will likely require a new fine alignment after.

Basic Imaging Tests

The camera was also focused on the screen based on the manufacturer's printed distance on the camera itself (using 22.5", or 0.572 m). Using the FLIR proprietary software, the camera appears to be in focus in IR (a hand was used as a good focusing tool for this). Additionally, the camera does pick up heat on the other side of the screen. A hand can be lightly seen warming the screen, as can a soldering iron tip. This was a very imprecise visual tool, but does indicate that the camera and screen are working roughly as expected.

Next Steps

A new optical post that is ~2.5" tall should be ordered to replace the one under the camera currently. The heating system also needs to be ordered and set up. Currently we are debating between a parabolic reflector with a hole in the back, and one without, as each would require a different mounting mechanism for the cartridge heater.

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.

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.

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.

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

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