Displaying reports 45481-45500 of 88335.Go to page Start 2271 2272 2273 2274 2275 2276 2277 2278 2279 End
Reports until 12:50, Tuesday 25 September 2018
H1 SEI
jim.warner@LIGO.ORG - posted 12:50, Tuesday 25 September 2018 (44141)
Prototype Common Mode ground code added to H1OAF model

After the install of the new long range RFM, Dave and I have worked on adding channels and code to calculate common mode ground motion, to eventually use for improving earthquake lock robustness. Right now both endstation ISI's are sharing their ground beamline supersensor (gnd sts - brs), ground Z, ETM suspoint length and St1 beamline CPS. The first two channels are needed for the common mode calculations, the suspoint is used for the OAF suspoint cavity length calculations. I don't know what the CPS is used for, but I kept it in the list of channels being shared. Previously all 4 of these channels were shared via muxing through the endstation PEM models, but only the suspoint channel was being used for anything. I've now added some code to the OAF to take the corner and endstation ground seismometers and calculate common mode ground velocities (i.e (ex_z+ey_z +cs_z)/3= site-wide common mode z ground motion). The plan is to eventually take these cm signals and subtract them from the ISI sensor correction and only isolate the platforms from the local differential motion, but that will require more invasive ISI & HEPI model changes. Attached screen shot shows the section I added to h1oaf. I also added 3 256hz dq channels for the cm x/y/z outputs. After Dave restarts the models I'll throw together an MEDM for the filter banks. The plan for now is to just figure out how to get the common mode calculations right and get data to try some offline subtractions.

Images attached to this report
H1 GRD (CDS)
thomas.shaffer@LIGO.ORG - posted 12:45, Tuesday 25 September 2018 - last comment - 13:17, Tuesday 25 September 2018(44142)
h1guardian1 rebooted

Rebooted the machine at 18:54 UTC (11:54 PST). All nodes naturally recovered except SUS_IM4 and SUS_ETMX. These nodes did not time out like we have seen in previous reboots, due to the timeout duration being extended (alog44092). Instead, the logs show that the nodes started and then stopped after "terminate called after throwing an instance of 'int'". I'm not sure where this error is coming from yet. A restart of the nodes recovered both.

Screen shots of the status logs and grd logs of the two failed nodes are attached.

Images attached to this report
Comments related to this report
thomas.shaffer@LIGO.ORG - 12:57, Tuesday 25 September 2018 (44143)CDS

Also, zotws20 cannot run many of the guardctrl commands. I ssh'd into zotws6 and "list -s" ran just fine. They are both running Debian 9.5. but the kernal release and version are different:

zotws20 = 4.9.0-7-amd64 | #1 SMP Debian 4.9.110-3+deb9u1 (2018-08-03)

zotws6 = 4.9.0-8-amd64 | #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21)

Attached a screen shot of the error.

Images attached to this comment
jameson.rollins@LIGO.ORG - 13:17, Tuesday 25 September 2018 (44144)

This has nothing to do with the kernel.  I'm not sure if it's related, but I note that the site environment variables are not being set appropriately on this machine.  In particular the GUARDCTRL_HOST variables is not being set properly to point to "h1guardian".  This might be a red herring, but after setting the variable correctly I can see the listing fine:

jameson.rollins@zotws20:~ 0$ GUARDCTRL_HOST=h1guardian guardctrl list
ALIGN_IFO
ALS_COMM
ALS_DIFF
ALS_XARM
ALS_YARM
BRSX_STAT
BRSY_STAT
DIAG_CRIT
DIAG_EXC
DIAG_MAIN
DIAG_SDF
FAST_SHUTTER
HIGH_FREQ_LINES
HPI_BS
HPI_ETMX
....

H1 ISC
stefan.ballmer@LIGO.ORG - posted 11:48, Tuesday 25 September 2018 (44140)
Some ALS debugging
Danny, Hang, Stefan, Daniel

Daniel hooked up two IFR function generators to simulate the ALS DIFF and COMM beat notes.

1) Just injecting a lot of noise (up to 100kHz broadband) into ALS_COMM did not produce enough cross-talk - only about 1/200 of the injected signal in COMM shows up in DIFF (plot 1)

2) However, when we started to simulate COMM noise by lowering the beat note strength enough that the PLL started missing beats, the noise also showed up in DIFF at about 1/4th the strength (about the ratio we see when COMM locks) (plot 2).

3) In situation 2, changing the COMM PLL feed-back gain actually reduced the noise coupling - I don't know whether that was already tried with the arm signal.


