Displaying reports 49661-49680 of 83192.Go to page Start 2480 2481 2482 2483 2484 2485 2486 2487 2488 End
Reports until 12:54, Wednesday 01 March 2017
H1 PSL (PSL)
travis.sadecki@LIGO.ORG - posted 12:54, Wednesday 01 March 2017 - last comment - 13:37, Wednesday 01 March 2017(34497)
PSL low temp alarm

We received a couple of PSL low temp alarms over the past hour.  Looking at the attached trend, over the past hour the temp has dropped from 73.3 degF to 69.2 degF, then turned over and started coming back up to 71 degF.  I notified Jason and he is going to look at the PSL enclosure to check that the air conditioning didn't turn on mysteriously.

Images attached to this report
Comments related to this report
travis.sadecki@LIGO.ORG - 13:37, Wednesday 01 March 2017 (34500)
Link

At Jason's request, here are some more trends of the PSL temperature on the table (TBLN = table north, TBLS =  table south) and the LVEA temperature.  All of the PSL temps seem to follow the same trends with slightly smaller magnitude of change.  The LVEA trend looks similar in shape to the PSL trends, but it only changes by ~0.1 degF.

Images attached to this comment
H1 CDS
david.barker@LIGO.ORG - posted 12:25, Wednesday 01 March 2017 - last comment - 12:28, Wednesday 01 March 2017(34495)
installed latest lockloss3 script, made this the default lockloss

Dave,  Joe B.

I have installed Joe's sys/common/scripts/lockloss3 script at LHO. The /ligo/cds/userscripts/lockloss symbolic link now points to the new file. I ran the script over the 3am PST H1 lockloss and was able to get the plots (BTW, wind speeds didn't seem too bad at the time of lock loss).

Handing this over to the operations and commissioning teams for use/evaluation.

Related service-request in FRS is https://services.ligo-la.caltech.edu/FRS/show_bug.cgi?id=7531

Comments related to this report
david.barker@LIGO.ORG - 12:28, Wednesday 01 March 2017 (34496)
Link

BTW: please do not try a global svn-update of sys/common/scripts, we have 4 files which may be in conflict with the repository. They are: guardlinks, lockloss-sus-sat, lockloss and quick_snap.

For lockloss3 install, I did a file-by-file update of lockloss2 and lockloss_utils.py

LHO VE
logbook/robot/script0.cds.ligo-wa.caltech.edu@LIGO.ORG - posted 12:10, Wednesday 01 March 2017 - last comment - 13:09, Wednesday 01 March 2017(34494)
CP3, CP4 Autofill 2017_03_01 
Starting CP3 fill. LLCV enabled. LLCV set to manual control. LLCV set to 50% open. Fill completed in 1998 seconds. TC B did not register fill. LLCV set back to 16.0% open.
Starting CP4 fill. LLCV enabled. LLCV set to manual control. LLCV set to 70% open. Fill completed in 1674 seconds. TC A did not register fill. LLCV set back to 37.0% open.
Images attached to this report
Comments related to this report
kyle.ryan@LIGO.ORG - 13:09, Wednesday 01 March 2017 (34498)
Link 

Increased LLCV %open values to 39% from 37% for CP4 and to 18% from 16% for CP3
H1 General
travis.sadecki@LIGO.ORG - posted 11:22, Wednesday 01 March 2017 (34492)
Commissioning mode at 19:19 UTC

Transitioned to Commissioning for the commissioning break from 19:00-22:00 UTC as directed by Keita.

H1 CDS
david.barker@LIGO.ORG - posted 10:55, Wednesday 01 March 2017 (34491)
work permits web listing cleaned up, now loads faster

FRS7340. Work permits older than 2017 have been put into a subdirectory called archive_2007-2016 (yep, the wp system is 10 years old this June 1st). This web page now loads considerably faster.

Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 10:16, Wednesday 01 March 2017 - last comment - 10:45, Thursday 02 March 2017(34490)
Look at T240 now in BRSY Enclosure

JimW HughR

The first attachment is from late afternoon yesterday, before the winds started picking up.  There is still a large difference between it and the ISI GND STS below 100mHz.  This may be thermal equilibrating or maybe the masses need centering again.  I'll look at this today; must be done at EndY.

The second attachment is from early this morning with sustained 20mph winds; pretty steady direction from the SW to SSW. The coherence and spectra look much better with the greater input.

The third attachment looks at coherence to the BRS Tilt.  The coherence to the right is when the wind is low and to the left shows when the wind is high.  Bottom line: not much difference between the colocated sensor and the GND seismo on the floor.

 

Images attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 21:21, Wednesday 01 March 2017 (34519)
Link

At the end of the commisioning break today, I went down to EY and recentered the masses on the T240. This sensor doesn't have the full integration into the data system, so it's not just a button push. Richards DB9 connector makes this pretty easy though. Pin 5 is the analog ground, so UVW are read by read getting the voltages from pins 1-3 to 5. To re-center, you need a 5V supply (Richard loaned me one), connect pin 7 to the supply ground and put the +5v on pin 6 for a(n actual) second. When I got to EY the masses were at 1-2v, after centering they were between .08-.2v.

