ID |
Date |
Author |
Type |
Category |
Subject |
542
|
Tue Mar 25 12:56:47 2025 |
Tyler | Update | TCS | FROSTI Analysis Finalization |
Upon final review of the FROSTI analysis included in the (hopefully) soon-to-be submitted instrument paper, I've made some adjustments to the reflectivity analysis that estimates the amount of power delivered to the test mass by the FROSTI. Initially, as detailed in elog 447, the delivered power was approximated to be 12.6 W (later adjusted to 12.9 W), with roughly 18% of this power being reflected by the test mass. After some final adjustments, this value now is closer to 12.0 W, with 10.2 W absorbed (15% power reflection). Below is a table showing the updated values for the FROSTI prototype tests:
|
Old Value |
New Value |
Delivered Power |
12.9 W |
12.0 W |
Absorbed Power |
10.6 W (18% reflectivity) |
10.2 W (15% reflectivity) |
Measured Peak Temperature Difference |
5.39 +/- 0.03 K |
5.26 +/- 0.03 K |
Model Peak Temperature Difference |
5.42 K |
5.21 K |
Measured Peak OPD |
765 +/- 9 nm |
771 +/- 7 nm |
Model Peak OPD |
630 nm |
654 nm |
|
570
|
Tue May 6 12:25:03 2025 |
Tyler | Configuration | CDS | Cymac ADC CSD measurement |
An initial measurement of the cymbal ADC CSD is attached below. As of now, it seems that the sensitivity limit is roughly the same as that of the Red Pitaya. |
577
|
Tue May 13 12:41:06 2025 |
Tyler | Update | TCS | A# Profiles Update |
Slides on the A# ITM FROSTI profile modeling efforts can be found here. |
595
|
Tue Jun 17 12:46:47 2025 |
Tyler | Update | Electronics | CyMAC ADC Noise |
Below are results from power spectra measurements of the CyMAC ADC, computed form 30 hours of time series data, compared to the performance of the Red Pitaya. The frequency resolution for the initial Cymac CSD is 2 Hz, and 216,000 spectra measurements are averaged together. As of now, it still looks like we haven't reached the correlated noise floor of the CyMAC. We have a few days worth of data to take from, so I'll look into using a longer period of time. |
597
|
Tue Jun 24 12:45:16 2025 |
Tyler | Update | General | Updated ADC spectra |
[Tyler]
Updated ADC noise spectra measurements using diaggui.
NOTE: Will update plots with proper axes |
602
|
Tue Jul 1 12:39:42 2025 |
Tyler | Update | TCS | A# FROSTI Profile Optimization Update |
[Tyler, Liu]
Slides |
605
|
Mon Jul 7 17:44:04 2025 |
Tyler | Update | General | Lab Organization |
[Tyler, Pooyan, Ma, Cece, Luke, Luis, Christina, Maple]
After acquiring some new equipment for the labs, a few of us spent time on Thursday and Friday sorting through everything and storing them into their appropriate places. New vacuum parts, power supplies, cables, and much more were included. The rooms are now ready for the lab tours commencing Tuesday afternoon. |
607
|
Tue Jul 8 12:15:04 2025 |
Tyler | Update | TCS | CyMAC ADC Noise Update |
[Tyler, Christina, Ma, Mary]
Below is attached the ADC noise floor of two CyMAC channels vs the Red Pitaya.
The frequency resolution of these RIN spectra are 16 Hz, with N_meas = 19,308,426 for the CyMAC, and N_meas = 263,024. |
610
|
Mon Jul 14 23:50:22 2025 |
Tyler | Update | | Cymac ADC update |
I've been looking into the performances of individual channels on the Cymac by computing their individual PSDs and corresponding CSDs that show their noise relation to each other. It appears some channels do have lower noise floors than others, and some combinations of these actually do perform similar to the Red Pitaya (showing below the CSD between CHs 3 and 5), although it doesn't look like it's much of an improvement. The best method as of now still appears to be phase-locking two separate ADCs to reduce the correlated noise floor further.
This can be further discussed at the July 22, 2025 group meeting. |
626
|
Tue Aug 12 12:35:19 2025 |
Tyler | Update | | CyMAC ADC Update |
[Christina, Ma, Tyler]
Updated CyMAC measurement, comparing 260 hrs of measurement time vs. 405 hrs. |
627
|
Tue Aug 12 13:28:00 2025 |
Tyler | Update | TCS | RH Fenicsx v. HV |
|
636
|
Tue Aug 26 13:09:03 2025 |
Tyler | Update | TCS | O6 RH Update |
[Tyler]
Below are slides giving an update on RH O6 design progress.
Slides |
637
|
Tue Sep 2 11:53:34 2025 |
Tyler | Update | TCS | RIN Infrastructure Update (09/02/2025) |
[Ma, Tyler]
Below are slides discussing RIN infrastructural updates related to the CyMAC.
Slides
|
642
|
Tue Sep 9 12:06:38 2025 |
Tyler | Update | TCS | RH O6 Update |
Slides |
134
|
Tue Jun 27 14:04:42 2023 |
Sophia A. | Update | Measuring Noise in Interferometer | Interferometer set up and connection to red pitaya |
Today we (Sophia and Tyler) constructed the set-up for the electrical noise calculation that I will be conducting this summer. I have included images of the setup below. Our system is effectively a green laser, that feeds into a type of polarizer, then into a beam splitter which sends the laser light down two arms into detectors. We started by connecting the detectors to an oscilloscope to determine whether the signal will exceed 1V, as the red pitaya (our planned data collection device) cannot receive signals with a higher voltage than 1V. We spent most of our time calibrating the oscilloscope and fine-tuning the set-up so that we would have approximately equal voltages in each arm of the interferometer. Once confirming that the output voltage would not meet or exceed 1V, we switched from an oscilloscope to the red pitaya for our measurements. Now that the system is set up, we will be able to run code in the red pitaya interface that will run an FFT on the signal, and then do noise analysis from there. |
162
|
Tue Jul 18 14:13:46 2023 |
Sophia | Update | Scripts/Programs | Update on Laser Noise Data Collection and Analysis |
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. |
174
|
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. |
175
|
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) |
183
|
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. |
186
|
Tue Aug 1 15:44:31 2023 |
Sophia | Update | Scripts/Programs | Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots |
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. |
194
|
Mon Aug 7 15:36:18 2023 |
Sophia | Update | Scripts/Programs | Update on Laser Noise Data Collection and Analysis: Dynamic CSD and PSD Plots |
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. |
196
|
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). |
206
|
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! |
207
|
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. |
391
|
Mon Jul 1 11:45:45 2024 |
Sid | Update | Interferometer Simulations | |
Progress update: Most of last week was spent getting set up with SIS, and learning how to do basic simulations. The goal for this week is to begin reproducing the methodology from T2000338. I have begun with studying perturbations to mirror curvature and position in a simple FP cavity, but thus far have been unable to get the same results. |
259
|
Thu Nov 9 13:57:58 2023 |
Shane, Luis, Aiden, Tyler | Update | Cleanroom | cleanroom cleaning and particle count |
[Aiden, Shane, Luis, Tyler]
cleaning cleanroom and particle count
- 12:30 pm: Tyler and Aiden started organizing cables in cleanroom
- 12:35 pm: started particle count in flow bench
- 0.3 u: 11681
- 0.5 u: 3284
- 1.0 u: 1039
- 12:50 pm: started cleanroom particle count
- zone 3:
- 0.3 u: 14549
- 0.5 u: 10351
- 1.0 u: 6194
- zone 4:
- 0.3 u: 10808
- 0.5 u: 4655
- 1.0 u: 1953
- 1:07 pm: began surface check and wipedown, including softwalls
- 1:19 pm: started vacuuming the floor
- 1:28 pm: finished vacuuming the floor
- 1:29 pm: started mopping the floor
- 1:33 pm: finished mopping the floor
- 1:34 pm: started cleaning the buckets
- 1:37 pm: started mopping with IPA wipes
- 1:39 pm: finished mopping with IPA wipes
- 1:40 pm: changed sticky floor mats
- 1:41 pm: started particle count
- zone 3:
- 0.3 u: 8397
- 0.5 u: 5071
- 1.0 u: 2618
- zone 4:
- 0.3 u: 6651
- 0.5 u: 4323
- 1.0 u: 2120
|
290
|
Mon Dec 11 12:58:57 2023 |
Shane, Luis | Update | CDS | DAC-ADC loopback test debugging |
[Luis, Shane]
Working on debugging last week's weird results for the ADC-DAC loopback test for channels 14 and 15. With DAC output channels 12-15 connected to ADC input channels 12-15: tried setting matrix coefficients for channels 12-15 to 1, and as with last week's results, DAC is outputting as expected for all three channels and ADC is not reading in the signal (hovering around -4,-5) for channels 14 and 15. Channels 12 and 13 still reading in correctly. Tried switching DAC output plug into channels 0-3, with ADC input plugged into channels 12-15, and all input/output signals were reading correctly. Then switched to plugging in DAC output to channels 12-15 and ADC input to channels 0-3, and saw that channels 0-3 were only able to receive the first two ADC input values. This shows that channels 12-15 are capable of receiving the correct inputs from other channels, but are failing to produce outputs for channels 14 and 15. |
254
|
Thu Nov 2 17:14:36 2023 |
Shane, Jon | Update | CDS | CyMAC set up permanentized |
CyMAC connections have been finalized and made permanent. Also tested voltages, which are all looking good. Warning: power is on. Do not touch power supply terminals or screws connected to grounding cables (see attached images 4 and 5; green wires on back of power supply with black and yellow covers, and exposed positive and negative terminals on back of power supply).
Also established connections from Anti-Aliasing chassis to ADC adapter board, Anti-Imaging chassis to DAC adapter board, and binary in/out chassis to BIO card, all mounted within Cymac host computer. Turned on CyMAC and ran test model, received error message likely pointing to timing signal not being successfully passed to the adapter boards. Next steps are checking to make sure correct timing signal is actually being output, and then checking internal ribbon cable in host chassis, which is another potential cause of the error.
|
171
|
Mon Jul 24 16:19:29 2023 |
Shane, Jon | Update | Electronics | Chassis semi-assembled and moved |
Began assembly on AA and AI chassis today, moved them both to top work bench shelf (image attached). They are delicate so please do not disturb them or put anything on top of them. |
176
|
Thu Jul 27 14:46:55 2023 |
Shane, Jon | Update | Electronics | AA chassis DC on/off switch assembled |
Made the first DC on/off switch assembly today and installed in anti-aliasing chassis. Second switch assembly to be completed later. |
191
|
Thu Aug 3 18:03:42 2023 |
Shane, Jon | Update | CDS | Anti-Aliasing chassis complete |
We finished installing the internal power supply cables in the anti-aliasing chassis today, which concludes its assembly. Work on AI, BI, BO chassis still underway. |
197
|
Tue Aug 8 17:03:22 2023 |
Shane, Jon | Update | CDS | Binary input chassis finished |
Finished assembly of the binary input chassis today, including DC on/off switch and LED installation. external cable assemblies still needed, but internal work done. |
210
|
Wed Aug 16 16:55:40 2023 |
Shane, Jon | Update | CDS | external power supply cables finished |
All four external power supply cables for the CyMAC chassis are now assembled. Using them now to test if chassis power up correctly. |
211
|
Wed Aug 16 17:17:02 2023 |
Shane, Jon | Update | CDS | Binary input chassis powering correctly |
Binary input chassis passed power-on test, and is lighting up as expected. Binary output chassis also successfully powered on. AA and AI chassis not powering on correctly, need to do some debugging to find the problem. |
225
|
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. |
231
|
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. |
236
|
Mon Oct 9 16:59:21 2023 |
Shane, Jon | Update | CDS | timing chassis power cable and AI chassis testing for CyMAC |
[Shane, Jon]
Today's CyMAC work:
- Finished assembling external power supply cable for the timing chassis (see attached image)
- Also did some debugging of AA and AI chassis re: power issues. After testing voltages at various test points on the power regulator board (TP1-TP6) in the AA chassis, it seems like it's the source of the problem. Used bench DC power supply to test, running 15V, and the correct voltage is coming in to the board but something significantly smaller is being output. We're also getting unexpected negative signs on voltage at certain test points, with leads in correct positions
- Upon further examination, it looks like the lights on the filter boards are actually turning on (in both the AA and AI chassis), though it's only 2/4 lights on each board and they are very faint
- Corrected DC on/off switch spade lug orientation in AI chassis.
- Tested AI chassis power regulator board to see if the problem was the same, and found again that voltage coming in was correct, and voltage going out was not.
- In case of interest in exact numbers, results were as follows:
- Voltage difference between TP1(+Vin) and TP6(-Vin) is ~30V
- Voltage difference between grounded chassis wall and TP1 (+Vin) is ~15V
- Voltage difference between grounded chassis wall and TP6(-Vin) is ~-15 V
- voltage difference between TP2(+Vout) and TP5(-Vout) is ~3V
- Voltage difference between TP3 (gnd) and TP2(+Vout) is -0.065V
- Voltage difference between TP5(-Vout) and ground is ~3V
|
244
|
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). |
137
|
Wed Jun 28 15:58:56 2023 |
Shane, Cao | Infrastructure | VAC | Power trip problem remains, source of smoke is insulation |
[Shane, Cao]
With the new change in wiring configuration described in elog 136, we tried to power up the heaters for baking the vacuum chamber again.
Given that we were worried about the turbo pump overheats, we set the setpoints of of bother high temperature controller and PID controller to be 120 deg C before turning the heaters on
1. Evidence of smoke originating from CoolSkin insulation
We then removed most of the CoolSkin insulation on the Pump and RGA lines ( apart from the one around the flexible bypass line connecting the two ) (see image Pumpline_afterRemoveInsul and RGAline_afterRemoeInsul) .
Upon removal of the insulation, we noticed that the insulating foam melted onto the heating tape (see image MeltedInsulation1 and MeltedInsulation2). This is the first indication that the smoke had most likely coming from the insulating foam itself
Once we started baking, upon reaching 80 degree range. We observed no smoke at the location that we removed the insulation. However, We observed smoked coming from underneath the insulation around the flexible pipe, and not from the velcro areas.
What could be causing this, given that the maximum operating temperature of the insulation is 200 deg C? Most likely, the heating tape is much hotter than we think it is. But given that the temperature sensor readout is much lower than 200 deg C, it's likely that this is due to poor thermal contact and it takes a while for sensor to reach a thermal equilibrium with the heating tape. Here, I suggest we should implement the following:
- We should look into usingsome form of thermal tape (if possible to secure the temperature sensors)
- Unfortunately or controller does not allow programming process, we will have to implement manual temperature stepping, emulating ramping process over the first hour, until slowly reach 120 deg C
- OR Tune the PID controller coeffs, especially P and I for longer rise time and settling time
2. The heaters still trip our power
Upon reaching 80 deg C,our main power trip. Unfortunately I don't know how to reset this. Do we need to contact facility on this? Reading elog 136, I noticed that both controllers are connected to the same circuit LP3B 6, which is the same circuit the some of the fan-filters and LED light panels of the cleanroom connected to. From the elog, the circuit has a 20 A limit . An max operation, the 2 heater controllers draw 30 Amps, approx 7 Amps for the fan-filters, and another 1.5 A for LED panel. The combination of these equipment must have overload the circuit and tripped it . Currently half the fans + lights are off in the cleanroom are off due to power trip. Here, I would make a suggestion that each heater controller should be connected to a separate circuit . Currently we LP3B 7 (same side next to LB3B 6) and LB3B 4 (opposite side of the rail) having no equipemts connected to them, but will require cable extensions. |
177
|
Fri Jul 28 13:07:39 2023 |
Shane, Aiden | Update | Cleanroom | cleanroom cleaning and particle count |
[Aiden, Shane]
cleaning cleanroom and particle count
- 11:08 am: started particle count
- zone 3:
- 0.3 u: 4198
- 0.5 u: 1080
- 1.0 u: 581
- zone 4:
- 0.3 u: 1247
- 0.5 u: 623
- 1.0 u: 415
- 11:24 am: break for removal of vac chamber insulation (pictures attached), with counts before removal as seen above, and counts after removal/replacement for zone 3 as follows:
- zone 3:
- 0.3 u: 2993
- 0.5 u: 415
- 1.0 u: 207
- 12:02 pm: began surface check and wipedown
- 12:13 pm: started vacuuming the floor
- 12:25 pm: finished vacuuming the floor
- 12:26 pm: started mopping the floor
- 12:32 pm: finished mopping the floor
- 12:32 pm: started cleaning the buckets
- 12:37 pm: started mopping with IPA wipes
- 12:43 pm: finished mopping with IPA wipes
- 12:45 pm: changed sticky floor mats
- 12:47 pm: started particle count
- zone 3:
- 0.3 u: 2951
- 0.5 u: 290
- 1.0 u: 41
- zone 4:
- 0.3 u: 290
- 0.5 u: 0
- 1.0 u: 0
|
228
|
Fri Sep 29 11:22:33 2023 |
Shane, Aiden | Update | Cleanroom | cleaning and particle count |
[Aiden, Shane]
cleaning cleanroom and particle count
- 10:06 am: ran zero count test on particle counter
- 10:07 am: started particle count
- zone 3:
- 0.3 u: 2203
- 0.5 u: 831
- 1.0 u: 540
- zone 4:
- 0.3 u: 374
- 0.5 u: 124
- 1.0 u: 124
- 10:25 am: began surface check and wipedown
- 10:34 am: started vacuuming the floor
- 10:44 am: finished vacuuming the floor
- 10:45 am: started mopping the floor
- 10:49 am: finished mopping the floor
- 10:50 am: started cleaning the buckets
- 10:57 am: started mopping with IPA wipes
- 11:01 am: finished mopping with IPA wipes
- 11:02 am: changed sticky floor mats
- 11:03 am: started particle count
- zone 3:
- 0.3 u: 2535
- 0.5 u: 374
- 1.0 u: 166
- zone 4:
- 0.3 u: 581
- 0.5 u: 41
- 1.0 u: 0
|
241
|
Fri Oct 20 16:38:02 2023 |
Shane, Aiden | Update | Cleanroom | Cleanrooom cleaning and particle count |
[Aiden, Shane]
cleaning cleanroom and particle count
|
28
|
Sat Feb 11 17:09:29 2023 |
Shane | Update | General | clean room particle counts 2/10/23 |
Took a round of clean room counts after the latest clean of vacuum chamber on Feb 10. Used 60 second sample time, 5 samples for each of the 5 zones. Plots attached for both occupied clean room (one person inside, attachment 1) and unoccupied clean room (empty attachment 2), as well as the raw data from the particle counter (attachment 3). |
32
|
Thu Feb 23 13:32:55 2023 |
Shane | Update | General | Clean room floor particle counts |
Here are the counts from the clean room floor today. The counts should be dated- the ones from today (2/23/23) are the last 8 in the chart. The first set of 2 measurements from today were under the table by the clean room entrance, the next two were under the table by the vacuum chamber, the next two were on the floor by the vacuum chamber lid, and the last two were on top of the table for comparison. All measurements were taken using 2 minute sample time. |
49
|
Thu Mar 9 13:51:42 2023 |
Shane | Update | General | Clean room counts 3/9/23 |
Here's the clean room counts from this morning. Also attached is rough diagram of where the five zones are in the clean room. Counts taken with 2 minute sample time, three samples in each zone. |
54
|
Wed Mar 22 15:25:00 2023 |
Shane | Update | General | Clean room recertification particle counts |
Attached are the five zone particle measurements for the clean room now that the fan speeds have been set to MEDIUM. 2 min sample time, 3 samples per zone. The occupied clean room measurements were unusual in that they generally got larger towards minute 6 instead of settling and going to zero, and for this reason didn't stay beneath the class 5 requirement at the end of the samples. The unoccupied counts look more similar to what was expected, and generally settle under the class five requirement. |
110
|
Wed May 31 12:16:28 2023 |
Shane | Update | Cleanroom | cleanroom particle counts (full 5 zone measurement) |
Attached is the full 5 zone particle measurement for the cleanroom after this week's cleaning, 5/31/23. |
133
|
Tue Jun 27 12:09:37 2023 |
Shane | Update | Cleanroom | cleanroom 5 zone particle count measurement |
Attached is 5 zone measurement for cleanroom particulate count. Zone 3 (in front of vacuum chamber) higher than usual, likely due to recent vac work. Slightly above ISO class 5 standard in 1.0 micron range, measuring 997 particles/cubic meter while ISO standard is 832 particles/cubic meter in this range.
Zero count test on particle counter performed prior to today's measurement. |
172
|
Tue Jul 25 15:35:14 2023 |
Shane | Update | Electronics | More chassis moved |
Finished basic assembly of binary input and output chassis today, and moved one to top shelf of work bench. The other is in corner of work bench (image attached). They are delicate, so please do not move them or place anything on top of them. |
182
|
Mon Jul 31 12:39:01 2023 |
Shane | Update | Electronics | LED cable assemblies installed |
Today I put together the two LED cable assemblies for the CyMAC and mounted them in the anti-aliasing and anti-imaging chassis. |