Strange - another chilled water pump trip - this time in the corner. CWP3 VFD unit tripped. I reset the 480volt circuit (pushed the reset button, did NOT cycle the breaker).

The pump started up with no issues. Currently I have left the system with two CWPs and their associated chillers running. Both CWP1 and CWP3 are running. I happened to be in the control room when Jeff reported an alarm The LVEA is recovering from a ~0.5 F temperature excursion.

PSL Status: 
SysStat: Green 
Output power: 35.9w  
Frontend Watch: Good
HPO Watch: Red  

PMC:
Locked: 0 days, 0 hours, 28 minutes
Reflected power:    4.9w
Power Transmitted: 19.9w 
Total Power:       24.7w 

FSS:
Locked: 0 days, 0 hours, 28 minutes
Trans PD: 0.003v

ISS:
Diffracted power: 12.831%
Last saturation event: 28 minutes 

Rolf, Jim and Dave. We have created RCG tag 2.8.5 from branch 2.8. This version has the bug fix to disable the 18bit DAC Anti-aliasing chassis when the new timed DACKILL part is activated. 

2.8.5 also has two dataviewer changes, these have already been installed at LHO by Jim prior to this release.

I have set the rcgcore and lho/h1 release pointers to use 2.8.5. All model builds from now on will use this release.

JimW JeffK HughR

We looked at HEPI TFs from March and this morning and see almost no differences.  Comparing TFs beween EndY & EndX also sees almost no differences either.

However, see the attached comparing the Isolation filters at the endy (Blue) and endx (Red).  Mag & phase both are quite different at our 8hz problem area.

Cleaning crew reports the emergency lights are on in the LVA at End-Y. Have informed John W. Will check if there is an open circuit breaker left over from Fridays power glitch.  

Kiwamu and Dave. Installed new LSC model, then restarted the DAQ. We had an NFS caching issue, even giving a period of at least 15 seconds between the  make-install and the restart, the model had cached the old INI file and we did not get the expected DAQ status of 0x2000. After verifying that the INI had indeed changed, we restarted the model once more and the new INI file was picked up by the model. 

After BSC1 closeout on Friday, undamped transfer functions were ran over the week end on the beamsplitter for both top and middle stage. During the measurement the ISI was damped. Measurements are clean, as seen on the results attached. For some reason a factor of two-ish appeared in the M2 level tf (model=2ish*meas) in all dofs.

Attached results are presented as below :
 
1. H1 M1-M1 undamped tfs compared with the model
2. H1 M2-M2 undamped tfs compared with the model
3. H1 M1-M1 undamped tfs compared with previous H1 BS measurement (last month, after wire baffle install), and L1 in vacuum
4. H1 M2-M2 undamped tfs compared with previous H1 BS measurement (last september, under vacuum), and L1 in vacuum
 

All scripts and data have been commited to the svn

I left the ISI just damped with the HEPI loops closed.  SEI tripped at 2027pdt.  The ISI went on L4C levels 2 seconds before the HEPI tripped for Actuators...  Maybe this makes sense compared to the previous trips where the ISI trips earlier wrt the HEPI when at least one stage of the ISI is isolated--when the ISI is isolating, it rings up its actuators faster as it drives in response.  Again, clear 8ish hz ring up on all the HEPI/ISI signals.

Looking at the TF/Coh between HEPI out & ISI L4C as expected there is coherence; the magnitude of the TF is reduced with the X & Y HEPI ISO Boosts are disabled.  Wait that makes sense as the ISI isolation is quieting the L4C...

Tested enabling the boosts.  Independently enabling either X or Y boosts rings up and trips the ISI within a minute or so.  While there is no foton magnitude difference between ISOL filter with and without boost, there is a 20 degree phase difference.

Given that the trip happens with just ISI damping and the boost seems to hasten things when the ISI is Isolated, JeffK recommends check for plant changes at ETMY HEPI.

J. Kissel, A. Pele

Ran transfer functions over the weekend, to assess if the SUS is free after first contact removal and closing doors. While the top stages look great, this is the first time I've been exposed to a factor of two missing between model and measurement for the lower stages. While we don't expect the model to account for the dynamics of the reaction chain (which is why we see a whole bunch of "extra" features in the main-chain dynamics), we don't expect an overall gain mismatch. Arnaud informs me that this is true of every QUAD except one stage of one (including L1 SUS ITMY). 

No reason to pull doors off, but we should figure out where this discrepancy lies. And also , we should develop a model of the lower stage dynamics which include both chains.

The mid-X weather station stopped running about 22:36 PDT Saturday Aug. 2.  Thunderstorms were reported in the area at the time.  Will need to visit MX to determine what the problem is.

LVEA:
	Viewport and deionizer Gate Valve survey and work on LVEA in preparation to pump down.
		Gerardo found three Viewports with scratches that will need to be replaced. 
	Kyle is doing a general readiness vacuum survey in LVEA.
	There will be a chamber close out checklist review in the control room today at 13:00.
	The Ameristat/C3 covers will need to be removed from around the HEIP piers at the BSC and HAM chambers. 

HAM6: 
	The north door will be removed for alignment and ISI work.
	The ISC table to be reinstalled on the north side.   
  
OpLevs:
	Jason working on the X-Arm Viewports. 
EE:
	Cabling work at HAM6. 
End-Y:
	Work on Rai’s deionizer experiment equipment installation. 
End-X:
	Apollo to torque bolts on BSC9 door. 
	Chamber close out review.
	Need to install gate valve for deionizer. 

J. Kissel, J. Batch,

Jim informed me this morning that other front-end models, seemingly unconnected to my h1isietmx model restart, had their framebuilder data corrupted immediately following my restart. Hence all frame data from these computers has been hosed since 2014-07-31 22:45 UTC. See Jim's complementary log here.

The corruption is a result of an mxstream glitch sent out by h1isietmx upon restart, that was sent across the ethernet connection to other computers on the same ethernet network (i.e. h1sush2b, h1oaf, h1pemmy, h1pemmx, h1susey and h1lsc). This is a known problem at least by Jim (who will subsequently write a bugzilla report).

To identify the problem:
- Open CDS_OVERVIEW screen
- Look for models / computers that have *both* the DAQ (Data AQuisition system) and the DDC (Daq Data Concentrator) showing red status in their CDS STATE WORD, (e.g H1:FEC-103_STATE_WORD).

To solve the problem:
- Log into corrupted front-end
- run /etc/start_streamers.sh
This reboots the mxstream process, occasionally glitches the framewriting PSL front end (?!), presumably fixes the problem, and restores the STATE WORD to green.

Restart mx_stream on the following front ends:

H1sush2b - models h1iopsush2b, h1susim
h1susey - models h1iopsusey, h1susetmy, h1sustmsy
h1oaf0 - models h1iopoaf0, h1pemcs, h1oaf, h1tcscs, h1odcmaster
h1lsc0 - models h1ioplsc0, h1lsc, h1lscaux, h1omc
h1pemmy - models h1ioppemy, h1pemmy
h1pemmx - models h1ioppemmx, h1pemmx

The streams were corrupted by the model restart of h1isietmx on Friday Aug. 1 at 1545 PDT, so data from these models is likely not valid over the weekend.