Sun Apr 7 13:42:51 2024, Michael, Update, Interferometer Simulations, Update on status of gtrace project 
|
[Pooyan, Michael]
After meeting and discussing the current state of our work with Prof. Fulda a few weeks ago, we have decided that the best next step for the gtrace project is its integration into finesse work. Our first step towards this integration involved creating a sequential beam trace in contrast to the previous non sequential gtrace simulations. A sequential beam trace not only allows for faster runtimes of the simulation (<1 second) but also allows for more direct reading of certain beam parameters (beam size, gouy phase, and angle of incidence). The sequential model was created alongside a yaml output which provides values of parameters, now including the angle of incidence on a mirror.
Last Monday, Pooyan gave a report to the Cosmic Explorer optical design team on the current state of our project and the ultimate goal of our work. During the same meeting another group working in the optical design team presented their own work with gtrace and optical design, focusing more on optimization of parameters based on desired beam sizes at each mirror. It might be a good idea to begin attempting to bring our individual projects together to allow for collaboration and further developments.
Currently, only the crab1 layout has a sequential trace model. Pooyan is currently working on creating a finesse model for crab1 to serve as a proof of concept for how gtrace could be integrated with finesse by providing useful values such as angles of incidence. |
Mon Jul 29 12:23:10 2024, Liu, Update, Interferometer Simulations, Update on mechanical resonances of CE BS with stiffener ring
|
Update on mechanical resonances of CE BS with stiffener ring is attached. |
Sun Aug 4 09:01:01 2024, Michael, Update, Interferometer Simulations, Update on SRC Mode Mismatch Analysis 
|
An update on my analysis to minimize mode mismatch/scattering by introducing toroidal mirrors to the SRC. |
Thu Jul 27 11:28:36 2023, Sophia , Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots   
|
This week I have successfully been able to implement our dynamic CSD and PSD plotting code, but along the way I encountered a few challenges which I will outline in this elog post.
Challenges:
1. Once I was able to plot the data through time, I produced a graph of the raw data (shown below in the top to images) which showed pulsed data instead of a continuous stream. On Tuesday (26th of July) Tyler and I fixed this issue, realizing that calling the starting the trigger in the red pitaya was the issue. When I commented that line of code out, it immediately started plotting continuously.
2. When that issue was solved, We then started having problems with the automatically generated lines in the python program which would double back on each new iteration. I am still dealing with this issue, because the line likes to follow the progression of the data intake instead of through the plot. Currently, I am trying to plot the data as a scatter plot and then add the line as this might make it care only about the data's distribution instead of the order of the points in the list, but I am still unsure. I might try out np.sort (or some equivalent to sort the entire data set before plotting) as well. |
Thu Jul 27 14:11:42 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots
|
Here's a screen recording of the dynamic raw data and PSD/CSD plots as they are now. Will begin working on implementing a code to generate the statistical estimator for the CSD uncertainty now. (Will talk to Tyler more about whether I can get the lines to happen or not) |
Mon Jul 31 19:27:30 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots    
|
An update on the CSD/PSD code:
The code is now taking a dynamic average of the points, and that has significantly reduced the noise that we were reading and the issues I was having with the lines in the plots. The graph for the CSD is still putting up a fight though, and amassing many lines that do not appear when just scatter plotted. I plan to fix that tomorrow, alongside inserting my own generated signal into the data. I have plotted the coherence alongside these graphs (as shown in the first screen recording and in one of the images), and it is significantly less than 1-- starting at or below 10^(-1).
As a note, I am unsure of why the raw data looks like this-- the laser goes through periods of extreme noise and I think this data was taken during one of them. |
Tue Aug 1 15:44:31 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots 6x
|
We have identified two problems facing the intensity noise calculations, which we are working to solve.
The first of these problems, is that the red pitaya appears to be taking data approximately 4 times faster than we would expect from the decimation rate based on how quickly it runs. To see if this was affecting our data, we plugged the red pitaya into a function generator. We found that my code is able to identify the driving frequency, but consistently gives predictions that are roughly 7% greater than we expect. When we drive at 100 Hz, the plot says the peak is at 107 Hz, when driven at 400 Hz, we see between 422-427 Hz, etc. While this implies that the red pitaya is not taking data at a faster rate than we would expect (if it did we would anticipate a lower than expected frequency, by a factor of roughly 4), it does imply some intrinsic issue with either the red pitaya or with the code. To fix this, I am going to use my code on artificially generated signals and see if we still observe these issues. |
Mon Aug 7 15:36:18 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots 7x
|
Today I was able to fix the red pitaya's plotting problem, and get my code to recognize driving frequencies from the function generator to within a 0.5 Hz estimation. The sinusoidal plots I have included are from sending a 1 Hz signal into the red pitaya to see the signal in real time. This allowed me to see exactly where the system was messing up, and fix from the ground up. Once I had that working, I began to test sending in frequencies in the range that my PSD/CSD code could observe and I was able to identify each driving frequency within 0.5 Hz. My code was able to correctly identify a 500 Hz signal, while other analyzed frequencies in the observable range have fallen lower than the sent in frequency by a less than 0.5 Hz. I believe this issue comes from the strange speed that the red pitaya is still acquiring data, even with my fixing it to now observe a continuous signal. |
Tue Aug 15 10:35:00 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots    
|
I have successfully added a button to my graphics, but it has posed a strange issue with the CSD and PSD values. When I plot my original code, I still see the pretty peaks that I was getting originally, while my new code (as shown in the video and in the last screenshot) is giving me more of a line. In my code that gives the peak values, the CSD values also tend to fluctuate in this new code as well (shown in the first screenshot), before returning to the real value.
I think that there is a problem with the averaging and am hoping to solve this issue today with Tyler. This is good progress though! |
Tue Aug 15 13:32:37 2023, Sophia, Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots  
|
I have now fixed all issues that I was having this morning, and have added text boxes which show the peak values of both PSD's and the CSD alongside the graphs. They also update continuously with the graph. This is shown in the top image. The laser was driven at 400Hz, and had 0.5V peak to peak voltage, both of which appear correctly in the below graphs.
Now that the code is almost fully working (we will finish debugging the screenshot method later today), our plan tomorrow is to drive the laser and see how the code performs with it. The below graph is from us driving the function generator at 100Hz to test the range.
Update:
Bottom graph is new version of graphs with better distribution of both graphs. |
Tue Jul 18 14:13:46 2023, Sophia , Update, Scripts/Programs, Update on Laser Noise Data Collection and Analysis 6x
|
We [Sophia and Tyler] have found a code which will partition our data and generate PSD's and CSD's automatically. We are now in the stage of writing this into a dynamic code, which so far has been fast-paced because of the framework we have built for it over the past few weeks.
Something to note is that we have found, especially over long periods of time, the laser goes through periods of extreme noise and the signals often cross from where we set them at some point throughout our data collection. We have made the assumption that this is something to do with the laser itself, and not our setup or surrounding space because of both the times that these noise/intensity spikes took place and the duration of the spikes (1.5-2.5 hours). To try and correct for this, we have been "cutting" the noise, and just looking at sections which don't include these big fluctuations. An example of the "noise cut data" is shown in the graph titled "Signals Over Time 7-18-23 Noise Cut Data" and all of the PSD/CSD graphs have been made using only these "noise cut" regions. |
Mon Jul 29 12:18:52 2024, Liu, Update, Interferometer Simulations, Update on FROSTI O5 ETM profile optimization
|
Update on FROSTI O5 ETM profile optimization is attached. |
Tue Aug 8 16:47:11 2023, Sophia, Update, Scripts/Programs, Update on Dynamic CSD and PSD Plots  
|
We have fixed our rapid plotting error, and realized that this has not been affecting our data intake! Below is a video of the code progressing, alongside grabbed images of the raw data. The data is now continuous, and performs as we expect. Next, I plan to add a widget which will dynamically show the peak values instead of them just being printed in the terminal after each iteration. (Ignore the red box-- it was from me struggling with a now fixed issue). |
Mon Sep 9 12:36:45 2024, Michael, Update, Interferometer Simulations, Update on Analysis of Mode Mismatch Minimization in A#
|
I have taken a closer look at the solution curve in the mirror parameter space which I have searched, focusing on the "resilience" of specific points, with the plan to analyze how certain conditions of the interferometer change as we move along this solution curve. |
Tue Mar 4 03:33:18 2025, Xuesi Ma, Update, , Update 6x
|
Spikes Appear Again, need to address it systematically.
Power on and off before reaching steady state ✔
At 12V, the rise and fall time of heater elements are different from 24V.
Initial guess is due to temperature in the chamber. However, it does not seem to be the case, 24V with 30c have the same hall time as 24V at lower temperature.
Attached are some graphs for rise and fall time
After a weekend of powering on, the main chamber pressure stabilized in the UHV region.
Temperature in the chamber seems also not to change. |
Thu Apr 3 13:23:37 2025, shane, Update, CDS, UPS interfacing
|
Update on UPS serial interfacing: the driver for the UPS webcard has been installed on spica (for UPS1 in room 1119) and logrus (for UPS2 in room 1129). Static IP addresses have been assigned for both and noted on the lab wiki. Neither is yet able to connect, as the initial ip address webpage connection test failed for both. In the process of troubleshooting now. |
Thu Nov 14 11:58:05 2024, Shane, Update, CDS, Turbo pump connection troubleshooting
|
Attempted connection to the TV551 turbo pump through Varian/Agilent's software on spica. Successful connection established, and we are able to read out al the readings associated with the pump (status, temperature, etc) through the software, which is actually pretty extensive and well organized. Was able to stop and restart the pump with no issues. Serial communications seem to be working fine, and the current serial settings (baud rate 9600, serial type RS232) all match what the Iolan was expecting with the previous connection test. Also notable: the code used for the previous (failed) connection test is written using 'Letter protocol', which is the older of the two communications protocols supported by these kinds of pumps. This rules out the pump being too old to accept the newer communication format as the issue, since it's the older format being used anyway. Will continue trouble shooting to determine why previous connection test failed. |
Thu Sep 14 17:05:38 2023, Shane, Jon, Update, CDS, Timing chassis setup and testing
|
Tested the setup today for the timing chassis (intended to provide the timing reference for the CyMAC). Was able to read the correct frequency, but voltage was significantly lower than needed. Still identifying source of problem, and looking into the relationship between the supportable ohm load and the voltage. |
Fri Sep 29 17:27:30 2023, Shane, Jon, Update, CDS, Timing chassis assembly progress (CyMAC) 
|
Worked on timing chassis assembly today for the CyMAC, settled on layout (see attachment 1). Frequency synthesizer and frequency divider tentatively mounted. Next steps involve putting together and installing an LED and DC on/off switch assembly like the one in the binary input chassis (attachment 2 for comparison; orange and black wires in BI chassis analogous to red and black wires in timing chassis). Will also use front and back panels of BI chassis as a template for the timing chassis panels, with the following alterations: two SMB feedthroughs in place of the ribbon cable connections shown on the back panel, the addition of an LED on the front panel to indicate power, and potentially a spot on the front panel for usb connection to programmable frequency synthesizer. |
Mon Oct 23 18:02:23 2023, Shane, Jon, Update, CDS, Timing chassis assembly complete  
|
Concluded assembly of timing chassis for CyMAC today; see attachment 1 for interior set up of chassis. Installed front and rear panels, wired on/off switch and LED assembly, and tested to confirm everything is powering on correctly. Also tested the outputted timing reference that will go to DAC and ADC adapter boards (see attachment 2 for output 1 and attachment 3 for output 2). |
Thu Oct 17 13:24:23 2024, Shane, Update, CDS, Timing Chassis issue identified 
|
[Ma, Luis, Shane]
Working theory for the timing chassis issues had been that the 1A breaker was tripping and causing the failure of the Valon 5015 and 3010 to output the timing signal correctly. We just tried bypassing the breaker, running 6 V on the benchtop power supply (set the current limit to 1.5A), with the 5010 generating the sine wave to pass to the 3010. All worked correctly, and there were no issues. Square wave outputted by the 3010 was exactly as desired (image attached) at the correct frequency, and this confirms the issue was the breaker, not the valon 5015. Ready to go ahead with ordering a new replacement breaker.
|
Fri Oct 25 10:56:30 2024, Shane, Update, CDS, Timing Chassis fixed and reinstalled
|
[Ma, Shane]
We replaced the 1A breaker in the timing chassis today with a 4A one, and tested that all is working well. The chassis successfully outputted the correct signal (image attached). The real time models have also been restarted and the CyMAC diagnostics screen is showing all green flags. Timing chassis has been closed up and reinstalled in the server rack.
|
Tue Oct 15 15:27:38 2024, Xuesi Ma, Update, ELOG, Timing Chassis Update 12x
|
I conducted separate tests on the '5015' and '3010a'. When powered individually, the '5015' outputs a signal at 33.55 MHz with an amplitude of 608 mV. It draws 1 A of current from the power source. The input signal for the '3010a' is 33.54 MHz with an amplitude of 670 mV (peak-to-peak) and a 15 mV DC offset. The output signal from channel 1 is a 65.5 kHz square wave with an amplitude of 3.28 V. The '3010a' draws 0.1 A of current.
Both the '5015' and '3010a' work fine when powered separately. However, when both are powered together, the power source behaves as if there is a short circuit. The current theory is that the switch or breaker is tripping, as it has a 1 A current rating. Since the combined current demand of both devices exceeds 1 A, this may be causing the issue.
Slides for 10/16/2024 Group Meeting |
Fri Apr 28 19:00:13 2023, Cao, Physics, VAC, Tighten CF ports on vacuum chamber
|
[Cao]
After Jon's comment yesterday that some of the connection did not seem to have good metal-metal contact, in particular the gate valve connection, I went through the ConFlat connections today and retighten them.
I found a lot of the CF connections are not particularly tightened and there were a lot of range left that can be tightened with the wrench. After re-tightening, the copper gaskets are not visible anymore. For example, see the attached images for the difference before and after tightening.
Note for future installation of CF
- After tightening the bolts/ screws in jumping order (to provide uniform torque) and there is resistance appearing in further tightening, start going through each screw/ bolts in a direction, each time applying a small torque until it resists to further tightened
- After each time going all the bolts/ screw and returning to the starting point, one will find they can further tighten the screws/ bolts. Repeat the process until no further tightening can be achieved
- The copper gasket should not be clearly visible at the connection
|
Mon Jul 17 11:46:24 2023, Pamella, Update, FLIR, Thermocouple plot. 
|
[Pamella]
- I collected data to plot a calibration with the heater. I took measurements with current and temperature (the thermocouple - thermometer) to compare with the FLIR measurements.
- I made a plot with this data and we can see how temperature vs current behaves.
Note: This data I measured manually.
|
Tue Jul 18 16:12:27 2023, Pamella, Update, FLIR, Thermocouple plot.
|
- I noticed that these measurements have some issues with the weather on different days. We can see in the photo attached below how different the temperatures are on different days, I took the data with the same procedure every day, but we can see the differences between them.
- To Do: I will do a new data collection using FLIR and thermocouple at the same time to plot comparison between both.
Quote: |
[Pamella]
- I collected data to plot a calibration with the heater. I took measurements with current and temperature (the thermocouple - thermometer) to compare with the FLIR measurements.
- I made a plot with this data and we can see how temperature vs current behaves.
Note: This data I measured manually.
|
|
Wed Aug 17 16:04:30 2022, Phoebe Zyla, Summary, Lore, Testing the Cartridge Heater and Collecting FLIR Data   
|
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. |
Tue Nov 21 22:09:44 2023, Aiden, Update, General, Testing Parts 8x
|
[Aiden, Luis]
Luis and Aiden vented the chamber today. We closed off the RGA section and then proceeded to open the the vent on the main body after turning off the turbo and backing pump. We then opened the lid and placed in all the stainless steel hardware that will be used in evaluating the FROSTI optics and heater elements. We also inspected the weldments before closing it up. Check the clean and bake data base where there is now a new section outlining the parts in each test. We then closed the lid, tightened the bolts, turned the backing pump back on and let the pressure drop until it was below 1e-1 torr. Then turned the turbo pump back on and after a few hours the pressure was back down to 4.16e-7 torr. The RGA was turned off during all of this and was turned back on when done even though we closed both valves to keep the RGA volume under vacuum. |
Mon Jun 17 11:47:46 2024, Liu, Infrastructure, General, Temporary cooling units for the labs 
|
Below are the temporary cooling units installed last week in labs 1119 and 1129. They are the temp. replacement for the building AC system, which will be shut down during the Physics roof replacement. |
Mon Jul 15 14:49:06 2024, Pooyan, Update, Computers, Synology NAS server setup
|
Installed a Synology NAS server (Synology RackStation RS1221) in lab room 1129, with host name “scribe” and ip “192.168.1.17”. It is mounted on the rack and each of its 8 storage bays has a 2TB SSD disk. It will be used to set up automated backups of all the lab machines (e.g., chimay, logrus, megatron).
One shared storage is set on it with SHR-2 as its RAID type. It can tolerate the failure of two disks and has 10.4TB of total capacity.
We can use both rsync and dd to create backups of the system. A suggested backup schedule could be daily rsync backups and bi-weekly disk snapshots using dd.
|
Wed Nov 27 12:27:45 2024, Luke , Summary, VAC, Summary of vacuum work
|
[Luke, Luis]
Update of current state of vacuum chamber
Current temp: 24°C
Current pressure: Main 1.77e-8, RGA 5.3e-9 [torr] (Gate valve open)
Summary of recent work-->
To try and reduce the leak in the turbo pump by reducing cross-connection, we replaced the copper gasket. This made no improvement to the leaks.
Initially: 1.9e-9 --->
Left side: 1.33e-9, Right side: 3.37e-9 (Gate valve open)
This is still a significant leak. We have tried to tighten the bolts further, but they are as tight as reasonably possible.
Things of note: While examining the knife edges, we found some very slight imperfections on the reducing cross's flange as seen in 474. This could be the source of our leak. We have replaced this gasket 1-2 times already and consistently have a slight leak. This imperfection is on the right side of the flange, which would be consistent with the measurements above.
Unless we want to use the liquid sealant or replace the gasket with an annealed gasket, we could try baking the system again, as this allowed us to reach UHV in the main volume before. It also allowed us to pass the RGA scan, which we are currently failing. (see attached) |
Thu Jun 27 11:09:14 2024, Liu, Update, Scripts/Programs, Straight edge STEP files and ray loss analysis   
|
Drawings and CAD models of the straight-edge designs are exported, and are visualized in SOLIDWORKS. Two are attached. One is a single edge of the evenly spaced polygon design with 16 edges, and the other is the 8x2 design, with two neighboring edges grouped together to replace the original single curved heater.
For the straight edge design in COMSOL, ray power detectors were placed at the heater's front surface. The irradiance is shown in figure. The amount of light rays deposited back to the heater is small when close to the center, where it is closer to the original ring. The ray power increases as we move further away from the center toward the edges. In addition, the total power integrated at the heater's front surfaces is about 21% of the original heater's emitted power. This could account for the power efficiency difference between the straight edge design and the ring design, as shown in plot for instance. |
Mon Sep 9 21:02:37 2024, Luke, Update, VAC, Steadystate temperature of flanges
|
I measured the temperature of the flanges and reconnected the RGA turning on its filament. I then turned off the PID controllers.
Here is a table that has the temperature of the different parts of the vacuum chamber.
Electronics |
Temperature (C) |
Pressure gauge (Main volume) |
81 |
Main turbo pump |
67 |
RGA |
53 |
Pressure gauge (RGA volume) |
60 |
Cal leak |
48 |
Mini tubo pump |
46 |
Pirani gauge (1.33") |
46 |
conical nipple (2.75") |
82 |
Lid |
112 |
Barrel lower |
125 |
Barrel upper |
122 |
RGA volume |
125 |
Bottom of chamber |
117 |
|
Mon Dec 2 00:11:23 2024, Michael, Update, Interferometer Simulations, Status Update on Toroidal Mirrors Project Work
|
As it has been significant time from my last update on this project, I compiled a few notes about what I have been working on, current issues, and my future plans. The past few weeks have been focused on me attempting to obtain a reliable symbolic expression for mismatch. This is important going forward as it allows us to determine optimal points in the parameter space and the surrounding behavior efficiently without significant computational cost. However this been quite difficult since I've encountered some fundamental discrepancies in the way values like the ABCD matrix and q-parameters are calculated/returned in Finesse. Since I have yet to resolve this, I'm focusing on next steps in developing tools for statistical simulations.
Update Slides |
Wed Nov 27 16:23:58 2024, Luke , Update, VAC, Started bake
|
[Luke, Luis]
The vacuum chamber is currently baking.
We stepped up to 125°C by increments of 30°C starting at 60°C. Everything went fine. After about 20 minutes of the PID controllers being set to 125°C, the flange closest to the RGA was 38°C, so we left it connected.
Current state as of 4:15:
The gate valve is open, and the filament of the RGA is on.
The temperatures are as follows:
PID right barrel upper: 105°C, RGA volume: 125°C
PID left barrel lower: 125°C, Lid: 82°C
The lower temperatures should climb as the whole system heats up.
I will come in Saturday afternoon to turn them off so that we can look at the pressures on Monday. |
Fri Feb 7 12:25:56 2025, Luke , Summary, VAC, Started bake
|
[Luke, Luis]
The vacuum chamber is currently baking.
We stepped up to 120°C by increments of 30°C starting at 60°C. We took about an hour break at 90°C to let the temperatures equilibrate.
Current state as of 12:20:
The gate valve is open, the calibrated Argon leak is open, and the filament of the RGA is on.
The temperatures are as follows:
PID right barrel upper: 113°C, RGA volume: 120°C
PID left barrel lower: 121°C, Lid: 114°C
The lower temperatures should climb as the whole system heats up.
|
Tue Jun 20 22:14:24 2023, Pamella, Cao, Infrastructure, VAC, Short term testing of vacuum heater controller units
|
[Pamella, Cao]
Fuse replacement
- Replace blown 10A fuse in ucontroller outside cleanroom
- Replace 10 A fuse in main power connection slot of the controller unit inside cleanroom
- Pamella wiped down unit outside cleanroom.
- Controller units turned on and temperature setpoint set to be 80 deg C
- Temperature settle in approx. 15 minutes(as recorded by the RTD). No problems with fuses observed
- Recording of pressure gauges (in Torr) :
- Before turning heater on :
- Gauge 1(main chamber): 3.73E-7
- Gauge 2(RGA line): 3.65E-7
- Gauge 3(Pump line): 3.8E-4
- After 15 minutes :
- Gauge 1(main chamber): 7.07E-7
- Gauge 2(RGA line): 6.12E-7
- Gauge 3(Pump line): 3.8E-4
- Reduce setpoint temperature to 60 deg C due to Pinrani gauge (Gauge 3) temperature limit
- Upon returned to lab to reduce temperature (35 minutes after turned on):
- Gauge 1(main chamber): 1.22E-6
- Gauge 2(RGA line): 9.98E-7
- Gauge 3(Pump line): 3.8E-4
- Once temperature has settled to 60 C (approx 20 mins after changing setpoint), pressure readout showed:
- Gauge 1(main chamber): 1.37E-6
- Gauge 2(RGA line): 1.10E-6
- Gauge 3(Pump line): 3.8E-4
- Heater left on for the whole afternoon, pressure readout upon returning to lab at 5:30 pm:
- Gauge 1(main chamber): 3.43E-6
- Gauge 2(RGA line): 2.61E-6
- Gauge 3(Pump line): 3.8E-4
|
Tue Feb 13 04:05:32 2024, Michael, Update, Interferometer Simulations, Shoelaces 1 Layout Simulated in GTrace 
|
I've worked on and have completed a first simulation of Cosmic Explorer's Shoelaces 1 layout. This is based off of Pooyan's original work with Gtrace much like the Long Crab 1 layout I worked on last week. This layout will allow me to quickly created the alternate shoelaces layouts. I've included an image of the dxf, and a desmos model for reference. |
Tue Jul 18 16:04:26 2023, Pamella, Update, FLIR, Setup FLIR with black wall (black body)  
|
[Pamella]
- Today I tried get data the heater with the black screen but doesn't looks possible have just one "energy" point straight to FLIR camera. Tyler and I tried different current and temperatures but keep very bad data. I attached a snap below.
- I attached a photo about the new setup below. The FLIR is in the most close point possible/safety with the heater. The heater is very close to the black wall but is not touch the screen so is safety.
|
Tue Jan 28 13:30:46 2025, shane, Update, CDS, Serial comms testing update
|
Attempted to communicate with the smaller vac pump (TwissTor 74) via Agilent software today. Was able to communicate with the pump via python serial connection code as usual, with no issues. When using the manufacturer software though, it was unable to 'locate' the pump and failed to connect to it. So manufacturer software works for the big (older) pump, but not the smaller, newer one. Unclear if this is somehow related to the fact that using the manufacturer software for the bigger pump involved manually connecting its controller to spica with a db9, and there was no obvious way to do that for the smaller pump's controller. |
Fri Aug 2 13:50:22 2024, Shane, Update, CDS, Serial Comm. Test (Agilent Turbo Pump)
|
Did a brief communication test with the agilent turbo pump today, to see if we could get serial communications up and running for it. Used a simplified python script with sockets package to establish a connection and send a simple command to query the pump's operational status. The connection was successful, and had no issues establishing. The command also sent successfully, and received a response. The response didn't make sense, though, as all the possible statuses correspond to integers 0-7, and this test returned the integer 15. Need to troubleshoot some more to figure out why it's returning nonsense values. Possible match-up issue with the way the information is being encoded on each end? At the very least, connection and command sending are both working fine, and this showed that the pin-out connections we were assuming (image attached) are correct for basic connection to work. |
Mon Apr 8 14:43:29 2024, Pooyan, Update, Interferometer Simulations, SIS update single and coupled cavities 
|
[Pooyan, Cynthia]
Attached is a brief recap PDF file. A video file showing separate HOMs plots for the cavity scan with ETM08 surface map is also attached.
The codes are available at https://git.ligo.org/uc_riverside/hom-rh/-/tree/main/SIS |
Mon Jun 24 14:28:51 2024, Cynthia , Update, Interferometer Simulations, SIS cavity with thermal effect
|
tried to run a cavity scan with thermal deformation and ring heater for ITM04 ETM08 (aLIGO mirrors). Not sure about the accuracy of the graph as there is some commands that still need to verified. |
Mon Sep 23 08:29:49 2024, Luke, Update, Interferometer Simulations, Ringheater update
|
Ringheater Update
If the link does not work here is the file. |
Sun Feb 16 16:45:18 2025, Luke , Update, General, Ringheater position optimization   
|
Over the last couple weeks I have been working on finding the optimal position of the ringheater's thermal profile.
Today I would like to give an update of where I am at and my next steps.
Using the python COMSOL interface I have been able to run and save deformation data sweeping through a great deal of potential combinations of widths and positions.
I then calculated their zernike coefficients and using a very simple "quality" function (02 - (40)*10 - (4-4)*10), where 02 stands for the zernike mode of quadratic deformation, I was able to generate a heat map of comparing the "quality" verses the width and position used.
Seen below are four plots. The first is simply the 02 coefficient of the decomposition followed by the negative of 40 and 4-4 then the "quality."
This 'quality' function was an arbitrary choice on my part. I believe that my next step would either be defining a more useful function or using finesse to model the actual effects of this surface deformation. |
Mon Aug 12 16:35:30 2024, Luke , Update, , Ringheater modeling Update  
|
|
Wed Oct 2 12:05:42 2024, Luke , Update, , Ringheater modeling Update
|
Power point slides |
Sat Jan 25 18:19:39 2025, Luke , Update, General, Ringheater modeling Update
|
Here is a quick update on some of the things I have been working on regarding my project. |
Sun Feb 23 16:00:07 2025, Luke , Update, Scripts/Programs, Ringheater modeling Update 
|
These are some plots:
The first shows the convergence of the 02 mode reducing the size of the mesh. The second shows the the numerical error of the zernike.
The first is found by sweeping a parameter that changes the size of the mesh. The HR surface was set to half a cm for all values.
The second by taking the inner product of a zernike mode with its self and calculating its deviation from pi for varying fineness of the mesh. |
Tue Aug 27 18:37:40 2024, Luke, Update, Interferometer Simulations, Ringheater model update   
|
Updated the model to produce a more circular deformation in the HR surface. The first three attachments are from irradiance patterns gotten from ray tracing. The last is from a pre-defined irradiance pattern. |
|