In all plots, the references are from arm locks yesterday. The COMM is always noisy (brown). DIFF has a noisy (dark blue, COMM locked) and a quiet (black, COMM unlocked) reference.
Images attached to this report
H1 AOS
david.barker@LIGO.ORG - posted 08:32, Tuesday 25 September 2018 - last comment - 15:17, Tuesday 25 September 2018(44138)
h1lsc0 crash at 3am, bad DAQ data from various front ends

At 10:08 UTC (03:08 PDT) it looks like h1lsc0 kernel panic'ed. Strangely we are getting bad DAQ data status from a strange collections of machines (all end stations which are on dolphin, corner ISC and susauxb123!) see attached image.

h1lsc0 console is showing a kernel panic error (I'll post it later).

I'll recover all systems execpt LSC before we start today's upgrade.

Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:46, Tuesday 25 September 2018 (44146)CDS
Opened corresponding to FRS Ticket 11528. Likely we can quickly close the ticket, since the system has been recovered, but I leave it open for Dave to comment as he sees fit.
david.barker@LIGO.ORG - 15:17, Tuesday 25 September 2018 (44149)

Here is the list of things I did until I was able to reset the DAQ status of these front end machines:

h1susauxb123: start streamers

h1lsc0: power computer down (after disabling its ix-dolphin switch port)

DAQ: restart

h1susauxb123: computer reboot. This system came back with no errors

h1asc0: computer reboot: This system came back with no errors

At this point, I could fix the DAQ mx stream on all the other models just by issuing a /etc/start_streamers.sh command.

H1 PSL
peter.king@LIGO.ORG - posted 08:29, Tuesday 25 September 2018 (44137)
Laser status
Entered the enclosure to find the status screen indicating that the NPRO had fainted however
the NPRO power supply indicated that the NPRO was on and the laser was up and running.  Not
sure what the discrepancy is due to.

    I left things the way they were.
Images attached to this report
H1 General
peter.king@LIGO.ORG - posted 08:13, Tuesday 25 September 2018 (44136)
LVEA transitioned to LASER SAFE
The LVEA has transitioned to LASER SAFE.

    This is under work permit #7836.

    A note in passing ISCT6 and SQZT6 doors I locked closed.
H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 22:22, Monday 24 September 2018 (44135)
158MHz VCO locks to beat note

Daniel, Nutsinee

Today we installed a phase frequency discriminator chassis (U7 on SQZ rack near ISCT6). The pump/PSL beat note RF signal and 158MHz LO went in and the output went to OPO common mode board. We unplugged the PZT output and only used the fast path error signal to feed into the 158MHz VCO. The 158MHz VCO now follows the beat note frequency. Here's a quick look at the control signal. More noise hunting+modeling is required to be able to pinpoint where all of them came from. We suspect temperature to be responsible for low frequency noise.

 

Sadly locking at 0 Hz beat note doesn't mean high 3MHz peak when using PSL LO. A feed forward from IMC land is required. A model has been modified to sum the OPO fast control signal with this feed forward signal and the output will go to the OPO PZT somehow (don't remember what we decided on). Once this is complete then we can work on the 3MHz hand-off.

 

Images attached to this report
H1 AOS
stefan.ballmer@LIGO.ORG - posted 21:11, Monday 24 September 2018 (44134)
trouble handing off DRMI_TO_POP
We started having trouble handing off in DRMI_TO_POP.

- The symptom is a ~10000ct offset in H1:LSC-POP_A_RF9_I_NORM_MON just before hand-off.
- We checked all the phasing of POP9 and REFL 9,27,135 - they all look reasonable.

- However the whole thing seems to be related to a CARM fringe offset. The offset only appears when switching CARM_TO_ANALOG.
- Moreover, while sitting at the end of CARM_TO_ANALOG, we jiggled the common mode board gain, and suddenly the offset dropped out. I am suspecting some sort of saturation in the common mode board might be the culprit for this one.


H1 ISC
stefan.ballmer@LIGO.ORG - posted 20:25, Monday 24 September 2018 - last comment - 20:33, Tuesday 25 September 2018(44133)
SOFT loop engagement now smooth for arbitrary large initial position offsets
The SOFT loop engagement has in the past always been a source of trouble, mostly because the initial offsets can be really big. Together with the double-integrator design (in control filters and suspension top stage filters) this usually is a recipe for disaster.

This should now be a thing of the past:

