Jim, Dave:
Sheila and Jenne made h1asc filter changes over the weekend and we noticed today that the diff file for this system was filled with many copies on a single filter. Investigating further we noted that the problem was with the three filters ASC_CHARD_P, ASC_CHARD_P_A and ASC_CHARD_P_B. Jim noted that these consist of a core name, and filters with additional suffixes, so we suspected a potential string matching issue. In the case of h1asc, the running H1ASC.txt file in the chans/tmp directory had 638 copies of the ASC_CHARD_P filter module, with varying header names.
We were able to reproduce the problem on the DAQ Test Stand. We made changes to the three filters and loaded them individually. When the "core" named filter (ASC_CHARD_P) was loaded many copies of this were created. Further individual loads compound the problem, which is why h1asc ended up with so many copies.
A bug has been opened for this: https://bugzilla.ligo-wa.caltech.edu/bugzilla3/show_bug.cgi?id=1014
We scanned all the H1 filter modules looking for filters which are core names to additional filters. We found 65 cases in the 8900 total number of filters. These filters are distributed over the following systems:
h1alsex
h1alsey
h1asc
h1calex
h1caley
h1iscex
h1iscey
h1lsc
h1oaf
h1odcmaster
h1omc
h1psldbb
h1pslfss
h1psliss
h1pslpmc
h1susetmx
h1susetmy
h1susitmx
h1susitmy
Until this issue is resolved, we recommend that users do not individually load filter modules and instead perform full filter file loads from the GDS_TP MEDM screen.
I gathered some new data points from today and fine tuned the calculator. The requested power and measured power now agree within 1%. A 10-day minute trend of PMC transmitted power shows that the PSL power itself fluctuates on the daily basis which will throw off the calibration slightly. The calculator must be re-tuned based on the maximum PSL power going to the IMC, given that the minimum power angle doesn't change.
J. Kissel, B. Weaver Work Permit: #5880 FRS Ticket: #5489 Integration Issue: #FRS 5506 ECR: E1500045 Betsy and I've installed the individual coil driver switching of HSTS M3 stages as per documentation linked above. The front-end model changes were prepared and described yesterday (see LHO aLOG 27223), though note, we found some bugs and have to recompile again this morning (LHO aLOG 27239), after making the MEDM screen modifications described in the this log. We've made modifications to the following MEDM screens: /opt/rtcds/userapps/release/sus/common/medm/hxts/ M SUS_CUST_HSTS_OVERVIEW.adl <--- made CD STATE and TEST/COIL ENABLE settings and readbacks for each quadrant independent, and linked to new non-generic HSTS screens mentioned below and created new screens: /opt/rtcds/userapps/release/sus/common/medm/hxts/ ? SUS_CUST_HSTS_M3_EUL2OSEM.adl <--- used to be generic with all HXTSs, but now specific to HSTSs ? SUS_CUST_HSTS_BIO.adl <--- used to be generic with all HXTSs, but now specific to HSTSs and screen shots of each are attached. Unfortuanely, because the BIO settings and EUL2OSEM matrix elements are new channels for the M3 stage, one has to, by-hand, re-enter every suspension's - Requested coil driver state - The TEST/COIL ENABLE switch - The M3 EUL2OSEM matrix elements. and then hit "LOAD MATRIX" on all of the M3 EUL2OSEM matrices. We used Betsy's screenshot from last night to do this (from LHO aLOG 27225). We've also made our best attempt at updating the safe and down.snap files which had to have the former, ganged BIO channels replaced with the individual coil BIO channels. This required quite an SDF dance: 1) On SDF SAVE SCREEN for each SUS, - change SAVE TABLE to "EPICS DB TO FILE" in order to update the snap file with the new epics database channel list currently running with the new model - change FILE OPTIONS SELECTION to "OVERWRITE" in order do this with the currently loaded snap file - Hit SAVE FILE (We did this with every safe, down, or observe snap file for a given suspension) 2) On SDF RESTORE SCREEN for each SUS, - SELECT REQUEST FILE that you want to load in with the new updates - LOAD TABLE This should cleared out any of the channels with have disappeared from the model and create a bunch of new channels which are NOT INITitallized. Since keeping track of all of these channels and snap files was a bear, I don't promise that we've gotten everything right. We'll just have to keep an eye on them over the next few weeks to check if we've missed anything. Jenne's working on updating all Guardians that controlled the M3 stages of the HSTSs, and coding up the 3-coil-motion necessary for switching the coil state one at a time like is done on the beam splitter.
[TJ, Jenne]
We have modified the ISC guardians to handle the new coil driver switching capabilities.
In the DOWN state of ISC_DRMI, all of the optics for which we switch coils are switched back to their high range states.
I've re-written what was once the "BS M2 switch fast" script that guardian called, and incorporated it in a more general form in the ISC_library. The COIL_DRIVERS state now calls this function from the ISC library for each of the optics that need switching. I've tested it in the guardian shell for PRM, and the script behaved as expected (same recipe as has always been used for BS before), so it should all work nicely.
It's possible that we will find (by running them in parallel in guardian shells, for example) that we can do the coil switching on all of the optics in parallel while maintaining lock. If this is so, we may need to push the coil switching into the suspensions' guardians. But, for now, we leave this as "future work".
Thankfully I had forgotten to hit "load" for the ISC_LOCK guardian, because once we started the COIL_DRIVERS state, I realized that I had made poor choices for the matrix elements that get turned off before we switch the analog state for a coil.
What now happens (and I had forgotten to incorporate in the new HSTS coil driver switching) is that when one coil gets zeroed in the eul2osem matrix, a matching set of coils must be zeroed in each column of the matrix. For example, if I am zeroing LL, then in the length degree of freedom, I need to also zero UR, and have the LR and UL matrix elements twice as large as normal. This keeps the optic balanced, with the actuation strength roughly the same. For pitch, I need to zero UL, so that pitch control is only using LR and UR (with 2x larger matrix values) for the duration that LL is off. For yaw, I need to zero LR. Anyhow, this has now been fixed, and the fixed version of the code successfully ran for the PRM. Recall that PRM was often the lockloss culprit, so it was commented out of the previous version of the guardian.
So, I believe that with this one lock data point, we can say that the new coil driver switching ability has been a success.
Below are RPN and Modescan scans for both LO and HI power.
Awesome, thanks Ed.
It should be noted that the mode scan measurement is not final; we still have alignment and mode matching work to do (as evidenced by the scans). I asked Ed to do these so we have a record of where we are now (still can't lock the DBB PMC due to alignment/mode matching issues, so no frequency or pointing noise measurements just yet).
Interesting to note is that the non-stabilized (no ISS) RIN of the HPO is not too much higher than the original reference (by eye <= a factor of 2 across the measurement range), and still well below the laser requirements.
David.M, Jenne.D, Richard.M
We tested some of the electronics for the L4C geophones which are soon to be installed as an array. These were three L4C Concentrator Chassis (D1600144, labelled '1', '2', and '3' on front) and two L4C Interface Chassis (D1600148, labelled '1' and D1600152, labelled '2').
These are all working correctly. The only alteration made was to swap the 9 pin plugs for 'L4C 6' and 'L4C 7' on the board of Interface Chassis D1600148 (currently labelled as Interface Chassis '1' on front), since they were the wrong way around.
I've attached a pdf with the pin layout for each chassis for reference:
Here are the trends from the past 12 days. The past couple of weeks have been agitated by a number of chiller trips and ongoing work.
Jenne, Sheila, Evan, Kiwamu
Today we aimed to have a long stable lock at 30 Watts. We did have one lock of more than half an hour at 30 Watts, which we lost due to commisioner error.
Also, the ISS 1st loop is oscillating pretty much every time we loose lock and needs to be fixed by hand. we are leaving IFO undisturbed at 23 Watts 7:50 UTC
[Jenne, Abdul, Lindsey (high school visitors)]
We used the picomotors on TMS Y to center the beams on the transmon QPDs. TRY_B looks much better now - no more factor of 40 between the amount of light on each segment. TRY_A still has an odd "butterfly" pattern, where the diagonal elements match, but the 2 diagonals are different from eachother by a factor of 2.
We reset the SOFT offsets with this new pointing, and successfully closed the SOFT loops. We may consider doing the same for TRX, but it's not nearly as necessary there. The Xarm picoing has been done, SOFT offsets reset with the new pointing to the diodes, and SOFT loops closed.
Now we're ready to move around a bit to see if we can minimize dP/dTheta.
I have put the CHARD blending back in, since the picomotor moving is finished.
Activity Log: All Times in UTC (PT) 23:00 (16:00) Start of shift 00:08 (17:08) Dave – Rebooting h1fw0, and nds0 due to h1fw0 instability, (See aLOG #27232) End of Shift Summary: Title: 05/16/2016, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT) Support: Jenne, Sheila, Evan Incoming Operator: N/A Shift Detail Summary: IFO has been locked and unlocked at various stages during the evening shift while the commissioning team is working on improvements and updates.
Sheila, Jenne, Evan
We have suspected for some time that the POPAIR B diode (which we use to extract POPAIR18 and POPAIR90 signals) is saturated in full lock, because these signals do not scale appropriately when increasing the PSL power. Now that we are seriously trying to use POPAIR90 to diagnose DRMI angular behavior during power up, we would instead like to use a signal that we can trust.
We tried a few different things today:
The last of these is the configuration that we have now. Whitening and dark offsets were set to give appropriate signal levels.
Careful examination will actually show that there appears to be a bit of saturation with this POPAIR45 signal as the power is increased. According to the POPAIR_A_LF channel, there is 83 mW (!) of dc power on this PD at 25 W. Probably we should be closing the POP beam diverter at this power, or else we need to swap some optics on the table.
Ideas for how to improve:
BBPD modifications are detailed in G1500595 by Koji. Page 5 shows the redlined drawing. Parts are available.
Unmodified BBPD S1200236 (which was POPAIR B) has been replaced with modified BBPD S1200239.
POP90 and POP18 are now supplied by this new diode.
After this afernoon's DAQ restart h1fw0 became very unstable. In the past rebooting the Solaris QFS writer has helped. We power cycled h1ldasgw0 at 17:14. We quickly got h1fw0 and h1nds0 processes restarted after the NFS server was available. Too early at the moment to see if the problem is fixed.
Transition Summary: Title: 05/16/2016, Evening Shift 23:00 – 07:00 (16:00 – 00:00) All times in UTC (PT) State of H1: IFO locked at ENGAGE_ISS_2ND_LOOP. Commissioners are working IFO. Commissioning: Working on improving IFO locking and stability. Outgoing Operator: Ed Activity Log: All Times in UTC (PT) 23:00 (16:00) Start of shift
Morning locking thwarted by a variety of issues:
15:00 EY 300NM Dust alarm sounding
15:27 Set Observatory Mode to Commissioning - IFO down haven't started aligning yet. Seemed to be the only viable option.
15:30 Monday meeting
16:07 John called about chiller issue at EY. He and Bubba are going to investigate.
16:27 Chandra out to investigate a RED condition on a diagonal annulus pump.
16:45 Peter and Jason into Ooptics lab
16:50 Karen and Chriatina to EX to put out mousetraps
17:30 Cheryl into optics lab
18:46 Dave and Jim re-starting the gateway between Guardian and Beckhoff in an attempt to resolve mysterious connection errors in the X-Arm.
19:01 turned of gateway and restarted guardian machine.
19:22 Dave will power cycle the guardian macine
19:44 Cheryl out of the optics lab
20:04 Patrick restarted the H1ECATX1 IOC and this seems to have resolved the guardian woes of the day.
20:50 Gamma Ray Burst - IFO in higher stages of lock acquisition.
21:03 Ken to MY to do some wiring
21:30 Bubba out to repair instrument air at EY chiller yard
22:03 Ken back
22:11 DAQ restart
22:30 Bubba back from EY chiller yard
J. Kissel, B. Weaver Work Permit: #5880 FRS Ticket: #5489 Integration Issue: #FRS 5506 ECR: E1500045 As a band-aid solution to the ganged-coil-driver-state-switching-lock-losses-during-acquisition, recently identified to be PRM (see LHO aLOG 27158), we're going to modify the M3 stage of the HSTS's library part to have individual control over coil switching similar to what was done with the M2 stage of the Beam Splitter some time ago (see E1500045). Because of the breakdown of suspension-type library parts, we must changes to /opt/rtcds/userapps/release/sus/common/models/ HSTS_MASTER.mdl MC_MASTER.mdl and instead of copying the un-library-parted BSFM_MASTER M2 COILOUTF bank, we created a new library part to be copied into the HSTS_ and MC_MASTER_M3 stages, called /opt/rtcds/userapps/release/sus/common/models/FOUROSEM_COILOUTF_MASTER_INDIVIDUAL_CTRL.mdl We've confirmed that these updated models compile, and they've been committed to the userapps repo. We'll work on MEDM screens tomorrow morning, once we've compiled the updated models and we have new channels. There will be some settings (namely the coil driver state settings) that will be lost from the channel name switch, so we'll make sure to replace those in the SDF system accordingly. We'll also make our best attempt EVER at preserving the alignment of these SUS after the restart.
Here are some screen captures of the HSTS BIO and EULER2OSEM matricies which we will be incorporated into new MEDM screens tomorrow.
J. Kissel, B. Weaver, [J. Betzwiser remotely] As usual, we were only able to find bugs in the above SUS model changes for individual coil driver state switching after we'd finished making the MEDM screen modifications. After checking the coil driver compensation functionality after the model changes, we were immediately reminded that the STATE MACHINE logic for those HSTSs stages which have modified TACQ drivers is different from those stages without modification. The beam splitter M2 stage -- which we'd used as an example for the new infrastructure -- which uses an unmodified TACQ driver, where as the recycling-cavity HSTS's (PRM PR2 SRM and SR2 -- at H1 at least) have both their M2 and M3 TACQ drivers modified for extra actuation range. Once we reminded ourselves which suspensions had which drivers modified, we found it best to create a new library part in the /opt/rtcds/userapps/release/sus/common/models/STATE_BIO_MASTER.mdl library capable of individual coil state switching library that uses the correct compensation switching code for the modified driver. It's obscure, but it's as simple as copying over the existing INDIVIDUAL_CTRL block, then changing inline TACQ $SUS_SRC/CD_STATE_MACHINE.c to inline TACQ_M2 $SUS_SRC/CD_STATE_MACHINE.c in each of the cdsFunctionCall block. I've attached screenshots of the updated STATE_BIO_MASTER library and the innards of the parts inside. Note that I've - changed the names of the library blocks associated with the TACQ drivers at the top level to better differentiate between the differences. - made the inline function call visible under the cdsFunctionCall block (right-click > Properties ... > Block Annotation tab > double click on "Description" block property token to add to the list of things for annotation > hit OK) so that the difference in the code call is obvious without digging into the properties. These new library blocks (and the renamed existing blocks for the unmodified driver) were hooked up to the HSTS master models according to their arrangement of TACQ driver modifications: [For H1 ONLY see E1400369 and E1200931] HSTS_MASTER MC1, MC3 No TACQ Driver Mods MC_MASTER MC2 M2 stage driver modified RC_MASTER PRM, PR2, SRM, SR2 Both M2 and M3 stages modified Also, for convenience, remember you can find details of the modification in L1200226, but in summary, the modified driver is a factor of 10 stronger than an unmodified driver (and there's no longer frequency response in the output impedance network, which is why the digital compensation has to change). Also, also, the state machine diagrams that outline how the digital compensation works with the analog driver state can be found in T1100507 These updated models have been committed to the sus/common/models/ directory of the userapps repo, so one needs not do anything different than the above update instructions to receive the bug fix. Since the distinction between whether no, one, or two of an HSTS's TACQ drivers are modified is made at the top-level of the model, i.e. by which of the HSTS_, MC_, or RC_MASTER blocks are used, there shouldn't be a need to change any top-level stuff at LLO to receive this model update. Just update that sus/common/model/ corner of the repo, and recompile, re-install, and re-start.
Tega, Ross, Jim, Dave:
We installed new code for the models h1susitmpi, h1susetmxpi and h1susetmypi. The new code required a DAQ restart, which TEAM-PI obtained permission from TEAM-COMMISSIONING for this afternoon.
The purpose for the change was to make the code more efficient and claw back some CPU time on the h1susitmpi model which was running long (15-16uS for a 64k model). This was successful, it is now running in the 9-10uS range. ETMX is unchanged at 7uS, there is hint that ETMY is running one micro-second longer from 3uS to 4uS.
Tega, Ross, Jim and Dave. Detailed changes made to the PI models. PI_MASTER: 1. Added OMC_PI_MODE library part. 2. Replicate the functionality of the "SUS_PI_DAMP" block in "SUS_PI_COMPUTE" and "ETM_DRIVER". 3. Removed the down-conversion blocks from SUS_PI_DAMP to avoid unnecessary computation in the h1susitmpi model. 4. Renamed OMC_PI as OMC_PI_DOWNCONV to better reflect functionality. 5. Rearranged the library parts so that Simulink blocks related to the OMC_DCPD are on the right whilst blocks that process the QPD data are on the left. h1susetmxpi: 1. Replace the ETMX_PI_DAMP block with the new library parts: SUS_PI_COMPUTE (block name: ETMX_PI_DAMP) and ETM_DRIVER (block name: ETMX_PI_ESD_DRIVER). 2. Moved the down-conversion blocks out of ETMX_PI_DAMP into a single block at the top of the model. 3. Added OMC_DCPD data into the PI control path using a switch that takes either the processed signals from the QPDs (ETMX_PI_DAMP) or the processed signals from the OMC_DCPDs(ETMX_PI_OMC_DAMP)". h1susetmypi: 1. Replace the ETMX_PI_DAMP block with the new library parts: SUS_PI_COMPUTE (block name: ETMY_PI_DAMP) and ETM_DRIVER (block name: ETMY_PI_ESD_DRIVER). 2. Moved the down-conversion blocks out of ETMY_PI_DAMP into a single block at the top of the model. 3. Changes needed to process OMC data are on hold for now. h1susitmpi: 1. Updated the links for ITMX_PI_DAMP and ITMY_PI_DAMP blocks to the new library part: SUS_PI_COMPUTE. The attached images show the before & after snapshots for each model.
Slightly more details:
A little further investigation shows that the power deviation during the second set of measurements started at 58th measurement where 19 W jumped to nearly 20 W and 54 W jumped to 56 W (first attachment). This jump did not correspond to the measured angles which stayed consistant throughout the measurement (second attachment). Third attachment shows the histogram of power of the first set of measurement (going back and forth between 0W and 3W) that didn't appear to have any power jump.
Kiwamu, Darkhan,
We updated the ETMY L1 stage (UIM) compensation filters FM2, FM3, FM4, FM7, FM8, FM9 of ETMY_L1_ESDOUTF_{UL,LL,UR,LR} with zeros and poles more accurately fitted to the most recent measurements by Jeff K. from ER8 (LHO alogs 20846, 21283). We have not updated the acquisition circuit zero-pole pair, because the measurements do not include the response of this circuit (for details see LHO alog 21142).
We've also updated the ETMY L2 stage (PUM) compenstation filters FM1, FM2, FM3, FM6, FM7, FM8 of ETMY_L2_ESDOUTF_{UL,LL,UR,LR} to their fitted values (LHO alogs 20846, 21232).
Python scritps were used to load new vailes into the Foton file, the scripts are based on Kiwamu's script for updating filter in the L3 stage (ESD) (LHO alog 27150). The scripts are committed to CalSVN at
Runs/PreER9/H1/Scripts/SUS/setH1SUSETMY_UIMDriver_compensations.py
Runs/PreER9/H1/Scripts/SUS/setH1SUSETMY_PUMDriver_compensations.py
Notes for CAL FOLKS:
J. Kissel, K. Izumi, D. Barker Dave noticed that these changes to the foton filter file never were pushed to the H1SUSETMY front-end with a LOAD COEFFICIENTS, so we 've loaded them just now. While at it, we've made the necessary update to the CAL-CS actuation compensation, which involved simply turning OFF (and subsequently deleting to avoid future confusion) FM6 of the H1:CAL-CS_DARM_ANALOG_ETMY_L2 and H1:CAL-CS_DARM_ANALOG_ETMY_L3 filter banks called "mis_coil" that were originally installed before O1 (see LHO aLOG 21275).
FRS 5510 (services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=5510) has been generated for this issue.