Displaying reports 45341-45360 of 84848.Go to page Start 2264 2265 2266 2267 2268 2269 2270 2271 2272 End
Reports until 14:05, Wednesday 21 February 2018
H1 SUS
filiberto.clara@LIGO.ORG - posted 14:05, Wednesday 21 February 2018 - last comment - 17:48, Wednesday 21 February 2018(40642)
ITMY UIM

While closing out the recently replaced SUS ITMY R0 RT OSEM (alog 40634), found short on UIM chain. Short is on cable SUS_ITMY_16, pin 5, cathode side of LED for UIM UR.

Comments related to this report
betsy.weaver@LIGO.ORG - 17:48, Wednesday 21 February 2018 (40651)

Sheila and Kissel have confirmed that this UIM UR LED is not used (and would be a much larger scope to fix).  So, we have opted to save this fix for a future  fix.  Attached shows the spectrum of all of the L1 and L2 stage OSEMs for ITMY - you can see the elevated noise on the black L1 UR trace.

Images attached to this comment
H1 SUS
betsy.weaver@LIGO.ORG - posted 14:01, Wednesday 21 February 2018 - last comment - 08:11, Friday 23 February 2018(40641)
BSC1 ITMY OSEM signal fix, logistical details

This morning, Kyle and Bubba finished removing the door to BSC1.  I entered the chamber and began poking the ITMY R0 Right BOSEM cable from the OSEM connection out through the structure to the Table Cable Bracket.  No change.  I then also tried all of the following which produced no improvement to the spectra:

- Reseating the cable in the Table Cable Bracket

- Unbundling the cables that were secured to the upper structure leg

- Reseating the cable on the BOSEM itself

- Swapped the RT cable with the Side - problem went away - which meant that the problem was the BOSEM itself.

Removed BOSEM from structure and attempted to find short on the unit - no luck.  Swapped unit which meant removing it from it's adjustment bracket and rebuilding before reattaching.

Once back on the structure found it was OK.  Set OLV and 50% flag setting.

Cleaned flooring, removed tools, looked for cable routing issues in case I undid some other nice work.

Left chamber.  Kissel ran a few TFs which showed healthy.  Fil checked for HIPOT on the ESD connection and started another rounf of ground loop checks.  Tacked up door.

 

Comments related to this report
jeffrey.kissel@LIGO.ORG - 08:11, Friday 23 February 2018 (40679)
Pictures of BOSEM to aide discussion.
Images attached to this comment
H1 SEI
patrick.thomas@LIGO.ORG - posted 13:44, Wednesday 21 February 2018 (40640)
H1 ISI CPS Noise Spectra Check - Weekly
FAMIS 6938

The script reports: "ETMY_ST2_CPSINF_V1 high freq noise is high!"

The following appear elevated:
ITMX_ST2_CPSINF_V1
ITMY_ST1_CPSINF_V2
ITMY_ST2_CPSINF_V2
BS_ST1_CPSINF_H1_I
BS_ST1_CPSINF_V2_I
BS_ST2_CPSINF_H2_I
BS_ST2_CPSINF_V1_I
BS_ST2_CPSINF_V2_I
HAM3_CPSINF_V1
Images attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 12:53, Wednesday 21 February 2018 - last comment - 13:14, Wednesday 21 February 2018(40638)
ETMY Hardware Watchdog Tripped on LED fault condition

This is just a FYI for future re-enabling of BSC10 ISI, the EY HWWD tripped after an LED fault persisted for more than 20 minutes. The fault condition has subsequently been removed, however the ISI trip is latched (ISI coil drivers are powered down) until such time the front panel reset button on the HWWD chassis is pressed.

Comments related to this report
david.barker@LIGO.ORG - 13:14, Wednesday 21 February 2018 (40639)

I've added more detail to the HWWD section of the CDS Overview MEDM (see attached). Each HWWD status color bar now has two elements. The left element turns RED if either PD or LED fault condition is active. The right element turns RED if the ISI system is tripped.

The left element can transition between RED and GREEN if the faults come and go. If the right element is RED, it can only be made GREEN by pressing the RESET button on the chassis itself.

I've also included a related display button to open the HWWD MEDM directly. Note that macro substitution rules requires the SITEMAP to be reopened for the button to work.

Images attached to this comment
H1 CAL (CAL)
richard.savage@LIGO.ORG - posted 12:26, Wednesday 21 February 2018 (40637)
EndY Pcal beams misaligned

