Today, Gerardo, Travis and I removed the PUM from the ITMy lower suspension and stowed it in it's cake tin and transport case. We only cleaned the front face since we were using the ergo arm on that surface. Most of the large glass rubble has shaken off the glass mass, but there is still particulate on it. Travis then cleaned up the horns on the ITMy in anticipation of gluing metal prisms near them. We fit checked the new prisms and prism gluing jig this morning. We had to do some filing on the jig as the clearance was too tight on the prism. The prisms and jig are now in C&B for processing. ETA of the prisms is likely next Monday. Tomorrow we will work on making the ITMy wire loop.
The third cleaning was completed first thing this morning and the "dirty room" was moved away from the chamber. The Apollo crew worked in and around HAM3 through-out the day. This morning, both doors and the support table were removed.The support table was preserved clean for later use. Later, the garbing and staging cleanrooms were moved into place on the west side of the chamber and loaded with all the appropriate accoutrements. Hoses were pulled to the chamber. Tools/tooling were retrieved from CNB. The checklist was updated, reviewed, and changed to reflect lessons from the H2 experience. Carolyn's documentation station was staged. It looks like things are ready to start in-chamber tomorrow.
Jeff Garcia is out at EY performing some tests on ETMy (B&K Hammer).
Richard, Vern, Jim, Dave
We have started building the test system for the new SUS software watchdog system. We are initially testing using the ITMY/BSC8 system. Richard verified all coil drivers for BSC8 suspensions (ITMY and FMY) are disabled.
Richard cabled the DAC output from TCS to the ITMY ADC system. In addition, the following DACs were connected back to the ITMY ADC0: ITMY DAC0, BSC8-DAC0 (HEPI) and BSC-DAC1 (ISI). Please see drawing D1200460 for details:
https://dcc.ligo.org/cgi-bin/private/DocDB/ShowDocument?.submit=Number&docid=D1200460&version=
Jim and Dave created a test model to run on h2tcsl0 to drive its DAC outputs. The model is called h2cdsswdawg and runs on an unused core on h2tcsl0 as dcu122. This model was tested to output analog voltages from h2tcsl0 DAC0 which are then digitized by h2susb478 ADC. One channels from TCS DAC0 is also fed back into a TCS ADC channel for verification, this was also tested.
We built a new model to replace h2susitmy on h2susb478. This model reads the ADC channels which are being used for the OSEM simulation in these tests, and it can be used to excite ITMY DAC0 channels. This model is called h2cdsswdb478 and has dcuid30 (replaces itmy model). We took out the h2itmyoptlev model for these tests.
All models are built using advLigoRTS/branch/branch-2.5. The DAQ was reconfigured to support these new models.
We made a first attempt at installing the software WD onto h2iopsusb478 but that is still a work in progress.
- LVC meeting is underway in Cambridge, MA. Assorted staff is off-site this week. - Apollo installing cable trays. Work was not as dusty as expected (very brief dust alarm). - TerryS and crew cleaning around HAM3. - Kyle leak-checking by BSC8. - Bob Rhodes on site working on HVAC. - CDS guests visiting this week to review code changes. - HEPI pipe welding at EX. - CDS people rebooting DAQ throughout the day. - Rear exterior LSB door is out of order (by Dale's office), Rodney is having a locksmith fix it. - OSB Doors locked at 16:10 PST.
Flooded O-ring at leak detector inlet with He after check and observed predictable permeation response
Rich Abbott reminded me of the fans in the I/O chasis, so I looked for coherence between a magnetometer (which detects the fan rotation frequency) and channels passing through the A to D in one of the chassis. I found coherence for all channels examined. Figure 1 shows coherence between an OSEM channel and my magnetometer channel and also shows that I was able to repeatedly move the coherence peak back and forth in frequency by covering/uncovering the fan ports (which changes the rotation frequency). We have had problems with fans in electronics for a long time – I found that the fans in coil drivers showed up in AS_Q, using the fan port covering technique, before S1 (here). My recollection was that, in this previous case, the coupling was through power supply ripple so Richard, Filberto and I tried powering the fans of the aLIGO chassis with a separate supply. Coherence was no longer evident. While a separate supply would mitigate this coupling, I do like Rich’s idea to eliminate all fans with vacuum suction cooling.
Robert S., Rich A., Richard M., Filberto C.
Figure: When there is no port covering, the right hand fan produces the blue peaks at about 570 Hz, the left hand fan produces the blue peaks at about 562 Hz. I adjusted the port covering to put both peaks at about 547 Hz (red). I went back and forth between the two states several times (the multiple red and blue traces).
Damping loops are now implemented on HAM-ISI Unit #2.
Watchdogs are set to their safe value:
CPS limit: 20,000 counts
GS13 Limit: 20,000 counts
Actuator Limit: 20,000 counts
Transfer functions are running over the weekend.
Baseline is too high -> should be low enough on Monday
The majority of staging for re-starting In-Chamber Cleaning at HAM3 is complete. The chamber cleanroom is in place. Both Phase 1 and Phase 2 cleaning are done: this means full garb is required to enter the cleanroom from this point forward. (I posted signs on the east and west side of the cleanroom and sent out an email.)Dust barriers, wrapping table, tooling, etc have been craned over to HAM3. A garbing cleanroom is in place. We will move the staging cleanroom ASAP. Drills have been checked with ~30 running for at least 10 seconds despite the fact that they have been sitting around for months. Paperwork has been generated.
The ISI was strongly excited on march 1 at its first rigid body mode (1.24Hz). Since L4Cs and GS13s have their resonance at 1Hz and T240 are fragile instruments, they may have been damaged during the intense shaking. The attached calibrated spectra shows that all geophones seem to be working properly. Spectra were measured with the ISI locked and unloaded (lower stages of the QUAD removed). Then motions measured by stage 1 (L4C, T240) and stage 2 (GS13) geophones are very close. CPSs seem to work too.
Today, we pulled 2 of the FirstContact(FC) sheets we sprayed on yesterday. Specifically, we pulled and inspected ITMy-HR and ITMY-AR. While it appears that some of the particulate generated from the fiber breakage and subsequent chamber removal activities were removed from our cleaning, we still saw particulate on the surface. It is on the order of what was observed when we left the ITMy and closed the chamber in Feb. We reapplied the FC to these 2 surfaces and proceeded to remove it from the lower structure. Using the ergo arm, Gerardo, Calum and I parked the ITMy in a v-block on a small optics table in the LVEA fiber welding cleanroom. We will continue to prep the optic and suspension for a wire hang. Pictures of the FC spray-on application are at: https://ligoimages.mit.edu/?c=1019 Note, this was a first article spray application - more secure and fool=proof fixturing will replace all of the foiling shown in the pictures if we proceed with the spray-on technique.
Attached are plots of dust counts > .5 microns. I have also included plots of the modes of the dust monitors that were disconnected to set the audible alarms. These show the approximate times when this took place.
Jim, Eric, Corey, Hugo
We recently received 5 production-GS13s from LLO: 3 verticals (Pods #: 30, 14, 88) and 2 Horizontals (Pods #: 93, 24). They are intended for HAM-ISI Unit #4.
We huddl-tested them before installation. One of them (Horizontal, pod #24) features the behaviour we have observed on GS13s with whether a broken flexure or a stuck mass. We tried tilting the instrument back and forth to unlock the mass. We could feel the mass moving. The ASD measured after tilting the instrument is the same as before.
Greg, Hugo,
Pod #24 was opened. The flexures were checked. Nothing abnormal was noticed. The instrument's leveling was quickly perfected and the pod was closed.
Attached power spectra shows that the instrument is still not working. It also shows that the rough leveling of the test bench is not the cause of this malfuctionning.
The audible alarms have been set on the following dust monitors: LVEA location 4 (clean room over test stand area): 20 raw counts @ .3 micron, 20 raw counts @ .5 micron LVEA location 15 (clean room over BSC 8): 20 raw counts @ .3 micron, 20 raw counts @ .5 micron LAB location 1 (OSB optics lab): 2000 raw counts @ .3 micron, 800 raw counts @ .5 micron LAB location 3 (OSB bake oven room): 2000 raw counts @ .3 micron, 800 raw counts @ .5 micron At the current sampling period of 1 minute, these raw counts should be multiplied by 10 to get particles per cubic foot. These alarm settings correspond to the current major alarm values for the alarm handler in the control room.
Dave B., Jeff G. The H2 FMX Simulink model was modified today to clean up some compiling errors and have a working FMX model running on "h2susb78". The model from FMY was used for FMX, which had not been updated with the latest BIO parts. There were several ADC and DAC channels out of order for the existing FMX model, but they have all been reconciled with the latest SUS control wiring diagram (D1001725-v9). The changes have been committed to the SVN under: '/opt/rtcds/lho/h2/userapps/trunk/sus/h2/models/h2susfmx.mdl' The new model was compiled and installed on the Front End this afternoon.
J. Garcia, J. Kissel, B. Shapiro After unlocking both the QUAD and the ISI, here are the latest results from H2 SUS ETMY. In summary, the chains look good and match other equivalent chains reasonably well, save the details below. My only concern is - There seems to be cross-coupling, most notably in the M0 Transverse direction (but present in other degrees of freedom *and in both chains*), between T/R at 1.25 Hz, and T/R/P 1.6 Hz. Other things that are not worthy: - The upper two Vertical mode frequencies are consistently higher than ITMY by ~2% (for main chain, same SUS but with metal erm for reaction chain). BUT, this would mean an equivalent increase in lower blade stiffness of sqrt(2%) = 0.04% -- by which I'm not alarmed, merely interested, since almost all other instances of SUS project wide have had *remarkably* consistent vertical modes. - Again focusing on the vertical TF -- Brett identified that we had accidentally left the UIM horizontal center of mass parameter, h1, at 0.005 m instead of the nominal production value of 0.000 m for the main chain, monolithic, 'fiber', parameter set. This offset, when present, (among other things, most notably) creates a cross-coupling of Pitch to the Vertical TF @ 2.76Hz. I've corrected this in the production model parameter set. Further, as you'll see in the attached, ITMY has some of this offset, where ETMY does not (good!). ------------ For persepective, one should probably start with allquads_120315_H2SUSETMY_ALL_TFs.pdf Here, I compare 2 chains, 4 measurements of monolithic main-chains, and 3 measurements of equivalent reaction chains. Main Chain H2 SUS ITMY 2011-12-02 -- Pre-cartridge install, Floating ISI, After IAS Adjustments, Stiffening Elements + Vibration Absorbers in Place, L1&L2 Aligned H2 SUS ITMY 2012-02-16 -- Post-cartridge install, Pre-ISI-Shakedown-Fiber-Failure, Floating ISI H2 SUS ETMY 2012-02-14 -- Pre-cartridge install, after major intra-chain rubbing was relieved H2 SUS ETMY 2012-03-14 -- Pre-cartridge install, after further UIM flag rubbing relieved, stiffening elements installed, etc (only thing missing is VA, which shouldn't effect anything). A quick scan through these TFs show that, for the most part, the most recent ETMY measurement matches the best ITMY measurement. In fact, comparing CYAN with MAGENTA, shows that the most recent round of UIM flag adjustment has greatly cleaned up all DOFs measurements. The only flaws visible are those mentioned above: - Cross-coupling, most notably in the M0 Transverse direction between T/R at 1.25 Hz, and T/R/P 1.6 Hz. - Slightly higher Vertical stiffness. Reaction Chain QUAD04 2011-11-22 -- Phase 1 approved measurement of H2 SUS ETMY, with metal ERM (on a solid stack) QUAD03 2012-01-24 -- Phase 1 approved measurment, with metal ERM (on solid stack) H2 SUS ETMY 2012-02-14 -- Pre-cartridge install, after major intra-chain rubbing was relieved H2 SUS ETMY 2012-03-15 -- Pre-cartridge install, after further UIM flag rubbing relieved, stiffening elements installed, etc (only thing missing is VA, which shouldn't effect anything). Here, in the most recent ETMY measurement, the reaction chain looks OK at first glance, but upon closer investigation shows the same 1.25Hz and 1.6Hz modes as the main chain, and the mid-frequency band just looks kinda noisier (though not as bad as 2012-02-14). -------------- The ALL_ZOOMED_TFs.pdf plot just shows a tighter X-axis for a better look at the details, and the first two attachments show a lot more information (cross-coupling, plus OSEM basis) on the CYAN measurements. Though it's difficult to blame a particular thing (*sigh* isn't that always the case?), my gut tells me there's still something rubbing between the chains. I know we've been having trouble with UIM flags... Also it's difficult to imagine a scenario where Transverse couples to Pitch... We'll keep thinking.
2012-03-14 and 2012-03-15 data shown in the above plots were taken by the following Schroeder Phased Matlab script: M0: ${SusSVN}/sus/trunk/QUAD/H2/ETMY/SAGM0/Scripts/collectTF_20120208_H2SUSETMY_allDoFs_0p01to50Hz.m R0: ${SusSVN}/sus/trunk/QUAD/H2/ETMY/SAGR0/Scripts/collectTF_20120207_H2SUSETMY_R0_0p01to50Hz_AllDOFs.m which save the data to the following .mat files: M0: ${SusSVN}/sus/trunk/QUAD/H2/ETMY/SAGM0/Data/2012-03-14_H2SUSETMY_M0_0p01to50Hz_allDOFs_tf.mat R0: ${SusSVN}/sus/trunk/QUAD/H2/ETMY/SAGR0/Data/2012-03-15_H2SUSETMY_R0_0p01to50Hz_allDOFs_tf.mat These were individually processed and plotted with ${SusSVN}/sus/trunk/QUAD/Common/MatlabTools/plotquad_matlabtfs.m (i.e. the script that makes the YYYY-MM-DD_[IFO]SUS[OPTIC]_[M0/R0]_ALL_TFs.pdfs) which saved the processed/analyzed data and plots in a standardized format to M0: ${SusSVN}/sus/trunk/QUAD/H2/ETMY/SAGM0/Results/2012-03-14_H2SUSETMY_M0_MATTF.mat R0: ${SusSVN}/sus/trunk/QUAD/H2/ETMY/SAGR0/Results/2012-03-15_H2SUSETMY_R0_MATTF.mat which where then added to the list off all Matlab/DTT measurements, and compared by ${SusSVN}/sus/trunk/QUAD/Common/MatlabTools/plotallquad_dtttfs.m (i.e. the script that makes the allquads_YYYY-MM-DD_[IFO]SUS[OPTIC]_ALL_TFs.pdfs)
Diagonalization measurements were run on the H2 ETMY M0 & R0 top masses yesterday. Results are attached. The results show ideal isolation for the two DoFs on both masses. Each DoF on both masses is at least 20dB isolated from the other OSEMs, which is well above tolerance. M0 Yaw: 25ct amplitude at 1.3Hz 21dB isolation M0 Vert: 1000ct amp. at 2.2Hz 25dB isolation R0 Yaw: 25ct amplitude at 1.3Hz 24dB isolation R0 Vert: 1000ct amp. at 2.2Hz 23dB isolation