40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 74 of 341  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  9286   Thu Oct 24 23:25:37 2013 JenneUpdateLSCEnd transmission triggering

Quote:

Software (schmidt triggering) for end transmission QPDs.

 I have modified the ETM suspension models to include a schmidt triggering block, so that we can choose between using the high gain low power Thorlabs PD and the low gain high power QPD. 

The Thorlabs high gain PD signal is used as the signal to trigger on, so we need to put appropriate thresholds in.

If things are "triggered", that will imply that the Thorlabs PD is seeing a lot of power, so we should be using the QPD SUM channel instead.  There is a "choice" block after the trigger block, to do this switching.

Since the LSC model will only see the output of this choice block, the gain that is currently in C1:LSC-TR[X or Y]_GAIN should be moved to the end SUS model.  We also need to find the correct gain for the QPD sum channels so that they are also normalized to "1" for single arm full power so that we can smoothly go between the 2 diodes.

Rana has promised to make screens, and write scripts for the switching stuff.

  12202   Mon Jun 20 14:03:04 2016 jamieConfigurationCDSEndRun GPS receiver upgraded, fixed

I just upgraded the EndRun Technologies Tempus LX GPS receiver timing unit, and it seems to have fixed all the problems.  cool

Thanks to Steve for getting the info from EndRun.  There was indeed a bug in the firmware that was fixed with a firmware upgrade.

I upgraded both the system firmware and the firmware of the GPS subsystem:

Tempus LX GPS(root@Tempus:~)-> gntpversion 
Tempus LX GPS 6010-0044-000 v 5.70 - Wed Oct 1 04:28:34 UTC 2014
Tempus LX GPS(root@Tempus:~)-> gpsversion 
F/W 5.10 FPGA 0416
Tempus LX GPS(root@Tempus:~)->

After reboot the system is fully functional, displaying the correct time, and outputting the correct IRIG-B data, as confirmed by the VME timing unit.

I added a wiki page for the unit: https://wiki-40m.ligo.caltech.edu/NTP

 

Steve added this picture

  8373   Fri Mar 29 16:35:54 2013 SteveUpdate40m UpgradingEndtable upgrade

 

 My full effort to get the optical table enclosure ready for the lab has failed today.

What I did: cut IR thermashield sheets to size for sides and top and sandwitched them beetween 1" and 1/4" acrylic.

                   The carpenter shop recut the bottom o -ring groove to 0.250" wide and 0.150" deep.

                   O-ring was cut and installed. So this was ready to go lab.

                  NO, I realized that the liner yellow acrylic was not cut correctly. It was larger than 1" wall.

                 The shop is cutting them down to fit and I have to resize IR shields

  8315   Wed Mar 20 14:00:21 2013 SteveUpdate40m UpgradingEndtable upgrade

As discussed at the 40m meeting: Koji, Manasa and Steve

We are planning to remove the whole 4'x2' optical table ETMY-ISCT with optics as it is tomorrow morning.
This way I can start placing the new 4'x3' table and acrylic enclosure in place.

  8318   Wed Mar 20 15:51:54 2013 ManasaUpdate40m UpgradingEndtable upgrade

Quote:

As discussed at the 40m meeting: Koji, Manasa and Steve

We are planning to remove the whole 4'x2' optical table ETMY-ISCT with optics as it is tomorrow morning.
This way I can start placing the new 4'x3' table and acrylic enclosure in place.

I will be removing all cables on the ETMY endtable and labeling them today before we remove the table tomorrow morning. If there is anything else that should be done before the swapping which we might have not considered, elog it and we'll have it all done.

Also,I've attached the updated inventory.

  8310   Tue Mar 19 14:21:57 2013 ManasaUpdate40m UpgradingEndtable upgrade : INVENTORY

THE INVENTORY FOR ETMY ENDTABLE.

We definitely need the polaris mirror mounts and cylindrical lenses. As for the rest, we can still go ahead and do the swapping without them.

 

  8312   Tue Mar 19 19:19:50 2013 JenneUpdate40m UpgradingEndtable upgrade : INVENTORY

Does "Ready (in stock)" for the base plates mean in stock at the company, or in hand and already here in the lab?

For the 2" mirror mounts, are we planning on making a decision soon, or a long time in the future....i.e. is this something that should go in the temporary solution column?

For the mode matching and collimating lenses, do we actually have the ones you want in our lens kits?  A lot of those kits are half empty.

  7704   Tue Nov 13 11:30:54 2012 ManasaConfiguration40m UpgradingEndtable upgrade for auxiliary green laser

I'm set on the mission to get the new bigger endtables setup for the auxiliary green laser; now that the tables are already here.

I want to have everything documented in this same thread for future reference. It has been a pain trying to filter relevant elogs. I'll be working on the layout redesign one at a time....starting with the ETMX end.

This is the simplest cartoon layout of  ETMX endtable (not the actual table layout):

ETMX_sch.png

I have been searching through the elogs for the beam parameters measured earlier. I'm assuming they would not have changed much and will make calculations based on them.

However, we will have to change a few not-so-good mounts and include/exclude some optics.

 

P.S. HR (steer) are necessary steering mirrors and HR are just folding mirrors for the drawing.

 

 

 

  8371   Fri Mar 29 00:27:06 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : Assembly

I am currently putting together all components so that they are ready to go on the table once leveling and installation of shield box is done. All dirty optics were drag wiped. These are stored in the cupboard along the Y arm.
I could not find the fiber coupling mount on the old endtable. Also the harmonic separator that reflects the trans beam to PDs and camera is labelled Y1-1064 (??) and I don't know what's the deal with this.
I am nearly 70% done with assembling…so the ex-endtable is almost empty.

Yet to do:
1. Mount 2" optics
2. Hunt, gather and mount appropriate lenses

Points I did not notice earlier:
We need some good 2" lens mounts and also order 2" lenses for IPANG and trans beam.

 

