Displaying reports 65601-65620 of 84513.Go to page Start 3277 3278 3279 3280 3281 3282 3283 3284 3285 End
Reports until 11:28, Wednesday 01 July 2015
H1 General
jeffrey.bartlett@LIGO.ORG - posted 11:28, Wednesday 01 July 2015 (19413)
Storage Dry Box Temp/Hum Data
Posted below are the data from DB1, DB4, and 3IFO-DES-CAB long term storage cabinets. All data are with normal ranges and expected patterns. The dip in RH recorded for 3IFO-DES-CAB starting on 06/23/15 is from the Dewar being filled. Greater pressure in the Dewar meant more flow through the cabinet, resulting in a lower RH. In short, the cabinets are working as expected.     
Non-image files attached to this report
H1 PSL
edmond.merilh@LIGO.ORG - posted 10:27, Wednesday 01 July 2015 (19411)
PSL DBB scans + ISS Scan
Non-image files attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 10:00, Wednesday 01 July 2015 (19410)
CDS model and DAQ restart report, Tuesday 30th June 2015

maintenance day restart log:

model restarts logged for Tue 30/Jun/2015
2015_06_30 11:25 h1iopsush2b
2015_06_30 11:25 h1iopsush56
2015_06_30 11:25 h1susim
2015_06_30 11:25 h1sussrm
2015_06_30 11:26 h1iopsush56
2015_06_30 11:26 h1susomc
2015_06_30 11:26 h1sussr3
2015_06_30 11:26 h1sussrm
2015_06_30 11:28 h1iopsusb123
2015_06_30 11:28 h1susbs
2015_06_30 11:28 h1susitmx
2015_06_30 11:28 h1susitmy
2015_06_30 11:29 h1iopsush2a
2015_06_30 11:29 h1iopsush56
2015_06_30 11:29 h1susmc1
2015_06_30 11:29 h1susmc3
2015_06_30 11:29 h1suspr3
2015_06_30 11:29 h1susprm
2015_06_30 11:47 h1hpiitmy
2015_06_30 11:47 h1iopseib1
2015_06_30 11:47 h1iopsush56
2015_06_30 11:47 h1isiitmy
2015_06_30 11:47 h1susomc
2015_06_30 11:47 h1sussr3
2015_06_30 11:47 h1sussrm
2015_06_30 12:05 h1iopsush56
2015_06_30 12:05 h1susomc
2015_06_30 12:05 h1sussr3
2015_06_30 12:05 h1sussrm
2015_06_30 12:07 h1iopseib2
2015_06_30 12:07 h1isibs
2015_06_30 12:08 h1hpibs
2015_06_30 12:08 h1hpiham1
2015_06_30 12:08 h1hpiitmx
2015_06_30 12:08 h1iopseib3
2015_06_30 12:08 h1iopseih16
2015_06_30 12:08 h1isiitmx
2015_06_30 12:10 h1hpiham2
2015_06_30 12:10 h1hpiham3
2015_06_30 12:10 h1hpiham4
2015_06_30 12:10 h1hpiham5
2015_06_30 12:10 h1hpiham6
2015_06_30 12:10 h1iopseih23
2015_06_30 12:10 h1iopseih45
2015_06_30 12:10 h1iopsush34
2015_06_30 12:10 h1isiham2
2015_06_30 12:10 h1isiham3
2015_06_30 12:10 h1isiham4
2015_06_30 12:10 h1isiham6
2015_06_30 12:10 h1susmc2
2015_06_30 12:10 h1suspr2
2015_06_30 12:10 h1sussr2
2015_06_30 12:12 h1iopasc0
2015_06_30 12:12 h1ioplsc0
2015_06_30 12:12 h1isiham5
2015_06_30 12:12 h1lsc
2015_06_30 12:14 h1ascimc
2015_06_30 12:14 h1asc
2015_06_30 12:14 h1calcs
2015_06_30 12:14 h1iopoaf0
2015_06_30 12:14 h1lscaux
2015_06_30 12:14 h1oaf
2015_06_30 12:14 h1odcmaster
2015_06_30 12:14 h1omc
2015_06_30 12:14 h1pemcs
2015_06_30 12:14 h1susauxasc0
2015_06_30 12:14 h1sushtts
2015_06_30 12:14 h1tcscs
2015_06_30 12:24 h1iopsush56
2015_06_30 12:24 h1sussrm
2015_06_30 12:25 h1iopsush56
2015_06_30 12:25 h1sussrm
2015_06_30 12:26 h1calcs
2015_06_30 12:26 h1susomc
2015_06_30 12:26 h1sussr3
2015_06_30 12:50 h1lsc
2015_06_30 14:02 h1omc
2015_06_30 14:27 h1nds0
2015_06_30 14:28 h1nds0
2015_06_30 14:36 h1fw0
2015_06_30 15:57 h1broadcast0
2015_06_30 15:57 h1dc0
2015_06_30 15:57 h1fw0
2015_06_30 15:57 h1fw1
2015_06_30 15:57 h1nds0
2015_06_30 15:57 h1nds1
2015_06_30 15:58 h1nds0
2015_06_30 16:06 h1fw1
2015_06_30 16:50 h1broadcast0
2015_06_30 16:50 h1dc0
2015_06_30 16:50 h1fw0
2015_06_30 16:50 h1fw1
2015_06_30 16:50 h1nds0
2015_06_30 16:50 h1nds1
2015_06_30 16:55 h1broadcast0
2015_06_30 16:55 h1dc0
2015_06_30 16:55 h1fw0
2015_06_30 16:55 h1fw1
2015_06_30 16:55 h1nds0
2015_06_30 16:55 h1nds1

