Jim and Dave

We compiled all the front end models against 2.8.3 except for the three models mentioned previously.

I installed all the models using the install-World option and a modified local rtsystab to skip aforementioned models.

I then did a DAQ restart to see if any INI files were modified which we were not expecting, and we were surprised by h1odcmaster and h1susetmy which have modified INI files. h1lsc was modified by this was expected due to Jamie's new model.

We then logged into each front end and restarted the models. Since IOP models were being restarted the sequence was

stop all user models

restart the iop model

start all the user models

As usual we had to press the BURT button on many models before they timed out.

GOTCHA. the bug which doesn't allow the h1odcmaster to be restarted without crashing the h1oaf0 computer was tested and is still there! Jim was able to take this node out of the dolphin fabric so we didnt have to re-restart anything.

PSL was the first to be restarted. I burt restored to 09:00 today and opened the shutter from the MEDM screen. All looks good.

I then viewed the safe.log files for each model to see which ones reported many connection errors. For those with more then a few dozen I manually burtrestored the following to 09:00 this morning;

hpiham[4,5,6]  isiham[2,3,5,6] sustmsy, suspr3, susim, susitmy, lsc

I tried burt restoring h1susetmy but it had errors due to a model change.

This is from last week.

We briefly measured the distance between optics and such, and used nanoscan to measure beam width/profile at various places though they were very very ugly.

See attached scribbling for layout (all dimensions in inches). Mirror names are arbitrary.

Measurement points are indicated by alphabet from A to I. Measurement points with prime (G'-I') means that the first lens in WFSB path (LWFSB1) was removed during the measurement.

The rest of the attachements are the nanoscan result. WFSB1.jpg-WFSB4.jpg=measurement point A-D. WFSA1.jpg and WFSA2.jpg=measurement point E and F. WFSC1.jpg-WFSC3.jpg=measurement point G', H' and I'.

I started conlog again after the shutdown for the ntp time server install. I set it to use a new channel list with additional daq and filter module channels provided by Dave B.

The channels scanned from the autoBurt.req files are in full.txt (98,328 channels)
The additional daq and filter channels are in include.txt (24,076 channels)
A set of noisy channels to exclude are in exclude.txt (37 channels)
The set of currently used channels are in full_plus_include_minus_exclude.txt (122,376 channels)

Alexa S., Patrick T.

We added the newly installed relay to the h1ecatx1 system manager and committed the change to svn. We used Daniel's GUI to restart everything and did a burtrestore to 9 am this morning.

Jim B., Patrick T.

The conlog program was stopped.
ntp was installed on h1conlog and set to read from h1boot.
The ntp service was stopped.
A step time update was done:
25 Feb 10:19:09 ntpdate[10216]: step time server 10.101.0.10 offset -105.644733 sec
The ntp service was started.

We are compiling and installing all models using RCG2.8.3. The following models will not be upgraded:

h1iopseib1 - compile error we are currently investigating (see below)

h1susitmy - testing Hardware Watchdogs and is built against trunk to include the HWWD part

h1iscey - wont compiile

To further investigate the h1iopseib1 error, I emptied the H1.ipc file and compiled the h1iopsusb123 model (the sender). I then tried h1iopseib1 and it again failed. So it does not look related the the IPC file shuffle yesterday and I restored the IPC file.

I am editing the cds/h1/rtsystab file to customize the "make World" model list.

When all software is in place, we will restart all the models (in about an hour)

We thought it prudent to have a spare PUM in-hand for the upcoming monolithic builds, so yesterday we started bonding ears to the PUM ITM03.  Gerardo sucessfully placed an ear on the S4 surface with an error of under 0.01mm misplacement (0.1mm is the tolerance, so well done Gerardo!).  On to the S3 ear...

We have been investigating the saturations of the BSC-ISI occurring during the locking process of MICH. Kiwamu has set MICH in a state that triggers and drives the BS but don't lock, so I can investigate the effect of the triggers and transients. 

Some observations and preliminary results:

- The beam Splitter M2 longitudinal drive saturates the ISI Stage 2 actuators as soon as the locking filter triggers and the OSEM start driving the SUS mass. An example is shown in first page. The yellow line in the top left corner shows the OSEM drive. The purple line in the top right corner shows the ISI DAC saturation. 

- It also saturated the GS13s, though the actuators always trigger the watch dogs trip. I turned the GS13 analog electronics in low gain mode. It reduces the GS13 signal to a few thousands counts (Red line, bottom right figure in the first page)

- This is happening even with Level 1 controller that has less loop gain at high frequency than level 2 or 3. An example is shown in first page of the document attached: Orange lines is for the compensator, Dark blue lines is for the Open loop, Dash lines show the boost (low frequency integrator). Turning off the boost doesn't change anything (it's really a high frequency problem, but I wanted to double check)

- After disabling the locking filter, I took transfer functions from OSEM actuator to ISI actuator output signal (SUS DAQ to ISI DAQ). It is shown by the black line in page 3. The ratio is near or above unity at many frequencies, meaning 1 count on the SUS DAQ output produces roughly 1 count at the ISI DAQ output. The SUS drive spectra is pretty white. The SUS DAQ is 18 bits, the ISI is 16 bits. Those three factors combined lead to the saturation of the ISI DAC.

