To eliminate the number of parts problem I rewrote a section of the ODC master as simple c code. Functionality and channel names stayed the same. The parts count dropped from 3549 to 536. The function that now does most of the work is MASKING_MATRIX in ODC_MASKING_MATRIX.c. I also added a hook to include IPS error checking to that c-function. sys/h1/model/h1odcmaster.mdl sys/common/model/ODC_MASTER_PARTS_V2.mdl cds/common/src/ODC_MASKING_MATRIX.c SVN revision 7282.
10:40 Check which models had new INI files after make install
13:47 Check new ham isi INI files, add new dust channels
14:15 new h1odcmaster file, channels unchanged, chnnums changed?
Stefan, Jim and Dave
Stefan created a new h1odcmaster.mdl model which drastically reduced the number of "parts to process" from 3,549 to 536. We started it after crashing the h1oaf0 for the last time, and then restarted it with no further crashing.
It required a DAQ restart.
Plotted the End-Y dust monitor data for the last 24 hours, (covering the cartridge install and subsequent activities at End-Y). Dust spikes are consistent with the cartridge installation and Apollo working on post-installation tasks. EY-DUST-1 covers from 06:00 to 12:00 02/25/14. EY-DUST-2 covers from 12:00 02/24/14 to 12:00 02/25/2014.
I added the channels to the ini file (cds_user_apps/trunk/cds/h1/daqfiles/ini/H0EDCU_DUST.ini) and Dave B. restarted the DAQ.
Fabrice, Dave.
WP4461: rebuilt, installed and restarted the models h1isiham[2,3,4,5,6]. Manually burt restored to 09:00 the models h1isiham[2,3,5,6] as before (ham4 has good safe.snap).
I set the end X ALS laser temperature to 31.77, the set current is at 1.84, and the doubling temp is 33.81. We have a beat note. I realinged the IR monitor PD and it reports 63mW now (power before pick off), and the green monitor reports 1.05mW
see alog 9057 for the last time I changed these values.
After Aaron installed the relay for the noise eater the laser came back to a set temperature of 32.9C, so we could not find a beat note at first. Richard is testing the relay now.
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'.
The lenses as installed are:
LWFSA1 +250mm
LWFSA2 -75mm
LWFSB1 +250mm
LWFSB2 -100mm
This is an adaptation of the mode-matching solution by Bram Slagmolen used for the OAT WFS in D1100607-v10, and shown in the attached plots. This is not the simplest possible solution, but it has the very desirable quality of having great flexibility with WFS placement while keeping 90 (+/-10) degree Guoy phase separation.
It is important to note that the nominal mode-matching solution used to generate this layout did not account for the beam quality issues. In theory, the input beam should have been small enough that the beam expansion properties of the layout would have been necessary to get a usable beam size on the WFS. If this ends up being an issue, the mode-matching can be modified to reflect reality.
WFSa1.jpg in the original entry was bogus (it was a copy of WFSb1). Attached is the correct one.
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...
Like NBC jinxed all of the ice skaters by praising them just before they fell at the latest Olympics, I spoke too soon about the PUM ITM03 ear. Just after writing the above alog, Gerardo and I inspected the S4 ear and discovered a large bubble near the corner of the ear. It had a small fiberous particulate in the bubble. SOmehow, after monitoring for 2-3 hours, this fiber migrated into the bond. We had placed a LIGo-approved Vectra Alpha 10 cleanroom wipe over the S4+ear flat for the night in the event a random bug decided to perch, so possibly this added to the particulate. Da*m.
With Mr. Barton's assistance, we loaded the mass into the ultrasonic cleaner and bathed it in water. Within 4 minutes the ear came off. The mass is now reloaded at the wash station and we'll work on the S3 ear we were already prepped for today.
Bubble is shown in far corner of ear in this picture.
Further comment to the events above - Margot and Gerardo found this PUM to be dirtier than normal when they pulled it out of the cake tin many weeks ago. AT that time, they did a methanol cleaning of the entire mass. When Gerardo and I were cleaning the flats of this mass, we also noticed that it still seemed dirtier than "normal" - meaning, when rinsing, the water did not run on the surface as we had seen on other flats. After we performed the standard cleaning of the flat, the water behaved "normally", meaning it clung to the full surface and "sheeted" off. After we removed the contaminated ear, we recleaned the flat, expanding the surface area getting cleaned to the entire flat, not just the area when the ear gets bonded as is the typical procedure. We hoped this would remove particulate that was previously closer to the bond area. During the second ear bond attempt, we also did not cover the bond overnight with an alpha 10 wipe, since we were skeptical of the origin of the fiber which showed up in the bond.
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:
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.
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;
[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!).
Thank you for the excellent work on validating this model!
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.
Congratulations all for reaching this milestone safely. That's five H1 cartridge insertions, plus the two for H2 chambers BSC6 and BSC8. Nicely done! Remaining in-chamber installation includes:
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.FOUROSEM_STAGE_MASTER_oplevfeedback.mdlQUAD_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
I missed a few alogs explaning some modifications on the models. so here's the current status :