from injection breadboard to blackbox 27 cm

from injection to readout breadboard 34 cm

last steering mirror to injection breadboard 5.5cm

size of camera 5.5 cm

beam after last steering mirror at 0

Also, In "Move read write with Cam" Vi there is a place where the lockin data was used to make the matrix for the map which is visible in the main VI. Since the previous configuration only allowed one input here, I only added ellipticity from the camera. Not sure how to introduce azimuth here on one single map.

In the averaging filter VI made copy of the previous filter 6 times to be able to filter Azimuth, Ellipticity, Power, S1, S2, S3. All of their output were added in cluster for ease of transfeering data from one Vi to another. In the Buffer filter file also I made the buffer for all variables.

The output of averaging filter was connected to the graphical displays on the main VI. The VI is perhaps ready for initial tests and for checking if everything was replaced in a proper manner. 

Tried to resolve labview crash/disappearing issue by

1. Tools>> Advanced>>Clear Compiled Object Cache

2. Windows Update

3. Added exclusion in windows defender for .vi programs

After an hour(ish) there was 460 points. 

So, I have increased the wait time to 30s and had started measurment for long term yesterday

filename: C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\Stability Check\Wed, May 29, 2024 11-25-51 PM.txt

Also, for some time I have noticed an isssue with Labview on Bigfoot PC. It closes automatically on its own. I don't know if something is crashing but this is happening even when there is no windows update. But, has been happening more since last windows update. Unsure if its due to some bug. 

We are now just saving some data at 10 seconds interval for about an hour, to see 

1. size of file generated (to understand what should be the wait time inlabview to have reasonable file size with same measurement continued for 1 day)

2. see how much deviation can the setup have if nothing is changing.

The camera is in transmission after BS.

foldername=C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\Stability Check

The wait time is 10s and averaging is off

filename = Wed, May 29, 2024 9-47-22 PM.txt

In "MovereadWritewithCam" file, I replaced the items where lockin amp signal were sent to write into measurement file with the ones from camera

Further Modification that were done

1. Duplicated average filter that was used and made modification to accomodate Azi, Ell, Power, S1, S2, S3 from camera. 

2. Duplicated "Move, wait, read, write" VI to make new and introduced pol cam control subvi inside it. Can save signal from camera now here, instead of lockin amp

3. Create a new global variable file for variable from camera

With Matsuo-san

Overview: Today, we tested if the cryocooler in our Lab can be operated in parallel with Matsuo-san cryocooler.

Conclusion: We cannot operate them together.

Deatils: One of the cryocolers in Matsuo-san's lab was already operating. At first, we closed the valve connected to the input of the GWSP cryocooler and observed the water pressure in Matsuo-sans lab.

The pressure with the valve open was: 0.25 MPa

After closing the valve, the pressure was: 0.28 MPa

Based on this we concluded that water was flowing into the GWSP cryocooler. After confirming this, we opened the valve again and turned on the cryocooler. At this point, I realized I had made some errors in the temperature sensor cabling as the readings were all over. Since the goal was to confirm the parallel operation, I continued with cooling. The cryocooler was turned on at 11:28 and was atleast working until 11:50 when I left the lab. When I returned around 12:50, the cryocooler was off and showed "Motor Temp: Err", so I concluded that the water pressure was insufficient for parallel operation and the compressor overheated. However, the compressor was not too hot to touch but may have just turned off a while ago. One thing to note is that the manual suggests using the arrow key and confirming that the LED display also shows "Water Flow Err" to confirm the issue is low water pressure, but I forgot to do this. In any case, the conclusion is that two cryocoolers can't be operated in parallel.