H1 SEI
hugh.radkins@LIGO.ORG - posted 09:53, Wednesday 01 July 2015 - last comment - 07:19, Thursday 02 July 2015(19409)
LHO SEI STS2 Update

I reported suspisions about the ETF (Stanford) Seismometer that is now wired up as the STS2-A or HAM2 ground sensor.  That was ten days ago and here is another look from earlier this morning.  Pretty much same conclusion:  The ITMY and HAM5 units show very good coherence even though they are separated by 30meters.  The HAM2 & ITMY sensors are just a couple meters apart and they are no showing the coherence they should: and the HAM2 & HAM5 sensors coherence is similarly poor..

While the problem may be cable or setup (level or igloo rubbing) I suspect the unit itself.

BTL: Any word on these instruments from your experiences?

Images attached to this report
Comments related to this report
richard.mittleman@LIGO.ORG - 07:19, Thursday 02 July 2015 (19421)

If you have it insulated and it isn't rubbing, then it is probably the standard STS needs to get fixed problem, and checked that the feet are locked

H1 PSL
edmond.merilh@LIGO.ORG - posted 09:04, Wednesday 01 July 2015 (19408)
PSL Weekly Report - Past 10 day Trends
Images attached to this report
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 09:01, Wednesday 01 July 2015 (19407)
Morning Meeting

Morning Meeting

Safety Meeting

Happy Holiday!

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 17:47, Tuesday 30 June 2015 - last comment - 17:50, Tuesday 30 June 2015(19402)
CDS Maintenance Summary

h1sush56 18bit DAC upgrade

Dave, Jim

We swapped all 5 DAC cards in h1sush56 with the upgraded firmware versions. The DAC cards were moved within the IO Chassis left by 4 slots to distance them from the new DC power board (D1301004). The 4th DAC card failed its autocal. We replaced this card with a new one, and it also failed autocal. We swapped the 4th and 3rd cards to see if this is a card or slot issue, now the 3rd card failed autocal. We put another new card into the 3rd slot and this time the calibration worked, so two cards which fail autocal have been detected.

h1guardian0 reboot

Dave

I rebooted h1guardian0 because its load average had risen into the 30's. This time the load average started around 12 instead of 7 before, so Ganglia was immediately complaining about overloading. It has since risen into the 20's, so rebooting is now short term relief.

h1sush2b reboot

Jim, Dave

h1sush2b had frozen up around 6pm last night. It required a reboot, which we knew would glitch all Dolphin connected computers so it was delayed until today's restarts. When we rebooted it this morning, we then restarted all corner station SUS, SEI and ISC. This in turn performed the autocal of all 18bit DACs which we indended to do today.

PEM ADC DQ channels

Dave

General ADC channels for occassional PEM work are being written to the frame. I set their gains to 0.0 to ensure they compress out in the frame when not in use. I changed SDF accordingly.

h1lsc new filters

The pending filter module change for h1lsc was applied today after the Dolphin glitch. The filter module H1LSC_SRCLFF has a rolloffs fllter,  which moved from the 5th to 10th location within the filter module.

GRB/SN notification code

Dave

This code has crashed when the offsite networking went down. I upgraded h1fescript0 and restarted the code.

Leap Second

Stefan, Greg, Patrick, Jim, Dave

we tested that the CDS systems handled the leap second addition correctly. All systems did so, but surprisingly conlog crashed (Patrick is investigating). Greg confirmed frames and correct. Dave and Jim check NDS clients dtt and dataviewer.