- re-ordered the filter modules to keep the switchable integrator and lead filters ahead of the always-on low-pass (see alog 44124).
- Set error point limiters before the control modules, but after the input matrix (in the blend filters) to 0.02.
- During engagement only a 0.1Hz pole integrator in FM5 (along with the DC gain, inverted plant and 10Hz LP in FM1, FM9 and FM10) are on. Plot 1 (red traces) show the total control filter frequency and step response. After this filter, we still have a gain of 2.5 and the suspension top stage 1/f integrator.
- Thus, during engagement with limiters on, the max signal to the suspensions can only be
   0.02 (limiter) x 10000 (control filter) x 2.5 (gain) = 500 cts
  This is small enough that the suspensions don't run away. Instead they perform a constant velocity move to shrink the SOFT error signals.
- The Guardian then looks for
   a) convergence of the SOFT control signals below 100cts, and
   b) convergence of the SOFT error signals below 75% of the limiter (or 0.015)
  When these conditions are met, Guardian turns the limiters off and turns on the true integrator and lead filter (changing the transfer function and step response to the blue trace in plot 1).
- Finally, after waiting for the 10 sec filter ramp time of the lead filter, Guardian turns up the gain to the nominal values of 4 for DSOFT and 6 for CSOFT.

Plot 2 shows the turn-on sequence for all SOFT control and error signals
Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 20:33, Tuesday 25 September 2018 (44159)
Here is another run of the new SOFT engage code. Worked flawlessly. Also, we once tried it with the final gains (4 & 6 respectively). That worked too.
Images attached to this comment
H1 General (CDS, ISC, SEI, SQZ, SUS)
jeffrey.kissel@LIGO.ORG - posted 17:30, Monday 24 September 2018 (44131)
SDF Reconciliation for CDS boots tomorrow- Take 2

(Betsy, for Betsy and Kissel)

This afternoon, Kissel and I embarked on the second round of SDF house cleaning. With the IFO set to down for a short bit, and after enlisting help from commissioners, we resolved most changes in the SAFE files. Things that were "interesting" yet accepted:

