The file is currently at ~controls/sballmer/bin/checkCompiledModel Usage: checkCompiledModel mymodel.mdl Example 1: ========== controls@opsws3:~ 0$ ./sballmer/bin/checkCompiledModel SIXOSEM_T_STAGE_MASTER.mdl SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1susmc1 | SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1susmc3 | SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1susomc | SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1suspr2 | SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1suspr3 | SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1sussr2 | SIXOSEM_T_STAGE_MASTER.mdl | LastModifiedDate "Thu Oct 11 10:00:18 2012" | h1sussr3 | Example 2: ========== controls@opsws3:~ 0$ ./sballmer/bin/checkCompiledModel h1isiham5.mdl h1isiham5.mdl | LastModifiedDate "Mon Aug 5 14:22:07 2013" | h1isiham5 | Name "SVN $Id: h1isiham3.mdl 3807 2013-02-13 23:39:29Z hugo.paris@LIGO.ORG $" Example 3: ========== controls@opsws3:~ 0$ ./sballmer/bin/checkCompiledModel MC_MASTER.mdl MC_MASTER.mdl | LastModifiedDate "Thu Jan 24 13:17:13 2013" | h1susmc2 | MC_MASTER.mdl | LastModifiedDate "Thu Jan 24 13:17:13 2013" | h1susprm | MC_MASTER.mdl | LastModifiedDate "Thu Jan 24 13:17:13 2013" | h1sussrm | Example 4: ========== controls@opsws3:~ 0$ ./sballmer/bin/checkCompiledModel hepitemplate.mdl hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpibs | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpietmx | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpietmy | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiham1 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiham2 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiham3 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiham4 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiham5 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiham6 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiitmx | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1hpiitmy | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1isiham2 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1isiham3 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1isiham4 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1isiham5 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" hepitemplate.mdl | LastModifiedDate "Tue Feb 12 09:30:54 2013" | h1isiham6 | Name "SVN $Id: hepitemplate.mdl 3774 2013-02-12 17:32:42Z vincent.lhuillier@LIGO.ORG $" Code: ===== #!/bin/bash # usage: # checkCompiledModel# # makes a list of all front end codes that use # and lists the LastModifiedDate of , as well as # the SVN Id string # # useful for # - figuring out which model uses which library # - what version things are compiled agains # # Author: Stefan Ballmer, 2013/10/20 # parameters model=$1 TEMPDIR=/tmp/tempDir_checkCompiledModel files='ls /opt/rtcds/${site}/${ifo}/target/${ifo}*/src/sources.tar.gz' # make temporary directory mkdir $TEMPDIR cd $TEMPDIR for f in $files do g='echo $f | sed 's/// /g' | awk '{print $6}'' # echo checking $g mkdir $g tar -xf $f -C $g data='find $g -name $model' for d in $data do lmod='grep LastModifiedDate $d' svnstr='grep "SVN $Id" $d' echo $model | $lmod | $g | $svnstr done done cd .. rm -rf $TEMPDIR
Jeff Kissel, Stefan Ballmer We started to modify to local svn copy of the suspension models to include a cleaned-up version of the ODC parts and an IPC sender to the ODC master Modifications to ODC library: - The ODC library parts were cleaned up and repackaged. They are in cds/common/model/ODC.mdl and cds/common/model/ODC_CHAN.mdl. There will be some further changes inside ODC.mdl, but the inputs and outputs won't change any more. - We decided to give up full backwards compatibility of the parts to get them clean up. In particular: - In ODC.mdl, we changed the number of inputs of the CHANS (bit combiner) block from 31 to 30, because the 31st bit cannot be used anyway (it is reserved for the parity bit) - In ODC.mdl, for the COMBINE_ODC block, we added one input for the bitmask and one output for a latched version of the ODC channel for epics. - ODC_CHAN.mdl contains a new all-in-one ODC block for use in front-end models (called CHANNEL). (see plots) - Files ODC_CHAN.mdl ODC.mdl Modifications to SUS master models: - ODC_CHANNEL_OUT is now recorded as uint32 at full rate - The new, all in one ODC library block (called CHANNEL) was installed (see plots). - Its output is routed to the last output of the master model. - Updated models: OMCS_MASTER.mdl HSTS_MASTER.mdl TMTS_MASTER.mdl QUAD_MASTER.mdl HLTS_MASTER.mdl BSFM_MASTER.mdl MC_MASTER.mdl - we also started to update HAUX_MASTER.mdl which did not have and ODC output at all. Jeff will finish this one tomorrow (as well as a possible merger with HTTS_MASTER.mdl) Modifications to suspension models - Added an ipc link (called H1:{OPTIC}_ODC_IPC) to the new ODC output from the master model - Updated models: h1sustmsx.mdl h1sustmsy.mdl h1susprm.mdl h1sussrm.mdl h1suspr2.mdl h1susbs.mdl h1suspr3.mdl h1sussr2.mdl h1sussr3.mdl h1susetmx.mdl h1susomc.mdl h1susetmy.mdl h1susmc1.mdl h1susmc2.mdl h1susitmx.mdl h1susitmy.mdl h1susmc3.mdl - All of them did recompile, but we did not install or run any of them yet. None of the listed files are in svn yet - Jeff will implement additional changes tomorrow.
I moved the new ODC library to a different file name to ensure backwards compatibility. Old ODC library: cds/common/ODC.mdl New ODC library: cds/common/ODC_CHAN.mdl : top level ODC part (called CHANNEL) with 30 bit inputs and a finished ODC channel output. It points to ODCV2.mdl intenally cds/common/ODCV2.mdl : updated ODC parts, contains: BITCOMBINE: for combining bits (bit-shifting); and PACK: adds summary bit and parity bit and generates a latched version of the ODC_CHANNEL for epics consumption Since all updated SUS models point to ODC_CHAN.mdl, they are now automatically up to date. I handed the SUS models off to Jeff for some more mods. Next on the to do list: update ISI and HPI - this will require changes to isi/common/models/isi2stagemaster.mdl isi/common/models/isihammaster.mdl hpi/common/models/hepitemplate.mdl
We developed and tested a prototype ODC Master model for use in the corner station on the Test Stand. Screenshots of the model are attached. We tested that the 32 bit word calculations all work properly, including the new C library part used to take the BITWISE AND of multiple inputs. We also tested the updated C library part for setting a high-order odd parity bit in a 32 bit integer channel, and showed that it worked properly. We plan to migrate the new code for ODC Master to the OAF FE machine next. Additionally, we carefully tested the new DAQ channel type setting "uint32". We found that the data appears to be written to disk properly in binary, but FrDump and the python FrUtils both display the data as signed integers, so a value of uint32: 2147483654 becomes int32: -2147483642.
- moved IMC_CUST_OVERVIEW.adl form ioo/h1/medm to ioo/common/medm - replaced all site-specific occurrences (LHO,lho,H1,h1) with their macro counterparts for ioo/common/medm/IMC_CUST_OVERVIEW.adl and ioo/common/medm/IMC_CUST_ODC.adl - verified that the screens work at bot observatories. - updated sus/common/medm/bsfm/SUS_CUST_BSFM_ODC.adl sus/common/medm/hxts/SUS_CUST_HLTS_ODC.adl sus/common/medm/hxts/SUS_CUST_HSTS_ODC.adl sus/common/medm/omcs/SUS_CUST_OMCS_ODC.adl sus/common/medm/quad/SUS_CUST_QUAD_ODC.adl sus/common/medm/tmts/SUS_CUST_TMTS_ODC.adl to include the COMBINE_ODC_BITMASK and a link to the corresponding subsystem. Also updated sys/common/medm/SYS_CUST_ODC_CHAMBER.adl sys/common/medm/SYS_CUST_ODC_ENDCHAMBER.adl sys/common/medm/SYS_CUST_ODC_HAM1.adl sys/common/medm/SYS_CUST_ODC_HAM2.adl sys/common/medm/SYS_CUST_ODC_HAM3.adl sys/common/medm/SYS_CUST_ODC_HAM4.adl sys/common/medm/SYS_CUST_ODC_HAM5.adl sys/common/medm/SYS_CUST_ODC_HAM6.adl sys/common/medm/SYS_CUST_ODC_SITE_OVERVIEW.adl All changes have been propagated to LLO.
Dave B., Jim B., Patrick T., Richard M., Robert S. This was an experiment to test a fix to the 'noise' documented in alog 8076. The problem may be that the sampling method used in the previous code (device support met_one_227b-1.0.1) may have initiated a short stage to purge the air path through the dust monitor before the start of each sample, and this was not happening with the new code (device support met_one_227b_comp_ctrl-1.0.0). The previous code used this command: "d" Start Counting (counter controlled): The counter will begin counting and control the count cycle based on the front-panel setting for period (sample time). From Robert's comments in his original iLIGO code (http://blue.ligo-wa.caltech.edu/apps/epics/3.12.2.pem.llo/release/r3.12.2.PEM.LLO/base/src/drv/ansi/drvDustMetOne227.c): The sample time is set in the dust monitor. This routine uses the "d" command (dust monitor control) rather than the "c" command (computer control). The advantage is that you can start several monitors almost simultaneously rather than sequentially. The monitor purges for two seconds before starting the sample - important for time stamping the sample. The new code uses the following command: "c" Start Counting (computer controlled): The counter will begin counting without waiting for an even second boundary (quick start). Counting will continue until stopped by the computer. The count cycle should be controlled by the computer. It may be that the "c" command does not run a purge prior to counting. I added the following separate command with a short sleep after it before the "c" command and started testing it with the dust monitors in the optics labs: "g" Active Mode: The counter will enter a mode that prepares it for counting. For example, the air pump may turn on to purge the air path. It is unclear if this runs for a set period or until it receives the next command. I added a one second sleep after each iteration through the dust monitors to address the code's high CPU use as well. I also added one second sleeps after caught exceptions in drv227b.cpp to provide some time to read the printed error message. 13:30: I stopped the dust monitor code for the optics labs and started the modified code. The sleep after the "g" command was set to 2 seconds. 14:00: I stopped the modified code, changed the sleep to 5 seconds, and restarted it. 14:14: I stopped the modified code again, changed the sleep back to 2 seconds, and restarted it. 15:00: I stopped the modified code. - I checked the modified code into subversion. - 18:03: I restarted the modified code in 'screen' on h0epics from /ligo/apps/linux-x86_64/epics-3.14.12.2_long_sc/iocs/dust/dust_met_one_227b_comp_ctrl-1.1.0. I have attached a plot of the dust counts in the Vacuum Prep Lab over this period. The change appears to have helped. I will let this run over the weekend.
Long story short - for those of us trending particulate from these channels, do we trust the magnitude of the signal, even though many signals are always showing ~80 cts?
No, do not trust the counts since October 8.
Brilliant.
It appears that it core dumped around Oct 19 2013 11:35:33 PDT. I'm going to restart it outside of 'screen' to see if I can reproduce the error and get better diagnostics.
[Stefan and Kiwamu] (Translated by J. Kissel)
Approximately 2 months ago (see alog 7490), Stefan and Kiwamu modified the output matrix of the IMC's ASC control system, such that the caviy-axis-basis ("DOF" basis) alignment is decoupled with the input pointing alignment.
Jeff K. asked me to write some more details for the procedure of how we did it
Here it is, translated by Jeff.
The procedure of the adjustment :
We're going to use the closed-loop, control output signals for these cross-coupled, cavity-axis-basis, loops as our metric of where the cross-coupled sensors think the cavity axis lies. We will then offset the error point of DOF3 (which controls the input pointing, with the PZT) at DC, to see how this affects all our controlled degrees of freedom (again at DC). Before we get started, there is some residual DC value of this control signal because the static alignment had not yet been tuned, and the integrators in the loops found the best spot for us. To make things easier to calculate later, we can offload this DC alignment control signal to the mirror/actuator basis (after the output matrix that we're trying to make better), such that the cavity-axis-basis control output signal is zero at DC. We have a script that already does this:
/opt/rtcds/userapps/release/ioo/h1/scripts/imc/mcwfsrelieve
I have written a python script to monitor the eight beam tube vacuum gauges and send emails to cell phones if a vacuum excursion is detected. It runs on sysadmin0 machine in the control room. It samples every 5 minutes, sending emails to John, Kyle, Richard, Ski and myself (both ligo-wa email and cell phone text messages).
code is in /opt/rtcds/userapps/release/cds/h1/scripts/ve_btvac_alarms_emailer.py
btvac = Beam Tube Vacuum.
This script performs the out-of-hours supplemental monitoring linked to the control room Alarm Handler and Wall Display striptools.
After some discussion with the SEI group, I made the following changes to the macro file naming at LHO to make both observatories identical and following the same standard (defined in T1300881) Removed opt/rtcds/userapps/release/isi/common/medm/*macro.txt from the svn - these were originally put there in error by Joe Betzwieser. MEDM screens were not affected by that on either site. Moved hpi/h1/medm/hepi/hepi$(chamber)_overview_macro.txt to hpi/h1/medm/hepitemplate/H1_hpi$(chamber)_overview_macro.txt This makes the hpi macro file names and locations consistent between the two sites. I updated the H1 site map, which was the only medm screens affected. Moved isi/h1/medm/{bsc/ham}isi/isi$(chamber)_overview_macro.txt to isi/h1/medm/{bsc/ham}isi/H1_isi$(chamber)_overview_macro.txt This affected the following medm screens: cds/h1/medm/SITEMAP.adl (the main sitemap) isc/h1/medm/H1IFO_ALIGN.adl ioo/h1/medm/H1IOO-MC.adl ioo/h1/medm/IMC_CUST_OVERVIEW.adl all of them were updated and checked in. ODC screen work updated hpi/common/medm/hepitemplate/HPI_CUST_CHAMBER_ODC.adl isi/common/medm/bscisi/ISI_CUST_CHAMBER_ODC.adl isi/common/medm/hamisi/ISI_CUST_CHAMBER_ODC.adl as well as the sys/common/medm/SYS_CUST_ODC*.adl files to include the ODC mask and a link to the corresponding subsystem medm screen. those files were also propagated to LLO, and the links now seem to work for both sites. Next: same thing for SUS
JimW GregG HEPI actuator attachment started today at BSC9. Jim and I were able to get all of the vertical actuators attached with very little movement on the system so far. However, the vertical actuators are still locked and any moves to HEPI should be avoided until the install is finished.
• Moving ISCT EX table from LVEA to air lock at end x -> Apollo • The dust monitor (unit#3) that was in the "beer garden" has been moved to the East door side of the BSC3 cleanroom -> Richard • Site fumigation -> Sprague • Installing cables into HAM 5 and 6 IO chassis -> Aaron • The front end computer was powered down to allow EE work on the IO Chassis of h1sush56 -> David
Unit '3' was moved from the LVEA test stand, not the "beer garden". Robert had moved unit '5' from the "beer garden" into the BSC3 clean room, but Richard told me it was moved back, and unit '3' was used instead.
Alog from yesterday. Did in-rack cabling for the STS-2 Seismometer Distribution Chassis for BSC1, BSC2 and BSC3. Each distribution chassis fans out to the HAM ISI chambers (HAM2-HAM6). The following schematics were used for reference: D0901301, D1000298, D1101576, and D1101584. See attached for the physical location of each seismometer. Filiberto Clara
Mitchell, Gerardo, Apollo (Scott, Randy, Tyler), Thomas We got the suspension and the box into chamber and mounted onto stage-0. The next steps are: - Photodiode cabling - Fine-tune alignment - Check balance - Set the eddy current dampening gap - Wipe down - Swing Back for first contact removal
Filiberto C, Thomas V We wanted to make sure that at least 3/4 of the photodiodes that were installed on the ITMX baffle worked since there were failures of all the other spares (under investigation). So after replacing a faulty cable, we found that all three have continuity and registered a signal when shined upon with a flashlight. The PDs that work are PD1, PD2, and PD4, a mapping of their locations on the baffle can be found in E1100867 pg 21.
Over the last few days I've been taking some passive noise spectra of the ISI-CPS on HAM6 to try and determine what the best grounding strategy is (Jeff made a nice cartoon of the options in T1300871).
Along the way I found out a few things
1) The HAM 6 CPSs had two problems that canceled each other out
There as a master in each crate (the box near the chamber that hold the CPS controllers)
and the cable which brings the sync signal from the power board was either bad or plugged in backwards (it isn't keyed)
I tunred one of the masters into a slave and replaced the cable
2) All of the racks that I have tested have there chasis grounded, so placing them on a cable tray creates a ground and possible ground loop.
3) Currently it is pretty likely that ALL of the CPS that are installed have grounds in the electroncs room rack AND at the chamber (Ground Loop Gaore)
4) The resistance to ground from the power cable ground to the chamber is 0.6ohms
5) the sync cable carries a ground from one rack to the next
After fixing the problems I took spectra under three conditions
Multiple grounds (electroncs room and chamber) these were bad
Single ground in the electronics room, red and green lines in the attached png (clean room on/off are the differences)
Single ground at the chamber, blue lines in the attached png
Given that set of data i think that we should plan on converting to a single ground at the chamber.
The attached pdf shows one spectra converted to m/rthz and the expected noise (we have measured something close to the expected noise on the bench for every unit in use)
I don't really know what to say about this except yuck
I left the CPS on HAM6 with a signal ground (+) at from the electronics room, the boxes are not in contact with the cable trays, there is an extra ground which connects the two boxes via the sync cable
[Betsy Travis Arnaud]
Today, since BSC2 chamber was accessible, we checked the polarity of the four magnets located on the second mass (M2) of the beamsplitter with the electronic polarity tester.
As we were expecting (see 7693), three of them were flipped (UL UR LR), so Betsy reversed them as in E1100108.
Also, we took the serial numbers of the 10 bosems. They are referenced in the updated chart in E1200343
Attached are some nice pictures of ITMX ETMX BeamSplitter and the baffles
Signs of M2-M2 coilout BS medm were flipped to :
UL = -1
LL = 1
UR = 1
LR = -1
New safe snapshots were saved under the svn
Both HAM2 and HAM3 chambers are now fully controlled (HEPI+ISI).
Those chambers feature:
- Standardized ISI damping loops (defined in: SeiSVN/seismic/HAM-ISI/H1/
- Standardized ISI blend filters (SeiSVN/seismic/HAM-ISI/Complementary_Filters_HAM_ISI/HAM-ISI_Generic_Comp_Filters.mat)
- Hybrid aLigo/eLigo blend filters are available (SeiSVN/seismic/HAM-ISI/Common/Blend_filters/Filters_HAM_ISI_Blend_Hybrid_24_Jul_2013.mat)
- All 3 levels of ISI isolation loops (UGF=10Hz, 25Hz, 35Hz - LHO aLog # 5355). Performance is mostly limited by the blend filters. Level 2 controllers give similar amount of isolation as Level 3. Level 2 controllers are prefferred for now - ISI Perfomance can be found in LHO aLog #7414
- HEPI position blend filters (IPS signals are multiplied by 1, L4C signals are multiplied by 0)
- HEPI position loops. UUG = 2 Hz. Should be set to 5Hz soon. HEPI position loops performance plots, and controllers, can be found in LHO aLog #8037.
Trun on Process:
Prepare:
Damp ISI:
Turn on HEPI:
Engage the isolation loops, on the ISI
I took performance spectra on the ISI, in air, earlier this week.
HEPI was running with 2Hz UUG IPS position loops. The ISI had Level 3 isolation loops running, with the hybrid aLigo + eLigo on RX/RY blend.
Performance plots are attached for reference.
Arnaud P. Betsy W. Did B&K hammer measurements on Friday feb 8th on the BeamSplitter that will be installed in BSC2. Config: BSC-ISI Unlocked, QUAD Unlocked, Baffles ON, Vibration Absorbers ON, Damping ON. Attached, pictures describing the position of hammer impacts, and accelerometer + corresponding pulse files.
Raw data has been exported from the B&K Pulse files, in accordance with the procedure outlined in the SUS Operations Manual (see How to do B&K Hammer Testing). Exported ASCII data files have been committed to the SUS svn at the following location, ligo/svncommon/SusSVN/sus/trunk/BSFM/H1/BS/BandK$, these files include the following (n.b. files have been renamed to comply with convention detailed in the Op's Manual) :- SimpleHammerDisplay3-BS-Bottom-SUSunlocked-ISIunlocked-VAfitted-Yimpact.pls SimpleHammerDisplay3-BS-Bottom-SUSunlocked-ISIunlocked-VAfitted-Yimpact.txt SimpleHammerDisplay3-BS-BottomLeft-SUSunlocked-ISIunlocked-VAfitted-Ximpact.pls SimpleHammerDisplay3-BS-BottomLeft-SUSunlocked-ISIunlocked-VAfitted-Ximpact.txt SimpleHammerDisplay3-BS-BottomRight-SUSunlocked-ISIunlocked-VAfitted-Ximpact.pls SimpleHammerDisplay3-BS-BottomRight-SUSunlocked-ISIunlocked-VAfitted-Ximpact.txt SimpleHammerDisplay3-BS-TopLeft-SUSunlocked-ISIunlocked-VAfitted-Ximpact.pls SimpleHammerDisplay3-BS-TopLeft-SUSunlocked-ISIunlocked-VAfitted-Ximpact.txt SimpleHammerDisplay3-BS-TopLeft-SUSunlocked-ISIunlocked-VAfitted-Yimpact.pls SimpleHammerDisplay3-BS-TopLeft-SUSunlocked-ISIunlocked-VAfitted-Yimpact.txt SimpleHammerDisplay3-BS-TopMiddle-SUSunlocked-ISIunlocked-VAfitted-Ximpact.pls SimpleHammerDisplay3-BS-TopMiddle-SUSunlocked-ISIunlocked-VAfitted-Ximpact.txt SimpleHammerDisplay3-BS-TopMiddle-SUSunlocked-ISIunlocked-VAfitted-Yimpact.pls SimpleHammerDisplay3-BS-TopMiddle-SUSunlocked-ISIunlocked-VAfitted-Yimpact.txt SimpleHammerDisplay3-BS-TopRight-SUSunlocked-ISIunlocked-VAfitted-Ximpact.pls SimpleHammerDisplay3-BS-TopRight-SUSunlocked-ISIunlocked-VAfitted-Ximpact.txt SimpleHammerDisplay3-BS-TopRight-SUSunlocked-ISIunlocked-VAfitted-Yimpact.pls SimpleHammerDisplay3-BS-TopRight-SUSunlocked-ISIunlocked-VAfitted-Yimpact.txt The above B&K data has been processed using v12 of the "BandK_plot.m" Matlab script, available in the /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools$ directory. The merged plot attached below shows:- pg1 - Y response of the structure to Y hammer impact excitations at various locations, from 1Hz to 400Hz. pg2 - X response of the structure to X hammer impact excitations at various locations, from 1Hz to 400Hz. pg3 - X response of the structure to X hammer impact excitations at various locations, ZOOMED IN from 50Hz to 400Hz. n.b. hammer impact locations are viewable in the attachment to the original aLOG entry above see "Hammer_Impacts.pdf".
For acceptance review, I reprocessed the data for the beamsplitter, after seeing a legend mismatch between the plotted results and the raw data from PULSE software.
Therefore the attached results below are the ones to look at, and are following the accelerometer axis convention represented on the last attachement
(1) BandK_results_X_Exc.pdf
(2) BandK_results_Y_Exc.pdf
(3) Picture of BS with axis convention and hammer impact location
The X and Y hits have been chosen to correspond to the "Top Middle" hits on the picture
Those results in X to X (blue of 1st pdf) and Y to Y (green of 2nd pdf) are not showing any high Q resonnances below 150Hz, meaning the vibration absorbers are working as expected, and the test passed succesfully.