Displaying reports 73301-73320 of 83004.Go to page Start 3662 3663 3664 3665 3666 3667 3668 3669 3670 End
Reports until 23:38, Tuesday 11 February 2014
H1 AOS
evan.hall@LIGO.ORG - posted 23:38, Tuesday 11 February 2014 - last comment - 10:22, Friday 14 February 2014(10006)
Transmon X QPD power budget

[Stefan, Lisa, Kiwamu, Yuta, Evan]

We are trying to center the transmitted X-arm IR on the transmon QPDs, so that we can have an IR alignment reference. The expected power on each QPD is determined as follows:

These numbers give an expected power of 3.7 µW on each QPD.

What we measured was about 600 cts for the sum output on each QPD. We can back out the power on the QPDs as follows:

This gives a power of 4.6 µW on each QPD.

Comments related to this report
evan.hall@LIGO.ORG - 10:22, Friday 14 February 2014 (10099)

[Keita, Yuta, Evan]

Some corrections:

  • The ETM transmissivity for red is 3.6 ppm (from the nebula page). The transmon table has four silver-coated mirrors, each with reflectance between 97% and 98%. Including these factors in the calculation gives an expectation of 2.4 µW.
  • In the measured count calculation, I forgot to include the 45 dB whitening gain and somehow goofed on the final number. Putting in this gain gives a measurement of 2.6 µW.

So the expected and measured numbers are actually much closer.

H1 SYS (INS, ISC, SEI, SUS)
jeffrey.kissel@LIGO.ORG - posted 22:49, Tuesday 11 February 2014 - last comment - 23:20, Tuesday 11 February 2014(10004)
X ARM SEI/SUS Performance Assessment -- Lisa is Pleased
J. Kissel, L. Barsotti, H. Radkins, J. Warner, R. Mittleman

What started out as a conversation of "I don't trust the optical lever calibration. The performance can't be that good" turned into "Wow, if we can hold that performance, ASC might be OK..." Excellent work, Jim, Hugh, and Rich. 

Here're some performance measurements of the H1 SUS ITMX and H1 SUS ETMX as measured by the ISI ST2 GS13s and SUS Optical Levers. The ORANGE shows the current performance, which puts the ITMX and ETMX pitch motion at 20 and 50 [nrad] RMS, and a maximum of 5e-8 and 1e-7** [rad/rtHz] at 0.45 [Hz]. I also attach model predictions for this ORANGE optic motion based on the ISI performance, and we can clearly see the ETMX optical lever spectrum is polluted by length-to-angle coupling and is not reporting the actual motion of the optic, so we should not trust Oplev ETMX as a viable pitch sensor when the ISI is performing as well as it is. 

From here on, we need to work on making sure that this performance is consistent. The ground motion (where my only quick indication in the control room is an 80 hour trend of the microseism BLRMS) was consistent between these two better days, so we need to study the performance over longer periods of time to see where we stand in the face of large ground motion.

-------------

I compare three times:
"Controllers" = Isolation Loop Control Filters; "Blends" Isolation Loop Sensor Blend Filters
(2014-02-14 01:00 UTC) TCrappy 
    ITMX HPI -- "Level 1" Controllers; "Pos" (Position-Sensor-Only) Blends
    ITMX ISI -- "Level 3" Controllers; ST1 "TCrappy" Blends (All DOFs), ST2 "100 mHz" XY, "250 mHz" ZRXRYRZ 
    ITMX SUS -- "Level 2.1" Damping Filters, designed 2013-06-14.

    ETMX HPI -- Level 1 Controllers; Position Sensor Only Blends
    ETMX ISI -- ST1 Level 3, ST2 Level 2 Controllers; ST1 TCrappy Blends (All DOFs), ST2 "100 mHz" XY, "250 mHz" ZRXRYRZ 
    ETMX SUS -- Level 2.1 Damping Filters, designed 2013-06-14.

(2014-02-10 01:30 UTC) TCrappy, PRMI Locked
    I *believe* this time is in the same configuration as ORANGE, but I'm not positive. Note, here ETMX was misaligned because team red was commissioning the PRMI. I show the spectra anyway because it's good to see a "dark" spectra.

