Displaying reports 60801-60820 of 84797.Go to page Start 3037 3038 3039 3040 3041 3042 3043 3044 3045 End
Reports until 08:25, Saturday 02 January 2016
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 08:25, Saturday 02 January 2016 (24637)
CDS model restart report Friday 1st January 2016

O1 day 106

model restarts logged for Fri 01/Jan/2016 No restarts reported

H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:08, Saturday 02 January 2016 (24636)
Ops Day Shift Transition
   Transition Summary:
Title:  01/2/2016, Day Shift 16:00 – 00:00 (08:00 – 16:00) All times in UTC (PT)
	
State of H1: 16:00 (08:00), IOF up in Observing mode for last 2.5 hours. Range and power are normal. Environmental conditions are good. 
 
Outgoing Operator: TJ
LHO General
thomas.shaffer@LIGO.ORG - posted 07:56, Saturday 02 January 2016 (24635)
Ops Owl Shift Summary
LHO General
thomas.shaffer@LIGO.ORG - posted 05:31, Saturday 02 January 2016 (24633)
Observing 13:29 UTC

Had to run through an initial alignment where Mich dark locked would not lock, then some trouble with the PRMI to DRMI transition. But now we are up and observing!

LHO General
thomas.shaffer@LIGO.ORG - posted 03:46, Saturday 02 January 2016 - last comment - 05:32, Saturday 02 January 2016(24632)
Lockloss 11:42 UTC

Not sure of the cause; the control signals all looked good, nothing on the seismometers, wind low, need to further investigate after locking.

Comments related to this report
thomas.shaffer@LIGO.ORG - 05:32, Saturday 02 January 2016 (24634)Lockloss

Nothing seen on general lockloss plot

Images attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 00:09, Saturday 02 January 2016 (24629)
Ops Owl Shift Transition
H1 AOS
travis.sadecki@LIGO.ORG - posted 00:00, Saturday 02 January 2016 - last comment - 01:05, Saturday 02 January 2016(24626)
OPS Eve shift summary

Title: 1/1 Eve Shift 0:00-8:00 UTC (16:00-24:00 PST).  All times in UTC.

State of H1: Observing

Shift Summary: Started the shift with the PSL down and being worked on by Jason and Corey (T. Vo was covering OPS duties).  Within the first hour of my shift, they had completed their work and I began initial alignment.  After a surprisingly straightforward alignment and locking, made it to NLN at 2:29 UTC.  Other than some excess noise from 10-30 Hz, range has been the typical ~80 MPc for the past 6 hours.  Environment is calm.

Incoming operator: TJ

Activity log:

In addition to the PMC diff that Betsy took care of here, I accepted a diff for H1:IMC-REFL_SERVO_IN1GAIN (setpoint -2.00, epics -1.00) in order to proceed to Observing.  I (actually T.Vo did, since he was already logged onto another workstation) also switched the omcparams.py starting voltage back to -24, which worked to get past the same problem described by Corey here.  Note: I did NOT commit the change in omcparams.py to the SVN.

Comments related to this report
corey.gray@LIGO.ORG - 00:37, Saturday 02 January 2016 (24630)OpsInfo

Were you able to get Input Align to work?  Or did you try Kiwamu's workaround?  (Just wanting to get data points on how Input Align step of Initial Alignment is going.).

travis.sadecki@LIGO.ORG - 01:05, Saturday 02 January 2016 (24631)
Input align worked fine for me.
H1 SUS (ISC)
brett.shapiro@LIGO.ORG - posted 22:38, Friday 01 January 2016 - last comment - 19:36, Tuesday 05 January 2016(24625)
Additional Updates to the quad Matlab model

svn up at .../SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production

All current model features are summarized in a table in G1401132.

Update to existing features

The main change in existing features is that the top mass damping now sees both the suspension and the cage, as in real life because we use OSEMs. Consequently, if you input seismic noise to a damped suspension it will enter both mechanically as usual, as well as through the damping loops. See Seismic_Noise_Propagation_2016_01_01.pdf. Page 1 shows longitudinal transfer functions from seismic noise to the test mass with and without the OSEMs seeing the cage. The second page shows the ratio of these transfer functions. Note that the ratio is greater than a factor of 2 at 4.5 Hz. Beyond 10 Hz the maximum is about 20% at about 10.5 Hz.

 

Two new features 

1. Additional inputs and outputs added to reflect the relative nature of the OSEMs - i.e. they measure relative displacements and actuate between two points

2. Suspension point reaction forces

The discussion above is one consequence of the first new feature. Another is that you can now make transfer functions between seismic noise and the top mass OSEMs, which is dramatically different from the seismic noise to top mass transfer function. See Seismic_to_Top_OSEMs_2016_01_01-2.pdf. These are obtainable in the model with the new 'toposem' field in the 'out' structure given by the generate_QUAD_Model_Production function.

