40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 123 of 337  Not logged in ELOG logo
ID Date Author Type Category Subject
  10786   Thu Dec 11 22:44:23 2014 ranaUpdateLSCQPD screens

All of the QPDX matrix fields had a missing underscore in them. So I committed all of the c1asc screens to the SVN (because no one but me and Jamie seems to be able to remember to do this).

Then I did find/replace on the QPDY screen and saved it over the QPDX screen and committed the new thing to SVN as well. Values are now accessible.

  10785   Thu Dec 11 18:12:46 2014 ericqUpdateLSC(Fixed) Y end whitening board

Quote:

Gain mystery

- It was not sure how the whitening gains have been given.

- The corresponding database entry was found in /cvs/cds/caltech/target/c1auxey/ETMYaux.db as

grecord(ao,"C1:ASC-QPDY_S1WhiteGain")
grecord(ao,"C1:ASC-QPDY_S2WhiteGain")
grecord(ao,"C1:ASC-QPDY_S3WhiteGain")
grecord(ao,"C1:ASC-QPDY_S4WhiteGain")

- The gains for S2-S4 were set to be 30. However, C1:ASC-QPDY_S1WhiteGain was set to be 8.62068.
And it was not writable.

- After some investigation, it was found that the database was wrong. The DAC channel was changed from S100 to S0.
The corrected entry is shown here.

grecord(ao,"C1:ASC-QPDY_S1WhiteGain")
{
        field(DESC,"Whitening gain for QPDY Seg 1")
        field(DTYP,"VMIVME-4116")
        field(OUT,"#C0 S0 @")
        field(PREC,"1")
        field(EGUF,"42")
        field(EGUL,"-22")
        field(EGU,"dB")
        field(LINR,"LINEAR")
        field(DRVH,"30")
        field(DRVL,"-10")
        field(HOPR,"30")
        field(LOPR,"-10")
}

- Once c1auxey was rebooted, the S1 whitening gain became writable. Now all of the channels were set to be +30dB (max). 

This exact situation was happening at ETMX. I did the exact same change to the database, now I can read and write all four gain segments.

  10784   Thu Dec 11 18:00:43 2014 ericqUpdateComputer Scripts / ProgramsMC error signal monitoring

The other day, I hooked up the agilent analyzer to OUT2 of the MC board, which is currently set to output the MC refl error signal.  I've written a GPIB-based program that continuously polls the analyzer, and plots the live spectrum, an exponentially weighted running mean, and the first measured spectrum. 

The intended use case is to see if the FSS or MC loops are going crazy when we're locking. Sometimes the GPIB interface hangs/loses its connection, and the script needs a restart.

The script lives in scripts/MC/MCerrmon

 

 

  10783   Thu Dec 11 17:45:54 2014 ericqUpdateComputer Scripts / ProgramsLockloss plotting

 With some advice from Jamie, I've gotten the lock loss plotting script that is used at LHO working on our machines. The other night, I modified the ALSwatch.py script to log lockloss times. Tying it together, I've written a small wrapper script that grabs the last time from the lockloss log, and plots it. 

It is: scripts/LSC/LocklossData/lastlock.sh

Jamie's going to make an adjustment to the pydv codebase that will let me implement the auto y-scaling that we like. We also will need to get a feel for the right timing window, once we see what kind of delay in the ALSwatch script is typical. 

Here's an example of the output, with the window of [-10,+2] seconds from the logged GPS time:

figure.png

 

  10782   Thu Dec 11 16:42:12 2014 JenneUpdateElectronicsXend QPD whitening board plan

Here is a little PDF of what I plan to do to both of the transmission QPD whitening boards later today.  The idea is to take away the remote gain slider inputs, and force the gains to always be at +30dB.

The red and blue notes are from Koji's elog 9854, and the green are my plans for today. 

I will cut the traces from the gain slider inputs, and pull the negative input of the AD620 to ground.  The positive input will be connected to the +5 voltage line, with a divider so that the positive input to the AD620 is about 666mV. 

The AD602 will be maxed out at +30dB with anything over 625mV. 

QPDwhiteningModification_11Dec2014.pdf

Unless there are objections, I will start these modifications in an hour or so.  I will also make the Xarm whitening always-on, just like Koji has already done for the Yend.

EDIT, JCD, 12Dec2014:  These are not the modifications that were made.  Please see ____ for actual modifications.

  10781   Thu Dec 11 15:40:04 2014 SteveUpdatesafetysafety training

 

 Katherine Dooley has received 40m specific basic safety training in the 40m lab

  10780   Thu Dec 11 12:50:12 2014 manasaSummaryGeneralPSL table optical layout

 I assembled the telescope to couple PSL light into the fiber. The maximum coupling that I could obtain was 10mW out of 65mW (~15%).

I was expecting to achieve 80-90% coupling from my design estimates. It makes me wonder if the beam waist measurements made by Harry during summer were correct in the first place. I would like to go back and check the beam waist at the PSL table.

Also, we need a pair of 8m (~25 feet) long SMA cables to carry the RF signal from the beat PD on the PSL table to frequency counter module on the IOO rack.

Steve says that we had a spool of SMA cable and it was borrowed by someone a few months ago. Any updates on either who is holding it or if it has been used up already would help.