TravisS and RickS

Yesterday, we switched on the Pcal laser at Yend to check the alignment of the beams after the replacement of the ETM.

With the ETM in the nominal alignment according to the optical lever, we found that the Pcal beams at the Rx side are badly misaligned, one beam actually missing the relay mirror.

This is likely due to either a) the ETM not being properly oriented or b) the Pcal periscope orientation having shifted during B&K measurements or the addition of vibration dampers back in January.

We plan to investigate early next week, going inside the vacuum envelope and installing the Pcal target on the ETM suspension structure.

H1 SEI
hugh.radkins@LIGO.ORG - posted 12:05, Wednesday 21 February 2018 (40636)
FRS 9477--HAM6 corner3 again noisy

See alogs 39484 to start, this covers the corner3 CPS laying on the rail and attempts to clear it.  It seemed okay after in chamber work on  30 November, alog 39579.  However, as I look again in an effort to close the ticket, it looks like while the position has not shifted (like it was doing before,)  the noise on the channel has increased.  The increase is not causal with door removal and the other corners' sensors do not show any similar time series noise expression.  This corner3 CPS satellite box is maybe the most vulnerable to proximal activity and there is of course the 5-way cross installation complication. Dang!  I will change the FRS status from PENDING to what ever it should be now.

The attached 120 day plot shows the HAM6 CPS local sensors.

Images attached to this report
H1 SUS
jeffrey.kissel@LIGO.ORG - posted 11:57, Wednesday 21 February 2018 - last comment - 12:00, Wednesday 21 February 2018(40634)
H1 SUS ITMY R0 RT OSEM Replaced
J. Kissel, B. Weaver

Far more details to come, but we've replaced the H1 SUS ITMY R0 LF OSEM in order to fix the noise / shorting problem (see LHO aLOG 40555, FRS Ticket 9683, Work Permit 7358). It's new open light current values are 

         Open Light Current / ct     GAIN          OFFSET
         (as ADC Counts)             (30000/olc)   (-olc/2)

R0 RT    29804                       1.007         -14902

I've accepted the new values in the SDF system.
Images attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 12:00, Wednesday 21 February 2018 (40635)

Serial number 466 was removed and serial number 298 was installed.

H1 SUS
filiberto.clara@LIGO.ORG - posted 11:56, Wednesday 21 February 2018 (40633)
ITMY ESD HIPOT

Following yesterday's work on BSC1 (alog 40622), we tested the ITMY ESD cables with the HI-POT tester. All pins were tested to 1KV and passed.

H1 CAL (CAL)
aaron.viets@LIGO.ORG - posted 11:38, Wednesday 21 February 2018 - last comment - 11:39, Friday 09 March 2018(40631)
Improved High-pass Filter in gstlal calibration pipeline

After a lot of experimentation, I have found a way to improve the attenuation of frequencies below 9 Hz in the calibration by 1-2 orders of magnitude, without significantly increasing the computational cost or latency of the pipeline. Here is a list of what I've changed and what I've kept the same:

Of all the things I tried, this is what worked the best. Reasons I did not make this even better include:

Several plots are attached to show the new features. The first 5 plots are the frequency responses and comparisons to the ideal models for each of the filters used. The last 3 plots are comparisons of C01 data with data produced using the new filters. The attenuation is better by about 1-2 orders of magnitude, and there is just a very small amount of ripple added below 20 Hz.

Images attached to this report
Comments related to this report
aaron.viets@LIGO.ORG - 06:22, Thursday 01 March 2018 (40780)

I have made some additional improvement in the high-pass filtering in the DCS filters. The additional changes I made were:

  • Addition of a separate high-pass filter in the inverse sensing path before the inverse sensing filter. This also uses Matlab's least squares FIR filter, firls(). The cutoff frequency used is still 9 Hz, although I experimented with other cutoff frequencies. The filter is designed to have a response that drops to zero at 5 Hz and below. The length of this filer is currently set to 0.75 seconds.
  • Shortened inverse sensing filter to 0.75 seconds. The inverse sensing filter was previously 1 second in length. Since DARM_ERR is filtered at 16 kHz, the total amount of filtering in this path (now increased from 1s to 1.5s) needs to be kept manageable.
  • The actuation filter and the high-pass filter before it are now both 3 seconds in length.
  • In addition to the filers themselves, I have added code that writes the transfer functions corresponding to the combined effect of all filters applied to each path (inverse sensing and actuation). These are included in the filters files, so that they cannot be incorrectly paired with the wrong filters. In the DCS filters files, the names of these numpy arrays are invsens_filt_tf, tst_filt_tf, and pumuim_filt_tf.  In the GDS filters files, the names are: res_corr_tf and ctrl_corr_tf.
  • I also added a numpy array in the filters files that contains the filters' approximated response function. In both DCS and GDS filters files, this is called filters_response_function. In the GDS case, this gives only the portion of the response function that is applied by the GDS filters, not including the front end.

