Due to oscialltions in the X arm IR loop that were causing difficulties in inital alingment, (22443), we made a small change to the Xarm locking filters today (WP#5558).  

There was a pole at 100 Hz that did not make much sense, we moved it to a kHz now, which gives us an extra 40 degrees at the ugf of 100 Hz.  Before and after rms and transfer function screenshots are attached.  This should solve the egregious problem with the 1206 Hz instability, but there are still problems with the loop, which due to the distribution filters in MC2.  These distribution filters are used in MCL, ALS COMM and CARM loops, so we will not try to fix these today.  

First, note that the rms of M2 and M3 are both dominated by things below 0.5 Hz, meaning that we need a boost in the top stage.  We could probably skip M2 altogether as we have done with the recycling mirrors.  Also, Evan and Jeff note that the loop is rather flat around 100 Hz, which is because of a 41z:150p in MC2 M3.    

[Jeff K, Duncan M]

ODC EPICS changes

With Jeff's assistance (and that of the on-duty operator) I have remotely updated the EPICS configuration for ODC to commission the state monitoring for the new PINJX infrastructure [alog 22445 22465 22470 22473].

Changes were made to EPICS records in the h1calex, h1iscex, and h1odcmaster models as follows

• h1calex: installed the configuration for the new CAL-PINJX_ODC system, basically a copy of the settings for CAL-INJ_ODC (calcs) with slightly different filter state references
• h1iscex: added the CAL-PINJX_ODC readbacks of the transient injection signal states (bits 10-13) to the ODC-X matrix for collection by ODC-MASTER
• h1odcmaster: added the injection bits from ODC-X to the ODC-MASTER matrix for bits (23-26) of ODC-MASTER

These changes have been monitored and accepted in SDF for the relevant models and can serve as a reference for L1 when the same changes are made next week.

ODC MEDM changes

Associated changes were made to the ODC MEDM screens in order to show the CAL_X ODC input. This required separating the SYS_CUST_ODC_MASTER_END.adl screen into separate screens for MASTER_X and MASTER_Y (no CAL_Y ODC). These changes were committed to userapps as r11886.

Added H1:SUS-SR3_M2_TEST_P_OFFSET to the exclude list and rescanned.

Added 70 channel names. Removed 11 channel names. All except H1:SUS-SR3_M2_TEST_P_OFFSET were H1:CAL channels.

Josh reported H1:PEM-EY_ACC_BSC10_ETMY_Z as glitchy in an email Oct 5. Today during maintenance I went down to EY and replaced the accelerometer and also put it through a different channel (channel 1) on the endevco (accelerometer power supply / signal conditioning box), pictures attached. The cable going into the sensor itself was slightly loose before I changed anything.

Looking back at the history of this channel (also attached), it looks like this accelerometer went down at ~17UTC on Sep 8 and started working again on Sep 14 ~19UTC for unknown reasons (possibly loose cable).  I don't know whether the glitchyness reported by Josh continued after the 14th, when the timeseries returned to expected values. In any case, there is a new sensor there now and spectra/timeseries both look good.

Also, I had noticed that H1:PEM-EY_ACC_BSC10_ETMY_X had been unplugged at the electronic racks, so I plugged it back in (looks like its been unplugged since last tuesday).

J. Kissel
ECR E1500386
WP 5553
II 1126

I've copied over the PCAL Inverse Actuation filter, as recently updated by Sudarshan (see LHO aLOG 22185). For the record, the foton design string is

zpk([0.01;0.01],[1215.5+i*6893.7;1215.5-i*6893.7;7000],3.4514e+12,"n")*gain(3994.47)

The filters have been turned ON as shown.

I've accepted the filter states in the SDF system. In the process, I've also made sure that the "CHANS NOT MONITORED" list is the same between CAL-CS and CAL-EX. In summary, they're the EPICs "readback" channels that get filled in with TINJ and the EXTERNAL ALERT system, and the ODC string records that tell what each ODC bit means (see attached screenshot).

Over the last few days, we've been trying out the new 45 mHz blend filters for the BSC ISIs, which are designed to help out during times of high microseism. 

This aLog is just meant to be a collection of logs relating to the switching, to help Team DetChar know which state things were in at which times, so they can hopefully make a comparison.  One of the things that might be most interesting is the effect on the artifacts that Josh pointed out in aLog 22405.

Some of the logs that have talked about the switching back and forth include aLog 22440 and aLog 22459.

Looking at the SWSTAT of the ISI-[chamber]_ST1_BLND_[x or y]_CPS_CUR_SWSTAT channels I can see when the blends were in each state.  FM7 is the nominal 90mHz blends (SWSTAT = 40000), and FM9 is the new 45mHz blend (SWSTAT = 40192).  Below is a table of the lock stretches in each state.

Re WP 5527 & alog 22305, I've returned the cabling to its nominal connections.

nm

I've rearranged the PRMI branch in the DRMI guardian, and added states to the ISC_LOCK guardian to request both these states and the ALIGN_IFO states used for PRMI  (finshing unfinished item from WP5533).  This is for use when you think that the DRMI alignment is bad (based on the AS camera and the flashes as seen in dataviewer)  and will not lock.  If DRMI is slow to lock but has been locked recently and looks well aligned on the AS camera, this procedure is probably not your best bet.

We will test this durring maintence recovery today, but the instructions replacing those in 21745 will be:

• From ISC_LOCK, request LOCK_PRMI.  
• Once it locks, align BS and PRM by hand until you are satisfied with the alingment (POP18_I_NORM_MON around 50 counts and POP90_I_NORM_MON around 80 counts, fairly stable)
• Request DRMI_LOCKED.  The guardian will realign SRM, attempt to make the transition without unlocking DRMI, and go back to LOCK_DRMI_1F if it fails. 

done!

J. Kissel

The former, old (I think it was installed during the H1 mini-run), redundant Inverse Actuation filter that had been installed in the CAL-INJ_TRANSIENT filter bank in FM1 and FM10 (but never turned ON). To avoid confusion, I've simply deleted these filters. The updated filter file,
has been committed to the userapps repo.