(2014-01-23 21:00 UTC) T100_N0.44
    The "best" configuration 2 weeks ago, (from LHO aLOG 9546), before we'd fixed the CPS beat frequency combs (see LHO aLOG 9675), and the 0.5 [Hz] comb from the busted T240 cable (see LHO aLOG 9612)"
    ITMX HPI -- "Level 1" Controllers; "Pos" (Position-Sensor-Only) Blends
    ITMX ISI -- "Level 1" Controllers; ST1 "T100mHz_N0.44" blends on XY and "750mHz" ZRXRYRX, ST2 "750 mHz" on all DOFs.
    ITMX SUS -- "Level 2.1" Damping Filters, designed 2013-06-14.

    ETMX HPI -- "Level 1" Controllers; "Pos" (Position-Sensor-Only) Blends
    ETMX ISI -- "Level 1" Controllers; ST1 "T100mHz_N0.44" blends on XY and "750mHz" ZRXRYRX, ST2 "750 mHz" on all DOFs.
    ETMX SUS -- "Level 2.1" Damping Filters, designed 2013-06-14.

There are several things to note, comparing ORANGE measurements against model:
ITMX (A "wire rehang" QUAD)
- Below 0.6 [Hz], the model is dead-on with the optical lever measurement. With a ~30 [m] lever arm, these ITM optical levers have the smallest longitudinal-to-angle, low-frequency, cross-coupling. Nice! This convinces me (in addition the input spectra I'd modelled in LHO aLOG 9734) that the model is a good predictor for the *real* optic motion in this frequency region. 
- Above 0.6 [Hz], (a) we have no idea what that strange fuzz is, and (b) I think both pitch and yaw are ADC noise limited. HOWEVER, I don't understand why the 1-3 [Hz] sensor noise is not visible, if this is the oplev-noise floor. Perhaps the BOSEM sensor noise is better than the stick-curve I use as the input.
- Notice that the BSC-ISI is meeting or beating the aLIGO requirements at all frequencies in this 0.1 [Hz] to 10 [Hz] band. BOOM.

ETMX (A "fiber" QUAD)
- In pitch, I claim that the only motion that is not an artifact of the optical lever sensing are the two bumps between 1-2 [Hz]. Below 0.6 [Hz], the longitudinal-to-angle coupling fundamental to such a short optical lever takes over, and we see mostly longitudinal motion confused for pitch. The remaining bits of the frequency band are electronics / ADC noise of the optical lever.
- This QUAD model DOES over-estimate the first pitch frequency (it predicts it to be 0.56 [Hz], and we've measured it to 0.51 [Hz]), so this, coupled with the L-to-A coupling, is why we don't predict the first pitch mode well at all.
- In yaw, the model prediction is better, especially below 0.6 [Hz] but the remaining spectrum only show hints of the tips of the resonant features.

About the ISI performance:
- Note that both of these chambers still don't have sensor correction. This might help to improve the performance even further in the 0.2 to 0.7 [Hz] band. Nothing amazing, but perhaps another factor of 2 to 3
- We really need a noise budget of the BSC-ISIs to assess what's limiting us in this frequency range. I still have a gut feeling that we're still getting bitten by tilt noise.
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 23:20, Tuesday 11 February 2014 (10005)INS, ISC, SEI, SUS
The raw DTT performance data was taken with the template:
${SusSVN}/sus/trunk/QUAD/Common/Data/2012-02-12_XARM_PerformanceComparison_ASDs.xml

The data was exported to text files here:
${SusSVN}/sus/trunk/QUAD/H1/ITMX/Common/Data/
2014-02-12_0100_H1SUSITMX_ISIINF_XYZRXRYRZ_asd.txt  in [nm] or [nrads]
2014-02-12_0100_H1SUSITMX_ISIWIT_LTVRPY_asd.txt     in [nm] or [nrads]
2014-02-12_0100_H1SUSITMX_OPLEV_PY_asd.txt          in [um] or [urads]

${SusSVN}/sus/trunk/QUAD/H1/ITMX/Common/Data/
2014-02-12_0100_H1SUSETMX_ISIINF_XYZRXRYRZ_asd.txt  in [nm] or [nrads]
2014-02-12_0100_H1SUSETMX_ISIWIT_LTVRPY_asd.txt     in [nm] or [nrads]
2014-02-12_0100_H1SUSETMX_OPLEV_PY_asd.txt          in [um] or [urads]

These were processed by the following two performance analysis scripts, which are getting closer and closer to an online noisebudget:
${SusSVN}/sus/trunk/QUAD/Common/FilterDesign/Scripts/
performance_H1SUSETMX_20140211.m
performance_H1SUSITMX_20140211.m

From which, all the important bits of the model are save into
${SusSVN}/sus/trunk/QUAD/Common/FilterDesign/MatFiles/
dampingfilters_QUAD_2013-06-14_performance_H1SUSETMX_2014-02-12_0100_model.mat
dampingfilters_QUAD_2013-06-14_performance_H1SUSITMX_2014-02-12_0100_model.mat

I attach ascii files of everything in case you don't want to dig around in the SUS SVN. The Optic Displacement Model files are in the usual LTVRPY order, and represent the total (thick dashed gray in the above model plots).
Non-image files attached to this comment
H1 ISC
lisa.barsotti@LIGO.ORG - posted 21:48, Tuesday 11 February 2014 - last comment - 00:09, Wednesday 12 February 2014(10003)
HOM frequency noise spectra from oplev measurement

Written by Yuta

Xgreen frequency noise spectra from alignment fluctuation (see alog #9429, #9384 for more information) was calculated using oplev spectra of ITMX.
Even if we keep our sideband frequency to be 24.407079MHz and set the demodulation phase to maximize 00 PDH slope, the frequency noise is ~40 Hz in RMS when DC misalignment is 1 urad. Maybe we can work it out without using sideband frequency / demodulation phase tuning technique.

[Method]
1. Get calibrated ITMX oplev spectra (Thanks to Jeff !).

2. Frequency noise from misalignment(HOM) can be written as

fn(t) = k (a(t) + a0)^2

where fn(t) is the frequency noise, k is the conversion factor, a(t) is alignment fluctuation and a0 is DC misalignment. Note that this effect is quadratic and estimated k=1e15 Hz/rad^2 if we keep our setting as is (see alog #9429) and we assume differential angular motion of ITM and ETM.
The spectrum of fn(t) can be calculated using the spectra of a(t) from the following formula.

fn(f) = k^2 * (conv(a(f),a(f)) + 2*conv(a(f),fliplr(a(f)))) + 2*k*a0*a(f)

where conv is convolution and fliplr gives flipped array. conv(a(f),a(f)) gives upconversion term and 2*conv(a(f),fliplr(a(f))) gives down conversion term.
(see this document for derivation if you can read Japanese)

[Result]
1. ITMXOplevspectra.png: Measured ITMX angular motion from oplev. Note that spectra above 0.5 Hz is not measuring the actual motion.

2. HOMfreqnoise_0urad.png: Frequency noise from HOM in the case when DC alignment is perfect. This gives 0.3 Hz RMS.

3. HOMfreqnoise_1e-1urad.png: Frequency noise from HOM in the case when DC alignment is off by 0.1 urad. This gives ~4 Hz RMS.

4. HOMfreqnoise_1e-1urad.png: Frequency noise from HOM in the case when DC alignment is off by 1 urad. This gives ~40 Hz RMS.

Images attached to this report
Comments related to this report
lisa.barsotti@LIGO.ORG - 00:09, Wednesday 12 February 2014 (10007)

Lisa

The idea was to revise the original estimate of the alignment-induced frequency noise between 1064 and 532 by using the actual motion of the test masses, after the improvement in the ISI performance.

H1 ISC
stefan.ballmer@LIGO.ORG - posted 21:22, Tuesday 11 February 2014 - last comment - 07:12, Wednesday 12 February 2014(10001)
Green arm alignment from scratch
Sheila, Stefan

The green arm maximum build-up had been trending down for a while to about 500cts, so we decided to do an arm alignment from scratch today.

Step 1: Baffle PDs
- We used the single shot beam to find the baffle PDs:
         TMS PIT    TMS YAW
  PD1    220.0      -226.7
  PD4    289.3      -288.6
  Center 254.65     -257.6
  
  PD1 is H1:AOS-ITMX_BAFFLEPD_1_VOLTS, and PD4 is actually H1:AOS-ITMX_BAFFLEPD_3_VOLTS 

Step 2: Follow with the arm
- We still had some fringing at the old TMS alignment (P 279.3, Y -245.3 - yes, that's 27urad from the new position...)
- Thus we stepped TMS first in pitch and then yaw, and roughly followed with the ETMX and ITMX.

Step 3: Arm dither: Control ETMX and ITMX instead of ETMX and TMSX
- We changed the feed-back scheme to leave the TMS untouched, and only align the arm to the input beam.
- This was done by feeding back PZT1 dither (DOF2) to ETMX, and PZT2 dither (DOF3) to ITMX.

Step 4: Move PR3 to center the green transmitted beam on the first reference iris on ISCT1.
- The new (good) PR3 alignment is
  PR3 P: -245.0  Y: -253.28

Step 5: Realign the green ISCT1 path
- We aligned the camera (and marked the spot on the monitor), realigned the transmitted green DC PD, and tweaked the COMM beat node up.


With this scheme we got about 915cts of green transmitted light - more than ever.


Step 6 (TBD): Diagonalize the dither drive matrix
- Evan and Yuta will do this soon.
Comments related to this report
stefan.ballmer@LIGO.ORG - 21:26, Tuesday 11 February 2014 (10002)
sheila.dwyer@LIGO.ORG - 07:12, Wednesday 12 February 2014 (10012)

After we realinged the beat note we had -31dBm on the RF mon.

H1 PSL
patrick.thomas@LIGO.ORG - posted 20:47, Tuesday 11 February 2014 (10000)
H1 PSL check
FSS, ISS NOT in nominal range

Output Power is 29.1 W (should be 30 W)
Frontend Watchdog is green
Only warning is 'VB program online'

PMC
locked for 1 day 8 hr
Reflected power is 10% of transmitted

FSS
reference cavity has been locked for 17 min (not good, should be days/weeks)
trans PD threshold is .3 V (not good, should be .9 V)

ISS
Diffracted power is 5.3% (not good, should be 10%)
Last saturation event was 23 min ago (not good, should be days/weeks)
H1 SUS
brett.shapiro@LIGO.ORG - posted 18:51, Tuesday 11 February 2014 - last comment - 09:20, Tuesday 18 February 2014(9999)
ETMX longitudinal modal damping filter installed
I temporarily installed a modal damping filter on the longitudinal degree of freedom of ETMX. The filter has 32 poles, so it is split between two modules, 'md_part1' and 'md_part2'. I plan to measure ringdown times of the test mass tomorrow using the green cavity signal. This is part of an effort to see what are the fastest possible ringdown times of the test mass with top mass damping. After the test I will remove the filters.

Normally a modal damping filter wouldn't need this many poles, but I decided to include the pitch dynamics in the estimator to get a more faithful reproduction of the 1st longitudinal mode frequency for this test.
Comments related to this report
brett.shapiro@LIGO.ORG - 09:16, Tuesday 18 February 2014 (10132)
Measured results taken last wednesday. See the attachment. The damping on each mode was set so that each would ring down to 1/e in about 9 seconds.

The first page shows the measured and modeled closed loop top mass to top mass transfer function with the longitudinal DOF damped modally. The next 3 pages shows the measured and modeled impulse responses of the UIM, PUM, and testmass respectively. The impulse is injected into the top mass with the test excitations, the measurement is taken with the OSEMs at the UIM and PUM and the green cavity at the test mass. The impulse was set so that it was faster the the highest frequency longitudinal mode.

The measurements and model agree quite well. In the ringdowns there is a noticeable phase shift by the end of the 20 seconds because the model has not been fit to the ETMX yet. The cavity measurement also has some extra error becuase the cavity had large drifts and it was difficult to get enough signal without unlocking the cavity.
Non-image files attached to this comment
brett.shapiro@LIGO.ORG - 09:20, Tuesday 18 February 2014 (10134)
Same plots but against the new fit of the ETMY model (and this is actually on ETMX). Also included are the number of seconds it takes to get to 1/e of the maximum.

I also tweaked the modeled pitch damping filter to make the first pitch mode have similar damping to the measurement. I didn't write down what the actual pitch damping filter is, so this is just a guess. This helps the cavity ringdown match the measurement more precisely. The pitch damping has a non-negligble influence on the cavity ringdown, since the first pitch mode is so close to the first longitudinal mode.
Non-image files attached to this comment
H1 SUS
brett.shapiro@LIGO.ORG - posted 18:45, Tuesday 11 February 2014 (9998)
SR2 system identification measurements
Brett and Andres

In an effort to get more data to improve sus models, we locked the top mass down on SR2 and measured spectra of the lower two masses. We then locked the middle mass down and measured spectra on the bottom mass. The data has been committed to the svn at .../sus/trunk/HSTS/H1/SR2/Common/Data.

I will process this data and see if it gives us a model that matches this suspension more accurately.
H1 SEI
hugh.radkins@LIGO.ORG - posted 18:32, Tuesday 11 February 2014 (9997)
ISI States

All ISIs are in Control Lvl3 except for ETMX Stage2 which is in Lvl2.  All Blends are TCrappy where available(only ETMx & ITMx) except for ITMX Stage2 is at 100mHz (Jim--should this be TCrappy?)  The ITMY & BS has 750mHZ blends on Stage 2.  For the BS & ITMY Stage1, T250mHz blends everywhere except the X & Y dofs have T100mHz_0.44 for BS and T40mHz_NO.44 onthe ITMY.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 17:58, Tuesday 11 February 2014 (9995)
Added new h1lscaux model to the CDS/DAQ system
Kiwamu created a new h1lsc0 model called h1lscaux. I have added it to the h1boot system and the DAQ. The DAQ was then restarted. 
h1lscaux was restarted to get the awgtpman to startup.
H1 DAQ (CDS)
david.barker@LIGO.ORG - posted 17:17, Tuesday 11 February 2014 (9994)
DAQ Restart
17:11PST, restarted DAQ against modified susaux models and latest Beckhoff ini files (4 channels added to c1plc2). Found that the models h1susaux(ex, h34) needed a manual start due to burt button not pressed quickly enough.
H1 SUS
arnaud.pele@LIGO.ORG - posted 17:16, Tuesday 11 February 2014 (9987)
SUS monitor channels added to frame/science frame #WP 4179

Today I finished up modifying the SUS monitor models as it has been deployed at LLO in december (alog 9964 and alog 10010), under ECR 1300261 in order to add the voltage and noise monitors in the frame + science frame for each individual osem. The following models were modified, recompiled, and commited to the svn :

h1susb123 (bs, itmx, itmy) rev 7070
h1susauxh2 (mc1, mc3, prm, pr3, im1, im2, im3, im4) rev 7087
h1susauxh34 (mc2, pr2, sr2) rev 7072
h1susauxh56 (srm, omc)  rev 7074
h1susauxex (etmx, tmsx)  rev 7083
h1susauxey (etmy, tmsy) rev 7085

Details of modifications are specified below :

For the quads :

M0/R0 Noisemon was changed from 1024 to 512Hz
M0/R0 Voltmon was changed from 1024Hz to 256Hz
L1/L2 Noisemon were created at a rate of 1024Hz
L1/L2 Voltmon were created at a rate of 256Hz

For the triple suspensions :

M1 M2 M3 Voltmon added at 256Hz
M1 Noisemon added at 512Hz, M2 at 1024Hz and M3 at 2048Hz

For the IMs and OMCs

M1 Voltmon added at 256Hz
M1 Noisemon added at 512Hz

For the TMS :

M1 Voltmon added at 256Hz
M1 Noisemon added at 256Hz

LHO General
patrick.thomas@LIGO.ORG - posted 17:10, Tuesday 11 February 2014 (9973)
Ops Summary
Fire department testing smoke detectors

09:15 Mike L. taking Kim on tour through LVEA, end Y
09:39 Jim B. upgrading GDS tools (WP 4432)
09:56 - 11:50 Mitchel R. cleaning up in LVEA west bay
10:31 Jaclyn S. to squeezer bay
10:35 Dave B. running OS updates on cdsssh, cdslogin, lhoepics
10:56 - 11:23 Stefan B. restarted h1odcmaster model, which crashed the h1oaf frontend and killed mxstreams. Dave B., Jim B. recovering
11:21 - 12:45 Joe D. working on PCAL assembly in H2 PSL enclosure
11:48 LN2 delivery ~10 min away
12:01 Jaclyn S. and Alexa S. to end Y to look at electronics
13:01 - 13:36 Justin B. to end Y to look at conditions for moving table in
13:03 Kris cleaning at end X
13:14 - 14:40 Karen at end Y
13:32 HVAC repair for chiller unit in MSR
? - 16:13 Mitchel R. cleaning up in LVEA west bay
X1 DTS
james.batch@LIGO.ORG - posted 16:48, Tuesday 11 February 2014 (9993)
Configuration changes for testing h1odcmaster
We are testing the h1odcmaster on the DAQ test stand, this has required that the H1.ipc file be replaced with a copy of the one from the h1 system (with host names changed from h1 to x1).  The previous H1.ipc has been saved as H1.ipc.11feb2014.  This will be restored when we are finished troubleshooting.
H1 ISC (ISC)
corey.gray@LIGO.ORG - posted 16:33, Tuesday 11 February 2014 (9981)
TMS-EY Alignment Work

(Corey, Doug, Keita, Yuta)

X-Translation Push

Started off the day securing the TMS with "hard stops" and installing (7) teflon-tipped dog clamps on the TMS Upper Structure & Pusher in preparation for our horizontal translation of ~6.5mm to the "left".  Doug watched us as we pushed the entire assembly this distance.

Yaw Alignment

After the big move, we then set up to fix the yaw of the structure.  This took a few iterations, because we noticed that after we Yawed and looked good, we would back off the Pusher and see that the structure springed back a little.  So we had to figure out how to overshoot and then have it spring back to nominal.  Once Doug was happy here, we torqued down all the Dog Clamps (25ft-lbs) and moved to pitch.

Pitch Alignment

The TMS was then freed up, balanced, and prepared for pitch work.  The back end of the TMS was seen to be pitched UP, so Yuta and I moved the TMS Table Counterweights toward the back, and we were able to get the Table pretty flat according to Doug.

Clean-Up & Tomorrow

So with this alignment, with a 0.0 Pitch & Yaw bias, we had a most excellent alignment of the TMS.  Doug and Jason were excused and we worked on finishing clean-up:  remove all Pusher hardware, re-install/torque removed Dog Clamps, re-adjust BOSEMs to new alignment, and then put TMS on EQ Stops.

NEXT UP:  Install tooling to secure the TMS for Cartridge insertion.

Images attached to this report
H1 SUS (CDS, SUS)
patrick.thomas@LIGO.ORG - posted 14:28, Tuesday 11 February 2014 (9989)
Arnaud restarting sus models
h1susauxb123
h1susauxh2
h1susauxh56
h1susauxh34
h1susauxex
h1susauxey
H1 ISC
patrick.thomas@LIGO.ORG - posted 13:20, Tuesday 11 February 2014 - last comment - 14:49, Tuesday 11 February 2014(9985)
Filiberto and Aaron ISC cabling at HAM6


			
			
Comments related to this report
patrick.thomas@LIGO.ORG - 14:49, Tuesday 11 February 2014 (9990)
Done.
LHO General (CDS, PEM, PSL)
patrick.thomas@LIGO.ORG - posted 17:40, Monday 10 February 2014 - last comment - 14:15, Tuesday 11 February 2014(9964)
Lighthouse LMS Express 7 crashed
This is the commercial software controlling the Lighthouse particle counters in the H1 PSL enclosure.

Logging into h0dust (Windows 7 Pro SP1 64 bit virtual machine) through VNC this afternoon I found the error message in the attached pictures.

I found two related events under Event Viewer (Local) -> Windows Logs -> Application on 2/7/2014 11:02:01 AM. The text of the errors is attached.

Searching for related information I found the following: http://support.microsoft.com/kb/2640103
Images attached to this report
Non-image files attached to this report
Comments related to this report
cyrus.reed@LIGO.ORG - 14:15, Tuesday 11 February 2014 (9988)

It looks like the LMS software install includes the .NET 4 runtime, but it was probably out of date at install.  4.5.1 is available through Windows Update, I would assume it includes the fix mentioned in the KB article (since it's over a year old now), but I haven't been able to confirm what's included in the update.  It's probably the first thing to try though, but it means downtime for the updates to install.

H1 SEI (SEI)
hugo.paris@LIGO.ORG - posted 15:38, Monday 10 February 2014 - last comment - 15:23, Tuesday 11 February 2014(9955)
HAM ISI Command Scripts Work Again

HAM3-ISI tripped recently and needed to be turned back on. Commissioners noticed that the command buttons were not working anymore.

It turns out that someone ran an SVN update on the following file: /opt/rtcds/userapps/release/isi/common/scripts/HAMISItool, which was to be updated along with new models, screens and scripts, after testing at MIT. Having a model/script mismatch, the command script would be looking for inexistent channels, and fail.

I reverted HAMISItool to -r5830. This script should not be updated from the SVN again, until the latest HAM-ISI update gets propagated.

HAM3-ISI was turned back on with Isolation Lv3 and 01_28 blend filters. Target values were not changed to ensure returning to previous alignment.

Comments related to this report
hugo.paris@LIGO.ORG - 10:53, Tuesday 11 February 2014 (9980)

The WD plotting software, which lives in the same folder, had stoped working too. It turns out that the related scripts were updated too, while they should not have been yet.

I reverted opt/rtcds/userapps/release/isi/common/scripts/wd_plots/ to -r6477, and the WD plotting software works again.

arnaud.pele@LIGO.ORG - 15:23, Tuesday 11 February 2014 (9991)

My bad, I updated the directory before modifying BSCISItool !

Displaying reports 73301-73320 of 83004.Go to page Start 3662 3663 3664 3665 3666 3667 3668 3669 3670 End