IMG_0433.JPGIMG_0434.JPG

  7705   Tue Nov 13 16:18:51 2012 ManasaConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : Circularize the 1W NPRO beam profile

With reference to measurements made earlier: elog

Beam parameters for Innolight 1W NPRO are:

wx0 = 160 um 

wy0 = 181.1 um

z0x = -9.17 cm

z0y = -10.19 cm

The beam is clearly elliptical.  We will introduce an additional pair of cylindrical lenses to circularize the beam before it enters the faraday.

I made calculations for the beam divergence ratio and checked with thor labs catalogue of cylindrical lenses to find pairs that will match the ratio. 

I propose to use lenses with focal lengths f1 = 22.2 mm and f2 = 25 mm. The beam diameter after the lenses will be dx = 164.05 um and dy = 163.19 um.

  7706   Tue Nov 13 20:13:07 2012 KojiConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : Circularize the 1W NPRO beam profile

These fs are too short.

Quote:

I propose to use lenses with focal lengths f1 = 22.2 mm and f2 = 25 mm. The beam diameter after the lenses will be dx = 164.05 um and dy = 163.19 um.

 

  7726   Mon Nov 19 20:03:53 2012 ManasaConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : ETMX layout on new table

I have attached the possible layout of the optics on the new ETMX endtable. More optics have been added when compared to the early cartoon layout considering that we need additional steering mirrors for reasons like: the table height in and out-of vac are different and several mounts have restricted movement in certain degrees of freedom. 

As you can see, there is enough room for filters and other last time additions that may arise.

I will proceed with calculations based on the distances from the CAD drawing and the spec of the optics if there are no comments or suggestions about the layout.

 

 

  7727   Mon Nov 19 20:17:53 2012 JenneConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : ETMX layout on new table

 

For convenience, I would include a steering mirror in front of the TRX PD.  Also, don't we usually have lenses in the oplev paths?  Also, also, do we need lenses in front of the green refl and TRX PDs?  Do you have a place in mind for the shutter?  Is there a way to compactify the layout a little bit, so that even if the lenses are different for each table, the general layout for both ETMX and ETMY is the same (with an empty space on ETMX where IPANG belongs on ETMY)?  I'm sure it is, since you've talked to Steve about this, but just to check: is the green refl PD far enough away from the edge of the table to accommodate the fancy new box?

  7728   Mon Nov 19 22:42:14 2012 KojiConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : ETMX layout on new table
  • I don't like the idea to place the cylindrical lenses right in front of the laser.
    This design requires the CLs to be tilted to avoid direct reflections going into the laser.
    It is also required that they are made of UV fused silica to avoid thermal lensing.

     
  • Instead, move the CLs after the farday while we keep L1, HWP, QWP after the laser.
    L1 should be UV fused silica lens. I should be placed with slight tilt.
    It is preferrable to place CLs after the faraday at somewhere the beam is not too small.
     
  • The HWP before the SHG can be moved to downstream of the steering mirrors as they can change the poralization.
    (Probably I am too paranoic.)
     
  • Why don't you use the harmonic separator right after the SHG crystal in stead of relying on an arbitrary transmission of the 532nm mirrors?
     
  • I am not confident about such a "nice" separation angle of the returning beam from the green faraday.
    Confirm the separation angle on the actual setup.

    The beams split in the polarizer rather than in the air like in your diagram.
    Then because of this small angle separation, the pick-off mirror may have a bit more critical distance than you indicated.
    (I could be wrong.)
  • I don't think the green faraday is IO-5-532-HP. It should be IO-?-532-LP.
    Rotate the tilt aligner 180deg so that we can easily access to the adjusting screws
     
  • The green PDA36A path needs more length and probably a focusing lens too.
     
  • After the PLCX lens, the beam is big (w=3mm) everywhere. Don't you want to use 2" mirrors and mounts?
     
  • We eventually will install steering PZTs for the green.
    On which mirrors do you want to install the PZTs?
    Do you have enough spare space for them?
     
  • The mount indicated "HS" is one of the trickiest mounts on the table as the big beam goes through the mirror.
    Probably you want to use 2" suprema mount with correct chirality.
     
  • How is the power budget of the IR trans path? Which is the low power PD and which is the high power PD?
    What's the transimpedance of them? Where is the crossover?
    How much power does go into the CCD? Is it a reasonable amount?

     
  • The IR transmon beam is even larger than the green beam (w=5mm)
    You definitely need a lens to shrink the beam. But we don't want to have the QPD and the CDD at the focus.
     
  • As Jenne pointed out, having a steering mirror for the IR PDA36A is a good idea.
    But do you really want to use the Si PD for the IR tmonitor?
  • I feel I don't want to have the pair of steering mirrors in the oplev incident path. One is enough.
    We should be able to accommodate optional mode-matching lenses in the incident path.
    We definitely don't want to have any lens in the returning path of the oplev.
  7813   Wed Dec 12 11:04:45 2012 ManasaConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : ETMX layout on new table

I have updated the layout to fix all the issues brought up. The last couple of 2" green steering mirrors will hold the PZTs for input steering. I will update with the list of optical components that we will be ordering for this layout. The ETMY endtable layout will be similar to this one, except that we will have IPANG setup at the empty space in the right top corner.

ETMX_endtable_New_Model.png

  8436   Wed Apr 10 14:25:04 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : LWE Alberto laser beam profile

I measured the beam profile of the Alberto laser (that will be the ETMY end laser) as I found the data inconsistent with the measurements done earlier.

Method

The laser was set to nominal current (ADJ =0) and the output measured 330mW. I used a 99% BS and measured the beam profile of the transmitted light at several points along propagation using Beamscan. I am attaching the data and matlab script for the fit for future reference.

LWE_Alberto_BP.png

  8427   Tue Apr 9 00:32:57 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : TRY temporarily in place