The X end slow computer was down this morning. So I used only the Y arm ALS to record the noise level for reference. DTT data for ALSY out of loop noise before opening PSL enclosure is saved in /users/manasa/data/141211/ALSYoutLoop.xml

  10779   Thu Dec 11 12:39:31 2014 diegoUpdateComputer Scripts / ProgramsFrequency Offset Locking scripts status

 I finished the polishing in the scripts/FOL directory, this is the current status and this post replaces my two previous posts on the subject:

  • the Raspberry Pi operates locally: everything is in its /opt/FOL directory, which is a mirror of /opt/rtcds/caltech/c1/scripts/FOL/ ; some backup/sync scripts should be set up, tell me what kind (sync direction, place to call the script from, etc..) is recommended and I'll set it up;

 

  • the /opt/FOL directory contains:
    • ADC_interface                 : Akhil's ADC interface software and dependencies;
    • akhilTestCodes                : Akhil's work directory with his programs and data;
    • backup                             : two zip files with a full backup of the FOL stuff for both chiara and domenica at 2014/12/08, before my work on the directory;
    • fcreadoutApp                   : the EPICS app compiled on domenica. I didn't modify anything in particular here, as I don't know much about EPICS Apps; I'm not even sure if it is used by now, as I launch EPICS manually by just giving him a .db file (see below).
    • armFC*                        : it is the single program that constantly fetches data for the channels: it takes as arguments the RPi device (/dev/hidraw0 for the X arm, and /dev/hidraw1 for the Y arm) and the value to write into the frequency counter (0x3 for initialization and 0x2 for actual use); hence, there is no more need for recompilation!
    • epics_channels.py :  this is the new version of the old codetorun.py script; it handles the initialization and the availability of the two beatnote channels;
    • fcreadout / freqCountIOC : these are the binaries of the EPICS apps that I found on chiara/domenica; they are not used as of now, but could be useful;
    • fcreadout.db           : it is the database file that is loaded by EPICS to handle the channels;
    • FOLPID.pl              : the Perl PID controller; it is still the old version, we will work on this one later on (see Manasa's schedule at elog 10760 for info)

 

  • Domenica's environment:
    • as I said, everything runs locally from /opt/FOL;
    • in particular, I added in /etc/inittab two lines that launch EPICS and the python script for the channels; respawn is supported so these processes should always be available. For this to happen, DO NOT MOVE armFC, epics_channels.py and fcreadout.db from the /opt/FOL directory on domenica!
    • I added a udev rule in /etc/udev/rules.d/98-hidraw-permissions.rules to let the controls user access the /dev/hidraw* devices without having to sudo all the time;
    • I updated the ~/.bashrc and /opt/epics/epics-user-env.sh files to fix syntax errors and add some aliases we usually use.
  10778   Thu Dec 11 10:08:10 2014 manasaUpdateGeneralIFO update

Status of IFO:

1. The X end slow computer is down. ETMX sliders and buttons on the ETMX suspension screens have gone white. I have disabled the ETMX oplev because it is largely misaligned in yaw. I am not poking it and leaving it as is for the time being.

2. The Y arm green alignment had drifted and GTRY was down to 0.15 . I tweaked the alignment using the last two steering mirrors and brought GTRY to 0.7 which gives a beat note of -14dBm.

  10777   Thu Dec 11 09:11:18 2014 manasaUpdatePSLPSL FSS Slow actuator

I am not sure if people have been noticing it lately; but the slow actuator on the PSL FSS has been railing up quite often these days. I found it at >0.8 and as high as 1.5 on certain occasions before resetting it to nominal zero.

It could be because the PMC alignment needs to be tweaked. The night crew should consider doing this before starting to lock.

  10776   Wed Dec 10 21:05:56 2014 KateUpdateSEIGuralp briefly powered down

 Kate & Jenne

About 2:30 this afternoon, we briefly powered off the Guralp (C1:PEM-SEIS_GUR1_{X,Y,Z}) in order to better align it with the other seismometers along its marked N/S direction. It had been visibly off by a few degrees. 

  10775   Wed Dec 10 16:12:29 2014 manasaSummaryGeneralDec 10 - PSL table

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

I was working around the PSL table today.

I wanted to modify the telescope that couples PSL light into the fiber; now that I have the translation stages for the lenses. I could not finish it as the locking work started earlier than usual this afternoon. I measured the out of loop noise for ALS error signals before I opened the PSL enclosure. X and Y beat notes were at -18dBm at 49.3MHz and -29.56dBm at 62.2MHz for this measurement. DTT data can be found in /users/manasa/data/141210/ALSoutLoop.xml; so there is reference to go back to in case of any damage done due to the work on the PSL table.

Also, I received the front and back panels for the Fiber chassis and put it together. Find photos (front panel and inside) of chassis in attachment. This will go inside the PSL enclosure tomorrow.

FiberMod_front.jpg    FOL_fiber.jpg

 

  10774   Wed Dec 10 15:05:32 2014 JenneUpdateElectronicsXend QPD whitening board modified already

In April, Koji logged that he had made some changes to the Yend QPD whitening board (elog 9854).  Today, I pulled the Xend board to see if it had the same modifications.  The filter shapes all seem to be the same (as in, the capacitors at the output filters were removed, etc.), and the final gain is the same.  I just realized that I didn't explicitly check if the whitening switches were pulled to ground to permanently turn on the whitenening, but hopefully I'll be able to see that in the photo. 

I have not made any changes today (yet) to the board, so the overall gain is still accessible via EPICS.  I wanted to do a quick check that we won't be saturating things at full power with the maximum gain, before I make a change.

IMG_1776.JPG

EDIT:  After comparing the photos here and in elog 9854, the X end board has the filter shape modifications that were done some time ago, but the whitening is not permanently enabled.  For the Yend board, Koji added a jumper wire connecting (for example) R97 and R106 to the grounded side of C69.  This jumper wire is not in place on the X qpd board.

Before I re-pull the board and modify it, I want to make sure I know what I'm going to do for the gain slider override.

  10773   Wed Dec 10 14:26:13 2014 steveUpdatePEMair cond maintenance and particle plot

Quote:

 

 AC maintenance is scheduled from 8am till 11am tomorrow morning.

 IFO air condition maintenance will continue tomorrow morning and it should be finished by 11:30AM

 We have new guys taking over this job: Sal and Chris so it takes longer. The units will be shut down for a bit.

They will not enter the IFO lab. The CES housed units will be worked on.

Attachment 1: 05.png
05.png
  10772   Wed Dec 10 14:22:37 2014 diegoUpdateComputer Scripts / ProgramsStatus of the new nodus

[Diego, Steve]

We ran a Cat 6+ Ethernet cable from the 1X7 rack (where the new nodus is located) to the fast GC switch in the control room rack; now I will learn how to setup the 'outside world' network, iptables, and the like.

 

I remind that the current hardware/software status is posted in elog 10697 ; if additions or corrections are needed, let me know.

 

After I check a couple of things, we can use the new nodus (which is currently known in the martian network as rosalba) as a local test to see that everything is working. After that (and, mostly, after I'll have the network working), we will sync the data from the old nodus to the new one and make the switch.

  10771   Tue Dec 9 16:07:16 2014 manasaSummaryGeneralDec 9 - FC module and fiber chassis

Quote:

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

Elaborate to do list:

1. The FC module should be mounted on the IOO rack. Domenica has to be powered up appropriately to the rack power supply.

2. The fiber chassis needs to be built. This will hold all the fiber components and will sit inside the PSL enclosure.
Fiber connectors and fiber couplers need to be installed in the chassis. Attached is the cartoon sketch of layout in the chassis.

3. User guide for FC module (work in progress)

1. FC module has been mounted on the IOO rack. The module gets it AC supply from the powerstrip already installed on the back side of the rack.

FCmodule.png

2. The fiber chassis has not been put together completely. We have still not received the front and back panels for the chassis; which is keeping me on hold. Diego is almost done with his housekeeping on Domenica. He will post an elog with all the details.

3. User guide for FC module (work in progress)

  10770   Tue Dec 9 16:06:46 2014 diegoSummaryGeneralDec 8 - Check Frequency Counter module

Quote:

Quote:

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

[Diego, Manasa]

We looked into the configuration and settings that the frequency counters (FC) and Domenica (the R pi to which the FCs talk to) were left at . After poking around for a few hours, we were able to readout the FC output and see it on StripTool as well.

We have made a list of modifications that should be done on Domenica and to the readout scripts to make the FC module automated and user-friendly.

I will prepare a user manual that will go on the wiki once these changes are made.

 

 I started working on the scripts/FOL directory (I did a backup before tampering around!):

  • I still need to make some serious polishing in the folder, and into the Raspberry Pi itself, in order to have a clean and understandable environment;
  • as of now, I created an single armFC.c program, which takes as arguments the device (/dev/hidraw0 for the X arm, and /dev/hidraw1 for the Y arm) and the value to write into the frequency counter (0x3 for initialization and 0x2 for actual use); hence, no more need for recompilation!
  • I improved the codetorun.py script (and gave the fellow a proper name, epics_channels.py) which handles the initialization AND the availability of the channels;
  • On the Raspberry Pi, I created two init scripts, /etc/init.d/epics_server.sh and /etc/init.d/epics_channels.sh, which start at the end of the boot process with default runlevels; the former starts the softIOc process (epics itself), while the latter executes the constantly running epics_channels.py script; as they are services, they can be started/stopped with the usual sudo /etc/init.d/NAME start|stop|restart

 

As a result, as soon as the Raspberry Pi completes its boot process, the two beatnote channels are immediately available.

 

 OUTDATED: see elog 10779

 

 Update and corrections:

 

  • I forgot to log that I added a udev rule in /etc/udev/rules.d/98-hidraw-permissions.rules in order to let the controls user access the devices without having to sudo all the time;
  • I updated the ~/.bashrc and /opt/epics/epics-euser-env.sh files to fix syntax errors and add some aliases we usually use;
  • since /etc/init.d/ doesn't support automatic respawn of processes, I purged the two scripts I did yesterday and added two lines to /etc/inittab. This works just as fine (I tried a couple of reboots to verify that) and the two processes now respawn automatically even if killed (and, I assume, if they die for any other reason)
  • Another thing I forgot: for the time being, during the cleanup, the Raspberry Pi works on the network share script directory. Once cleaning is done and everything is fixed, everything will run locally on the RPi, and the scripts/FOL directory on chiara will be used as backup/repository.
  10769   Tue Dec 9 03:41:06 2014 JenneUpdateCDSEPICS running slow - network issue?

[Jamie, EricQ, Jenne, Diego]

This is something that we discussed late Friday afternoon, but none of us remembered to elog. 

We have been noticing that EPICS seems to run pretty slowly, and in fact twice last week froze for ~2 minutes or so (elog 10756). 

On Friday, we plotted several traces on StripTool, such as C1:SUS-ETMY_QPD_SUM_OUTPUT and C1:SUS-ETMY_TRY_OUTPUT and C1:LSC-TRY_OUTPUT to see if channels with (supposedly) the same signal were seeing the same sample-holding.  They were.  The issue seems to be pretty wide spread, over all of the fast front ends.  However, if we look at EPICS channels provided by the old analog computers, they do not seem to have this issue. 

So, Jamie posits that perhaps we have a network switch somewhere that is connected to all of the fast front end computers, but not the old slow machines, and that this switch is starting to fail. 

My understanding is that the boys are on top of this, and are going to figure it out and fix it.

  10768   Tue Dec 9 03:34:52 2014 JenneUpdateASCPOP yaw razor tuning

With the re-do of the IFO alignment last week, I think that the beam was no longer about halfway on the POP22 razor blade.  To fix this, I locked the PRMI on sideband, removed the razor blade, and then put it back in such that it occluded about half of the light.  

I'm not entirely sure why, but when I put the razor in, POP22 went from 104(ish) to 45(ish) but POPDC  went from 5200(ish) to 1600(ish).  [The 'ish'es are because the PRC wasn't angularly stabilized, so there was some motion changing the power levels that leaked out to the POP port].  The ETMs were misaligned, so this should not be a carrier vs. sideband effect, since they'll both share the cavity axis defined by the ITMs and the PRM.  It is possible, although I didn't check, that there is some oplev light scattered into the POP photodiode that is now blocked by the razor blade.  This light would only be at DC and not the 2f frequencies.  Since the signal levels for POP22 vs. POPDC didn't change with and without the table top on (and with and without room lights on), I don't think that it is an effect of ambient light getting into the diode.  To check if it is oplev light I should (a) just look, and (b) try to lock the PRMI without the ITMX oplev laser being on to see if there is a difference in the POPDC signal.

Anyhow, under the assumption that the POP22 signal level is correct, I tuned up the PRCL ASC a little bit.  These changes are now in the carm_cm_up script, and the carm_cm_down script resets things.  Before the PRC is locked, I have FM1 and FM7 (the basic servo shape and a 40Hz lowpass) on, the gain set to zero, and the input off.  After lock is acquired, the input is turned on, and the gain ramps from 0 -> 10 in 3 seconds.  Then FM2 and FM6 (boosts at 1 and 3Hz) are engaged.

In the plot below, the dark blue and red curves were taken when there was no angular control on the PRC.  Pink was taken last week with the old QPD yaw ASC on.  Light blue is today's version of the in-loop performance of the POP22 yaw ASC loop.  I didn't save the trace unfortunately, but the DC QPD saw out-of-loop improvement between about 0.8Hz - 4 Hz. 

Also, has anything happened with the LSC rack in the last few weeks that might be causing lots of 60Hz noise? I saw these large lines last week, but I don't think I remember them from the past.

PRC_YAW_QPDvs22_8Dec2014.pdf

After I got the PRCL ASC working, I tried several iterations of locking.  ETMX is still being annoying, although the last hour or so have been okay.  CARM keeps getting rung up right around the transition to the sqrtInv error signal.  Since CARM and DARM are kind of entangled, it took me a few iterations to figure out that it was CARM that is ringing up, and not DARM.  I'm a little worried about the phase loss from the 1kHz lowpass that we turn on just before the transition to sqrtInv.  I want to keep the lowpass off until after we have transitioned DARM also over to DC transmission.  I tried once, but I lost lock before starting the CARM transition.  Anyhow, the ETM alignment issue is annoying.

Also, Jamie, Q, Diego and I were discussing last Friday, but none of us elogged, that we think there might be something wrong with one of the Martian network switches.  I'll start a separate thread about that right now, but it slows things down when you can't trust EPICS channels to be current, and I (without evidence) am a little worried that this might also affect the fast signals.

  10767   Tue Dec 9 00:30:27 2014 manasaSummaryGeneralDec 9 - Elaborate to do list

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

Elaborate to do list:

1. The FC module should be mounted on the IOO rack. Domenica has to be powered up appropriately to the rack power supply.

2. The fiber chassis needs to be built. This will hold all the fiber components and will sit inside the PSL enclosure.
Fiber connectors and fiber couplers need to be installed in the chassis. Attached is the cartoon sketch of layout in the chassis.

3. User guide for FC module (work in progress)

Attachment 1: FOL_FiberChassis.pdf
FOL_FiberChassis.pdf
  10766   Mon Dec 8 20:53:51 2014 diegoSummaryGeneralDec 8 - Check Frequency Counter module

Quote:

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

[Diego, Manasa]

We looked into the configuration and settings that the frequency counters (FC) and Domenica (the R pi to which the FCs talk to) were left at . After poking around for a few hours, we were able to readout the FC output and see it on StripTool as well.

We have made a list of modifications that should be done on Domenica and to the readout scripts to make the FC module automated and user-friendly.

I will prepare a user manual that will go on the wiki once these changes are made.

 

 OUTDATED: see elog 10779

 

I started working on the scripts/FOL directory (I did a backup before tampering around!):

  • I still need to make some serious polishing in the folder, and into the Raspberry Pi itself, in order to have a clean and understandable environment;
  • as of now, I created an single armFC.c program, which takes as arguments the device (/dev/hidraw0 for the X arm, and /dev/hidraw1 for the Y arm) and the value to write into the frequency counter (0x3 for initialization and 0x2 for actual use); hence, no more need for recompilation!
  • I improved the codetorun.py script (and gave the fellow a proper name, epics_channels.py) which handles the initialization AND the availability of the channels;
  • On the Raspberry Pi, I created two init scripts, /etc/init.d/epics_server.sh and /etc/init.d/epics_channels.sh, which start at the end of the boot process with default runlevels; the former starts the softIOc process (epics itself), while the latter executes the constantly running epics_channels.py script; as they are services, they can be started/stopped with the usual sudo /etc/init.d/NAME start|stop|restart

 

As a result, as soon as the Raspberry Pi completes its boot process, the two beatnote channels are immediately available.

 

  10765   Mon Dec 8 15:54:39 2014 manasaSummaryGeneralDec 8 - Check Frequency Counter module

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

[Diego, Manasa]

We looked into the configuration and settings that the frequency counters (FC) and Domenica (the R pi to which the FCs talk to) were left at . After poking around for a few hours, we were able to readout the FC output and see it on StripTool as well.

We have made a list of modifications that should be done on Domenica and to the readout scripts to make the FC module automated and user-friendly.

I will prepare a user manual that will go on the wiki once these changes are made.

 

  10761   Mon Dec 8 09:03:49 2014 steveUpdatePEMair cond maintenance tomorrow morning

 

 AC maintenance is scheduled from 8am till 11am tomorrow morning.

  10760   Sun Dec 7 13:11:57 2014 manasaSummaryGeneralFrequency Offset Locking - To Do List

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

Attachment 1: FOLtodolist.pdf
FOLtodolist.pdf
  10759   Fri Dec 5 15:41:45 2014 JenneUpdateComputer Scripts / ProgramsNodus on fast GC network

Apparently, some time ago Larry Wallace installed a new, fast ethernet switch in the old nodus rack. Q and I have just now moved nodus' GC ethernet cable over to the new switch.  Dan Kozak is going to use this faster connection to make the data flow over to the cluster not so lag-y.

  10758   Fri Dec 5 02:44:43 2014 JenneUpdateGeneralIFO alignment shenanigans

[Jenne, Q, Diego]

OMG, today sucked alignment-wise.  Like, wow. 

I think that the problem with the ASS is with the input pointing part of the system.  I found that if I disable the TTs for the Yarm (iin practice, the outputs are held at zero), I could run the Yarm ASS at full gain of 1, and it would do an awesome job.  The first time I did this, I by-hand optimized the TTs by running the test mass loops to make them follow the input pointing.  After that, I haven't touched the TT pointing at all, and we've just been running the test mass loops for the Yarm ASS.  The Xarm seems to not have this problem (or at least not as drastically), so I left it as it was, touching BS as well as ITMX and ITMY, although the gain still needs to be about 0.3.

I feel pretty good about the IFO alignment now, although it is slightly different than it has been.  The transmitted arm powers are higher than they were before I changed the ASS procedure, and there seems to be a little less power fluctuation with alignment.  Q points out that I don't have concrete evidence that this is a good alignment, but it feels right. 

It was a significant enough change that I had to go down to the Yend to realign the green to the new arm axis.  Xgreen we did with the remote PZTs.  I also realigned both of the beatnotes on the PSL table. 

While I was on the PSL table, I quickly touched up the PMC alignment.

The biggest problem, the one that sucked up more hours and energy than I'd like to admit, is ETMX's jumping.  So frustrating.  Sometimes it is time-coincident with engaging the LSC, sometimes not.  I thought that it might be because there are too many violin filters, but even if I turn off all violin filters to ETMX, it jumped a few times while the cavity was locked.  Sometimes it moves when the cavity is just locked and seems happy, sometimes it moves when nothing is resonating except for the green.  It takes a few minutes to recover the alignment enough to lock, and then it'll jump again a few minutes later.  I haven't gone down to squish the cables today, although I did it yesterday and that didn't seem to do anything. 

We had a few hours of time when it wasn't jumping, so we tried a few times to lock the IFO.  The last several times we have lost lock because the PRC loop rang up.  We measured the loop at low-ish arm powers, but it kept losing lock at higher powers before we could measure.  At least 3 times, the PRC lockloss took out CARM and DARM too.

Anyhow, it has been a long day of not accomplishing anything interesting, but hopefully the IFO will feel better tomorrow.

  10757   Fri Dec 5 00:52:51 2014 JenneUpdateSUSETMX 2nd order violin

We looked at the spectra of POX and POY during IR lock, and Q saw a peak at 1285 in POX only.  We're actuating on the ETMs, so it must be an ETMX violin mode, although it doesn't match the others that are in the table.

Anyhow, I added it to FM9.  While I was doing that, I realized that yesterday I had forgotten to put back the 3rd order ETM violin notch, so that is also in FM9.

  10756   Thu Dec 4 23:45:30 2014 JenneUpdateCDSFrozen?

[Jenne, Q, Diego]

I don't know why, but everything in EPICS-land froze for a few minutes just now.  It happened yesterday that I saw, but I was bad and didn't elog it.

Anyhow, the arms stayed locked (on IR) for the whole time it was frozen, so the fast things must have still been working.  We didn't see anything funny going on on the frame builder, although that shouldn't have much to do with the EPICS service.  The seismic rainbow on the wall went to zeros during the freeze, although the MC and PSL strip charts are still fine. 

After a few minutes, while we were still trying to think of things to check, things went back to normal.  We're going to just keep locking for now....

  10755   Thu Dec 4 03:09:06 2014 JenneUpdateLSCBump in Darm Plant: Lockloss after measurement

We were sitting around arm powers of 6, and that loop measurement had finished.  I was about to go down to arm powers of 5ish, but we lost lock.  I'm not sure why.  There's some slow stuff going on in some of the servos, but nothing jumps out at me as a loop oscillation.  It does however kind of look like the PRMI lost lock just before the arm powers went down?  Perhaps this somehow triggered a lockloss?

The time is 1101721675.

Wide view plots:

Arms6_3Dec2014_powers.png

Arms6_3Dec2014_errctrl.png

Arms6_3Dec2014_auxerr.png

Arms6_3Dec2014_angles.png

Zooms:

Arms6_3Dec2014_powers_Zoom.png

Arms6_3Dec2014_errctrl_Zoom.png

Arms6_3Dec2014_auxerr_Zoom.png

Arms6_3Dec2014_angles_Zoom.png


We're stopping for tonight because ETMX is back to its lame-o jumping around.  I went in and squished the cables, but it's still happening.

Also, the FSS PC drive has been high the last few minutes (only starting after we quit for the night).  When the MC re-locks, it sounds like an ocean wave dying out as the noise goes down a little bit.  But, after a few minutes, it'll get mad again and unlock the MC.

Also, also, I noticed this on Monday with Diego, but the LSC-ALS[x,y] filter module gains sometimes mysteriously get set to zero.  WTF?  Eric and I have both independently checked, and we cannot find a single script in the scripts directory with the string "LSC-ALS", so we aren't deliberately changing those.  Does anyone know what might be going on here?

  10754   Thu Dec 4 02:59:05 2014 ericqUpdateLSCBump in Darm Plant

[J,Q]

After some housekeeping (ASS is wonky, alignment of X green beat was bad, tuning of demod angles, fm gains for REFL165), we were able to bring the PRFPMI up to arm powers of 8 very stably. 

We were keeping an eye on the DARM OLG, to make sure the gain was correct. We then saw a bump around 120Hz. Here is the bump. 

Dec4_darmbump.pdf

Changing CARM offset changes its amplitude. Maybe it's a DARM optical spring. It didn't occur to me until after we lost lock that we could have tweaked the DARM offset to move it around if this was the case. 

Unfortunately, due to some unexplained locklosses, we weren't able to get back into a state to measure this more... which is annoying. During that stable lock, Jenne stated that PRCL and DARM noises were looking particularly good. 

We may want to tweak the way we handle the transmission PD handoff; maybe we want to force the switch at a certain place in the carm_up script, so that we're not flipping back and forth during an IR handoff; I think this may have been responsible for a lock loss or two. 

  10753   Thu Dec 4 01:24:47 2014 JenneUpdateSUSPRM volin 3rd harmonic

Earlier this afternoon, while locking PRMI, I saw a big peak at 1883.48 Hz.  This comes closest to the PRM's 627.75 Hz *3, so I infer that it is the 3rd order harmonic of the PRM violin mode. 

While putting this in, I noticed that my addition of ETM filters the other day (elog 10746) had gotten deleted.  Koji pointed out that Foton can do this - it allows you to create and save filters that are higher than 20th order, but secretly it deletes them.  I went into the filter archive and recovered the old ETM filters, and split things up.  I have now totally reorganized the filters, and I have made every single optic (ETMs, ITMs, PRM, SRM, BS, MC2) all the same. 

FM1 is BS 1st and 2nd harmonics, and FM6 directly below that is a generic 3rd order notch that is wide enough that it encompases 3*BS. 

FM2 is the PRM 1st and 2nd order, and FM7 below it is the PRM 3rd order. 

FM3 is the SRM 1st order, FM4 is the ETMs' 1st order, and FM5 is the MC2 1st and 2nd order filters. 

All of these filters are triggered on if any degree of freedom is triggered.  They all have a ramp time of 3 sec. We may want to consider having separate trigger options for each optic, so that we're not including the PRM notch on the ETMs, for example, and vice versa. 

When all of these filters are on, according to Foton we lose 5.6 degrees of phase at 100 Hz.

  10752   Thu Dec 4 00:26:07 2014 JenneUpdateASCPOP yaw razor blade installed

We would like the option of feeding back the POP beam position fluctuations to the PRM to help stabilize the PRC since we don't have oplevs for PR2 and PR3.  However, we cannot just use the DC QPD because that beam spot will be dominated by carrier light as we start to get power recycling. 

The solution that we are trying as of today is to look at yaw information of just the RF sidebands.  (Yaw is worse than pitch, although it would be nice to also control pitch).  I have placed a razor blade occluding about half of the POP beam in front of the POP PD (which serves POPDC, POP22 and POP110).  I also changed the ASS model so that I could use this signal to feed back to the PRM.  Loop has been measured, and in-loop spectra shows some improvement versus uncontrolled.


Optical table work:

The POP beam comes out of the vacuum system and is steered around a little bit, then about 50% goes to the DC QPD.  Of the remaining, some goes to the Thorlabs PD (10CF I think) and the rest goes to the POP camera.  For the bit that goes to the Thorlabs PD, there is a lens to get the beam to fit on the tiny diode.

There was very little space between the steering mirror that picks off the light for this PD, and the lens - not enough to put the razor blade in.  The beam after the lens is so small that it's much easier to occlude only half of the beam in the area before the lens.  (Since we don't know what gouy phase we're at, so we don't know where the ideal spot for the razor is, I claim that this is a reasonable place to start.)