A similar set of plots is included, with several additions:

  •  I have implemented a new test of the filters that combines all the filters in the inverse sensing and actuation paths to show how well they approximate the model response function. A larger-than-expected error shows up above 1kHz where the contribution from the actuation filters drops to zero. I'm not yet sure why this is, but I'm not too concerned since it does not show up in the other response function plots, described next
  • I have also used a modified version of Maddie's response function plotting script to make plots of the response function as derived from the transfer function between DARM_ERR and DeltaL_free, and compare this to the model response function. (These are the last 3 files.) Errors from 10 Hz to 5 kHz look comparable to what they were before these changes. Note the small ~2% error just above 1kHz - this is due to the fact that the actuation is downsampled to 2 kHz in the gstlal calibration pipeline. At ~1kHz, the TST stage actuation still contributes a few percent to the total strain, leading to this ~2% error when it gets lost in downsampling. Notice also the few % error just above 10 Hz. There is a similar feature in the filters response function plot (described above), and in the PUM/UIM stage actuation filter.

It's also worthwhile to remind ourselves of the list of reasons why we wanted to improve this filter/what we wanted to improve:

  • Search groups prefer aggressively high-passed data. Hopefully this is sufficient, as doing much better would significantly increase computational cost.
  • Apparently the noise below 10 Hz has added to the difficulty of the data-cleaning effort. (?)
  • It is ideal, when data goes public, that people don't find anything that could be mistaken for something significant below 10 Hz.
  • There may sometimes be a need to model the high-pass filters in the gstlal calibration pipeline. Although common IIR filter representations like Butterworth, Chebyshev, and elliptic filters can be implemented as FIR filters, they are generally not the most effective. It takes a lot of taps to get a good filter; so it is more effective to use a different method (like minimizing the integrated squared error) to get the best filter we can for the lowest computational cost. Thus, the solution I propose to this problem is to use the transfer function that I have added into the filters files.
  • There has been concern about the error around 10 Hz seen in the inverse sensing filter in these GDS filters and similar ones. GDS filters I've produced with the new high-pass filter do not show this behavior. However, as noted above the PUM/UIM stage filter does seem to introduce ~1% error just above 10 Hz. It is not clear whether this is related to high-pass filtering, but it is worth investigating.
Images attached to this comment
aaron.viets@LIGO.ORG - 11:39, Friday 09 March 2018 (40925)

After further investigation, I've found that the the noted ~1% errors in the PUM/UIM stage filters just above 10 Hz are most likely due to notches in the actuation models at those frequencies, and do not seem to be affected by the high-pass filtering. One way to get rid of those errors is to remove the time-domain Tukey window from the filters. However, this generates a lot of noise in the spectrum due to the fact that the filters do not fall off smoothly.

I also found that the "shelf" seen at low frequency in the ASDs (the noise from DC to ~0.25 Hz) may be an artifact of the relatively low frequency resolution (I used 3-second FFTs, so 0.33 Hz resolution) in the calculation of the ASDs. I have produced another ASD from the same data using 64-second FFTs averaged over 12 hours. The "shelf" is not seen here. I also investigated the possibility that this is a DC component (in which case it would still be present in the new ASD I plotted, but not shown due to the higher resolution). I added a feature the the gstlal calibration pipeline that allows the option to remove a DC component from the data before filtering it. The method is to simply downsample the input data to 16 Hz (with high-quality anti-aliasing), take a running average of 16 seconds, and then upsample (with high-quality anti-imaging) and subtract the result from the input data. This can be done with zero latency by shifting the timestamps becuase the phase of a DC component is zero regardless of timestamp shifts. The result of removing the DC component before filtering was indistinguishable from not removing it, implying that this is not a DC component.

The attached plot shows a high-resolution spectrum comparison of C01 data to data produced using the new high-pass filters.  There appears to be a line present around 3 Hz.  The small differences between C01 and the new DCS data above 10 Hz are due to the fact that the kappas were not applied in producing the new data (I used the same data to produce the comparison to the modeled response function, which requires not applying the kappas).

