cut-paste from David's email 03:07 30/6/2010

1) Threads, displayed as a tree format so that you can follow threads, with the 
tree organized either alphabetically or by date (and with filters for author, 
entry age, etc.), one could follow what has been written in a recent thread 
about the system they are working on and then add another entry to that thread. 
No need for users to type a matching keyword, since the "Add Entry To This 
Thread" does that automatically. One would like to be able to title a thread -- 
this could just be the first entry title, but it would be useful to be able to 
edit that to cover the thread content and to make it easier to search for

2) searching across the installations (certainly LLO and LHO) is needed. I think 
it would be neat to be able to search the Virgo Cascina installation as well -- 
that is a question of international politics, I suspect. We would need a 
pull-down list to know which one(s) were being searched, and would want to be 
able to identify several or all.

3) reduced Recent Author list for searches, and autocompletion on author names, 
ideally making reference to the recent author list to order options

4) can an individual's input and search settings be remembered for the next 
login from that individual? Hugh works on SEI at LHO -- would be a nice way to 
get things on the right foot. Could be a big thing software wise, but would 
reduce a lot of the effort in getting going.

5) notifications: ability to put in aliases here (maybe trivial, could be 
maintained elsewhere), but would allow subsystems and the team to be notified 
for certain entries

SNS has these 'features'; are there some we want to plan to integrate?

   1.

      BulletIntegrates with work orders -- if nothing else, having all work
      orders appear as logbook entries would be quite valuable, I think.

   2.

      BulletGroup notification, daily orders and required readings

   3.

      BulletUser bookmarked entries

Also, one can filter at the view page by ordered posting time, author, or 
priority, a nice feature.

Their initial data message entry keyword/category input looks like this.



I think something like this would be very good for us; sounds like a database 
dimensionality question, though, so to be resolved soon if so. Breaking things 
down into more columns seems attractive.

entry types: Progress (default), Problem, Repair, Maintenance, Status

Categories:
Safety (might want to impose notification to all recent authors, or all authors, 
or something for this entry?)
QA
SYS
IOO
PSL
SUS
SEI
COC
AOS
ISC
DAQ
DCS
FMP
INS

Location: L1, H1, H2, LHO, LLO, MIT, CIT, Other

Priority: Urgent, high, normal (default)

Added "bug" task to the "Logbook Admin" section. Seems that putting
the "B" word in the title causes it to be displayed differently?

 HTML tag is not WYSIWYG
			
			


		
		

When using the PRE html tag to preserve the formatting of a block of text,
additional lines are added to the text.

DB and CG.

killed g1hamisi and g1x01, then rebooted the frontend computer
to clean up its memory [boot performed at 13:50]

DAQD would not run because it needed awgtpman present, so changed daqdrc
to allow running with no awgtpman (otherwise just kept spawning).

Started g1x01 and g1isiham, burt restores worked ok.

Mem usage at this time is (free -m):
[controls@seiteststand ~]$ free -m
             total       used       free     shared    buffers     cached
Mem:          7986       2406       5579          0         82       1062
-/+ buffers/cache:       1262       6724
Swap:         1983          0       1983



Also copied the epics bin area from CDS to the /opt/apps/epics binary directory, but
StripTool does not work.

This messages was sent to cds-software and lsc-sei.

I will be updating the aLOG this morning during the maintenance period.
 I will be working on the system starting at 11am Pacific.  It is
expected that I will be done by 11:30am Pacific.

This update will be a minor one which brings the code into a state where
it is portable between LLO & LHO in anticipation of LLO using this
software.  I will begin adding requested features next week.

If you are working on a log entry and are not ready to submit it by that
time, please save it as a draft (Click the 'save to draft' button).
Your entry will be stored and you will be able to finish editing it later.

It has been shown there have been issues with our H3 GS-13.  Before pulling out the GS-13, the ISI table was visually checked for mechanical shorts (none were found).  As another system/pod check, the ISI table was tilted in a couple of different states(by placing weight on table) such that the pod would be angled "down" & angled "up".

H3 is unique in that it is the GS13 whose axis is perpendicular to the Support Tubes (vs. H1 & H2 who are symmetrically angled wrt the Support Tubes).  For our set up, the "crane-Southern" Support Tube is the side where the "TOP & unfixed" end of the H3 GS13 is.  The "crane-northern" end of the GS13 is where the "BOTTOM & bolted-down" end of the GS13 is.  Because of this geometry, it was easy to put weight on the table such that we tilt the TOP or BOTTOM of the GS13.

With the TOP tilted down, we did not notice any change in the H3 performance (we were looking at DataViewer, the signal looked noisy, and would only show big seismic bumps and then quickly damp that out, and return to the noisy state).  

With the BOTTOM tilted down, H3's performance totally changed---for the better.  H3's signal looked like its fellow H1 & H2.  A Power Spectrum confirmed that H3 looked like the other GS13s when the BOTTOM was tilted down.  The attachment's top plot shows the GS13s with the ISI weight down on the Northern end of the table.  The bottom plot shows a balanced & unlocked ISI from last week (where we had an ugly H3).

After this, we decided to swap this GS13 for our one & only extra Horizontal GS13.  For documentation, there is a Serial Number on the base flanges for these guys.  

Original/old H3 GS13 is S/N 046
New H3 GS13 is S/N 068

Will post performance of our new H3 after the swap is made (not a trivial or quick task).

Removed entries for awg and tp from /opt/rtcds/geo/g1/target/gds/param/diag_T.conf file as general cleanup.  The lines were unneeded for description of awg and tp services, the awg and tp services are established and registered with diagconfd when awgtpman is started from the startup_g1x01.cmd and startup_g1isiham.cmd scripts.  Any awg or tp entries in the diag_T.conf file would be at best duplicates.

Jonathan wrote a cronjob on alog to create two backup files daily: sql dump file
of the text content and compressed tar file of the graphical files.

I just wrote a cronjob, which runs on control100 within CDS, to scp these files
into /data/backup/alog every morning at 05:30. From there they are rsynced to 
the CDS backup disk, and then written to tape.

This backup scheme will be replaced with rsync later because the graphical file will
get very large very quickly.

The H2 DAQ rack is a new style (beige) rack located in the MSR nearest
the hallway. It has two Sun X4270 computers, which will be the H2 DAQ
frame writers/QFS masters.

Cyrus is working on installing sol10 on these systems. He will also test the
DAQ networking switches and spare units using this rack.

We encountered a problem with the rack mount KVM switch in this rack, the internal
power connector to the PCB is flakey. The flatscreen monitor signals this with
a "cable not connected" error and powers itself down.

added the following sus tags (as requested by Betsy)
X1 SUS QUAD
X1 SUS BS/FM
X1 SUS HSTS
X1 SUS HLTS
X1 SUS OMC
X1 SUS IOAUX

Today, dtt was used to obtain spectra for the LHO HAM ISI Assy #1 located at the SEI Test Stand.  This measurement was run with the dial indicators disconnected.  Two measurements were run:  The first one ("T1") had H1V1H2V2 Displancement Sensors & ALL GS13's.  The second measurement ("T2"), had H3V3 Displacement Sensors.  Two measurements were needed because of the ~0.3Hz noise seen between both Displacement Sensor "mini-racks".

One blaring feature (see attached spectra) is the H3 GS13---something looks amiss with it.  Checked the rack for anything obviously wrong, but all HAM Interface Chasis looked fine.

Vincent suggested putting a 300count vertical offset on the H3 Actuator, and this clearly showed something wrong with this GS13 (see attached screenshot).