The second new feature is that there are now outputs for the suspension point reaction forces on the ISI. These are obtainable in the model with the new 'suspoint' field in the 'out' structure given by the generate_QUAD_Model_Production function. These reaction forces allow us to dynamically couple the quad model to the ISI model. Thus, if we wanted, we can make one big ISI-SUS model.

 

Under-the-hood updates

This update includes significant under-the-hood modifications to how the pieces of the model are put together. Essentially, Simulink files now define the connections and signal flow, where previously this was all done with append/connect commands in the generate script. The motivation for this change is to make the model more extensible and maintanable by humans. The append/connect commands had become virtually unreadable with the dozens of inputs and outputs now in the model. Now someone can look at a more intuitive graphical representation in a simulink file to read or modify how the model is layed out.

There are 4 simulink files defining the 4 possible layouts of the quad model:

1) A single undamped chain - generate_QUAD_SingleChainUndamped_Simulink.slx
2) A single damped chain - generate_QUAD_SingleChainDamped_Simulink.slx
3) Two undamped chains - generate_QUAD_BothChainsUndamped_Simulink.slx
4) Two damped chains - generate_QUAD_BothChainsDamped_Simulink.slx

 

For reference, this is a summary of the history of model revisions in the svn:

generate_QUAD_Model_Production.m

rev 7359: now reads foton files for main chain and reaction damping

rev 7436: Changed hard coded DAMP gains to get the correct values for LHO ETMX specifically.

rev 7508: Restored damping filter choice for P to level 2.1 filters as opposed to Keita's modification. Cleaned up error checking code on foton filter files, and allowed handling of filter archive files and files with the full path.

rev 7639: renaming lho etmy parameter file

rev 7642: Adding custom parameter file for each quad. Each one is a copy of h1etmy at this point, since that one has the most available data.

rev 7646: added ability to read live filters from sites, and ability to load custom parameter files for each suspension

rev 7652: updated to allow damping filters from sites from a specific gps time (in addition to the live reading option)

planned future revision - seismic noise will progate through the damping filters as in real life. i.e the OSEMs are relative sensors and measure the displacement between the cage and the suspension.

rev 7920: big update - added sus point reaction forces, top OSEMs act between cage and sus, replaced append/connect command with simulink files

ssmake4pv2eMB5f_fiber.m

no recent (at least 4 years) functional changes have been made to this file.

* quadopt_fiber.m

- rev 2731: name of file changed to quadopt_fiber.m, removing the date to avoid confusion with Mark Barton's Mathametica files.

- rev 6374: updated based on H1ETM fit in 10089.

- rev 7392: updated pend.ln to provide as-built CM heights according to T1500046

- rev 7912: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit.  Same as h1etmy.m.

* h1etmy.m

- rev 7640: created the H1ETMY parameter file based on the fit discussed in 10089.

- rev 7911: the update described in this log, where the solidworks values for the inertias of the test mass and pum were put into the model, and the model was then refit. Same as quadopt_fiber.m.

Non-image files attached to this report
Comments related to this report
brett.shapiro@LIGO.ORG - 10:37, Saturday 02 January 2016 (24638)

The quad model was tagged on the SVN both before and after this update. The tagged models are at 

before this update:
/ligo/svncommon/SusSVN/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev7652_ssmake4pv2eMB5f_fiber-rev3601_fiber-rev7913_released-2016-01-01.mat
This version reflects the model after the previous recent update discussed in log 24456, which updated the test mass and PUM inertias with solidworks values. No model features were changed in this update.

After this update
/ligo/svncommon/SusSVN/sus/trunk/Common/SusModelTags/Matlab/quadmodelproduction-rev7920_ssmake4pv2eMB5f_fiber-rev3601_fiber-rev7913_released-2016-01-01.mat

The tags were created using the following script:

/ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/tagsusdynamicalmodel.m    rev 7923

jenne.driggers@LIGO.ORG - 16:32, Monday 04 January 2016 (24694)

Just as an FYI, I have done this svn update.

brett.shapiro@LIGO.ORG - 19:36, Tuesday 05 January 2016 (24717)

MInor updates and fixes:

1) The simulink files were generating warnings in Matlab 2012b because they were saved in 2013a. I resaved them in 2012b, recommited, and the problem has gone away. Matlab versions 2013a and 2015b are fine as well. No promises for versions earlier than 2012b.

2) While fixing the simulink diagrams, I added some extra inputs based on a disucssion with Brian Lantz. These are 'osem like' force inputs acting between the top mass and the cage for the purpose of testing the reaction force outputs on the ISI. These will not impact any prior features of the model.

H1 General (OpsInfo)
travis.sadecki@LIGO.ORG - posted 20:24, Friday 01 January 2016 (24624)
OPS Day mid-shift summary

Observing for 2 hours at 75-80 MPc.  There seems to be a bit of excess noise below ~30Hz in DARM which seem to correlate with some excess noise in PRCL and MICH.  Wind and seismic are both calm. 