I swapped out the old 50mm lens and put in a 35mm lens a little closer to the PD, which gave me just enough room to squeeze in the razor blade.  This change meant that I had to realign the beam onto the PD, and also that the demod phase angles for POP22 and POP110 needed to be checked.  To align the beam, before placing the razor blade, I got the beam close enough that I was seeing flashes in POPDC large enough to use for a PRMI carrier trigger.  The PRMI carrier was a little annoying to lock.  After some effort, I could only get it to hold for several seconds at a time.  Rather than going down a deep hole, I just used that to roughly set the POP22 demod phase (I -phase maximally negative when locked on carrier, Q-phase close to zero).  Then I was able to lock the PRMI sideband by drastically reducing the trigger threshold levels.  With the nice stable sideband-locked PRMI I was able to center the beam on the PD. 

After that, I introduced the razor blade until both POPDC and POP22 power levels decreased by about half. 

Now, the POP22 threshold levels are set to up=10, down=1 for both MICH and PRCL, DoF triggers and FM triggers.


ASS model work:

POP22 I and POP110 I were already going to the ASS model (where ASC lives) for the PRCL ASS dither readbacks.  So, I just had to include them in the ASC block, and increased the size of the ASC input matrix.  Now you can select either POP QPD pit, POP QPD yaw, POP221 or POP110I to go to either PRCL yaw, PRCL pit, CARM yaw or CARM pit. 