Comments related to this report
david.barker@LIGO.ORG - 17:50, Tuesday 30 June 2015 (19403)

Clocks on control room wall did not show the 23:59:60 second when applying the leap second. Rather they skewed ahead on second over the following two minutes. The one showing local time did this first, so for about a minute the two clocks differed by one second until the UTC clock caught up.

H1 SUS (DetChar, SUS)
sheila.dwyer@LIGO.ORG - posted 17:45, Tuesday 30 June 2015 - last comment - 10:41, Wednesday 01 July 2015(19401)
MC2 M3 LL zero crossing glitches

I sent a small excitation into MC2 M3 LL last night (29/06/2015 22:37 UTC) and again today after the autocalibration was done (7/1/2015 00:35 UTC). 

The attached screenshot shows the voltmon channel, both before and after.  There isn't a clear difference, it seems like there could be a discontinuity at the zero crossing in both cases, but it is not obvious from the time series if things are better or not after the autocalibration.  

Images attached to this report
Comments related to this report
joshua.smith@LIGO.ORG - 10:41, Wednesday 01 July 2015 (19412)DetChar, SUS

Hi Sheila, looks like your autocal did reduce the glitches somewhat between those two times. In the attached file I used the NOISEMON channels in the frames. But you could also watch the FASTIMON channels during injections from on site (thanks TJ). 

Images attached to this comment
H1 AOS
nicolas.smith@LIGO.ORG - posted 17:30, Tuesday 30 June 2015 (19399)
MICH CPS Feedforward

(jim nic)

We've implemented the ISI CPS -> MICH feedforward (MICH freeze). It was a fairly simple process:

We installed the feedforward coefficients that Ryan suggests in his writeup. These could be re-measured to potentially improve the subtraction.

Then we compared the spectrum of the feedfoward signal and the MICH control signal. We saw a relative gain of 188, so this was added to a filter bank in the feedforward path.

We added a 50Hz low pass to the feedforward path so we aren't injecting too much noise.

When the feedforward path is enabled, we have a reduction in the MICH control signal RMS by a factor of 2-3. See attached figure (reference traces are with FF turned off).

The CPS has a 9Hz feature. Jim says it's from HEPI. This is injected into the MICH control signal, but the change to the RMS is insignificant.

Also attached is the settings of the MEDM screens. Several of these are 'hidden' because they have only been autogenerated and not added to the main screens.

Finally, the easy way to turn on and off the feedforward is by setting the channel H1:LSC-CPSFF_GAIN to 0 (off) or 1 (on). It has a 10 second ramp.

Images attached to this report
Non-image files attached to this report
H1 DAQ (DAQ)
stefan.countryman@LIGO.ORG - posted 17:25, Tuesday 30 June 2015 (19398)
UTC Leap Second Added Successfully in all 3 active Timing IRIG-B Modules
Dave, Daniel

All Timing IRIG-B Modules at LHO are now currently showing the correct number of leap seconds: 17

The leap second was added automatically at 23:59:59 UTC on June 30th, 2015 using the leap second functionality on the IRIG-B.
H1 DAQ (CDS)
james.batch@LIGO.ORG - posted 17:19, Tuesday 30 June 2015 (19397)
Rebuilt daqd for DAQ system, restarted for leap second
Patched ldas-tools-1.19.32 with new leap second data, rebuilt and installed in /opt/rtapps.  Built new versions of daqd for the frame writers, NDS, broadcaster, and data concentrator.  Restarted data concentrator to get new daqd running on the DAQ.  Frames are being written with the correct value for leap seconds.
H1 CDS
patrick.thomas@LIGO.ORG - posted 17:09, Tuesday 30 June 2015 - last comment - 17:31, Tuesday 30 June 2015(19395)
Conlog failed on leap second
Jun 30 16:59:59 h1conlog1-master kernel: [12118377.100031] Clock: inserting leap second 23:59:60 UTC
Jun 30 17:00:11 h1conlog1-master conlog: ../conlog.cpp: 301: process_cac_messages: MySQL Exception: Error: Duplicate entry 'H1:ASC-ODC_CHANNEL_OUTMON-1435708800004681820-3' for key 'PRIMARY': Error code: 1062: SQLState: 23000: Exiting.
Jun 30 17:00:12 h1conlog1-master conlog: ../conlog.cpp: 331: process_cas: Exception: boost: mutex lock failed in pthread_mutex_lock: Invalid argument Exiting.
Comments related to this report
patrick.thomas@LIGO.ORG - 17:31, Tuesday 30 June 2015 (19400)
Restarted
LHO VE
kyle.ryan@LIGO.ORG - posted 17:04, Tuesday 30 June 2015 (19394)
CP2 alarms are response of CDS work earlier in the day (no CP2 delivery today)


			
			
