Displaying reports 49661-49680 of 85499.Go to page Start 2480 2481 2482 2483 2484 2485 2486 2487 2488 End
Reports until 08:00, Wednesday 14 June 2017
LHO General
patrick.thomas@LIGO.ORG - posted 08:00, Wednesday 14 June 2017 (36880)
Ops Owl Shift Summary 
TITLE: 06/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Lost lock at the beginning of the shift from large earthquakes in Mexico and Guatemala. No clear reason for second lock loss. Current lock seems more stable.
LOG:

10:06 UTC Untripped watchdogs
10:09 UTC Attempting to relock
10:19 UTC Starting initial alignment
TMSX had to be moved to get green locked high enough on the X arm, likely because it tripped from the earthquake
10:54 UTC Initial alignment done
11:32 UTC Observing
11:40 UTC GRB
12:07 UTC GRB
12:13 UTC Lock loss
12:56 UTC Observing
13:58 UTC Karen to optics lab
14:15 UTC King soft water through gate. Here to pull water samples.
14:20 UTC Dust alarms in vacuum prep lab
14:23 UTC Ken to warehouse with pickup truck
14:40 UTC Karen out of optics lab
H1 General
patrick.thomas@LIGO.ORG - posted 05:52, Wednesday 14 June 2017 - last comment - 05:56, Wednesday 14 June 2017(36877)
NLN 
NLN at 12:45 UTC. Current SDF differences attached. Need to determine what to do about H1:ALS-Y_LOCK_STATEREQUEST and H1:ALS-C_LOCK_REQUESTY.
Images attached to this report
Comments related to this report
patrick.thomas@LIGO.ORG - 05:55, Wednesday 14 June 2017 (36878)
Link 

Changing H1:ALS-C_LOCK_REQUESTY to Red Locked seemed to fix both. Accepted the offsets.
patrick.thomas@LIGO.ORG - 05:56, Wednesday 14 June 2017 (36879)
Link 

Back to observing at 12:56 UTC.
H1 General
patrick.thomas@LIGO.ORG - posted 05:26, Wednesday 14 June 2017 (36876)
Lock loss 
Lock loss at 12:13 UTC. I was working on damping PI mode 27 but I don't think it was anywhere near high enough to cause a lock loss. Range had been degrading prior.
H1 General
patrick.thomas@LIGO.ORG - posted 04:33, Wednesday 14 June 2017 (36875)
Observing 
Back to observing at 11:32 UTC. Accepted attached SDF differences.
Images attached to this report
LHO General
patrick.thomas@LIGO.ORG - posted 04:02, Wednesday 14 June 2017 (36874)
Ops Owl Mid Shift Summary 
Earthquake has substantially subsided. Finished initial alignment. Attempting to relock.
LHO FMCS (CDS)
patrick.thomas@LIGO.ORG - posted 02:01, Wednesday 14 June 2017 - last comment - 02:22, Wednesday 14 June 2017(36870)
FMCS medm screens

I'm confused. I was almost certain I had updated the FMCS medm screens actually linked from the sitemap. However running svn update in /opt/rtcds/userapps/release/fmcs/h0/medm gave:

U    H0FMCS_CORNERSTATION_AH3.adl
U    H0FMCS_CORNERSTATION_CY.adl
U    H0FMCS_OUTBUILDING_CY_MY.adl
U    H0FMCS_OUTBUILDING_AH_EX.adl
U    H0FMCS_OUTBUILDING_MX.adl
U    H0FMCS_OUTBUILDING_MY.adl
U    H0FMCS_OUTBUILDING_AH_EY.adl
Conflict discovered in 'H0FMCS_CORNERSTATION.adl'.
Select: (p) postpone, (df) diff-full, (e) edit,
        (mc) mine-conflict, (tc) theirs-conflict,
        (s) show all options: tc
G    H0FMCS_CORNERSTATION.adl
U    H0FMCS_OUTBUILDING_AH_MX.adl
U    H0FMCS_OUTBUILDING_AH_MY.adl
U    H0FMCS_CORNERSTATION_AH1_2.adl
U    H0FMCS_OVERVIEW.adl
U    H0FMCS_OUTBUILDING_CY_EX.adl
U    H0FMCS_OUTBUILDING_CY_EY.adl
U    H0FMCS_OUTBUILDING_EX.adl
U    H0FMCS_OUTBUILDING_EY.adl
U    H0FMCS_OUTBUILDING_CY_MX.adl
Updated to revision 15730.

The conflict is because I had just started to edit this screen.

The screens linked from the sitemap now reflect the changes I had made. I'm not sure where I checked in the changes from if it was not /opt/rtcds/userapps/release/fmcs/h0/medm. I have a copy of these screens in my home directory but they do not seem to be an svn working copy. Did someone revert /opt/rtcds/userapps/release/fmcs/h0/medm to an earlier revision?