Compiled, installed and restarted the ASS model.


Engaging the servo:

I took reference spectra of POP QPD yaw and POP 22, before any control was applied.  The shapes looked quite similar, but the overall level of POP22 was smaller by a factor of ~200.  I also took a reference spectra of the POP QPD in-loop signal using the old ASC loop situation.

Q looked at Foton for me, and said that with the boost on, the UGF needed to be around 9 or 10 Hz, which ended up meaning a servo gain of +2.5 (the old POP QPD yaw gain was -0.063).  We determined that we didn't know why there was a high-Q 50Hz notch in the servo, and why there is not a high frequency rolloff, so right now the servo only uses FM1 (0:2000), FM6 (boost at 1Hz and 3Hz) and FM7 (BLP40). 

The in-loop residual isn't quite as good with POP22 as for the QPD, but it's not bad. 

Here's the loop:

ASC_PRCLloop_POP22err.pdf

And here's the error spectra.  Pink solid and light blue solid are the reference traces without control.  Pink dashed is the QPD in-loop.  Red and blue solid are the QPD and POP22 when POP22 is used as the error signal.  You can definitely see that the boosts in FM6 have a region of low gain around 1.5Hz.  I'm not so sure why that wasn't a problem with the QPD, but we should consider making it a total 1-3Hz bandpass rather than a series of low-Q bumps.  Also, even though the POP22 UGF was set to 9 Hz, we're not seeing any suppression above about 4Hz, and in fact we're injecting a bit of noise between 4-20Hz, which needs to be fixed still. 