Images attached to this comment
H1 SEI (ISC)
hugh.radkins@LIGO.ORG - posted 11:22, Wednesday 21 February 2018 (40632)
EndX Xend EX ETMX BSC9 HEPI Locked on Stops

WP 7364 -- Locked EndX HEPI this morning, pretty close to operating position, Z not so much.  Will leave this WP open until the HEPI is unlocked.

ETMX found in ISI DAMPED HEPI OFFLINE.  Took SEI guardian manager to DAMPED--this took the HEPI to Robust Isolated.  The HEPI was then locked onto its stops as closed to the Isolated position as possible: dX dY dRX dRY are all under 10um(urad), and dRZ is less than 200nrads. dZ is 83um but I figured this was the least significant dof for the upcoming task.  These di values are the difference from the nominal isolated position.  HEPIs for the BSC don't have a 'down' lock so it is difficult to keep it from squirting up as the sides are pinched into position.

Of note, when the ETMX Optical Lever was recentered on 15 Feb, it was done without the HEPI holding the nominal orientation.  Fortunately, Jim and I have debiased the HEPI position onto the DSCW springs and as you can see on the attached plot, the isolated/not isolated amounts to about 6 Oplev yaw plot units (urads?Yes urads).  Still, nominally, oplev centering should be done with the HEPI fully isolated (ISI not so important.)

The attached 3 hour plot has the HPI & SEI guardian states (chans 1 & 2), the OpLev Pit & Yaw (3 & 4), with the rest being the HEPI position residuals. Note the annotations showing the shift in the OpLev Yaw when the HEPI Isolates and the residuals go to zero.

Images attached to this report
H1 CAL
evan.goetz@LIGO.ORG - posted 10:55, Wednesday 21 February 2018 - last comment - 05:13, Thursday 10 May 2018(40630)
DARM model in Python
Summary:
The core functionality of the Matlab DARM model has now been replicated in Python. Attached are figures in a single PDF file showing the primary results. By eye, these look reasonable. A more detailed study comparing to the Matlab model is forthcoming. I also replicated a study made for the L1 detector by Joe B. (see LLO aLOG 29622). I propose to call this code pyDARM.

Details:
I have ported most of the core functionality of the DARM model from Matlab into Python. So far, I have done spot checks by eye to make sure that the results look sensible. I have not yet done a detailed study comparing to the Matlab version, but will do so soon.

I have produced plots showing:
1) DARM digital filters
2) Sensing function
3) Actuation function
4) Open loop gain
5) Frequency dependent actuation authority of each stage compared to inverse sensing
6) Ratio of each stage to the overall calibration

As can be observed, the scale of each figure appears reasonable (comparing with, e.g., G1700316), the OLG is stable, and with a UGF with the correct value (by eye). The contribution of each suspension stage is closely matching L1's results using the Matlab model (see LLO aLOG 29622).

What was done:
- Write python version of Matlab functions to parse Foton filter files and to compute IOP downsampling filters from RCG code coefficients
- Exported numerical values of zeros, poles, gain, delay from analog AA and AI models (these are objects in .mat files)
- Exported ASCII file of the frequency response for the suspension force-to-length for each stage. This is read in and used in the python DARM model, and so far can only be at specific frequency points
- DARM filter bank digital filters computed, sensing function and actuation functions are computed from parameters
- Intermediary data products can be accessed
- Code structure is "flatter", meaning less jumps between different functions/files. Hopefully this makes the code more accessible and readable.

Required python modules (so far): scipy (e.g., filters), numpy (e.g., arrays/array math), collections (for namedtuples), matplotlib (for plotting)

Quirks found along the way:
- You can't directly multiply or add filter objects together in Python (the + and * functions are not overloaded in Python). I had to code up my own version to 1) add filters by using polynomials from roots, computing a transfer function filter, and then converting to a zpk object, all using scipy built-in functions; and 2) multiply filters by appending zeros together, poles together, and multiplying gain.
- The scipy sos2zpk() function is not exactly like Matlab's version. I found an extra zero and pole when converting because Matlab removes any zeros in the 3rd and 6th positions of an sos section before computing a filter from the sos coefficients

