Some questions about look-back times for framed data served by our internal NDS servers have been asked recently, so for the record here are the current look-back times for each type of frame
nds | science frames | commisioning frames | second trends |
nds0 | 02 days 04 hours | 10 days 12 hours | 25 days 12 hours |
nds1 | 02 days 11 hours | 10 days 21 hours | 24 days 11 hours |
data was obtained by the script /opt/rtcds/userapps/release/cds/h1/scripts/report_daq_framewriter_lookback_times.bsh
TITLE: 04/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Recovering
INCOMING OPERATOR: Travis
SHIFT SUMMARY: PSL work looks to be done, now trying to recover the IFO
LOG:
15:00 JeffB to LVEA to lock 3IFO cabinet, back 15:15
15:00 PeterK to PSL Jason at 15:45, out 17:30
15:30 JeffB and Fil to Diode room
15:45 Ed to LVEA to take a picture
16:00 JeffB to CER/Diode Room
18:30 Peter Jason to PSL, out at 20:00
22:00 Sheila to IOT1
I have restarted the DCS Disk2Disk scripts using their standard configuration, with CDS fw0's filesystem as the primary source of frame data and CDS fw1's filesystem as the backup source of frame data, for DCS archiving of raw (science), second-trend, and minute-trend data. (The primary and backup source of data had been switched temporarily earlier this week due to DCS maintenance.)
The Temperature spike at the ENDY did give the BRS a jostle but it seems to have recovered as has the temperature.
The attached trends are 2 days of the BRSY position, velocity, VEA temp, ground seismo Y, wind and the BRS DRIFTMON. To me, the most interesting thing is the ring up in the BRS signals near the beginning of the traces likely related to the seismic spike seen. I suspect this is a VEA entrance that got pretty close to the BRS (stick to the sides if you can rather than the ends of the enclosure.) This ring up was still not quite enough to trigger the damping so no too bad and you can see how long it takes to ring down without the capacitive damping.
Also, late in the trends, one can see the winds start to pick up and it kicked the BRS enough to trigger the damping--the velocity hit 3000. Maybe we'll need to bump up the damping threshold??
Hugh, you are likely right on both counts. The ring-up was very likely a person going close to the BRS box and yes, the high threshold could be set a bit higher at 4000, to prevent trigerring the capacitive damping during wind-speeds below~35-40 mph.
The ideal solution to this problem would be if we could figure out a way to keep the damping at Q~50 without adding noise. We failed to do this during our trip (see 26596, 26465), most likely because one of the capacitors was shorted, which we realized too late. If we changed the damping scheme it may be possible to have it constantly damped. Worth thinking about more.
Yesterday I installed a Sorenson power supplt into the rack I placed in the closet in the LVEA. It was connected to the fuse block and powered up. After testing for the proper voltages/polarities at the drops, power was connected to the Beckhoff interlock modules and visual confirmation of function was confirmed. The total current draw for 7 of these units, as they currently sit under power, is approximately 600µA.
Why are we installing a noisy switching supply in the LVEA? These Sorensons were banished for a reason...
They were not banished. Some issues were attributed to them and we removed them. This unit powers a digital system and is far enough away from sensitive systems based on measurements done for PSL UPS on the floor.
All time in UTC:
00:29 Chandra to Mid X.
00:40 Chandra back
00:56 Chandra going back out.
Chandra back shortly after.
06:00 Everybody's gone home. I'll end my log here.
Fewn notes:
- No commissioning tonight.
- Jamie paused DIAG_SDF Guardian node because we're not using it and it's saturating the log.
- Changed PSL RS calibration -- "Power in" changed from 56 W to 52 W (got this from last night observation), minimum angle from -25 to -23 (also from observation), min power from 1 to 0 (observation), wave number from 1 to 2 (it should have been 2 all this time).
- Added a new CO2 rotation stage graphics for my own amusement. Will likely be your amusement too once it's working.
- CP6 alarm is still going off.
It looks like the chilled water pump CWP1 at EY tripped off at ~5:00 pm this evening. For some reason the second chiller has not started so I have restarted the tripped water pump. Hopefully this will make it through the night.
I only got a verbal alarm for the high EY temperature. FMC alarm handler didn't go off (I looked after I heard the verbal alarm so I thought the high EY temp was part of the daily temp fluctuation and didn't think to look further). This is not very good.
I put back the links to the old screens and added links to the new Beckhoff screens.
I have updated the control room alarm handler configuration file to match the move to Beckhfoff controls at MX and MR. The alarm handler has been restarted to use it. The configuration file is '/opt/rtcds/userapps/release/cds/h1/alarmfiles/ve.alhConfig'. It is in svn at 'cds_user_apps/trunk/cds/h1/alarmfiles/ve.alhConfig'.
After 15 hrs, CP6 finally registers a real value on the liquid level read back. Currently at 98.5%. I opened the Dewar valve and set the LLCV to 55% (normally runs between 60-65%). I'll be here for a while working on CAD drawings so I'll monitor it.
Magnehelic reads a hair over 40 in. H20 (maybe 40.4?) when liquid level reads back 97.8%. Ratios match what we expect!
Raised LLCV to 57%.
Raised level to 60% valve open (liquid level reads 85.7%).
I was going to manually fill CP6 a bit before I left, but the bypass valve is frozen shut. Liquid level is 80.5% in the red, but LLCV is set to its normal value of 60%. Should be good and ready for some Beckhoff PID action in the morning.
75% @ 0240 hrs. local
Today I modified CDS to use the new Beckhoff MR vacuum controls channel names. I verifed that my procedures for this are correct. Procedures are in the wiki page:
https://lhocds.ligo-wa.caltech.edu/wiki/MigratingVacuumControlsCdsFromVmeToBeckhoff