The TRY path on the end table is temporarily in place to help IFO locking.
The Y arm transmission was steered to get TRY back on the PD and the camera. I found that TRY is a couple of inches off in yaw at the end table (comparing to the CAD layout and the earlier layout) and I believe it is because of the changes in input pointing.
I've used a Y1 mirror to steer the Y transmission to an R98% BS. The reflected beam falls on PDA520 and the transmitted beam is steered to the camera. The earlier normalization of TRY is no more valid as the power distribution at the PD has changed.

  8430   Tue Apr 9 08:37:54 2013 SteveUpdate40m UpgradingEndtable upgrade for auxiliary green laser : TRY temporarily in place

Quote:

The TRY path on the end table is temporarily in place to help IFO locking.
The Y arm transmission was steered to get TRY back on the PD and the camera. I found that TRY is a couple of inches off in yaw at the end table (comparing to the CAD layout and the earlier layout) and I believe it is because of the changes in input pointing.
I've used a Y1 mirror to steer the Y transmission to an R98% BS. The reflected beam falls on PDA520 and the transmitted beam is steered to the camera. The earlier normalization of TRY is no more valid as the power distribution at the PD has changed.

Temporary  acrylic wind guard added between enclosure and ETMY transmission window to help IFO locking

  8341   Mon Mar 25 18:42:38 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : Timeline

 Endtable upgrade - timeline and progress chart. End table upgrade wiki page updated.

 

  8228   Tue Mar 5 00:24:52 2013 ManasaConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : customized mount

 Drawing of customized mount for endtable doubler crystal (PV40+PVP2+NP9071) modified and updated on the endtable upgrade wiki page.

  8418   Fri Apr 5 01:28:56 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : populating the table

I started populating the end table; the TRY path to start with. I found that I need to redo the cables/electronics layout around the table as we have only one cable feedthrough hole with the new box right now. I need another hand with this and will have Annalisa help me tomorrow.

P.S. I misaligned PRM and restored ETMY to get TRY flashes. I tweaked ETMY to see strong TEM00 flashes.

Old slider positions on medm screen in case we need to restore them:

        TT1    TT2     ITMY    ETMY

P   -1.3586  0.8443   0.9114   -3.7693

Y   0.3049   1.1507  -0.2823  -0.2761

 

  8425   Tue Apr 9 00:15:18 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : populating the table

[Den, Annalisa, Manasa]

The Alberto laser was moved from the PSL table. The height of the heat sink rendered a beam height of only 3 inches. I did not want to deal with changing beam height at the table. So, we went ahead and used the old heat sink. I used the beam scan to make measurements of the beam width to match my mode-matching calculations and found some mismatch with the measurements done earlier. So I will measure the beam width again before alignment.

I will also have to change the layout because of the supporting posts that have come up with the new box. Annalisa is doing a COMSOL model to check what the thickness of these supporting posts should be so that the box stays stiff.

  8458   Wed Apr 17 02:20:13 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

 

Assembly progress:

1. ETMY oplev setup has been put together. Because of the shift in the TRY path, I had to modify the oplev path on the table as well.

TRY_OPL.jpg

2. Green laser setup coming together:
    (i) Used a HWP after the NPRO to convert s-polarization to p-polarization. (Verified by introducing a PBS after the HWP and then removed later).
    (ii) Lens focuses the beam into the Faraday.
    (iii) Used steering mirrors to align the beam to the faraday. With 320mW before the Faraday, I was able to get 240mW after the output aperture. The spec sheet for the faraday specifies a 93% transmission; but what I measure is only 75%.

GRY.jpg

 

  8522   Thu May 2 01:19:41 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

I started to put together optics at the endtable. I am attaching the layout with the green blocks showing the optics that are assembled and will not be moved henceforth unless somebody contradicts.

1. Power after HWP = 314mW
    Power before faraday = 310mW
    Power after faraday = 300mW (the power loss while aligning the faraday earlier was due to the AR coating on the focusing lens before the faraday - it was AR coated for visible and that accounted to the power lost)

2. Since we do not know the length of TGG inside faraday, I measured the beam profile after the faraday so that I can trace the beam without any errors to calculate exact mode matching solutions.

3. The NPRO beam seems to be obviously elliptical as seen on the IR card and also from beam profile measurement. So we cannot skip including cylindrical lenses in the layout.

ETMY_0502.png

 

  8543   Tue May 7 19:06:45 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

I have updated the waists (W)  and beam diameters (D) at 1064nm optics on the endtable.

I am not able to locate the characteristics of QPD-Y and oplev PD and hence took the beam diameter to be half of the detector surface area to determine their positions.

Beam diameter on PDA520 used for TRY was calculated using the transimpedance and responsivity of the PD from an old elog in 2004.

ETMY_endtable_New.png 

  8556   Thu May 9 01:36:32 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

Progress with end table:

Parts in green show assembled optics that will not require any changes. Parts in yellow are in place but will need either change of lenses in their optical path or change in position.

0509.png 

  8560   Thu May 9 22:29:23 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

[Annalisa, Manasa]

More optics have been put on the table. Direction of the rejected beam from the 532nm faraday estimated to be ~1.7 deg along -y axis.

Transmon QPD, TRY and camera have beams on them for locking Y arm. Oplev configuration is waiting for it's lens to arrive.

 

  8561   Fri May 10 20:05:21 2013 AnnalisaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

I rotated some mounts along the green beam path, and I started aligning the beam again.

The beam is aligned up to the waveplate just before the doubler crystal, even if I couldn't reach more than 88% transmission for the Faraday. Next week I will finish the alignment and I'll put the lenses that Manasa already ordered.

 

  8565   Mon May 13 21:35:55 2013 AnnalisaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

Yend table - Current status

OPLEV

Today the 2m focal length lens along the oplev path (just after the laser) has been added. In Manasa's layout it allows to have a beam waist of 3.8mm on the OPLEV QPD, even if it seems to be smaller.