- New Test Mass L3 LOCK P/Y FM7 Stop27 filter (commissioners needed to add this along with last week's Stop28 filter but this still needs to be sorted out)

- Accepted new IMC PZT offset, but these will likely need to change during the subsequent lock due to hysteresis (if this model goes down, currently not expected to)

-Quite a few ALS settings accepted or reverted (Sheila was surprised just now to find that the ALS COMM PLL OFFSET slider was unresponsive...)

- Sheila and Kissel found that the PRM M2 Coil Driver state and the M2 Lock Output SW SDF settings were saved in the wrong state so were accepted (correct state: coil driver in State 3 and output OFF)

- OMC DCPD Gains found in the unbalanced state so fixed (both A and B gains set to 1000)

But the weirdest was:

- Some strangeness in the SDF setpoints for LSC REFL RF9 Phase and ITM Baffle PD Gains/Offsets (on different PLCs!) which stated that the settings were changed within a few minutes of Sept 19 13:49, yet the SDF as-found EPICS values were correct. So we accepted the correct values. No one in the room could confirm these older setpoints, but we did find an alog (44064) pointing to SDF model work around that time...

We also accepted all of the optic DRIVEALIGN offsets (alignment sliders) so that restore should go smoothly.

It's as reconciled as it's gonna get for tomorrow's CDS boots of LSC, ASC, SUS.

LHO VE
kyle.ryan@LIGO.ORG - posted 17:23, Monday 24 September 2018 (44130)
~1615 hrs. local -> Started Vertex turbo pump (Near HAM5)

Prep. for leak testing tomorrow

H1 CDS
david.barker@LIGO.ORG - posted 17:01, Monday 24 September 2018 (44129)
Removed non-existant channels from GDS broadcast list, added channels for WP7832

The process of adding channels requested by WP7832 to the GDS broadcast list requires removing old channels some of these new ones replace. I took the opportunity to scan the complete channel list in H1BROADCAST.ini and found that 20 channels no longer exist in the running DAQ (most don't exist, some are commented out in the INI files). These were removed from the file.

WP7832 adds 16 new channels to GDS. These will be installed during tomorrow's DAQ restart.

H1 AOS
thomas.vo@LIGO.ORG - posted 16:37, Monday 24 September 2018 (44128)
HWS Spherical Power w/ Past 14 Days

Below is a table where we compare the readings on the HWS with different CO2 and RH lensing which ideally should be the same if the amount of CO2 actually corrects the applied amount of ring heaters.  There are a few caveats to the measurement though, the ITMX HWS are particularly sensitive to the beamsplitter's pointing (long term and short term drift).  But what this tells us is that the step down in common lens brought the spherical power closer to the "cold" state before any TCS was applied which maybe makes sense on why the PRC gain got better after Stefan made an adjustment.

TCS Configuration

ITMX HWS Spherical Power

(udiopters)

ITMY HWS Spherical Power

(udiopters)

Before TCS Work -13.0 -15.0
50 Watt Preloading (RH + CO2) -20.0

-13.0

25 Watt Preloading (RH + CO2) +2.0 +20.0
25 Watt RH but reduced CO2 common Lens -12.5 +10.0
Images attached to this report
H1 General
jim.warner@LIGO.ORG - posted 16:13, Monday 24 September 2018 (44114)
Shift Summary

16:45 Nutsinee to ISCT6

18:00 Dave power cycling BS gige cam in CER

19:15 Peter Betsy to LVEA

19:15 JeffK taking pictures of PSL racks

20:30 Kyle to LVEA

20:30 Ed to HAM7 area

 

 

 

H1 CDS
david.barker@LIGO.ORG - posted 16:07, Monday 24 September 2018 - last comment - 16:21, Monday 24 September 2018(44126)
new h1build machine built

A new RCG3.4.3 build machine (same name of h1build) has been built. In the new system the build machine is a diskless front end sans hardware. The original disk'ed h1build machine, which runs the Slow Controls SDF faux-models, has been renamed h1ecatmon0.

The controls password for the build machine is in shared secrets LHO CDS controls Password

The build directory is /opt/rtcds/lho/h1/rtbuild/current

 

Comments related to this report
david.barker@LIGO.ORG - 16:21, Monday 24 September 2018 (44127)

I shut down the old h1guardian0 machine this morning (its HDD has been saved). The intent was to reuse this V1 computer for the new h1build, but I was not able to diskless boot it (possible BIOS changes needed) so I ended up reusing its rack slot and cables, and used the old h1iscex V1 machine which was removed last Tuesday for the build machine.

H1 SQZ (SQZ)
nutsinee.kijbunchoo@LIGO.ORG - posted 13:39, Saturday 22 September 2018 - last comment - 20:14, Monday 24 September 2018(44102)
OPO now locked to pump/PSL beat note

Daniel, Nutsinee

The OPO is now locked to pump laser/PSL beat note with beat note error signal (from TTFSS preamp) goes to input of the OPO common mode board and 158MHz to common mode board LO. We bypassed the PZT driver box completely to reduce the gain to the OPO PZT (PZT driver box has a gain of x22, and a pole at 400Hz). 10Hz low pass filter was added between OPO common mode board output and in-vac PZT driver to give it a low frequency roll-off, which (according to the sketchy writing on the box) attenuated the signal by a gain of 10. Haven't looked at the spectrum or transfer function (will add that to the comment later). A stable beat note frequency is needed for 3MHz locking (with PSL being an LO).

 

Problem: It will lock +-50kHz sideband instead of 0Hz beat note frequency. Next step is to try using a PFD instead of an IQ demod.

Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 20:14, Monday 24 September 2018 (44132)

Correction: The error signal and LO went into an IQ demod board and the output of that went to input of the common mode board. 

H1 TCS (TCS)
thomas.vo@LIGO.ORG - posted 11:32, Friday 21 September 2018 - last comment - 15:45, Monday 24 September 2018(44087)
RH and CO2 Cool Down

There's been a lot of wondering about the CO2 alignment relative to the center of the optic so we decided yesterday afternoon we decided to step down the CO2 X/Y and look at the centering, and then overnight we stepped down the Ring heaters on both X and Y.  Attached are the contour plots showing that the centering isn't that different between X and Y, but Jenne pointed out that Y is not as good as X, it's off in yaw and so we can probably do more optimization there.  However, this does not capture the effect of miscentering the IFO beam on the test mass which from this ALOG shows that the IFO beam is quite a bit different from the center as well.

Images attached to this report
Comments related to this report
georgia.mansell@LIGO.ORG - 15:45, Monday 24 September 2018 (44125)

I wanted to compare the spot positions according to the Hartmann, for the ring heater (test mass geometric center), CO2 beam, and IFO beams. All of this information is already on the log but I wanted it in one image, see dodgey screenshot of screenshots attached.

It seems like on ITMX the CO2 and ring heater beams are somewhat concentric, but the IFO beam appears ~2cm off in pitch (2 uncalibrated-hartmann-basis cm). I'm not sure how reliable this measurement of the IFO beam centering is: it disagrees with the spot position measurements we did on friday which suggested we are more off center in pitch than in yaw.

On ITMY the CO2 seems better aligned to the IFO beam than the ring heater, but all 3 are slightly different. These miscenterings might contribute to the astigmatism seen with the CO2 lasers are on.

Images attached to this comment
Displaying reports 45481-45500 of 88335.Go to page Start 2271 2272 2273 2274 2275 2276 2277 2278 2279 End