Side Note: As previously reported, there are two sensors somewhere inside the cryostat, but I could not see them (I asked about it to Satoshi Tanioka at GWADW but he doesn't remember). However, since the temperature of this sensor did not drop drastically, I concluded they are not connected to the cold-head. I will look for them again when I open the cryostat.

Next Step: I am now discussing with Matsuo-san to have standalone test for our cryocooler to confrim if the water pressure is enough. Also, we should try to install a pressure guage near the water supply for our cryocooler.

The error was due to mismatch between 64bit windows and 32 bit labview version. The problem has been resolved and the version of thorlabs labview module was synced to identify libraries for 32 bit 

1. ON PCI PC: We needed Thorlabs camera in PCI. There was conflict between the version of labview that was used to make VIs for Bigfoot pc and the PCI pc. Sadly, we can't open labview made in new version in a labview of olderversion. Which meant had to make it again for pci pc. 

2. In any case, the three subvi are prepared for start, control and closing the camera. Just need to resolve the issue of identifying camera by labview. Currently labview can't detect the software and libraries of camera. We had similar issue in past which happened due to poor installation methods (like plugging in camera before installation, or not restarting the pc)

1. On Bigfoot PC: Increase buffer size for enhanced averaging. Can do upto 200 averages.

2. Also, decrease time  in iterating while loop to do long term stability checks.

Logan, Michael

Logan learned about how to adjust the transmission and blocking polarizer setup of the Faraday isolator. It seems everything was mostly in place regarding polarization - the required input is p-pol for IO-5-1064-HP. With current QWP/HWP setup about 300 to 1 p-pol vs s-pol could be reached, checked via PBS and power meter.

We thought there were some issues with the FI not transmitting close to 100% but this turned out to be putting the power meter too far upstream, and then also small alignment tweaks. I could get about 95%+ transmission just aligning by hand. I tried to tweak with the micro adjusters but it turns out the platform is stuck and adjusting yaw makes it bump upwards (hard to describe without a picture). We should buy a better mount.

The initial point of this exercise was to check the contribution of the FI to some weird possible HOM seen on the beam profiler, hence why I put the micro-adjuster underneath to adjust pitch and yaw of the FI. I think at this stage we should just get on with it - check the output of the FI with the beam profiler and see if we can get rid of the weird mode. Super optimal transmission is not so important.

[Hugo, Marc, Shalika]

Since sometimes now (maybe from last electric shutdown) one of the wifi relay in the central building broke (in storage) room.

In addition the ethernet switch seems broken as well. NOC is aware of this issue.

In the mean time, we placed a small switch on top of LC table and connected all TAMA pcs to it. We get internet from the new DGS switch.

Internet is back on all pc but at least PCI pc has now issue finding the Matlab license...

[Hugo, Marc, Shalika]

laser diode 1A : 1.6mW

z = 20 mm gives distance between blades and last mirror on injection = 171mm

 horizontal cut

Y: 103 mm cut (power halved) (power on dc 1.1) after hav power on dc was 0.55

X:374mm

z = 20 : Tue, May 28, 2024 2-14-49 PM.txt

z = 40 : Tue, May 28, 2024 2-21-29 PM.txt

z = 60: Tue, May 28, 2024 2-25-28 PM.txt

z = 80: Tue, May 28, 2024 2-29-48 PM.txt

verticale:

X: 313

Y : 191

z = 20 : Tue, May 28, 2024 11-32-57 AM.txt

z = 40 : Tue, May 28, 2024 2-01-31 PM.txt

z = 60: Tue, May 28, 2024 2-06-27 PM.txt

z = 80:Tue, May 28, 2024 2-10-41 PM.txt

after realignment horizontal

z = 20 : Tue, May 28, 2024 4-14-32 PM.txt

z = 40 : Tue, May 28, 2024 4-30-15 PM.txt

z = 60 : Tue, May 28, 2024 4-34-03 PM.txt

z = 80 : Tue, May 28, 2024 4-37-59 PM.txt

In the end we recovered normal incidence in both vertical and horizontal directions (within 0.026deg).

We wanted to prepare for linear polariscope measurement but the lockin amplifier showed strange error (undr) related to the chopper signal...

We'll start with polarization camera measurements in the coming days

[Logan, Marc]

We added one of the 2 remaining RF amplifier to the 500MHz clock output.

We soldered it to the NIM rack +12V and ground used for the LNVR. Note that we could have tried to use the +12V from the LNVR but were a bit worried to further damaged the clock..

The output of the clock is now +7.9dBm.

The output of the following splitter are

1 : -1.73dBm ; 2 : -6.19 dBm ; 3 : -5.09 dBm ; 4 : -5.33 dBm

Finally, we connected DDS2 to each output of the splitter and checked the signal output from DAC0.

We got about -9 dBm from all.

Next steps are fixing the clock crystal (was not fixed anymore) and the RF amplifier ; recover the electronic connections and recover squeezing.

The birefringence properties remained same. Comes from the fact that we do J/Co

after adding this, the jones matrix and info on birefringence was weird....I lost the crcuial info on the polarization properties rather than it working as a proper filter. So, not using this anymore.

Had actually picked it from a paper talking about improving noise in jones matrix. 

after this the jones matrix of mirror is not [1,0][0,-1] anymore. the 1's have changed to 0.8 ish. 

Added power factor of sqrt(Output power/ Input Power) in jones vector. This is to take account the power getting halved after BS