krishna.venkateswara@LIGO.ORG - 10:45, Thursday 02 March 2017 (34537)SEI
Link

I looked at 2-k seconds of data from Wednesday night at 6:00 UTC. Plots are attached. The ASD is in rad/rt(Hz). Once again, the T240 seismometer on the platform sees a substantially larger low-frequency signal compared to the BRS or the ground STS. This instrument performed much better when it was on the ground.

This suggests that it is picking up extra signal when it is on the platform, which is not real tilt (as the BRS signal is much smaller). It is unlikely to be temperature since Hugh's additional foam insulation made no difference. It could be temperature noise on the table feet so it may be a good idea to wrap the feet also in the same foam insulation and see if that makes any difference.

Another possibility is that the low-frequency excess could be some form of (parametric) down-conversion from the excess high frequency motion of the platform (10-50 Hz). We have seen such noise on the BRS flexures, so it would not surprise me if similar noise exists in seismometers. I'm more surprised that the platform is shaking so much at high frequencies. I think this calls for a better design of the platform feet.

Non-image files attached to this comment
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 09:50, Wednesday 01 March 2017 (34489)
CDS O2 restarts: Friday 24th - Tuesday 28th February 2017

model restarts logged for Tue 28/Feb/2017
2017_02_28 09:38 h1isiham2
2017_02_28 09:45 h1asc
2017_02_28 09:47 h1dc0
2017_02_28 09:48 h1fw1
2017_02_28 09:49 h1broadcast0
2017_02_28 09:49 h1fw0
2017_02_28 09:49 h1fw2
2017_02_28 09:49 h1nds0
2017_02_28 09:49 h1nds1
2017_02_28 09:49 h1tw1
2017_02_28 11:33 h1lsc

Maintenance day. New ISI-HAM2 and ASC models with associated DAQ restart. Bug fix of LSC model. h1brsex restart 11:55 (not shown)

model restarts logged for Mon 27/Feb/2017 - Fri 24/Feb/2017 No restarts reported

H1 General
travis.sadecki@LIGO.ORG - posted 08:53, Wednesday 01 March 2017 (34486)
Ops Day Shift Transition

TITLE: 03/01 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 34mph Gusts, 27mph 5min avg
    Primary useism: 0.13 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY:  Observing for just over 3 hours.  Other than wind being at the edge of causing issues, no problems.

 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 08:02, Wednesday 01 March 2017 (34485)
Ops Owl Shift Summary
Ops Shift Log: 03/01/2017, Owl Shift 08:00 – 16:00 (00:00 - 08:00) Time - UTC (PT)
State of H1: Locked at NLN, range is 62.4 Mpc  
Intent Bit: Observing
Support: N/A
Incoming Operator: Travis

Shift Summary: A2L DTT script Yaw & Pitch are rung up; did not run repair script. Lost lock – Several wind gusts above 35 mph, and one near 45 mph at the CS. Trying to relock. Ran initial alignment and relocked the IFO. Accepted HPI-HAM2_IPS_HP_SETPOINT_NOW SDF and went back to Observing.  

 
Activity Log: Time - UTC (PT)
08:00 (00:00) Take over from TJ
11:50 (03:50) Lockloss – Several wind gusts in the high 30s and one over 40 mph
13:34 (05:34) Relocked; back to Observing after clearing HAM2 SDF
13:50 (05:50) Damped PI Mode28
14:00 (06:00) Damped PI Mode27
15:15 (07:15) Bubba & Apollo – Going to Mid-X
16:00 (08:00) Turn over to Travis

 

H1 SEI
jeffrey.bartlett@LIGO.ORG - posted 05:42, Wednesday 01 March 2017 - last comment - 16:44, Wednesday 01 March 2017(34484)
HAM2 SDF Diss 
   After relocking there was a SDF difference with the HPI-HAM2_IPS_HP_SETPOINT_NOW. Accepted the difference and went into Observing.
Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 09:00, Wednesday 01 March 2017 (34487)
Link

Thanks for the log Jeff.  This reminds (smacks in the face) me now that I've removed the HEPI Pringles from the Restore Target DOF list, these will all have to be put into the Not Monitored list.  These are the DC positions that the Isolation loops drive to.  When the loops first start, we load the current free hanging position into the "SETPOINT_NOW" channel so the loop starts with no DC load.  After the loop is on and is stable, we load the "Target Position" to move too.  All HEPI loops were driving to Targets but the Pringle loops are AC coupled so loading a DC Target position just was wasted effort that got the loop nowhere in the end.  So this Setpoint Now channel will be different every time there is a platform trip and re-isolation. 

What I don't understand is why there isn't a VP difference too and why this HP difference is so small.

For the ISIs, all HAMs load all DOF Targets, for the BSCs, none of the Targets are loaded; hence, the Not Monitored Lists.

I probably could do this while Observing but I'm reluctant in case the fussing around sets an SDF flag; I'll get it during commissioning later.