PRC_YAW_QPDvs22_3Dec2014.pdf

  10751   Wed Dec 3 21:41:12 2014 JenneUpdateComputer Scripts / ProgramsMatlab license updated

It seems that the old Matlab servers went down a week or so early, so I have updated the Matlab license information in 

/cvs/cds/caltech/apps/linux64/matlab/licenses/

per the instructions on https://www.imss.caltech.edu/content/updating-matlab-license-file

EDIT: Q did this also for the control room iMac

  10750   Wed Dec 3 08:36:49 2014 SteveUpdateLSCgood IFO status
Attachment 1: goodStatus.png
goodStatus.png
  10749   Wed Dec 3 02:01:57 2014 KojiUpdateLSCIR Resonance Script Status

The other night (before the holidays), I tried ALS offset tuning  with IR POX/POY signals and it worked pretty good.
I didn't need to tune the offset after the scanning script stopped.

Once we are at the foot hill of the main resonance, I ran something like

ezcaservo -r C1:LSC-POX11_I_MON C1:LSC-ALSX_OFFSET -g -0.003 &
ezcaservo -r C1:LSC-POY11_I_MON C1:LSC-ALSY_OFFSET -g -0.003 &

(... I am writing this with my memory. I could be wrong but conceptually the commands looked like these)

  10748   Wed Dec 3 01:46:12 2014 KojiUpdateLSCTried cav pole compensation trick - fail

Where did these 200Hz, 6kHz come from?


I wonder what are the correct filters to be incorporated in the filter banks for the cav pole compensarion.

Facts:

1. ALS Common and Diff have the cavity pole for the green (fcav_GR)

2. IR DARM has the cavity pole of the arms for IR (fcav_IR_DARM)

3. IR CARM (REFL, POP, POX, or POY) has the double cavity pole (fcav_IR_CARM)

Calculations:

1. T(ITM_GR) = 1.094%, T(ETM_GR) = 4.579% => F=108.6 (cf. https://wiki-40m.ligo.caltech.edu/Core_Optics)
L = 37.8 m (cf. http://nodus.ligo.caltech.edu:8080/40m/9804)
=> fcav_GR = c /( 4 L F) = 18.3 kHz ... ignore

2. T(ITM_IR) = 1.384%, T(ETM_IR) = 13.7ppm => F=450.4
=> fcav_IR_DARM = 4.40 kHz

3. The common cavity pole is lower than fcav_IR by factor of power recycling gain.
=> fcav_IR_CARM = fcav_IR / (P_TR * T_PRM)
P_TR is normalized for the locked arm cavity with the PRM misaligned.
T_PRM is 5.637%

e.g. for the TR of 100, fcav_IR_CARM = 4.40/(100*0.05637) = 780Hz

                         (IR CARM) o--|
                                      +--[CARM 780Hz zero / ??? pole]
(ALSX) o--|   |-[ALS C 780Hz pole]----|
          | M |
(ALSY) o--|   |-[ALS D 4.40kHz pole]--|
                                      +--[DARM 4.40kHz zero / ??? pole]
                         (IR DARM) o--|

???Hz pole is to ensure the servo filters does not have infinite gain at f=infinite, but in practice we probably can ignore it as long as it is provided by a roll-off filter

  10747   Wed Dec 3 01:18:15 2014 diegoUpdateLSCIR Resonance Script Status

Tonight I started testing a new method for the fine scan:

  • the idea is to use the zero crossings of the PO*11_ERR_DQ signals after (or as an alternative of) the fine scan, but such signals are quite dirty, so I need to find some good way to smooth/filter them;
  • I didn't manage to make many tests, because:
    • once arms were locked fine with ALS, the CARM & DARM lock wasn't very robust, in both acquiring and maintaining lock;
    • during the night, the slow OFSs of the arms misbehaved, and at least once per arm they raised their warning box (independently from each other, and it was hastily recovered), even for values that had been perfectly fine before; I am confused about this;
    • as a result, notwithstanding many tries, the beatnotes are gone;
  • I have enough information to push the script a little further, but I'll do more testing soon;

 

  10746   Tue Dec 2 02:44:45 2014 JenneUpdateLSCTried cav pole compensation trick - fail

[Jenne, Diego]

First, random notes:

  • saw a violin peak in CARM / DARM at 638.0Hz.  Assumed it was one of the ETMs, even though it doesn't match any of the frequencies in our handy-dandy chart: wiki resonances
    • Put an extra notch in the ETM violin filters.
    • Just now realized that I was actuating MC2 at the time for CARM (although 638 is also not what we have in the chart for MC2).  The MC2/ETM violin filters should be shared between eachother.
  • Measured CARM and DARM loops on ALS comm and diff, gains should be 8, not 6.  Fixed in Lock_ALS_CARM_and_DARM script. 
  • MC has been fussy tonight.  I started actuating CARM on ETMs, and that helped, but we've still had several unexplained MC locklosses. 
    • PC and FSS Slow are okay right now, but they have been mad earlier tonight.  Do we need to check the PID tuning for FSS slow?
  • When I first started locking this evening, I was able to hold nice high arm powers (with the usual factor of 2+ RIN), so the IFO seemed okay except for the fussy MC.

Koji suggested last week that we put a cavity pole filter into the ALS error signals, and then compensate for that in the CARM and DARM servos.  The idea is that any RF signals we want to transfer to will have some kind of frequency dependence, and at the final zero CARM offset that will be a simple cavity pole. 

I put a pole at 200 Hz, with a zero at 6 kHz into the LSC-ALS[X,Y] filter banks in FM1, and then also put a zero at 200 Hz with a pole at 6 kHz into both the CARM and DARM servos at FM7.  Ideally I wouldn't have the 6kHz in there, but the compensation filter in the CARM/DARM servos needs a pole somewhere, so I put in the zero in the ALS signals so that they match.  Foton thinks that multiplying the two filters should give a flat response, to within 1e-6dB and 1e-6 deg. 

We can lock CARM and DARM on ALS with the new filters, but it seems to be not very stable.  We've measured transfer functions in both configurations, and between 50-500Hz, there is no difference (i.e., our matching filters are matching, and cancelling each other out).  We sometimes spontaneously lose lock when we're just sitting somewhere with the new configuration, and we cannot run any find IR resonance scripts and stay locked.  We've tried the regular old script, as well as Diego's new gentler script.  We always fail with the regular script during the coarse scan.  With Diego's script, we made it through the coarse scan, but spontaneously lost lock while the script was calculating the location of the peak.  So, we determine that there is something unstable about the new configuration that we don't understand.  Turning off all the new filters and going back to the old configuration is just as robust as always.  Confusing. 

 

  10745   Tue Dec 2 01:27:22 2014 diegoUpdateASCASS Scripts for arms

I updated the medm C1ASS page for the Arm scripts:

ON : same as before

FREEZE OUTPUTS: calls new FREEZE_DITHER.py script, which sets Common Gain and LO Amplitudes to 0, therefore freezing the current output values

START FROM FROZEN  OUTPUTS: calls new UNFREEZE_DITHER.py script, which sets Commong Gain and LO Amplitudes as in the DITHER_ASS_ON.py script, but no burt restore is performed

OFFLOAD OFFSETS: it's the old "SAVE OFFSETS", calls the WRITE_ASS_OFFSET.py script

OFF: same as before

StripTool: same as before

 

 

  10744   Mon Dec 1 20:12:52 2014 ericqUpdateModern ControlRebirth of CESAR / ESCOBAR

 I've uploaded a note at T1400735 about a new implementation of CESAR ESCOBAR ideas I've been working on. Please send me any and all feedback, comments, criticisms!

Using the things I talk about in there, I was able to have a time domain simulation of a 40m arm cavity transition through three error signals, without hardcoding the gains, offsets, or thresholds for using the signals. Some results look like this:

gssimSweep.pdf

I'm going to be trying this out on the real IFO soon...

  10743   Mon Dec 1 17:43:22 2014 JenneUpdateLSCReset Yarm trans normalization

After Koji and I reset the transmission normalizations last Friday, he did some alignment work that increased the Yarm power.  So, I had set the transmission normalization when we weren't really at full Yarm power.  Today I reset the normalization so that instead of ~1.2, the Y transmission PDs read ~1.0.

  10742   Mon Dec 1 17:19:22 2014 JenneUpdateGeneralPMC align

[Diego, Jenne]

Tweaked up the input alignment to the PMC.  Now we're at 0.785.

  10741   Mon Dec 1 17:13:57 2014 SteveUpdateVACRGA scan pd78 -day 63

Quote:

 Our first RGA scan since May 27, 2014 elog10585

 The Rga is still warming up. It was turned on 3 days ago as we recovered from the second power outage.

 

 

Attachment 1: RGAscanD63.png
RGAscanD63.png
  10740   Mon Dec 1 16:34:20 2014 JenneUpdateGeneralIFO wake-up

 

 After its' several days of rest, it is time to wake up the IFO. 

  • FSS temp was railed at +10, which was making the MC not want to lock.  Set it to zero, locked the MC, and ran the MC WFS relief scripts.
  • PMC trans is down to 0.686, so I'll probably want to tweak that up before I get too carried away for tonight. 
  • c1iscex computer was frozen, which I suspect is why Steve found ETMX tripped this morning.  Soft reboot, and we're back to normal.

With that, it's time for a new week of locking, and trying to catch up with the big kids at the sites.

  10739   Mon Dec 1 15:41:38 2014 SteveUpdateGeneralX end fiber insulated and on cable tray

Quote:

Quote:

Quote:

[Steve, Diego, Manasa]

Since the beatnotes have disappeared, I am taking this as a chance to put the FOL setup together hoping it might help us find them.

Two 70m long fibers now run along the length of the Y arm and reach the PSL table.

The fibers are running through armaflex insulating tubes on the cable racks. The excess length ~6m sits in its spool on the top of the PSL table enclosure.

Both the fibers were tested OK using the fiber fault locator. We had to remove the coupled end of the fiber from the mount and put it back in the process. So there is only 8mW of end laser power at the PSL table after this activity as opposed to ~13mW.  This will be recovered with some alignment tweaking.

After the activity I found that the ETMY wouldn't damp. I traced the problem to the ETMY SUS model not running in c1iscey. Restarting the models in c1iscey solved the problem.

 

 AP Armaflex  tube 7/8" ID X 1" wall insulation for the long fiber in wall mounted cable trays installed yesterday.

The 6 ft long sections are not glued. Cable tied into the tray pressed against one an other, so they are air tight. This will allow us adding more fibers later.

 Atm2: Fiber PSL ends  protection added on Friday.

 

[Steve, Manasa] 

Two 70m long fibers are now running through armaflex insulating tubes along the X arm on the cable racks. The excess length of the fiber sits in its spool on top of the PSL enclosure. 

Fibers were checked after this with the fiber fault locator (red laser) and found OK.

 X-arm  AP Armaflex tube insulation is cable tightened into cable tray. Only turning 6 ft sections are taped together.

Remaining things to do: install ends protection tubing

  10738   Mon Dec 1 07:30:29 2014 SteveUpdateSUSETMX damping restored

ETMX sus damping restored and PMC locked manually.

  10737   Wed Nov 26 22:24:28 2014 JenneUpdateLSCDARM loop improved, other work

[Jenne, Koji]

We have done several things this evening, which have incrementally helped the lock stability.  We are still locking CARM and DARM on ALS, and PRMI on REFL165.

  • Saw peaks in CARM error signal at 24Hz and 29 Hz, so put in moderate-Q resonant gains. 
  • DARM at low frequency was much noisier than CARM.  We discovered that we had put in a nice boost at some point for CARM in FM1, but hadn't transferred that over to DARM.  Copying FM1 from CARM to DARM (so replacing an integrator with a boost below ~10Hz) dropped the DARM noise down to match the CARM noise at low frequencies.
  • Koji noticed that we were really only illuminating one quadrant of the Xend QPD, so we aligned both trans QPDs.  Also, I reset the transmission normalization so that all 4 diodes (Thorlabs and QPDs at each end) all read 1 with good alignment.
  • We've got some concerns about the ASS.  It needs some attention and tuning.
    • The X ASS needs an overall gain of about 0.3.  This may be because I forgot to put the new lower gains into the burt restore after Rana's oplev work, or this may be something new.
    • When Koji did a very careful arm alignment, we turned on the Y ASS and saw it methodically reduce the transmitted power.  Mostly it was moving ETMY in yaw.  Why is the DC response of the ASS not good?  The oplev work shouldn't have affected DC.
    • We don't like the way the ASS offloads the alignment.  Maybe there's a better way to do it overall, but one thought is to have an option to offload (for long-term alignment fixing, so maybe once a day) and another option to just freeze the current output (for the continual tweak-ups that we do throughout the evening).  We'd want the ASS to start up again with these frozen values, and not clear them.
  • ETMY was being fussy, in the same way that ETMX had been for the last few months.  I went down to squish the cables, and found that it was totally not strain-relieved, and that the cable was pulling on the connector.  I have zip tied the cable to the rack so that it's not pulling anymore.
  • At high arm powers, it is hard to see what is going on at the AS port because there is so much light.  Koji has added an ND filter to the AS camera so that we can more easily tweak alignment to improve the contrast.

Something that has been bothering me the last few days is that early in the evening, I would be able to get to very high arm powers, but later on I couldn't.  I think this has to do with setting the contrast at the AS port separately for the sideband versus the carrier.  I had been minimizing the AS port power with the arms held off resonance, PRMI locked.  But, this is mostly sideband.  If instead I optimize the Michelson fringes when the arms are held with ALS at arm powers of 1, and PRM is still misaligned, I end up with much higher arm powers later.  Some notes about this though:  most of this alignment was done with the arm cavity mirrors, specifically the ETMs, to get the nice Michelson fringes.  When the PRM is restored and the PRMI locked, the AS port contrast doesn't look very good.  However, when I leave the alignment alone at this point, I get up to arm powers above 100, whereas if I touch the BS, I have trouble getting above 50.


Around GPS time 1101094920, I moved the DARM offset after optimizing the CARM offset.  We were able to see a pretty nice zero crossing in AS55, although that wasn't at the same place as the ALS diff zero offset (close though).  At this time, the arm powers got above 250, and TRY claimed almost 200.  These are the plots below, first as a wide-view, then zoomed in.  During this time, PRCL still has a broadband increase in noise when the arm powers are high, and CARM is seeing a resonance at a few tens of Hz.  But, we can nicely see the zerocrossing in AS55, so I think there's hope of being able to transition DARM over. 

DARMcrossing_Power.png

DARMcrossing_ErrCtrl.png

DARMcrossing_AuxErr.png

DARMcrossing_Angles.png

Now, the same data, but zoomed in more.

DARMcrossing_Power_Zoom.png

DARMcrossing_ErrCtrl_Zoom.png

DARMcrossing_AuxErr_Zoom.png

DARMcrossing_Angles_Zoom.png


During the 40m meeting, we had a few ideas of directions to pursue for locking:

  • Look into using POX or POY as a proxy for POP and instead of REFL, for CARM control.  Maybe we have some nice juicy SNR.
  • Check the linearity of our REFL signals by holding the arms on (or close to) resonance, then do a swept sine exciting CARM ctrl and taking a transfer function to the RF signals.
  • Q is going to look into the TRX QPD, since he thought it looked funny last week, although this may no longer be necessary after we put the beam at the center of the QPD.
  • Koji had a thought for making it easier to blend the CARM error signals.  What if we put a pole into the ALS CARM signals at the place where the final coupled cavity pole will be, and then compensate for this in the CARM loop.  Since any IR signals will naturally have this pole, we want the CARM loop to be stable when it's present.
  • Diego tells us that the Xarm IR beatnote is basically ready to go.  We need to see how big the peak is so we can put it into the frequency counter and read it out via EPICS.  The freq counter wants at least -15dBm, so we may need an amplifier.
  10736   Wed Nov 26 05:15:48 2014 JenneUpdateLSCPRFPMI tonight PRMI 100Hz osc?

[Jenne, EricQ]

Just to get our day started right, we tweaked up the alignment of the Ygreen to the Yarm (after IR alignment), and also touched up the X beatnote alignment on the PSL table.  Ran the LSC offsets script, and then started locking. 

All of the locking tonight has been based on CARM and DARM held on ALS comm/diff, and PRMI held on REFL165.  Today, CARM was actuated using MC2.  No special reason for the switch from ETMs. The AS port is noticeably darker when using REFL165 instead of REFL33. 

Around 12:33am(ish), we were able to hold the arms at powers of about 100, for almost a minute.  The fluctuations were at least 50% of that value, but the average was pretty high.  Exciting.

Q and I tried a few times to engage the AO path while the arms were held at these high powers.  Q hopefully remembers what the gain and sign values were where we lost lock.  We didn't pursue this very far, since I was seeing the 50Hz oscillation that Koji and I saw the other day.  I increased the CARM gain from 6 to 10, and that seemed to help significantly.  Also, messing with the PRMI loops a bit helped.  Q increased the pole frequency in FM 5 for both MICH and PRCL from 2k to 3k.  While he had Foton open, he made sure that all of the LSC DoF filters use the z:p notation. 

I then did a few trials of trying to transition CARM over to normalized REFL11I.  Now that I'm typing, it occurs to me that I should have checked REFL11's demod phase.  Ooops.  Anyhow, using the phase that was in there, I turned on a cal line pushing on ETMs CARM, and found that using -0.002*REFL11I / (TRX + TRY) was the right set of elements.  I also put an offset of 0.05 into the CARM CESAR RF place, and started moving.  I tried several times, but never got past about 30% normalized REFL11 and 70% ALS comm. 

During these trials, Q and I worked also on tweaking up the PRMI lock.  As mentioned last night, PRCL FM3 eats too much phase (~30deg at 100Hz!), so I don't turn that on ever.  But, I do turn on FM1 (which is new tonight), FM2, 6, 8 and 9.  FM8 is a flat gain of 0.6 that I use so I can have higher gain to make acquisition faster, but immediately turn the gain down to keep the loop in the center of the phase bubble.  MICH needed a lowpass, so in addition to FM2, I am now also triggering FM 8, which is a 400Hz lowpass that was already in there. 

Now, my MICH gain is 2.4, with +0.75*REFL165Q, and PRCL gain is -0.02 with -3*REFL165I.  Triggering for both MICH and PRCL is 1*POP22I + 5*TRX with 50 up, 0.1 down. 

In my latest set of locks, I have been losing lock semi-regularly due to a 100Hz oscillation in either the PRCL or MICH loops.  If I watch the spectra, most times I take a step in CARM offset reduction, I get a broad peak in both the MICH and PRCL error signals.  Most of the time, I stay locked, and the oscillation dies away.  Sometimes though it is large enough to put me out of lock.  I'm not sure yet where this is coming from, but I think it's the next thing that needs fixing.

Here is a shot of the spectra just as one of these 100Hz oscillations shows up.  The dashed traces are the nominal error signals when I'm sitting at some CARM offset, and the solid traces are just after a step has been made. The glitch is only happening in the PRMI, not CARM and DARM. 

PRFPMI_currentErrSigs_25Nov2014.pdf

  10735   Tue Nov 25 14:52:14 2014 ericqUpdateOptical LeversOpLev RINs

 At Rana's request, I've made an in-situ measurement of the RIN of all of our OpLevs. PSL shutter closed, 10mHz BW. The OpLevs are not neccesarily centered, but the counts on darkest quadrant on each QPD is not more than a factor of a few lower than the brightest quadrant; i.e. I'm confident that the beam is not falling off. 

I have not attached that raw data, as it is ~90MB. Instead, the DTT template can be found in /users/Templates/OL/ALL-SUM_141125.xml

Here are the mean and std of the channels as reported by z avg 30 -s, (in parenthesis, I've added the std/mean to estimate the RMS RIN)

SUS-BS_OLSUM_IN1 1957.02440999 1.09957708641 (5.62e-4)
SUS-ETMX_OLSUM_IN1 16226.5940104 2.25084766713 (1.39e-4)
SUS-ETMY_OLSUM_IN1 6755.87203776 8.07100449176 (1.19e-3)
SUS-ITMX_OLSUM_IN1 6920.07502441 1.4903816992 (2.15e-4)
SUS-ITMY_OLSUM_IN1 13680.9810547 4.71903560692 (3.45e-4)
SUS-PRM_OLSUM_IN1 2333.40523682 1.28749988092 (5.52e-4)
SUS-SRM_OLSUM_IN1 26436.5919596 4.26549117459 (1.61e-4)
 

Dividing each spectrum from DTT by these mean values gives me this plot:

 RIN.pdf

ETMY is the worst offender here...

  10734   Tue Nov 25 02:04:19 2014 JenneUpdateLSCPRFPMI tonight - need some PRCL and MICH tuning at high arm powers

Take-away for the night:  We need to do some more fine-tuning of the PRCL and MICH loops when we have arm resonance.

Koji sat with me for the first part of the night, and we looked back at the data from last week (elog 10727), as well as some fresh data from tonight.  Looking at the spectra, we noticed that last week, and early in the evening today, I had a fairly broad peak centered around ~51Hz.  We are not at all sure where this is coming from.  The PRMI was locked on REFL 33 I&Q, and CARM and DARM were both on ALS comm and diff.  This peak would repeat-ably come and go when I changed the CARM offset.  At high arm powers (above a few tens? I don't know where exactly), the peak would show up.  Move off resonance, and the peak goes away.  However, later in the night, after an IFO realignment, I wasn't able to reproduce this effect.  So.  We aren't sure where it comes from, but it is visible only in the CARM spectra, so there's some definite feedback funny business going on. 

Anyhow, after that, since I couldn't reproduce it, I went on to trying to hold the PRMI at high arm powers, but wasn't so successful.  I would reduce the CARM offset, and instead of a 50Hz peak, I would get broadband noise in the PRMI error signals, that would eventually also couple in to the CARM (but not DARM) error signal, and I would lose PRMI lock. I measured the PRCL and MICH transfer functions while the arms were at some few units of power, and found that while MICH was fine, PRCL was losing too much phase at 100Hz, so I took away the FM3 boost.  This helped, but not enough. I had 1's in the triggering matrix for TRX and TRY to both PRCL and MICH, so that even if POP22 went low, if the arms were still locked then the PRMI wouldn't lose lock unnecessarily, but I was still having trouble.  In an effort to get around this, I transitioned PRMI over to REFL 165 I&Q. 

While the arms were held around powers of 2ish, I readjusted the REFL 165 demod phase.  I found it set to 150 deg, but 75 deg is better for PRMI locking with the arms.  For either acquiring or transitioning from REFL33, I would use REFL165I * -1.5 for PRCL, and REFL 165Q * 0.75 for MICH.  (Actually, I was using -2 for REFL165I->PRCL, and +0.9 for REFL165Q->MICH, but I had to lower the servo gains, so doing some a posteriori math gives me -1.5 and +0.75 for what my matrix elements should have been, if I wanted to leave my servo gains at 2.4 for MICH and -0.02 for PRCL.) I don't always acquire on REFL165, and if it's taking a while I'll go back to putting 1's in the REFL33 I&Q matrix elements and then make the transition. 

With PRMI on REFL 165 I&Q, I no longer had any trouble keeping the PRMI locked at arbitrarily high arm powers.  I was still using 1*POP22I + 1*TRX + 1*TRY for triggering PRCL and MICH.  My thresholds were 50 up, 0.1 down.  The idea is that even if POP goes low (which we've seen about halfway up the CARM resonance), if we're getting some power recycling and the arms are above 1ish, then that means that the PRMI is still locked and we shouldn't un-trigger anything.  I didn't try switching over to POP110 for triggering, because POP22 was working fine.

Earlier in the night, Koji and I had seen brief linear regions in POX and POY, as well as some of the REFL signals when we passed quickly through the CARM resonance.  I don't have plots of these, but they should be easy to reproduce tomorrow night.  Koji tried a few times to blend in some POY to the CARM error signal, but we were not ever successful with that.  But, since we can see the PDH-y looking regions, there may be some hope, especially if Q tells us about his super secret new CESAR plan. 

Okay, I'm clearly too tired to be writing, but here are some plots.  The message from these is that the PRMI loops are causing us to fluctuate wildly in arm transmission power.  We should fix this, since it won't go away by getting off of ALS.  The plots are from a time when I had the PRMI locked on REFL165, and CARM and DARM were still on ALS comm and diff.  All 3 of these colored plots have the same x-axis.   They should really be one giant stacked plot.

HighPower_7pt3sec_Powers.png

HighPower_7pt3sec_ErrAndCtrls.png

HighPower_7pt3sec_AuxErrs.png

Also, bonus plot of a time when the arm powers went almost to 200:

CARMDARMonALScommdiff_StayingAbove5_upTo175_24Nov2014.png

ELOG V3.1.3-