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.
After the reboot noted above, Fabrice and I started a fresh Matlab from the iMac at the SEI Test Stand. After this, I checked the memory usage, and had the following:[controls@seiteststand ~]$ free -m
total used free shared buffers cached
Mem: 7986 4303 3682 0 97 2615
-/+ buffers/cache: 1590 6395
Swap: 1983 0 1983
So here, matlab has been running for ~10 min. I ran this command immediately after opening and the "free memory" was 4400 and then 4000. It seems to be leveling out at 3400 as we are now running a measurement in matlab.
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.
I have concluded my updates. The following was updated: * The login code is no longer hardwired with the server name (portability fix) * Increased spacing between reports to improve readability * Removed the 'Logged in as' text to help all the controls fit better in the upper portion of the screen * Made some modifications to the css and html to layout the quick keyword and task search a little better * Added a self referential link to each log entry * Updated the login logic to again display user and password entry boxes when not doing apache (Shibboleth/LIGO.ORG in our case) authentication (portability/bootstrap fix) * Updated some minor bits of apache configuration to ensure all http requests are properly redirected to https I had hoped to address Corey's author name issues, however Corey and I were unable to reproduce the problem today. In the next set up updates I hope to have a more comprehensive fix in place. Also I will work with Dave Barker to add another color scheme so that LLO & LHO can be differentiated easily.
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).
Entry above was made by Corey Gray (When I'm logged in, not sure why I have to enter the "author name" every time I do something here).
[Corey, Hugh, Jim, Mitchell] Back in business! After about 90minutes we had a new H3 ready to go. Like I said it wasn't trivial. It took 3 people garbed up inside working for 90minutes. There are also tons of bolts which had to be dealt with--always scary because one always has the fear of possibly galling a bolt. But yes, once the GS13 was securely installed, one could clearly see that its signal on Dataviewer was much better (and more like H1 & H2). The table is probably not ideally level (due to the swap work), but went ahead and ran a high-resolution power spectrum [attached], and the results clearly point out a better looking H3. As for the old H3 GS13-- * When was it last tested? (right before it was sent up?) * What should we do with this GS13? (send to LLO?) * Do we have any more spares? (we just have one Vertical spare now)
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.
Both machines are loaded with Sol 10. h2daqfw1 had some bus errors from one of the PCIe cards on first boot, which I'll have to investigate more closely when I return from vacation after the Jul 4 holiday. Re-seating cards may help if the issue persists. Also still to do is add non-root accounts to h2daqfw0/1, configure iLOM, configure the switches in the rack (verifying first that we actually have the correct switches installed), basic network throughput tests, etc. A current stab at a (test) IP numbering scheme is as follows: 172.17.0.1/24: h2daq test stand 172.17.0.1/28: Routers, switches, gateways 172.17.0.17/28: DAQ Servers Currently assigned: 172.17.0.1: (Reserved for default route(r), not installed) 172.17.0.18: h2daqfw0 172.17.0.19: h2daqfw1
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
H2 is back baby! Added tag "H2 DAQ" for the construction of the aligo H2 DAQ rack in the MSR.
The electronics test racks for seismic testing at LLO are through the initial setup and checkout. There are two racks. llosei1 - HAM-ISI testing llosei2 - Seismometer huddle testing David Kinzel assembled the racks, installing the equipment shipped from Pasadena and Hanford. Keith and Rolf got the front-end computers set up. Ben and Sam Abbott were here this week to do the electronics checkout with the initial models. The test racks are presently on the CDS network, but are reachable from outside at llosei1 - llocds.ligo-la.caltech.edu Port 9001 (DNS name dts1 within llocds) llosei2 - llocds.ligo-la.caltech.edu Port 9002 (DNS name dts2 within llocds) * We clearly need some X2 tasks added
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).
The screenshot I tried attaching above didn't seem to work (it was a .tiff screen shot from a Mac & was treated as a quicktime file when I tried clicking it from the log). Attached here is a .jpg version of the same file. Hopefully this works.
I am attaching a Power Spectrum from last week. It looks like H3 was fine. Also, looking at the time series, it seems that there is some signal, but much lower (about two order of magnitudes on the power spectrum). Could it be a BIO filter improperly switched?
Are Fabrice's spectra with the table locked, and Corey's without? The high-frequency (>10 Hz) structure has changed dramatically on *all* the sensors between those two spetra. If these two spectra were taken with the table in the exact same state, then this might be another clue...
(Vincent L., Richard M., Corey G.) There is no BIO for the SEI Test Stand. And yes, it should be noted that the spectra from Fabrice's post was from a couple weeks ago. It was a quick one we ran with the SYSTEM LOCKED (we were performing a quick check to investigate the 0.3Hz signal on the Displacement Sensor Mini-Racks). So, it was wrong for me to say everything looked good from that spectra--I had assumed assumed the ISI was un-locked. Last Friday, we performed a few more checks on the GS13. The most telltale check was a cable swap. From the "feedthrough interface", the GS13 Horiz/Vert cable runs to the H/V location. Here is a connection to a plug which splits into two separate cables--one goes to the Horiz GS13 & the other goes to the Vert GS13. We unplugged the H3/V3 cable here, and ran it to the H1/V1 cable. Dataviewer showed that the problem stayed with the H3-GS13 (i.e. H1 was now ugly). Therefore something is wrong with H3 GS13. Reconnected cables to their original configuration. As another check, we locked up the Table and ran another power spectrum [attached]. Sure enough, we had similar results to what we saw a couple of weeks ago (i.e. Fabrice's post)---where all the spectra, for the most part, look similar. Thinking their may be a mounting issue, or something wrong with the mechanical structure of the GS13 inside, we will take a look for any rubbing in the area of H3/V3. We'll then take off the H3 door, and perform some checks on H3 (while watching with DV & quick spectra).