The laser is closer to the box wall than the layout shows (it's on the line n.1 instead of line n.9), so maybe it has to be moved in the position shown in the layout, as Steve suggests, to leave empty space just before the window.

Rana suggests a 2mm diameter beam on the QPD, so a new calculation has to be done to add a second lens.

GREEN

The beam has been aligned until the doubler, but after the crystal it it has a small tilt, so a better alignment has to be done.

Moreover, the beam waist has to be measured after the Faraday for the green, in way to choose the focal length of the lenses necessary for the mode matching.

Then the three steering mirrors to send the beam into the arm have to be put.

TRANSMON PATH

A lens which has to be put on the Transmon path (already ordered) has to be added, and the beam alignment on the QPD-y and on the PDA520 has to be done.

  8576   Tue May 14 21:03:15 2013 AnnalisaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

 

GREEN

The new lenses arrived, and I put the right 250mm before the doubler. I'm still not so confident with the alignment, because I cannot get more than 11-12 uW out from the "green" Faraday, with more than 200uW going in.

TRANSMON

I replaced the Y1 mirror with an HR1064-HT532. The alignment has to be done. Today the 50cm focal length lens arrived, and I'm going to put in tomorrow.

 

  8584   Wed May 15 21:27:39 2013 AnnalisaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress

 

GREEN

I still have problems in maximizing the power out from the doubler. I realized that the real green power I obtain is about 30 uW, and it is the power which really enters the Faraday.

Before I was measuring it just after the Harmonic separator, and there was some residual IR beam which increased the power on the power meter, that's why I obtained about 200 uW.

I also tried to slightly vary the position of the mode matching lens, but I was not able to get more than 30 uW on the power meter.

TRANSMON PATH

The 50 cm focal length lens has been added in the position shown on Manasa's layout, and the beam has been focused on the PD.

 

 

  8486   Wed Apr 24 15:27:59 2013 ManasaUpdate40m UpgradingEndtable upgrade for auxiliary green laser : progress: New layout

Layout that will be improved upon over the next few days.

Things that need to be updated:
1. Waist size at all optics
2. Beam size at detectors and choice of lenses
3. IPANG & green PD proposed positions

 ETMY_endtable_New.png

  7889   Thu Jan 10 12:41:06 2013 ManasaConfiguration40m UpgradingEndtable upgrade for auxiliary green laser : wiki page

 

I have created a wiki page linked here with all details about the endtable upgrade.

The page has links to the new drawing for doubler post to hold the tilt-aligner that holds it. The Faradays will also be mounted similarly on tilt aligners placed on these posts. The bulk mounts will be made of aluminium similar to the colorful cylindrical mounts (images of which can be seen in the archived layouts on the wiki) that hold the He-Ne lasers and few faradays now.

  3762   Fri Oct 22 16:59:21 2010 JenneUpdateElectronicsEpic Takeover

As the suspension work winds down (we'll be completely done once the ETMs arrive, are suspended, and then are placed in the chambers), I'm going to start working on the RF system. 

Step 1: Figure out what Alberto has been up to the last few months.

Step 2: Figure out what still needs doing.

Step 3: Complete all the items listed out in step 2.

Step 4: Make sure it all works.

Right now I'm just starting steps 1 & 2.  I've made myself a handy-dandy wiki checklist: RF Checklist.  Hopefully all of the bits and pieces that need doing will be put here, and then I can start checking them off. Suggestions and additions to the list are welcome.

  3764   Fri Oct 22 18:22:27 2010 AlbertoUpdateElectronicsEpic Takeover

Quote:

As the suspension work winds down (we'll be completely done once the ETMs arrive, are suspended, and then are placed in the chambers), I'm going to start working on the RF system. 

Step 1: Figure out what Alberto has been up to the last few months.

Step 2: Figure out what still needs doing.

Step 3: Complete all the items listed out in step 2.

Step 4: Make sure it all works.

Right now I'm just starting steps 1 & 2.  I've made myself a handy-dandy wiki checklist: RF Checklist.  Hopefully all of the bits and pieces that need doing will be put here, and then I can start checking them off. Suggestions and additions to the list are welcome.

 There's also a page dedicated to the progress in the PD upgrade process:

http://lhocds.ligo-wa.caltech.edu:8000/40m/Upgrade_09/RF_System/Upgraded_RF_Photodiodes

There you can find a pdf document with my notes on that.

  15007   Mon Nov 4 11:41:28 2019 shrutiUpdateComputer Scripts / ProgramsEpics installed on donatella

I've installed pyepics on Donatella running

sudo yum install pyepics

Pip and ipython did not seem to be installed yet.

  12828   Tue Feb 14 10:43:06 2017 gautamBureaucracyEquipment loanEquipment to Cryo Lab

PZT Buzzer Box (Thorlabs HV Supply + Manual + 2*PZT Buzzers) ---> Cryo Lab (Brittany + Aaron)

  9660   Fri Feb 21 12:45:57 2014 ericqUpdateLSCEquivalent Displacement Noise from QPD Dark Noise in SQRTINV

EQ UPDATE: Measured it wrong the first time, fixed now.

I measured the spectra of the SQRTINV channels from dark QPDs, with offsets adjusted to imitate various transmission levels. (While the dark noise stays constant in terms of, say, TRX counts, 1/sqrt(TRX) isn't linear, and so the noise coupling depends on the TRX offset). 

SQRTINVspectra.pdf

I did some calculations to turn this into the equivalent displacement noise when using SQRTINV as an error signal. This depends on where on the fringe you are locking, since the slope of SQRTINV vs. position is not constant, and can only really be treated as linear down to about 1/3 of a line width away from full resonance. In my calculations, I assumed a coupled arm line width of 38pm, and a full transmission of 700 counts in TRX/Y. 

The QPD dark noise RMS when two line widths away (TR = 40) is about 5fm, and only goes down from there. 

SQRTINV_DarkNoise.pdf

  9693   Wed Mar 5 18:04:36 2014 ericqUpdateLSCEquivalent Displacement Noise from QPD Dark Noise in SQRTINV

At today's meeting, it was suspected that these noise levels were far too low. (ELOG 9660)

I've attached the math I did to get the conversions, as well as the dark noise SQRTINV spectra at various imitated transmission values and the python script that does the converting. 

I've gone over my calculations, and think they're self-consistent. However, a potential source of misestimation is the treatment of the Lorentzian profile simply existing with the coupled arm line width (38pm). The conversion to m/rtHz is directly proportional to the line width of the transmission peak, so if it is much broader in practice (because of imperfect PRC buildup or something), the noise will be that much worse.

I'm open to any other feedback about what I may have done wrong!

 

  11525   Mon Aug 24 14:05:47 2015 ericqUpdateSUSEricG Investigating L2A

This afternoon, I showed Eric Gustafson some of the basics of making swept sine measurements with DTT. We turned off the f2a filters and oplev damping on the BS and made a cursory measurement of the transfer function from position drive to the oplev signals. 

He will be in the lab periodically to continue this line of investigations. 

  15178   Thu Jan 30 17:31:28 2020 JonUpdatePSLErrant FSS_INOFFSET change

A script I was testing errantly set C1:PSL-FSS_INOFFSET => 10 V at about 5:30 pm. I manually reverted the channel value to 0, but I don't know what the value was initially. Someone please check this value if there are problems locking the FSS.

  15179   Thu Jan 30 17:41:10 2020 gautamUpdatePSLErrant FSS_INOFFSET change

You can trend the data for the past few hours and see what the appropriate value. I think these tests should only be done when whoever is running a test is in the lab.

P.S. I was surprised that the IMC didn't lose lock when this step was applied. I manually stepped this voltage between +/- 10 V and didn't see any response in the FSS readbacks. Either the channel doesn't work, or there is a divide by 40 in the physical circuit or something...

Quote:

A script I was testing errantly set C1:PSL-FSS_INOFFSET => 10 V at about 5:30 pm. I manually reverted the channel value to 0, but I don't know what the value was initially. Someone please check this value if there are problems locking the FSS.

  1175   Thu Dec 4 16:29:20 2008 josephbConfigurationComputersError message on Frame Builder Raid Array
The Fibrenetix FX-606-U4 RAID connected to the frame builder in 1Y7 is showing the following error message: IDE Channel #4 Error Reading
  17010   Mon Jul 18 04:42:54 2022 AnchalUpdateCalibrationError propagation to astrophysical parameters from detector calibration uncertainty

We can calculate how much detector calibration uncertainty affects the estimation of astrophysical parameters using the following method:

Let \overrightarrow{\Theta} be set of astrophysical parameters (like component masses, distance etc), \overrightarrow{\Lambda}be set of detector parameters (like detector pole, gain or simply transfer function vaue for each frequency bin). If true GW waveform is given by h(f; \overrightarrow{\Theta}), and the detector transfer function is given by \mathcal{R}(f; \overrightarrow{\Lambda}), then the detected gravitational waveform becomes:
g(f; \Theta, \Lambda) = \frac{\mathcal{R}(f; \overrightarrow{\Lambda_t})}{\mathcal{R}(f; \overrightarrow{\Lambda})} h(f; \overrightarrow{\Theta})

One can calculate a derivative of waveform with respect to the different parameters and calculate Fisher matrix as (see correction in 40m/17017):

\Gamma_{ij} = \left( \frac{\partial g}{\partial \mu_i} | \frac{\partial g}{\partial \mu_j}\right )

where the bracket denotes iner product defined as:

\left( k_1 | k_2 \right) = 4 Re \left( \int df \frac{k_1(f)^* k_2(f))}{S_{det}(f)}\right)

where S_{det}(f) is strain noise PSD of the detector.

With the gamma matrix in hand, the error propagation from detector parameter fractional errors \frac{\Delta \Lambda_j}{\Lambda_j}to astrophysical paramter fractional errors \frac{\Delta \Theta_i}{\Theta_i}is given by (eq 26 in Evan et al 2019 Class. Quantum Grav. 36 205006):

\frac{\Delta \Theta_j}{\Theta_j} = - \mathbf{H}^{-1} \mathbf{M} \frac{\Delta \Lambda_j}{\Lambda_j}

where \mathbf{H}_{ij} = \left( \frac{\partial g}{\partial \Theta_i} | \frac{\partial g}{\partial \Theta_j}\right ) and \mathbf{M}_{ij} = \left( \frac{\partial g}{\partial \Lambda_i} | \frac{\partial g}{\partial \Theta_j}\right ).


Using the above mentioned formalism, I looked into two ways of calculating error propagation from detector calibration error to astrophysical paramter estimations:

Using detector response function model:

If we assume detector response function as a simple DC gain (4.2 W/nm) and one pole (500 Hz) transfer function, we can plot conversion of pole frequency error into astrophysical parameter errors. I took two cases:

  • Binary Neutron Star merger with star masses of 1.3 and 1.35 solar masses at 100 Mpc distance with a \tilde{\Lambda} of 500. (Attachment 1)
  • Binary black hole merger with black masses of 35 and 30 at 400 MPc distance with spin along z direction of 0.5 and 0.8. (I do not fully understand the meaning of these spin components but a pycbc waveform generation model still lets me calculate the effect of detector errors) (Attachment 2)

The plots are plotted in both loglog and linear plots to show the order of magnitude effect and how the error propsagation slope is different for different parameters. 'm still not sure which way is the best to convey the information. The way to read this plot is for a given error say 4% in pole frequency determination, what is the expected error in component masses, merger distance etc. I

Note that the overall gain of detector response is not sensitive to astrophysical error estimation.

Using detector transfer function as frequency bin wise multi-parameter function

Alternatively, we can choose to not fit any model to the detector transfer function and simply use the errors in magnitude and phase at each frequency point as an independent parameter in the above formalism. This then lets us see what is the error propagation slope for each frequency point. The hope is to identify which parts of the calibration function are more important to calibrate with low uncertainty to have the least effect on astrophysical parameter estimation. Attachment 3 and 4 show these plots for BNS and BBH cases mentioned above. The top panel is the error propagation slope at each frequency due to error in magnitude of the detector transfer function at that frequency and the bottom panel is the error propagation slope at each frequency due to error in phase of the detector transfer function.

The calibration error in magnitude and phase as a function of frequency would be multiplied by the curves and summed together, to get total uncertainty in each parameter estimation.


This is my first attempt at this problem, so I expect to have made some mistakes. Please let me know if you can point out any. Like, do the order of magnitude and shape of error propagation makes sense? Also, comments/suggestions on the inference of these plots would be helpful.

Finally, I haven't yet tried seeing how these curves change for different true values of the merger event parameters. I'm not yet sure what is the best way to extract some general information for a variety of merger parameters.

Future goals are to utilize this information in informing system identification method i.e. multicolor calibration scheme parameters like calibration line frequencies and strength.

Code location

  17011   Mon Jul 18 15:17:51 2022 HangUpdateCalibrationError propagation to astrophysical parameters from detector calibration uncertainty

1. In the error propogation equation, it should be \Delta \Theta = -H^{-1} M \Delta \Lambda, instead of the fractional error. 

2. For the astro parameters, in general you would need t_c for the time of coalescence and \phi_c for the phase. See, e.g., https://ui.adsabs.harvard.edu/abs/1994PhRvD..49.2658C/abstract.

3. Fig. 1 looks very nice to me, yet I don't understand Fig. 3... Why would phase or amplitude uncertainties at 30 Hz affect the tidal deformability? The tide should be visible only > 500 Hz. 

4. For BBH, we don't measure individual spin well but only their mass-weighted sum, \chi_eff = (m_1*a_1 + m_2*a_2)/(m_1 + m_2). If you treat S1z and S2z as free parameters, your matrix is likely degenerate. Might want to double-check. Also, for a BBH, you don't need to extend the signal much higher than \omega ~ 0.4/M_tot ~ 10^4 Hz * (Ms/M_tot). So if the total mass is ~ 100 Ms, then the highest frequency should be ~ 100 Hz. Above this number there is no signal. 

 

  17017   Tue Jul 19 07:34:46 2022 AnchalUpdateCalibrationError propagation to astrophysical parameters from detector calibration uncertainty

Addressing the comments as numbered:

  1. Yeah, that's correct, that equation normally \Delta \Theta = -\mathbf{H}^{-1} \mathbf{M} \Delta \Lambda but it is different if I define \Gamma bit differently that I did in the code, correct my definition of \Gamma to :
    \Gamma_{ij} = \mu_i \mu_j \left( \frac{\partial g}{\partial \mu_i} | \frac{\partial g}{\partial \mu_j} \right )
    then the relation between fractional errors of detector parameter and astrophysical parameters is:
    \frac{\Delta \Theta}{\Theta} = - \mathbf{H}^{-1} \mathbf{M} \frac{\Delta \Lambda}{\Lambda}
    I prefer this as the relation between fractional errors is a dimensionless way to see it.
  2. Thanks for pointing this out. I didn't see these parameters used anywhere in the examples (in fact there is no t_c in documentation even though it works). Using these did not affect the shape of error propagation slope function vs frequency but reduced the slope for chirped Mass M_c by a couple of order of magnitudes.
    1. I used the get_t_merger(f_gw, M1, M2) function from Hang's work to calculate t_c by assuming f_{gw} must be the lowest frequency that comes within the detection band during inspiral. This function is:
      t_c = \frac{5}{256 \pi^{8/3}} \left(\frac{c^3}{G M_c}\right)^{5/3} f_{gw}^{-8/3}
      For my calculations, I've taken f_{gw} as 20 Hz.
    2. I used the get_f_gw_2(f_gw_1, M1, M2, t) function from Hang's work to calculate the evolution of the frequency of the IMR defined as:
      f_{gw}(t) = \left( f_{gw0}^{-8/3} - \frac{768}{15} \pi^{8/3} \left(\frac{G M_c}{c^3}\right)^{5/3} t \right)^{-3/8}
      where f_{gw0} is the frequency at t=0. I integrated this frequency evolution for t_c time to get the coalescence phase phi_c as:
      \phi_c = \int^{t_c}_0 2 \pi f_{gw}(t) dt
  3. In Fig 1, which representation makes more sense, loglog of linear axis plot? Regarding the affect of uncertainties on Tidal amplitude below 500 Hz, I agree that I was also expecting more contribution from higher frequencies. I did find one bug in my code that I corrected but it did not affect this point. Maybe the SNR of chosen BNS parameters (which is ~28) is too low for tidal information to come reliably anyways and the curve is just an inverse of the strain noise PSD, that is all the information is dumped below statistical noise. Maybe someone else can also take a look at get_fisher2() function that I wrote to do this calculation.
  4. Now, I have made BBH parameters such that the spin of the two black holes would be assumed the same along z. You were right, the gamma matrix was degenerate before. To your second point, I think the curve also shows that above ~200 Hz, there is not much contribution to the uncertainty of any parameter, and it rolls-off very steeply. I've reduced the yspan of the plot to see the details of the curve in the relevant region.
Quote:

1. In the error propogation equation, it should be \Delta \Theta = -H^{-1} M \Delta \Lambda, instead of the fractional error. 

2. For the astro parameters, in general you would need t_c for the time of coalescence and \phi_c for the phase. See, e.g., https://ui.adsabs.harvard.edu/abs/1994PhRvD..49.2658C/abstract.

3. Fig. 1 looks very nice to me, yet I don't understand Fig. 3... Why would phase or amplitude uncertainties at 30 Hz affect the tidal deformability? The tide should be visible only > 500 Hz.

4. For BBH, we don't measure individual spin well but only their mass-weighted sum, \chi_eff = (m_1*a_1 + m_2*a_2)/(m_1 + m_2). If you treat S1z and S2z as free parameters, your matrix is likely degenerate. Might want to double-check. Also, for a BBH, you don't need to extend the signal much higher than \omega ~ 0.4/M_tot ~ 10^4 Hz * (Ms/M_tot). So if the total mass is ~ 100 Ms, then the highest frequency should be ~ 100 Hz. Above this number there is no signal.

 

  17029   Sun Jul 24 08:56:01 2022 HangUpdateCalibrationError propagation to astrophysical parameters from detector calibration uncertainty

Sorry I forgot to put tc & phic in the example. 

I modified astroFisherLib.py to include these parameters. Please note that their meaning is that we don't know when the signal happens and at which phase it merges.

It does not mean the time & phase from a reference frequency to the merger. This part is not free to vary because it is fixed by the intrinsic parameters.  

It might be good to have a quick scan through the Cutler & Flanagan 94 paper to better understand their physical meanings.

 

  11119   Sun Mar 8 03:27:48 2015 JenneUpdateLSCError signal blending for CARM/DARM transitions

This elog will be about work that happened yesterday.  I will write a reply to this with work from this evening's success.


[Rana, Jenne]

Work started with the plan of trying ALS fool, using the new triggering scheme (elog 11114).

The PRMI was having a bit of trouble holding lock with REFL165, so we checked its demod phase.  On Monday (elog 11095) we rotated the REFL165 phase from -91 deg to -48 deg while in PRFPMI configuration (I think the -91 was from PRMI-only phase setting).  However, Friday night we saw that MICH was super noisy, especially when the CARM and DARM offsets were near zero.  Rana rotated REFL165's phase until the MICH noise seemed to get lower (by at least an order of magnitude in the control signal), while we were at zero offset everywhere. We were not driving and looking at any lines/peaks, just the overall spectra.  The final REFL165 demod phase is -80. 

We tried engaging the fool path with no success. 

First, Rana moved the low frequency boost in the MC filter bank from 20:1 to 0.3:0.03.  This gave the whole loop at least 20 or 30 degrees of phase at all frequencies below the design UGF (a few hundred Hz?  Don't quite remember).  To check this, we put in a "plant" filter, and turned on the locking filter (3:3000^2) and the low freq boost and the plant, and the phase never touched 180 at any low freq.  This is so that we can ramp on this filter bank's gain without having an unstable unity gain crossing anywhere.  Also, I added two +10dB filters to the first two filter modules, so that we could ramp on the gain at the input rather than the output.

Last night we were actuating CARM on MC2 and DARM on the ETMs, and the MC filter bank was set to actuate on MC2.  Even with super duper low gain in the MC filter bank, so that the control signal was much less than one (1) count, it would make CARM unhappy.  The CARM filter bank's output was doing +/- a hundred or more counts, so why a few tenths of a count mattered, we couldn't figure out.  We were using the power trigger for the MC filter bank, but not the zero-crossing trigger.  Since the fool tuning was checked while actuating on the ETMs, we wonder if maybe the tuning isn't valid for MC2 actuation?  Maybe there's enough of a difference between them that the fool needs to be re-tuned for MC2 actuation?  Fool had the complex pair of poles at 1Hz, the "comp1" filter to give phase lag, and a gain of 22. 

I think that at some point we even turned off the fool path, but left the MC path on with a little bit of gain, and the audible noise over the speakers didn't seem to change in character at all. Weird. 


We ended up leaving the fool path for another time, and started working on error signal blending at the CARM filter bank input.  This is pretty similar to Kiwamu's self-locking principle.

Our goal was to ramp up the gain of the RF error signal at low frequency, while letting ALS keep hold of things at higher frequencies. 

CARM and DARM sweeps from earlier seemed to indicate that the RF signals are valid without normalization above transmitted powers of 50 or so, so we thought we'd give those a whirl for this error signal blending.

From doing a CARM sweep through resonance, we guessed roughly that the REFL11 (non-normalized) slope was about a factor of 10,000 larger than the ALS slope.  We put a 1e-4 into the input matrix element REFL11I -> CARM_B.  For some reason, REFL11 seemed to be centered around -250 counts, so we put an offset of +0.025 ( = 250*1e-4) into the CARM_B filter module to compensate for this. 

Since we thought that a gain of 1 in the CARM_B filter bank would make it equal to ALS, we tried some lower gains to start with.  0.3 kicked it out of lock, so we ended up liking and using 0.15.  With this low gain on, we tried turning on a low frequency boost, 20:1, but that didn't do very much.  We turned that off, and instead turned on an integrator, 20:0, which totally made things better.  The transmitted arm power was staying higher more of the time.

From a DARM sweep, we thought that AS55Q (non-normalized) should also have an input matrix element of 1e-4 for DARM.  We gave DARM_B a gain of 0.1, which seemed good and not too high.  Again, trying the gentle boost didn't do much, so we went with the integrator. 

At this point, since both RF signals were being used as error signals with integrators, we declared that at least at DC we were on RF signals.  Hooray!! 

After this, we started increasing the CARM_B gain a little, and decreasing the CARM_A gain.  When Rana finally set the CARM_A element to zero, we lost lock.  We realized that this is because we didn't include a zero to compensate for the arm cavity pole, which the IR signal will see, but the ALS won't. 

We decided that the plan of attack would be to get back to where we were (DC error signals on RF), and try to start engaging the AO path. 

 

  11120   Sun Mar 8 04:04:19 2015 JenneUpdateLSCError signal blending for CARM/DARM transitions

As I (very excitedly) reported in elog 11116, I was able to follow the error signal blending procedure from last night, and get CARM and DARM onto digital non-normalized RF signals.  The lock held for about 3 minutes after this transition (elog 11118 has plot of this). yes

I was then able to script what I did (in the carm_up script), and repeat the transitionyes. Q joined me in the control room, but we have not been able to complete the transition a third timeno.

Here's the sequence that worked the two times:

  • Go to zero CARM and DARM offsets 
    • CARM is locked on ALS comm through the CARM_A filter bank (CARM_A gain = 1)
    • DARM is locked on ALS diff through the DARM_A filter bank (DARM_A gain = 1)
  • Lower CARM servo gain to 5 (from 7)
  • Lower DARM servo gain to 5 (from 7)
  • Lower PRCL servo gain to -0.03 (from -0.04)
  • Lower MICH servo gain to 2.5 (from 3.0)
  • Set up _B error signals
    • CARM_B has 1e-4*REFL11I, no normalization
    • DARM_B has -1e-4*AS55Q, no normalization
  • Give CARM_B a gain of 0.15
  • Turn on CARM_B FM7 (integrator)
  • Give DARM_B a gain of 0.1
  • Turn on DARM_B FM7 (integrator)
  • Slowly increase CARM_B gain, lowering CARM_A gain when gain peaking happens
    • CARM_B to 0.3, sleep 2
    • CARM_B to 0.5, sleep 2
    • CARM_A to 0.8, sleep 2
    • CARM_B to 0.6, sleep 2
    • CARM_A to 0.6, sleep 2
    • CARM_B to 0.7, sleep 2
    • CARM_A to 0.4, sleep 2
    • CARM_A to 0.2, sleep 2
    • CARM_B to 0.8, sleep 2
    • CARM_A to 0
  • Slowly increase DARM_B gain, lowering DARM_A gain when gain peaking happens
    • DARM_B to 0.2, sleep 2
    • DARM_A to 0.8, sleep 2
    • DARM_B to 0.3, sleep 2
    • DARM_A to 0.6, sleep 2
    • DARM_B to 0.4, sleep 2
    • DARM_A to 0.4, sleep 2
    • DARM_B to 0.5, sleep 2
    • DARM_A to 0
  • This is where I started working on the ETMX alignment to improve dark port contrast.  DARM kept having gain peaking, so I was lowering the DARM servo gain as I worked on the ETMX alignment.  I didn't make note of what the final gain was when I lost lock, but whatever it was, it wasn't right.

After those two attempts, we ran the LSC offset script, since that hadn't been done since early yesterday.  We did a quick CARM sweep, and REFL11 seemed to be centered around 0 counts, so we removed the 0.025 count offset from the CARM_B filter bank.

For later attempts, we keep seeing oscillations in the lockloss plots around 50 Hz, as if we're seeing gain peaking at the low side of the phase bubble.  We have tried turning off various filters at various levels of RF gain, but none of the combinations seems to be excellent.  Turning off the FM6 bounce/roll filter in CARM was particularly bad (immediately lost arm transmitted power), but others weren't good either (eg turning off FM3 boost lost arm powers within a second or so).  When we lose arm powers, the RF signals aren't valid, so if you don't turn them off fast enough (and ALS is still on with enough gain), you'll lose the full IFO lock.  If you're fast though, you can turn off the CARM and DARM _B outputs and not have to start from scratch. 

There seemed to be a very fine line to walk between not enough gain (~50Hz oscillations), and too much gain (200-300Hz oscillations).  It has been pretty frustrating later in the evening.  We seem to only have about 3dB of gain margin on the low side, when all the boosts are on.  Not excellent. 

When the RF signals had a moderate amount of gain, but ALS was still holding CARM and DARM, Q checked the phases of REFL11 and AS55 with excitation lines.  He rotated AS55 from -55 deg to -30 deg (+25 deg) and REFL11 from 144 deg to 164 deg (+20 deg).


Prior to the all-digital attempts, I tried several times to turn on the AO path, without success.  I think that the best that I got was 0dB on the CM board input 1 gain, +14dB on the CM board's AO gain, and -30dB on the MC board's AO gain before the mode cleaner lost lock. 

I was hoping that I could get CARM entirely to RF signals, and that would make things more stable and less complicated, and I could try again to turn on the AO path, but we haven't been able to do this tonight.


A few times in the later attempts we tried turning on the UGF servos for CARM or DARM.  I'm not sure if the lines kicked things out of lock, or if the UGF servos went a little crazy, or what, but we never survived for more than a few seconds after turning on the excitations.


There is a problem with the optical lever servos.  I had thought I'd been seeing it ever since Q re-did the models, and now I'm pretty sure that's what's up.  Q is hot on the trail of figuring out what may have changed that shouldn't have.  We may want to revert to an old Foton file, and re-copy the old filters into the new filter banks just in case.  The watchdog damprestore scripts have been tweaked to clear the oplev filter bank histories before turning on the oplevs, and this seems to solve the symptom of kicking the optic when oplevs are engaged. 


Although we haven't been able to make the transition to RF-only a third time, I think we're getting there.  Progress has certainly been made in the last 2 days!

  11121   Sun Mar 8 13:51:41 2015 ranaUpdateLSCError signal blending for CARM/DARM transitions

According to the official rules, we only need 8 seconds to declare it "locked".

I wonder if the double cavity pole compensation filter for CARM was on for all the attempts yesterday? IF it looks like it will not saturate, it would be more stable to have the whitening on for REFL11 / AS55. Since on Friday, I set the REFL165 demod phase just by minimizing the MICH control signal with the arms on resonance, we ought to check out the PRMI degeneracy with the ETMs misaligned.

Speaking of signal mixing: Although we weren't able to get the carrier term cancelled in the 3*f1 signals by the relative mod phase method, I wonder if we can do it by mixing the 3*f1 and 3*f2 signals in the input matrix. Might help to keep the PRMI more stable, if that's an issue.


P.S. I have done some scripts directory / SVN cleanup. Adding some directories that were not in (like lockloss) and then removing stuff from the repo using 'svn rm --keep-local  filenames' for the image and data files.

ELOG V3.1.3-