- I added significant filtering in all six dofs of Stage 2 ISI loops to reduce the ISI controls reaction. The new SUS DAC to ISI DAC transfer function is shown in page 3.

- With this controller, the ISI remains on much longer while the BS OSEMs attempt to lock, but it eventually saturates (see p. 4 just before it trips). In the five tests I did, the ISI stayed on 40 seconds minimum, and about 2.5 mn max (versus tripping on the first rising edge with the standard level 1 controller). We'll do more analysis and full lock tests tomorrow.

There is a large wandering peak in the IMC error signal.  (measured at Imon).  A movie is attached.  We tried several things to try to pin down where this comes from.  This wandering peak also shows up in the end station PLL and goes away when the IMC is unlocked.  

This afternoon I checked out some signals from the PSL to see if there were any similar wandering peaks in them and didn't see anything.  I looked on the TTFSS Field box mixr(in2) fastm test2, on the ISS Photodiode A output Photodiode B output. PMC mixer out. Unless there are better signals to look at, I would conclude this isn't from any of the PSL loops, but the IMC itself.  

Alexa and I also tried a few things to see if the wandering peak would go away under different conditions.  It does sometimes go away, but this seems unrelated to the things we tried.  We tried:

• turning off the ISS,
• turning off the slow feedback from the COMM PLL to the IMC VCO,
• turning off the COMM PLL,
• changing the gain on the FSS,
• unlocking the arm cavity,
• misalinging ETMX.  

We saw the wandering peak in each of these situations. We also had a look at Imon with the IMC unlocked, it wasn't clear what we were looking at when the mode cleaner was flashing.  We misalinged MC1 to look at the dark noise, and didn't see any wandering peak there. We also looked at the IMC open loop gain, there are no resonances or notches there, I remeasured several times and got the same result each time. (53kHz ugf 45 deg phase margin).

Alexa noticed that the UGF is higher than it used to be: she measured it in alog 10069 to be 28 kHz. The neither the settings on the MC board nor the transmitted power have changed.  

We have not been able to do the COMM handoff tonight, although the arm cavity and COMM PLL seem to be quite stable.  

We also attempted to measure the COMM PLL spectrum using the single shot green beam, to get a measurement of the laser frequency noise.  the beat note was about 10mV peak to peak (measured with 1MOhm impedance on the scope) which was not enough for us to lock the PLL. 

Fabrice and I did more testing on the HAM4 guardian today.   I've been lacking in posting, so I bit of recap.  Last week we started testing the ISI_HAMX guardian code on the HAM4 ISI:

USERAPPS/isi/common/guardian/ISI_HAM4.py

This links against the isi/common/guardian/isiguardianlib that Charles Celerier wrote.  A graph of the full system is included below.

The code has been behaving very well, but there have been a few discrepancies between the code and the desired mechanical behavior that we're ironing out.  As of today we were able to cycle through all the states without tripping the watchdogs.  Ultimately a couple of tweaks to the deisolation process did the trick.

It seemed that the shutting off of the ISO Boost_F filters was causing the isolation loops to saturate.  We fixed this by adding a 5 second ramp to all ISO Boost_* filters for all degrees of freedom.  Similarly, the ramp down of the isolation gains, which happens right after the boosts are shut off, was also happening too quickly.  This was particularly true when the platform location was far from the equilibrium position.  After a bit of trial and error we were able to survive the full deisolation process with 150um/urad offsets with a 20 second gain ramp to zero.  Preferably we'll come up with a more systematic way to set these ramp times down the line, but these should do for the moment.

Some additional comments:

The cart bias offsets are set right before reaching full isolation. However, the guardian reaches its fully isolated state (*_ISOLATED) before the platform location has reached it's final position.  I suggest the global guardian behavior would be more robust if the guardian does not transition to the full *_ISOLATED state until the platform reaches the desired location, within some tolerance.  This might be accomplished by tuning the loops to ramp slower to the desired offset and eliminate some of the ringing after the ramp.

We're getting a bunch of guardian notifications about ISO filter states during _RESTORYING_CART_BIAS_OFFSETS states.

Another day of testing and I think we're ready to stand up guardian nodes for HAM2 and HAM3 ISIs.

Fabrice, Hugh and I had a look at the arm cavity signals with sensor correction on and off this afternoon.  The arm cavity locking was not stable because there was no feedback to the top mass, (it turns out the PRMI guardian was reseting the XARM gain to 0).  Anyway, I learned something usefull....

With the sensor correction on, the ETM Stage 2 X drive is in phase with our refl controls signal as well as the slow feedback from the COMM PLL to the IMC VCO, using up about 1/4 of the range of each.  With the sensor correction off (Which Fabrice did by setting H1:ISI-ETMX_ST2_SENSORCOR_X_MATCH_GAIN to 0 from the normal setting of 1.15) this signal is greatly reduced, and we use less of the range of both VCOs.  However, the OPLev sees more pitch motion.  Fabrice says that we can also use a compromise sensor correction that would give less benefit in pitch and also introduce less longitudnal motion. 