Comments related to this report
patrick.thomas@LIGO.ORG - 02:16, Wednesday 14 June 2017 (36871)
Link

More confusion. The link in the SITEMAP.adl file in /opt/rtcds/lho/h1/medm points to /ligo/lho/h0/fmcs/medm not /opt/rtcds/userapps/release/fmcs/h0/medm.

/ligo/lho/h0/fmcs/medm is an svn working copy already at the most recent revision.

Perhaps something changed with the SITEMAP instead?

patrick.thomas@LIGO.ORG - 02:22, Wednesday 14 June 2017 (36872)
Link

patrick.thomas@zotws3:~$ which sitemap
/ligo/apps/debian8/utils/bin/sitemap
patrick.thomas@zotws3:~$ cat /ligo/apps/debian8/utils/bin/sitemap
#!/bin/bash
source /ligo/cdscfg/stdsetup.sh
cd /opt/rtcds/lho/h1/medm
exec medm
    -noMsg
    -macro "USERAPPS=/opt/rtcds/userapps/release/"
    -attach
    -displayFont fixed
    -x SITEMAP.adl &> /dev/null &
LHO General
patrick.thomas@LIGO.ORG - posted 00:29, Wednesday 14 June 2017 (36867)
Ops Owl Shift Transition 
TITLE: 06/14 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Earthquake
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 9mph Gusts, 7mph 5min avg
    Primary useism: 0.26 μm/s
    Secondary useism: 0.17 μm/s 
QUICK SUMMARY:

Just lost lock coincident with earthquake.
H1 General
patrick.thomas@LIGO.ORG - posted 00:27, Wednesday 14 June 2017 - last comment - 03:04, Wednesday 14 June 2017(36866)
Earthquake & Lock Loss 
Lock loss at 7:06 UTC.

tconvert on GPS time for Seismon gives Jun 14 2017 06:38:54 UTC for time of earthquake and Jun 14 2017 07:15:03 UTC for arrival of R-20 Wave.

Seismon and USGS/Terramon do not exactly agree.
Images attached to this report
Comments related to this report
patrick.thomas@LIGO.ORG - 00:43, Wednesday 14 June 2017 (36868)
Link 

Verbal alarms just announced an incoming earthquake at 07:32 UTC. Seismon has updated to the attached screenshot.

07:38 UTC USGS has reported it
07:39 UTC Spike seen on BLRMS
Images attached to this comment
patrick.thomas@LIGO.ORG - 00:47, Wednesday 14 June 2017 (36869)
Link 

07:45 UTC Watchdogs starting to trip
patrick.thomas@LIGO.ORG - 03:04, Wednesday 14 June 2017 (36873)
Link

The following watchdogs tripped:

ISI ETMX stage 2

ISI ITMY stage 2

ISI ITMY stage 1

ISI ETMX stage 1

SUS TMSX

ISI ETMY stage 1

ISI ETMY stage 2

 

Images attached to this comment
LHO General
thomas.shaffer@LIGO.ORG - posted 00:00, Wednesday 14 June 2017 (36859)
Ops Eve Shift Summary

TITLE: 06/14 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Commissioning activities started the shift with Robert doing some baffle testing, then at 03:13 we went back to Observing and have been there since.
LOG:

H1 OpsInfo (SEI)
thomas.shaffer@LIGO.ORG - posted 22:27, Tuesday 13 June 2017 (36865)
Added SEI Configuration to OPS_OVERVIEW

I added some SEI configuration images to the OPS_OVERVIEW. Jim and I were talking the other day and thought that this would be useful. It will look at SEI_CONF Guardian node and display the image accordingly. It currently does not show all the states that SEI_CONF can go to, only the "popular" ones for now.

Images attached to this report
H1 General
thomas.shaffer@LIGO.ORG - posted 20:15, Tuesday 13 June 2017 (36862)
Back to Observing and LVEA Swept

Robert swept the LVEA and gave me the all good to go back into observing. We are Observing at 61Mpc on a 4hr lock.

H1 CAL (CAL)
aaron.viets@LIGO.ORG - posted 13:45, Thursday 27 April 2017 - last comment - 20:27, Tuesday 13 June 2017(35840)
DCS filters for LHO data starting at 1173225472 
I have produced filters for offline calibration of Hanford data starting at GPS time 1173225472. The filters can be found in the calibration SVN at this location:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1DCS_1173225472.npz

The new filters have EPICS and calibration line parameters for computing SRC detuning parameters. See
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=35041

For suggested command line options to use when calibrating this data, see:
https://wiki.ligo.org/Calibration/GDSCalibrationConfigurationsO2