In getting back to Low Noise, I had to change the OMC PZT starting voltage in omcparams.py back to -24 from the -30 that Corey changed it to earlier today.  I did NOT commit the changes to SVN since they seem to be in flux.

H1 PSL
betsy.weaver@LIGO.ORG - posted 18:42, Friday 01 January 2016 - last comment - 23:40, Friday 01 January 2016(24622)
SDF PMC REF channel TEMPORARILY set to NOT MONITORED

Because the H1:PSL-PMC-REF slider was adjusted to land on a value with much larger precision than the SDF file can deal with, it was in alarm out to the 10e-16 digit which could not be cleared with the ACCEPT button.  The correct way to clear this bug is to write the epics slider to a smaller precision value (truncate it to the 10 e-8 or something digit).  However, we are all the way back to Nom LOW Noise, and didn't want to risk this minute slider adjustment - SO, we set the channel to be NOT MONITORED until the next lock loss, when we should:

 

- Set this channel (H1:PSL-PMC-REF) to be MONITORED again in SDF

- Type in the SDF setpoint value (1.18615) into the slider value and check that it is no longer in error on SDF.

Comments related to this report
betsy.weaver@LIGO.ORG - 18:43, Friday 01 January 2016 (24623)

Images attached to this comment
jason.oberling@LIGO.ORG - 23:40, Friday 01 January 2016 (24627)OpsInfo

This was actually a temporary change we had to make to help the PMC lock that I had forgotten about.  This setting can be reverted to its orginal value of 1.35V once the channel is set to be MONITORED again in the SDF.

H1 General
travis.sadecki@LIGO.ORG - posted 18:30, Friday 01 January 2016 (24620)
Observing at 2:29 UTC

After a remarkably smooth recovery from the PSL incursion, we are back to Observing.

H1 PSL (DetChar, ISC, PSL)
jason.oberling@LIGO.ORG - posted 16:57, Friday 01 January 2016 (24619)
PSL FSS RefCav Alignment

J. Oberling, C. Gray

After this morning's NPRO shut-off, we noticed the FSS RefCav TPD was down to ~1V (the RefCav Refl spot showed that the pitch had moved significantly as well).  At the rate of decay (see attached 7 day trend), there was a good possiblity of the TPD not surviving until maintenance Tuesday (1-1-2016), so we decided, with M. Landry's permission, to go in a adjust it.  In the interest of returning to operation quickly, we only adjusted the periscope mirrors to bring the TPD back up; no investigation as to the cause of the alignment shift was done.

We began by adjusting only pitch on the top periscope mirror.  This only got us back to half way, so I decided to include the bottom periscope mirror and walk the beam.  Walking the beam down got the TPD to ~1.47.  We then did a small yaw tweak to the top periscope mirror only, which got us to ~1.51V.  We then measured the visibility of the cavity, and then turned the ISS back ON and left the PSL enclosure.  Total time in the enclosure was ~30 minutes.

Images attached to this report
H1 PSL (PSL)
jason.oberling@LIGO.ORG - posted 16:48, Friday 01 January 2016 - last comment - 23:41, Friday 01 January 2016(24617)
PSL NPRO Turned Off

J. Oberling, C. Gray

At 21:01:51 UTC the PSL NPRO shut off (see attached trend of NPRO diode power, NPRO power, and PSL power watchdog), reason unknown.  The PSL watchdog tripped 3 seconds later at 21:01:54 UTC, so the NPRO definitely shut off first.  After Corey's phone call I drove to the site to reset the PSL.  The only thing I found wrong was that the NPRO power supply was ON, but not sending power to the NPRO (key ON, power supply OFF).  The UPS the NPRO power supply is plugged into did not show an error, and there were no other obvious indications that something went wrong, so I turned the NPRO back ON.  It powered up without issue, and we turned the 35W FE laser on from the LDR.  After fiddling with the PMC and FSS (as usual after a laser shutdown), everything with the PSL was locked and operating properly.  It is still unknown why the NPRO shut off.  At this point I suspect a glitch with the UPS; we have seen this behavior before, where a glitch in the UPS causes the NPRO to shut off with no idication of what went wrong.

At this point we noticed the FSS TPD was down to ~1V, which is getting close to the point where ALS becomes unhappy.  A 7 day trend of the RefCav TPD is attached.  At that rate of decay the FSS might not have lasted until maintenance day on 1-5-2016, so we decided (with M. Landry's permission) to go in and do a quick adjustment of the RefCav alignment.  I will detail that in a follow up alog.

Images attached to this report
Comments related to this report
thomas.vo@LIGO.ORG - 18:31, Friday 01 January 2016 (24621)

In order to get the PMC locked, we also tweaked the H1:PSL-PMC_REF from 1.35V to 1.19V, this caused a notification in SDF.

jason.oberling@LIGO.ORG - 23:41, Friday 01 January 2016 (24628)

Thanks Thomas, I had forgot we made that change.

Displaying reports 60801-60820 of 84797.Go to page Start 3037 3038 3039 3040 3041 3042 3043 3044 3045 End