Reports 1-1 of 1 Clear search Modify search
AdV-COM (AdV commissioning (1st part) )
bersanetti, ruggi - 0:07 Friday 23 March 2018 (40881) Print this report
Arms relocked, ITF_LOCK revived

This afternoon we resumed the recovery of the ITF, starting again from pre-aligning the arms themselves (and the PRM position). Outcome:

  • the demodulation phases of RFC, B7 and B8 have been retuned, the arms' ones in particular with good precision;
  • we locked both arms, after some work on the WI driving balancing (see Fig.1);
  • the arms are in much better condition w.r.t. yesterday, due to the decreased frequency noise and work on the INJ side (see Fig.2);
  • the corrections on the ITMs are therefore much less saturating, allowing a more stable lock and, in principle, a sensitive error signal for the drift control to work as intended;
  • indeed we restored the drift control, but quite big offsets are needed in order to correctly zero the error signal;
  • we restored the normal functionality of Metatron, now we can start using ITF_LOCK again.

At this point we looked into MICH, but our fringe signal (B1p/(B1p+x B4), a.k.a. LSC_B1p_SUM_NORM) is much smaller than usual, spanning from 0 to just 0.2; to be checked if the intercalibration between B1p_DC and B4_DC has changed, or something needs to be realigned. Looking at the signals, the issue seems related more to B1p than B4.

We leave the arms locked, so ITF_LOCK is in LOCKED_ARMS. Note that the automatic FmodErr tuning is still disabled (via ITF_LOCK.ini), it could be worth tomorrow to check also the automated tuning, but after a first manual one (which can be done much faster).

Images attached to this report
Comments to this report:
carbognani - 8:44 Friday 23 March 2018 (40882) Print this report

This night , at around 02:20 UTC after an unlock of the North Arm:

2018-03-23-02h20m41-UTC>WARNING-The North Arm has unlocked! Relocking the arm...

both ITF_LOCK and CARM_DARM_LOCK nodes went into error:

2018-03-23T02:20:42.382Z CARM_DARM_LOCK W: Traceback (most recent call last):
  File "/virgo/ext/metatron/metatron-1.4/lib/python2.7/site-packages/guardian/worker.py", line 461, in run
    retval = statefunc()
  File "/virgoDev/Automation/userapps/META_library.py", line 148, in wrapper
.......
    data[0].value = value
TypeError: string expected instead of NoneType instance


2018-03-23T02:20:42.383Z ITF_LOCK W: Traceback (most recent call last):
  File "/virgo/ext/metatron/metatron-1.4/lib/python2.7/site-packages/guardian/worker.py", line 461, in run
    retval = statefunc()
  File "/virgoDev/Automation/userapps/META_library.py", line 148, in wrapper
    return func(*args, **kw)
....
  File "/virgo/ext/metatron/guard_dep/epics-3.14.12.2_long/Linux-x86_64-CL7/pyext/pyepics/lib/python2.6/site-packages/epics/ca.py", line 1009, in put
    data[0].value = value
TypeError: string expected instead of NoneType instance

 

This morning we tried to drive again all nodes to DOWN and relock the arms and this could be immediately achived:

2018-03-23T07:12:46.916Z ITF_LOCK [LOCKED_ARMS.enter]

Those errors are under investigation.

genin, tacca - 10:49 Friday 23 March 2018 (40887) Print this report

We retuned the demodulation phase of the RFC this morning it was wrong by 0.4rad.

We change the value in the SIB2 photodiode config file from 2.6 to 2.2.

As you can see on the attached plot, there is a large improvement below 100Hz. The bump above 100Hz is normal.

The mid-frequency fluctuation of B7 and B8_dc have been reduced a lot thanks to this retuning.

Images attached to this comment
Search Help
×

Warning

×