Addendum: Checked the SVN, someone must have saved the OBSERVE.snap earlier in the day, to clear the diffs after the HAM2 HPI trip during maintenance; I remember Jim mentioning the trip in the morning.  Then the old e-11 diff popped up; not sure why that happens.  Regardless, I'll get these into the Not Monitored list and it will be a thing of the past.

thomas.shaffer@LIGO.ORG - 16:44, Wednesday 01 March 2017 (34508)
Link

I didn't put the updated script in ISC_LOCK that will switch the SDF reference files since I was worried that I would leave and then something would go wrong. This should hopefully fix this SDF diff in the future. I've tested it a few different ways and it all seems good, but I will do it this shift if I get the opportunity.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 04:29, Wednesday 01 March 2017 (34483)
Ops Owl Mid-Shift Summary 
   Locked and Observing until 11:50 (03:50). Wind and microseism have been building all shift. Base winds in the mid 20s with gusts up into the mid-30s. Lock broke about the time of gusts at the CS into the Mid-40s. 

   Winds over the past 20 minutes appear to be laying down. Will do IA if cannot relock.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 00:30, Wednesday 01 March 2017 (34482)
Ops Owl Shift Transition
Ops Shift Transition: 03/01/2017, Owl Shift 00:08 – 16:00 (00:00 - 08:00) - UTC (PT)
State of H1: IFO locked at NLN, at 30.8W and 64.7 Mpc  
Intent Bit: Observing
Weather: Wind is up to a Moderate Breeze, Clear, lower 40s  
Primary 0.03 – 0.1Hz: Y & Z at 0.02um/s, X a bit above 0.1um/s
Secondary 0.1 – 0.3Hz:  At 0.2um/s 
Quick Summary: Observing for 8.0 hours. The A2L script has a problem.  The A2L Pitch and Yaw signals are somewhat rung up at this time. Guardian is reporting two seismic differences with HAM2, which will clear with the next restart of the Guardian code. 
Outgoing Operator: TJ
LHO General
thomas.shaffer@LIGO.ORG - posted 00:00, Wednesday 01 March 2017 (34479)
Ops Eve Shift Summary

TITLE: 03/01 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 66Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Locked my whole shift, I had an error with a2l so I could not run it. I also accidentally knocked us out of Observing for about 40sec.
LOG:

H1 ISC
thomas.shaffer@LIGO.ORG - posted 23:23, Tuesday 28 February 2017 (34481)
Out of Observing to attempt run a2l

Out of Observing from 07:12 - 07:19. Tried to run a2l but there was an error, I'm guessing related to some changes today.

 

Traceback (most recent call last):
  File "./a2l_min_LHO.py", line 107, in <module>
    matrix.asc_ads_input[dof,sensor]=0
AttributeError: 'module' object has no attribute 'asc_ads_input'

H1 General
thomas.shaffer@LIGO.ORG - posted 20:34, Tuesday 28 February 2017 (34480)
Ops Mid shift report

Locked for 4.5hrs with a range of 65Mpc.

We were out of observing for about 40sec when I ran a test that imported the wrong file and caused one SDF diff. I rectified it immediately.

H1 CAL (CAL)
aaron.viets@LIGO.ORG - posted 13:43, Tuesday 31 January 2017 - last comment - 12:01, Wednesday 01 March 2017(33771)
DCS filters for LHO data starting at 1169326080 
I have produced filters for offline calibration of Hanford data starting at GPS time 1169326080. The filters can be found in the calibration SVN at this location:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/GDSFilters/H1DCS_1169326080.npz

For information on the associated change in calibration, see:
https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=33585

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 4251:
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/TDfilters/H1_run_td_filters_1169326080.m

The parameters files used (all in revision 4251) 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_1169326080.conf
ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CAL_EPICS/D20170124_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. Kappas were applied in both the GDS plots and the DCS plots with a coherence uncertainty threshold of 0.4%.
Time domain vs. frequency domain comparison plots of the filters are also attached. Lastly, brief time series of the kappas and coherences are attached, for comparison with CALCS.
Images attached to this report
Non-image files attached to this report
H1DCS_kappas_1169719424.pdf
Comments related to this report
shivaraj.kandhasamy@LIGO.ORG - 12:01, Wednesday 01 March 2017 (34493)CAL
Link 

Here is a plot that compares the ratios of GDS and DCS (CO1) data (expected vs measured). Above ~8 Hz, the expected and measured ratios agree. Below ~8 Hz the we see difference. This comparison doesn't account for the FIR implementation of ~9 Hz high pass filter used in GDS and DCS data. If there is difference between how this implemented it could produce the difference we see here (need to be checked).  The code used to make this plot is added to svn,
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/CALCS_FE/CALCSvsDARMModel_20170124.m 
This is just an updated version of the code Jeff used to make the CALCS and GDS comparison.
Images attached to this comment
Displaying reports 49661-49680 of 83192.Go to page Start 2480 2481 2482 2483 2484 2485 2486 2487 2488 End