LHO VE
kyle.ryan@LIGO.ORG - posted 17:03, Tuesday 30 June 2015 (19393)
Vacuum activities
Kyle, Gerardo 

Connected LD to HAM6 annulus aux. cart (in parallel i.e. "split" flow) and sprayed audible flow of helium around entire periphery of East and South door outer O-rings pausing for 5 seconds at each leak check slot -> no LD response -> Began pumping HAM6 

Also, backed X-end turbo with LD (LD only, scroll removed) and sprayed new, untested, conflats at X-end with 20 seconds of audible helium flow - OK -> resumed backing turbo with scroll pump
H1 AOS
nicolas.smith@LIGO.ORG - posted 12:59, Tuesday 30 June 2015 - last comment - 17:10, Tuesday 30 June 2015(19383)
H1LSC model changes for MICH Freeze

(nicolas kiwamu jeff)

We will try to implement the MICH freeze technique soon. In order to facilitate this, we made the necessary changes to the LSC frontend model. The ISI model changes were already done by Arnaud a few weeks ago.

We have compiled, installed, and restarted the new model.

It should be noted that the new model will change some of the labeling of LSC input matrix elements. Kiwamu is aware of this and plans to update the Guardian automation code to reflect this.

The detailed changes are below:

We updated the lsc library part from the SVN which includes the new signal paths for MICH freeze feedforward.
The input terminals of the lsc library part had changed, this required shifting many signals to account for a new signal being fed into inputs 10 and 12.
We added the IPC receivers for the signals from the ISI models. These feed directly into inputs on the library model.

Comments related to this report
kiwamu.izumi@LIGO.ORG - 17:10, Tuesday 30 June 2015 (19396)

WP5319

In addition to the update of the LSC frontend model, we also updated the h1omc model in order to make it to the latest (see LLO alog 18707 for detail). In order to do so, we downloaded the lateset common omc and lscomc models from the svn and compiled h1omc with the latest common models in place. We also moved the ETM suminng junctions from the inside of the lsc block to the top level as was done in LLO. For now the ITM outputs are terminated as we do not have IPC senders for them.

As Nic mentioned above, we had to change a few guardian codes such that they are adapted to the new LSC input matrix. I edited the following codes:

  • ALIGN_IFO.py
  • ISC_DRMI.py
  • ISC_library.py

I basically replaced all the old matrix (LSC-ASPD_DOF) by the old style PD_DOF matrix in all the above three codes. We had a chance to test ALIGO_IFO and set it to the MICH_DARK state, which seems to be working fine so far. I did not get a chance to test any other states of ALIGN_IFO or the reset of the two codes yet.

H1 SEI
jim.warner@LIGO.ORG - posted 10:35, Tuesday 30 June 2015 - last comment - 08:36, Wednesday 01 July 2015(19378)
HAM3 23hz line coming from MC2

Hugh and I went to HAM3 this morning to see if we could find the cause of the 23 hz line. Finding nothing at the chamber, we decided to start turning stuff off to see if we could get it to go away. Taking the ISI and HEPI down did nothing, but turning the suspension off made the line go away. I then started turning the SUS back on and as soon as I took MC2 to aligned, the 23hz peak showed up. Jeff said that it was likely the sat amplifier needed power cycled, so Hugh is filing an FRS and this is being handed off to Richard. Attached image shows HAM3 GS-13s between 20 and 30 hz. Red is from last night, when everything was on, blue is everything off, green is MC2 aligned (everything else off).  HEPI L4Cs and both SUS also saw the peak.

Images attached to this report
Comments related to this report
jim.warner@LIGO.ORG - 13:42, Tuesday 30 June 2015 (19385)

After all the restarts earlier and Richard power cycling MC2, the line is gone. See attached. Red trace is from 8 hours ago, blue is from a couple minutes.

Images attached to this comment
richard.mittleman@LIGO.ORG - 07:34, Wednesday 01 July 2015 (19405)

Do we know what power cycling does? how often dows this kind of thing happen?

hugh.radkins@LIGO.ORG - 08:36, Wednesday 01 July 2015 (19406)

Richard--The thought/idea is and maybe there is some way we could verify it, that the satellite amplifier goes into oscillation.

Displaying reports 65601-65620 of 84513.Go to page Start 3277 3278 3279 3280 3281 3282 3283 3284 3285 End