To do list (short term):
- More detailed study comparing Python with Matlab models
- Read in a config file
- Make an L1 model to check for any differences
- See if there is a way to read Matlab .mat file and objects therein. This didn't look trivial when I tried at first, which is why the analog AA and AI models were exported as well as the frequency response of each suspension stage
- Address how to get the force-to-length transfer function for each stage for arbitrary frequencies
- Add computations for GDS / DCS pipelines

Longer term:
- Hook this into a pipeline from measurement to model to uncertainty estimate pipeline
Non-image files attached to this report
Comments related to this report
evan.goetz@LIGO.ORG - 10:32, Thursday 22 February 2018 (40662)
Attached is an updated figure to include the inverse sensing contribution ratio to the overall calibration. Observe that the inverse sensing has impact on the overall calibration above ~10 Hz.
Non-image files attached to this comment
duncan.macleod@LIGO.ORG - 05:13, Thursday 10 May 2018 (41925)

Evan, this looks great, but I don't see any links to the actual pyDARM code? Can you push that to a git repository somewhere? I would be happy to help with python packaging if needed so that this is trivially distributable.

LHO VE
chandra.romel@LIGO.ORG - posted 10:33, Wednesday 21 February 2018 (40629)
CP4 turbo valved out

Valved out CP4 turbo around 10:30 am local for bake enclosure work nearby. Expect pressure at PT-245B to drift up.

H1 PSL
peter.king@LIGO.ORG - posted 09:34, Wednesday 21 February 2018 - last comment - 10:17, Wednesday 21 February 2018(40626)
PSL Mac mini
One of the PSL Enclosure's Mac minis is dead.  Its hard disc cannot be repaired.  The computer will be replaced in the near future.


Carlos / Peter
Comments related to this report
david.barker@LIGO.ORG - 10:17, Wednesday 21 February 2018 (40628)
LHO VE
chandra.romel@LIGO.ORG - posted 18:07, Tuesday 20 February 2018 (40624)
CP4 bake enclosure installation

The installation of CP4's bake enclosure started today. All parts were delivered and the uni-strut framing is ~1/3 installed. We will resume at 6:30am tomorrow surprise I'll post some pictures tomorrow.

LHO VE (VE)
gerardo.moreno@LIGO.ORG - posted 17:44, Tuesday 20 February 2018 (40623)
Turned on X-End Station Purge Air

This morning the purge air skid was turned on.  The dew point was measured at -33 oC after the drying towers cycled twice each.

H1 General (SUS, VE)
betsy.weaver@LIGO.ORG - posted 17:16, Tuesday 20 February 2018 - last comment - 07:48, Wednesday 21 February 2018(40622)
ITMY R0 RT OSEM short - attempted fix at feedthru

After Kyle and Gerardo slow vented the corner, Gerardo and I pulled the 4.5" feed-thru for ITMY CABLE #7 and #8.  We then pulled both in-vacuum cables off the feed-thru in order to swap in a fresh copper gasket.  I re-tightened the back-shell screws and inspected cable #8 and then reseated it - it felt better going in that it came out so we had hope.  Running th spectra showed no improvement however.  We then tried to inspect the ~1ft of cable we were able to pull out through the feed-thru hole and wiggle things before reattaching it to the chamber.  Still no change in spectrum.  Boo.

We'll embark on pulling the door tomorrow.

(Sad face.)

Comments related to this report
betsy.weaver@LIGO.ORG - 07:48, Wednesday 21 February 2018 (40625)

Note, due to some miscommunication, Gerardo started to loosen the conflat screws on the ESD 4.5" feed-thru before I joined him for this work.  So we swapped that copper gasket and reseated the cable and feed-thru. 

H1 ISC
keita.kawabe@LIGO.ORG - posted 16:53, Tuesday 20 February 2018 - last comment - 09:51, Wednesday 21 February 2018(40619)
No ALS retro-reflaction from EY yet

Green beam was injected into TMSY and into EY, green centering on TMS QPD is working but no retro reflection from EY. I scanned TMSY PIT and YAW and observed green beam in ISCTEY but it would be much easier to just look at the beam in chamber. Will continue tomorrow.

EY was put back into laser safe.

Comments related to this report
travis.sadecki@LIGO.ORG - 09:51, Wednesday 21 February 2018 (40627)

The lack of retro-reflection from ETMy was likely due to an optic face shield being installed.  The shield was removed this morning so TMS work can continue.

Displaying reports 45341-45360 of 84848.Go to page Start 2264 2265 2266 2267 2268 2269 2270 2271 2272 End