Once Daniel and I got the top mass feedback going, the loops are all fine.  Our drive to the top mass clearly introduces pitch motion on the optic, so we need to diagonlaize the drive to the ETM, which Arnaud and Jeff agreed to help us with. 

Right now the arm cavity has been locked for about an hour, I will leave it that way for the night, with the alignment dithers, and top mass feedback on.  The COMM PLL automation is also running overnight. We have low winds (below 50th percentile) and low microseism tonight.

I also started a rudimentary LSC_XARM Guardian just to manage the feedback to the top mass, so we will not shoot ourselves in the foot as much in the future. It's not working yet, but coming soon.

Written by Yuta

Now that the mystery of the PD signal chain and the BS actuation efficiency for Michelson are solved (see alog #10213 and #10127), I corrected what we've found missing/wrong in the noise budget (NB) model.

[Motivation]
We wanted to check the validity of the NB model.


[What are missing/wrong?]
Things that were missing/wrong in the NB model "DRMI_Live.slx" copied from LLO was;

• The calibration for the suspension model was wrong
• Analog/Digital AI filters are not implemented
• Whitening gain values for PDs were missing (e.g. H1:LSC-REFLAIR_A_RF45_WHITEN_GAIN)
• Gains in the PD filter banks were missing (e.g. H1:LSC-REFLAIR_A_RF45_I_GAIN)
• Analog/Digital AA filters were wrong
• Choice of AIR and in-vac PDs were missing
• Optickle gives demodulated signal with the demod gain of 0.5. So, the factor of 2 was missing.
• The PD cable loss was not considered (I'm not sure how to treat with this kind of things in the Full IFO NB model)

[What files do I use?]
The NB model and functions for our Michelson lives in /ligo/svncommon/NbSVN/aligonoisebudget/trunk/MICH/H1. They are based on LLO DRMI NB model but corrected the things mentioned above.
The essential files are

run_NB.m: main script
make_MICH.m: function called from run_NB.m
./Params/paramNbH1MICHtest.m: parameter file
MICH_Live.slx: simulink model

They use the following Optickle files which live in /ligo/svncommon/IscCVS/iscmodeling/LentickleAligo/PRMI/ParamFiles for optical simulation.

optL1DRM.m: constructs Optickle model
probesH1DRM_00.m: puts probes for the Optickle model
paramH1MICH.m: parameter file


[Result]
Attached plot shows the comparison of the OLTF of the MICH loop from the measurement (see alog #10127) and from the NB model. They agree within ~20%. This error mainly comes from the power measurement error.

Note that the Matlab function "linmod" doesn't work correctly when the Optickle block is put in the NB simulink model. Do something like;

[systm,flexTfs] = linFlexTf('MICH_Live');
systm = prescale(systm,{freq(1) freq(end)});
systm = linFlexTfFold(systm,flexTfs);

to plot transfer functions (Thanks to Chris Wipf!).

h1isiham3: Fabrice fixed h1isisham3, there was a new input port not grounded.

h1susitmy: is running a special trunk version with HWWD parts installed, will leave this model out of the upgrade

h1iscey: not spoken with the ISC group on this one yet

h1iopseib1: a real puzzler. the model has not been changed since 14 Nov, it compiled 16 Dec but wont compile on either 2.8.3 or 2.8.2 today. the H1.ipc file was changed, but this model receives the same IPC channel as h1iopseib2,3 and they compile fine. Comparing the models by eye shows no difference. I copied the Rx part from seib2 to seib1 and still b1 fails and b2 compiles. Will need to scratch our heads a little more. Perhaps a regeneration of H1.ipc from scratch is in order.

No issue to report other than missing zippers on the SEI Ceiling Sock.

Clean room back up with the Cartridge ready to go down at lunch.  Torqued to Support Tubes and closed up by 1430pst.

Thanks to Apollo Scott, Mark & Bubba, SUS Travis and SEI Jim.

Corey helped too and took lots of photos.

As we might need feedback loops from the optical lever to stabilize the motion of the test mass of ETMX and ITMX, the simulink models were temporary modified to include a link from the optical lever to the PUM and UIM masses.

This was done by copying over what has been done for the beamsplitter optical lever :

• FOUROSEM_STAGE_MASTER.mdl was modified to include two oplev inputs going through the OLDAMP filter bank (copied from BS). cf FOUROSEM_STAGE_MASTER_before/after.png.
• The new part was copied and renamed : FOUROSEM_STAGE_MASTER_oplevfeedback.mdl
• QUAD_MASTER.mdl was also copied and renamed QUAD_MASTER_oplevfeedback.mdl  and points to the new FOUROSEM_STAGE_MASTER_oplevfeedback.mdl part for L1 and L2 stages (cf QUAD_MASTER_before/after.png)

A backup of the models h1sus{etmx/itmx}_Feb3rd2013.mdl was made under /opt/rtcds/userapps/release/sus/h1/models