Displaying report 1-1 of 1.
Reports until 12:26, Monday 17 June 2013
H1 CDS
david.barker@LIGO.ORG - posted 12:26, Monday 17 June 2013 - last comment - 15:38, Monday 17 June 2013(6776)
status of the burt restore safe.snaps

During the recovery of the front end models I took the opportunity to review the status of the safe.snap files.

Of the 79 models, we had 19 safe.snap failures (24%).

here is the list of the failed models

Missing safe.snap files:

h1iopsusauxb123, h1susauxb123, h1susauxh2, h1susauxh34, h1isitst, h1hpiitmy, h1hpibs, h1hpiitmx, h1isiitmx, h1hpiham1, h1susauxey, h1asc

safe.snap files out of date:

h1susim, h1hpiham3, h1isiham2, h1isiham3, h1iscey

Also noted that some safe.snap files are not links to svn files but static files within the target area. Presumably these are not under svn control, here is the list:

h1hpiham6, h1isiham6, h1hpiham2, h1hpiham3,  h1hpiham4, h1hpiham5, h1isiham4, h1isiham5, h1pslfss, h1lsc, h1ascimc

NOTE, apologies, the hpi isi ham4,5,6 are hard linksed to their SVN files.

Comments related to this report
hugo.paris@LIGO.ORG - 15:38, Monday 17 June 2013 (6778)

I updated the safe.snap files for h1hpiham2 and h1hpiham3. Hard links were reset and checked OK.

I made a snafe.snap for h1ihpiham1, and the related hard link. 

Those snap files were commited under the svn:
h1hpiham1  -r4746
h1hpiham2  -r4747
h1hpiham3  -r4748

 
The safe.snap files of h1isiham2 and h1isiham3 need to be updated, to account for the recent addition of the oplev. I would need to turn the control off of those ISIs to update the safe.snap which cannot be performed without pertubating HIFO-Y. I will hold off for now.
Displaying report 1-1 of 1.