The h1isiham3 model running on h1seih23 was quite old, from June 8th. Before we start ISI testing we (Hugo and I) upgraded this model by bringing in the latest L1 HAM3 model and converting L1->H1. From now onwards we should maintain the h1isiham3 model as separate from the l1isiham3. The new model required new Dolphin IPC channels from the h1susmc2 model, so that model was rebuilt from L1 but was not restarted on h1sush34. I had some problems recompiling the h2suspr2 model, there are IPC errors between MC2 and PR2 which are currently unresolved.
There are still some errors with the H1 ISI HAM3 medm screens. There appears to be residual links to M1 and S1 systems. I'll work with Hugo to resolve the H1 screens.
We have been working on resolving a post creek bake misalignment problem with the lower blade break off heights on H1-MC3. We have tuned out a lot of the difference, but the break off heights are still slightly out of spec. We are going to take transfer functions of the M1 level to see if MC3 performance is within tolerance despite the misalignment of the lower blade break off heights. These are the open light values for BOSEMs on HSTS MC3. The offsets and gains, listed below' have been entered into MEDM. The BOSEMs have been adjusted to 50% light. Plan is to take a set of TFs tonight when the lab is quiet. OSEM S/N OLV Offset Gain T1 571 30360.8 -15180 0.988 T2 565 28718.9 -14359 1.045 T3 312 30896.5 -15448 0.971 LF 74 27143.9 -13572 1.105 RT 313 30112.7 -15056 0.996 SD 694C 25573.4 -12787 1.173
This afternoon we obtained the spectra of the lower stages (M2 and M3) of MC2 in both the damped and undamped states (using plothsts_spectra.m). The spectra were taken over the lunch hour so the LVEA activity should have been pretty quiet. Data was committed to svn. WIll post a PDF shortly.
As well, I used awggui to try to verify that I could see drive on the coils of these lower stages (for example, exc H1:SUS-MC2_M2_COILOUTF_UL_EXC while watching the OSEMINF_OUT_DQ channel for UL). This will need to continue later as at first pass, I couldn't see much signal on the M2 AOSEMs.
I really messed up but at least I remembered! For the past couple weeks as we've been doing initial alignment and Actuator connection, I failed to correct the elevation numbers in HAM3 for the Xarm slope. Oh boy...In case you care to know---The LIGO coordinate frame is not co-planar with the gravity field in most places and in fact there is a 2.4mm shift between them moving from BSC2 (where we set them equal) just to HAM3. This shift is what I forgot to include in my elevation calcs when positioning HAM3 ISI Optical Table. So today we disconnected and relocked the eight HEPI Actuators and cranked the HEPI DSCW Springs to pull the platform up to position. Jason (IAS) was called in ~1400 and he gave us a bit of horizontal correction. Tomorrow we'll reconnect the Actuators and ask for another IAS shot to put this back to bed. At least we are getting better at Actuator connecting! Thanks to Eric, Mitchell and Jason.
Activities of the day of which I was informed:
- Elli K. to visit Y-END station, ALS table work, 8:57 - 11:18 am.
- Karen R. clean floor in the LVEA, 9:00 - 11:58 am.
- Hugh R. work in and around HAM03, all day.
- Filiberto C. work in the corner station VEA, briefly around 10:38 am.
- Karen R. work @ Y-END, clean different areas, including the floor inside the vacuum support equipment room, 1:45 - 3:45 pm.
- Cheryl V. work at Y-END, TMS, 2:51 - 3:55 pm.
- Jason O. alignment work, 2:55 - 3:50 pm.
We found that the reference cavity had lost lock.
I relocked it by disconnecting the fast and slow inputs, tweaking a bit the temperature knob and re-connecting the input cables.
The cavity is now likely locked to a different FSR from before. This means that the beat note at the end station might now be falling out of the PD bandwidth.
We have to go to end Y and adjust the ALS laser temperature to get the beat note in the PD range again.
I have taken the calibration data and analyzed it. The plot of the linear response curve is attached. I used a polynomial fitting program in python to get these numbers. This should give you the conversion from volts to micro-radians. Slope Y-intercept Pitch [ 1.01902201e+06 8.42886118e+00] Yaw [ 9.83122943e+05 -1.19329010e+01]
Please hold off on using these calibration parameters, it looks like the SUS readout channels that map out the quadrants on ETMY and ITMY were not correct and I will need to re-calculate if this is true. Updates soon to come.
The QPD mapping did prove to be different than what was previously shown on the MEDM screens. Here are the new values for the linear response curve. The units are micro-radians/volts. The lever arm is taken to be 6 meters still Pitch [ 1727.67131855 23.41350328] Yaw [ 1666.80728788 -33.14694715] It is relevant to address that a positive pitch on the ETMY quad suspension MEDM on the m0 stage will yield a higher intensity on the two lower quadrants of the optical lever QPD, giving a negative pitch as viewed facing the QPD. Also, a positive yaw in the quad suspension MEDM will yield a higher intensity on the two left quadrants of the optical lever QPD, giving a negative yaw as viewed facing the QPD. For alignment purposes this will be important to note. The next step is to take measurements over the course of at least 2-6 hours and measure the drift as a function of time.
I copy and pasted wrongly into the screen the pitch and yaw are reversed, this is signal(1/m) vs translation(micro-radians) which gives units of micro-radians*meters. Slope Y-intercept Pitch [1666.80728788 -33.14694715] Yaw 1727.67131855 23.41350328] Apologies
I have returned the broadband photodetector (S1200235) to its original box in MY.
The tripleteststand is malfunctioning - Symptoms are GPS time for user model and IOP model freezes at some time (identical for both), killing the user model and restarting the IOP results in a GPS time of 0, and the IOP indicates no ADC/DAC cards exist. There is an interesting dialog which can be brought up using the dmesg command: [13290.003398] x1ioptriple: Allocated daq shmem; set at 0xffffc9001a10d000 [13290.003399] x1ioptriple: configured to use 5 cards [13290.003400] x1ioptriple: Initializing PCI Modules [13290.003408] x1ioptriple: ADC card on bus a; device 4 prim a [13290.003409] x1ioptriple: adc card on bus a; device 4 prim a [13290.003415] x1ioptriple: pci0 = 0xffffffff [13290.003423] resource map sanity check conflict: 0xffffffff 0x1000001fe 0xffc00000 0xffffffff reserved [13290.003426] ------------[ cut here ]------------ [13290.003431] WARNING: at arch/x86/mm/ioremap.c:98 __ioremap_caller+0xd5/0x301() [13290.003432] Hardware name: X8DTU [13290.003433] Info: mapping multiple BARs. Your kernel is fine. [13290.003434] Modules linked in: x1ioptriplefe(+) mbuf [last unloaded: x1ioptriplefe] [13290.003437] Pid: 5760, comm: insmod Not tainted 2.6.34.1 #7 [13290.003438] Call Trace: [13290.003442] [] warn_slowpath_common+0x77/0x8f [13290.003444] [ ] warn_slowpath_fmt+0x3c/0x3e [13290.003446] [ ] __ioremap_caller+0xd5/0x301 [13290.003449] [ ] ? T.484+0x13/0x15 [13290.003451] [ ] ? pci_bus_read_config_dword+0x66/0x74 [13290.003452] [ ] ioremap_nocache+0x12/0x14 [13290.003457] [ ] mapAdc+0x65/0x251 [x1ioptriplefe] [13290.003461] [ ] mapPciModules+0x6c1/0x824 [x1ioptriplefe] [13290.003465] [ ] init_module+0x242/0x97d [x1ioptriplefe] [13290.003468] [ ] ? init_module+0x0/0x97d [x1ioptriplefe] [13290.003471] [ ] do_one_initcall+0x59/0x149 [13290.003475] [ ] sys_init_module+0xd1/0x231 [13290.003477] [ ] system_call_fastpath+0x16/0x1b [13290.003478] ---[ end trace 31c35fdb3a0a9ba9 ]--- [13290.003481] ioremap reserve_memtype failed -22 [13290.003483] x1ioptriple: pci2 = 0xffffffff [13290.003485] resource map sanity check conflict: 0xffffffff 0x1000001fe 0xffc00000 0xffffffff reserved [13290.003487] ioremap reserve_memtype failed -22 [13290.003488] x1ioptriple: ADC I/O address=0xffffffff 0x0 [13290.003491] BUG: unable to handle kernel NULL pointer dereference at (null) [13290.003919] IP: [ ] mapAdc+0xd8/0x251 [x1ioptriplefe] [13290.004137] PGD 1b7cbc067 PUD 1b7c84067 PMD 0 [13290.004352] Oops: 0000 [#1] SMP [13290.004562] last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:27:01.0/class [13290.004974] CPU 2 [13290.004979] Modules linked in: x1ioptriplefe(+) mbuf [last unloaded: x1ioptriplefe] [13290.005596] [13290.005801] Pid: 5760, comm: insmod Tainted: G W 2.6.34.1 #7 X8DTU/X8DTU [13290.006215] RIP: 0010:[ ] [ ] mapAdc+0xd8/0x251 [x1ioptriplefe] [13290.006637] RSP: 0018:ffff8801b7d49dc8 EFLAGS: 00010292 [13290.006846] RAX: 000000000000003f RBX: 0000000000000000 RCX: 000000000000003f [13290.007059] RDX: 0000000000020cc5 RSI: ffffffff8179c135 RDI: 000000000000000a [13290.007272] RBP: ffff8801b7d49df8 R08: 000000007ffffff2 R09: 000000000000000a [13290.007487] R10: 0000000000000006 R11: 00000000ffffffff R12: ffffffffa000f130 [13290.007701] R13: ffff8801be8ad800 R14: 0000000000000000 R15: 0000000000000000 [13290.007914] FS: 00007f957e7836f0(0000) GS:ffff880001e40000(0000) knlGS:0000000000000000 [13290.008326] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [13290.008537] CR2: 0000000000000000 CR3: 00000001a165d000 CR4: 00000000000006e0 [13290.008746] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [13290.008955] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [13290.009165] Process insmod (pid: 5760, threadinfo ffff8801b7d48000, task ffff8801bdd0f200) [13290.009571] Stack: [13290.009771] 0000000000000000 ffffffffa000f130 0000000000000001 0000000000000000 [13290.009985] <0> 0000000000000000 0000000000000000 ffff8801b7d49e48 ffffffffa00087b7 [13290.010401] <0> ffff8801b7d49e18 00000000b7d49e58 ffff8801b7d49e48 ffff8801b7d49e58 [13290.011023] Call Trace: [13290.011231] [ ] mapPciModules+0x6c1/0x824 [x1ioptriplefe] [13290.011445] [ ] init_module+0x242/0x97d [x1ioptriplefe] [13290.011659] [ ] ? init_module+0x0/0x97d [x1ioptriplefe] [13290.011872] [ ] do_one_initcall+0x59/0x149 [13290.012081] [ ] sys_init_module+0xd1/0x231 [13290.012291] [ ] system_call_fastpath+0x16/0x1b [13290.012501] Code: 00 02 00 00 e8 0c cc 01 e1 8b 35 91 e8 49 00 48 89 c2 49 89 c6 48 c7 c7 fc d3 00 a0 31 c0 e8 a9 57 00 00 4e 89 34 fd 20 5e 01 a0 <41> 8b 36 48 c7 c7 19 d4 00 a0 31 c0 e8 90 57 00 00 4a 8b 14 fd [13290.013247] RIP [ ] mapAdc+0xd8/0x251 [x1ioptriplefe] [13290.013468] RSP [13290.018602] CR2: 0000000000000000 [13290.019122] ---[ end trace 31c35fdb3a0a9baa ]--- The only way to recover is to power the computer off, then power the I/O Chassis off at the power supply, wait, then power up the I/O Chassis, then the computer. The IOP model can be started normally at that point, followed by the user model. So far, the system has died three times since Wednesday July 18.
[Bram, Alberto]
Both the ALS REFL PD and the TMS green QPDs are showing larger counts than before the weekend. It looks like the trend started sometime between Friday and Saturday night.
See attached plots. The REFL PD is set with a negative gain so that it reads 0 when the arm was unlocked, and it beceomes postive when the arm is locked.
Now we read around -4000 cts when the arm is unlocked.
Also the green QPD segments, both A and B read around 2200 cts, vs about 2000 as they did before.
We're not yet sure if this means that there's actually more physical power in the beam going. If that was the case, then it would be quite strange.
Could it be a DAQ artefact?
This maybe have to do someting with the PLL being out of lock, with the intergrator railing both the temp and the PZT feedback. Although I don't know the mechanism, but it may seem that there is more green being generated???
After we disabled the PLL servo and cleared the integrator (in Beckhoff), the pwoer seemed to be fine. When we engaged the temp controller (slow servo and integrator in the Beckhoff), after a little while (2-5 min), the power on the green REFL_PD_DC seemded to 'increase'.
We haven't measured the power levels in the end-station, as we had bigger fish to fry... see a later post.
The H2 ETMY optical lever is fully installed with the beam reflecting off the front surface of the optic, picture of the beam is attached to show beam size. Calibration data has been taken and being processed, the linear response curve needs to be implemented in the C-code written by Jeff Kissel. The hysteresis within the gears of the translation stage on the receiver side could be a factor in the accuracy of the calibration.
This alog gives a quick status of the seismic systems (HEPIs and ISIs) used for the single arm test (BSC6 and BSC8).
BSC-ISI:
ISI-BSC8 has been running with damping loops and Isolation loops since the end of May with decent isolation performance. https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=2976
ISI-BSC6 commissioning started more recently. An overall amplification of the motion was immediately noticed around 1Hz (QUAD mode). By the time, writing the commissioning scripts and controlling HEPI was the priority and the no time was spent on ISI-BSC6 to fix the “1Hz” issue.
This week, some modifications were made to the complementary filters that are used to build the blend filters. The initial filters were replaced by less aggressive ones (smaller bump around the blend frequency (750mHz, 250mHz) and less roll off on the low pass. I have attached a link to bode plots of the 4 complementary filters currently used.
LHO_ISI_BSC6_BSC8_OAT_Complementary_Filters_2012_07_20.fig
The blend and isolation filters currently implemented on the two ISIs are designed using the following parameters:
- Blend at 750mHz on all degrees of freedom except on stage 1 in the Y direction where a 250mHz Blend is used instead.
- UGF: 15Hz on all DOFs
- Phase margin > 45deg
- Gain margin>20dB
- Gain peaking <2
The isolation filters used on the two ISIs are pretty closed. Spectra were measured on the ISIs in the undamped and the isolated state. The performances are OK for now. Optimization will be done later.
Stage 2 GS13 spectra are presented below. The scrip that is used to measure the spectra in the different configuration is currently being reworked. The tails of the spectra in the two uncontrolled and the controlled configurations should match better.
BSC-ISI – ITMY (BSC8):
- LHO_ISI_BSC8_ASD_m_CART_ST2_GS13_Undamped_vs_Isolated_2012_07_18_162209.fig
BSC-ISI – ITMY (BSC6):
- LHO_ISI_BSC6_ASD_m_CART_ST2_GS13_Undamped_vs_Isolated_2012_07_19_151614.fig
The HEPI was commissioned fairly quickly to lock stage 0 of the ISI to the ground. Recently, the TMS-QUAD alignment offsets were offloaded on HEPI-BSC6 (250*10^-6 rad in the +RZ direction).
The HEPI are tuned using the following parameters:
- Blend at 800mHz
- UGF: 10Hz
- Phase margin > 45deg
- Gain margin>20dB
- Gain peaking <2
- Pringle modes are controlled (AC)
- No sensor corrections but the STS-2 are in place, connected, leveled and working.
I have attached spectra of the super sensor signals when the HEPI is uncontrolled and controlled.
HEPI – ITMY (BSC8):
- LHO_HPI_BSC8_ASD_m_Super_Sensors_H_Undamped_vs_Isolated_2012_06_20_170452.fig
- LHO_HPI_BSC8_ASD_m_Super_Sensors_V_Undamped_vs_Isolated_2012_06_20_170452.fig
HEPI – ETMY (BSC6):
- LHO_HPI_BSC6_ASD_m_Super_Sensors_H_Undamped_vs_Isolated_2012_07_02_155724.fig
- LHO_HPI_BSC6_ASD_m_Super_Sensors_V_Undamped_vs_Isolated_2012_07_02_155724.fig
Calibration check:
Some measurements were made to check the calibrationand the basis change matrices used on HEPIs and ISIs. Spectra All sensors when no damping on the ISI. Some glitches still need to be fixed (factor of two on HEPI). Couple of glitches still needs to be fixed.
- LHO_ISI_BSC8_ASD_HEPI_BSC_ISI_Undamped_2012_07_18_020214.fig
- LHO_ISI_BSC6_ASD_HEPI_BSC_ISI_Undamped_2012_07_18_020214.fig
During the “1Hz chase” on ISI-BSC6, the reconstruction scripts that are used to build the hundred of filters, required to control the ISI, from a unique set of measurements (ISI undamped) were fully verified for the first time. Excellent agreements between measurements and simulations were seen even on the cross couplings between stages. These scripts allow a huge gain of time during commissioning.
A nice step forward was done during the last few weeks.
[HAM3 In-chamber work from 11:30am-1:15pm]
After staking out ISI Corner3 Cabling work on Thursday, I went about dressing the Corner 3 GS13 pigtail cable, one of the more important to dress since these are the only ISI cables which come from the suspended Stage1 to Stage0 (we have to be careful there are no seismic shorts). So between Stage 1 & 0, the cable must be dressed just right--not too tight, and not too loose. Between Stages, you also have to elimate any sort of rubbing. Basically you have to have a good eye's view and be very precise with clamping these cables.
This is hard for Corner3 on HAM2 & HAM3.
So, in to Chamber and on top of the table I went. To minimize head rushes/passing out, and gettingoverly overheated, I slowly did work in small steps (either upside down, or by keeping head level with torso and reaching down to the breadboard area). I removed all other ISI cables from the tiny breadboard we had. I then dressed the H3 & V3 GS13 cables to their own clamp on Stage0. I did this such that each cable had a nice & clean "S" run between stages. After that I installed the Grounding Bracket (with Extension cable bolted on) on the breadboard. And I finally connected the pigtail cable to the Bracket.
During this work, I managed to drop an allen wrench, and it fell below the ISI and landed directly in the center of the HAM Chamber. Funnily, it wasn't easy to get to the tool! I ended up performing endoscopic surgery and used a clean cable to pull out the tool. Note: this work yielded a "white glove" test in that afterward, my glove ended up getting fairly filthy after rubbing up against the Chamber floor (see attached dirty glove).
So, the GS13 cables are dressed for Corner3 (see attached photos & video).
As for other cables....
For the H3 CPS & Actuator, I'd say we bypass the tiny breadboard, and pull these cables straight down off of Stage0 & then take them to the Center flange (D2). For the V3 CPS & Actuator, I'd also try to avoid the center breadboard (because it's just hard to do work in there) and go straight to the flange.
Check ResourceSpace for views of PR3 coming out of the can and MC2 receiving the optic. Both activities occurred on 7/12/12.
Aligned the cavity using tdsdither @ 19:20.
Left the cavity locked w/o VCO offloading servo to ETMY so we can make a (somewhat) longer term comparison of the ETM angle with (yesterday) and without (tonight) the length drive.
Also QPD servo was disabled so we can see how good or bad the alignment is going to be without active pointing servo.
ETMY L1 damp filters are on (as usual only for L and P).
Attached is a trend of cavity length drift from the yesterday.
The first lock stretch is a 3-hours one that I mentioned in https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=3517. The second lock stretch lasted until this morning.
CH2 is the output of the ETMY M0 lock filter. Using 0.48nm/ct calibration, it seems as if the length drift for both of the stretches was about 110 um. You should be able to stitch these two together, so it is something like 220 um over 16 hours period. This could be tidal.
I don't know if our tidal prediction software still works, wiki page says it doesn't work on Linux workstations.
CH3 and CH4 are the output of ETMY oplev. I think these were calibrated by Thomas, but I couldn't find any alog about that, so for now it is uncalibrated.
CH5 is the reflected power which mimics the transmitted power.
Attached are plots of dust counts > .5 microns in particles per cubic foot.
Found x1tripleteststand had time frozen at Wednesday evening (July 18). Could not get models to run, even after restarting the tripleteststand computer and cycling power with the I/O chassis power switch. Appeared the DAC and ADC cards could not be found. Ended up turning off power to computer, then turning off power supply to I/O chassis, then powering back up in order. Started IOP model, then user model, both started properly. Given the timing, possibly a lightning induced power glitch?
GregG, JimW The HAM2 ISI is now floating on HEPI. Well, not now, 'cause we lightly re-engaged earthquake stops, but it is currently mostly supported by the springs. We haven't done a level or height check yet, as I don't know where our references are or what height we need to look for, but we are basically ready to start working with IAS on figuring out where we need to move to. Should be able to hammer that out next week.