The filters were produced using this Matlab script in SVN revision 4584:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1173225472.m

The parameters files used (all in revision 4584) were:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/modelparams_H1_2017-01-24.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/H1_TDparams_1175954418.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/callineParams_20170411.m
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/D20170411_H1_CAL_EPICS_VALUES.m

Several plots are attached. The first four (png files) are spectrum comparisons between CALCS, GDS, and DCS. GDS and DCS agree to the expected level.
Brief time series of the kappas and coherences are attached, for comparison with CALCS.
Time domain vs. frequency domain comparison plots of the filters are also attached.
Images attached to this report
Comments related to this report
aaron.viets@LIGO.ORG - 10:19, Tuesday 13 June 2017 (36842)
Link 

As a sanity check, I have calibrated data from early June to test whether these filters are up to date. Spectrum comparisons between the C00 frames and these filters are shown, and some unexpected discrepancy is noted at higher frequencies. Time series of the kappas are attached as well. These agree with the summary pages (i.e., the GDS pipeline).
Images attached to this comment
aaron.viets@LIGO.ORG - 11:49, Tuesday 13 June 2017 (36846)
Link 

It is now evident that this change did not occur during the vent, as the attached ASD ratio plot is from C01 and C00 data from May 08, 2017 at 14:00:00 UTC (GPS 1178287218), right before the vent.
Images attached to this comment
aaron.viets@LIGO.ORG - 13:22, Tuesday 13 June 2017 (36854)
Link 

It seems this change occurred during maintenance on Tuesday, April 11. The first ASD ratio is from data right before maintenance activities, and the second is from right after. Also it is confirmed that this is not being caused by a difference in the applied kappas (so the EPICS records agree). The most likely culprit is a change in the inverse sensing filtering.
Images attached to this comment
jeffrey.kissel@LIGO.ORG - 16:25, Tuesday 13 June 2017 (36861)
Link 

Relevant aLOGs around April 11th -- LHO aLOG 35474, and more specifically the comment, LHO aLOG 35476 which a "small change in writeEPICs code" is mentioned.

Can we compare the EPICs records committed to the repo around that time?
aaron.viets@LIGO.ORG - 20:27, Tuesday 13 June 2017 (36863)
Link 

I traced the problem to the GDS filters installed on April 11: https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=35462
Simply regenerating those filters seems to have fixed the problem, as shown in the attached ASD ratio plot comparing C01 to the corrected GDS filter output right after maintenance on April 11. The filters were generated as described in the above aLOG, except that the SVN revision was 4781, so the exact reason for the problem is unknown.

The C00 data affected by this problem starts on April 11 (GPS 1175976351), and it is still currently being affected, until we restart the GDS pipeline, no later than next Tuesday, June 20. The C01 frames are not affected by this and should be fine.
Images attached to this comment
H1 CAL (CDS)
aaron.viets@LIGO.ORG - posted 08:57, Tuesday 11 April 2017 - last comment - 20:31, Tuesday 13 June 2017(35462)
New GDS filters for LHO to compute SRC detuning parameters 
[Jeff K, Aaron V]

I have produced new GDS filters for LHO that include new paramters (pcal correction factors and EPICS) necessary to compute SRC detuning parameters. It will also be possible to subtract the calibration lines from the strain, producing the additional channel GDS-CALIB_STRAIN_CLEAN, if we desire. The filters can be found in the calibration SVN at this location:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1GDS_1175954418.npz

For information on GDS calculations of SRC detuning parameters, see:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=35041  (note that we now compute Q-inverse instead of Q)
https://alog.ligo-la.caltech.edu/EVNT/index.php?callRep=11785

The filters were produced using this Matlab script in SVN revision 4537:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1175954418.m

The parameters files used (all in revision 4537) were:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/modelparams_H1_2017-01-24.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/params/2017-01-24/H1_TDparams_1175954418.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/callineParams_20170411.m

ASD plots comparing GDS and the front-end CALCS model are attached. These agree with those on the summary pages from the same day (4/10), as expected. Also, time domain vs. frequency domain comparison plots of the filters are attached. Lastly, a time series plot of the kappas from GDS and CALCS is attached, as well as histograms. These show the expected output.
Images attached to this report
Comments related to this report
aaron.viets@LIGO.ORG - 20:31, Tuesday 13 June 2017 (36864)
Link 

It was discovered that the output of these filters did not agree with the C01 frames. These GDS filters have been regenerated with SVN revision 4781, and the discrepancy has disappeared. For more details on this issue, see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=36863 .
Displaying reports 49661-49680 of 85499.Go to page Start 2480 2481 2482 2483 2484 2485 2486 2487 2488 End