Differences between revisions 315 and 413 (spanning 98 versions)
Revision 315 as of 2018-08-29 15:16:23
Size: 4322
Editor: MarkBarton
Comment:
Revision 413 as of 2019-04-26 13:22:17
Size: 3503
Editor: MarkBarton
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Line 6: Line 5:
==== Report for week of 8/13 ====
 * KAGRA was closed Mon/Tue 8/13-14 due to O-Bon.
 * Enzo and team debugged an issue with height of the SR3 keystone coupling to yaw of the payload as measured by the OL. We suspect a ferromagnetic item on the SF damper, but we're not sure.
==== Report for the week of 4/15 ====
 * Fabian debugged a dead stepper on SR3 (broken driver channel) and a dead geophone on SRM (unplugged cable). He made another update to the table used by the Python script for the stepper driver MEDM screen to reflect the remapping.
 * Fabian monitored the pumpdown and he and Hirata-san did post-pumpdown checks of all the suspensions. They were all healthy.
 * Hirata-san participated in the health checks and learned about the computer systems.
 * Mark did major revisions to the MEDM menu on the OVERVIEW screen with scripts for making `safe.snap` files and snapshots of setpoints. He made the `safe.snap` files in directories under `/opt/rtcds/kamioka/k1/target` into symbolic links to files in `/opt/rtcds/userapps/release/vis/k1/burtfiles`, alongside the setpoint files, so that they could be backed up to the SVN (as at LIGO).
 * Mark did major updates to his `vistools.py` Python package for manipulating the suspensions (based on his LIGO `sustools.py`). He added entries for Type B suspensions to the internal database and added commands for manipulating SET and DCCTRL blocks. He also added commands to simulate pressing on the `CLEAR HISTORY` and `LOAD COEFFICIENTS` buttons.
 * Mark started updating the `TYPEB.py` Guardian definition file to use `vistools.py`. So far only the `ENGAGING_IP_CONTROL` state has been fully rewritten and tested, but other states will be simple adaptations. It should be easy to do Type A and other Guardians in the same style.
Line 10: Line 13:
==== Report for week of 8/20 ====
===== SR3 =====
 * Hatoya-san and Enzo gathered date for a study of yaw mode Q damping time as a study of damper ring height.
===== SR2 =====
 * We continued with cabling work.
 * We configured the second pico driver and connected it.
 * We assembled the LBB damper rings in the tank, craned them to near the top and hooked them. While the tank was open we also set the jacks below the mushroom that will support the suspension to nominal height.
==== Report for the week of 4/22 ====
 * Fabian debugged an anomaly he found in the SRM (klog 8672) and found it was OK if the BF was high enough (klog 8733).
 * Mark and Terrence worked on improvements to the Guardian and the vistools.py package.
  * We debugged a problem where vistools.py triggered channel access timeouts when a Vis object was created in a live Guardian (it worked fine in a plain iPython session or the interactive mode of the Guardian). It turns out that in the live mode of the Guardian, the Ezca instance used for accessing the suspension is not a global variable (contrary to the documentation) but is associated with the GuardState class. Worse, creating a second Ezca instance upsets things. We came up with a workaround to grab and reuse the Ezca object already defined.
  * Mark added many new functions to vistools.py, including one to read the BIO WD status, and a group to manipulate the OLSET and OLDCCTRL filter blocks.
  * Terrence rewrote the TYPEB.py Guardian from scratch in terms of functions from vistools.py.
  * We removed the RESET state.
  * We renamed the DCCTRL_ONLY state to FLOAT and reimplemented it to switch the DCCTRL INPUT switches off (instead of the HOLD switches on).
  * We revised the OL_DAMPING_ENGAGED and neighboring states (ALIGN, MISALIGN etc).
  * We changed the RTMs to remove the TM_OSEM_DAMP blocks and to have the SET blocks connect only to the DCCTRL blocks (not the DAMP blocks).
  * We updated the PAYLOAD and OVERVIEW screens to reflect the RTM changes. We also fixed some broken links and fields related to the BIO functions.
==== Plan for week of 4/29 ====
 * Glorious 10-day break!
Line 18: Line 27:
===== SRM =====
 * We reserved and configured two pico drivers.
 * We checked the prism gluing and all the jigs came away successfully.
 * Fabian assembled the RM.
 * Hirata-san added ballast masses to the IM and we weighed it, as well as the RM and the optic in the mirror box.
 * We suspended the optic and RM.

==== Report for week of 8/27 ====
===== SR3 =====
 * We did an inventory of arc weights to see if we had enough for SRM and found that we had only enough for a basic allocation for all of type B (172 kg for BS and 103.2 kg per SR) with almost no spare for tuning.
 * Using SR3, we did a quick study of the IP frequency as a function of the number of arc weights, to see how much more we might need. 3 pairs of small arc weights (10 mm thick, 4.53 kg each) brought the frequency below 0.1 Hz, 4 pairs made it unstable. If SR3 is typical we would need about 27 kg extra per suspension.
 * After the IP study, we left three pairs of 10 mm arc weights installed on the IP for more investigation with the digital system (instead of a stopwatch).

===== SR2 =====
 * We finished routing the in-vacuum cables, and connected everything through to the rack for final testing.
 * We brought a basic 103.2 kg set of arc weights (3 large (38 mm) and 6 medium (19 mm)) into the SR2 cleanbooth.

===== SRM =====
 * Panwei calibrated 6 OSEMs to be used on the IM.
 * We brought in all the remaining arc weights from the pallet into the SRM cleanbooth, and Hirata-san cleaned up 1 large arc weight and 3 mediums left over from the BS that complete a basic set of 103.2 kg, plus about 5 kg spare. (However 27 kg of these are on loan to SR3.)
 * We assembled and installed the bottom section of the security structure under the optic and RM.
 * We set up a new OL for setting the pitch. We found the reflection off the AR surface was much weaker than for SR2 and SR3, but fortunately the HR surface is almost flat (ROC≈300 m) so we were able to use the HR reflection instead.
 * ''We set the pitch of the SRM and RM and tightened the wire clamps.''

==== Plan for week of 9/3 ====
 * Mark, Enzo, Hirata-san, Fabian, Kozu-kun, Panwei at Kamioka Mon-Fri.
 * (Mark possible trip to LIGO Hanford - TBD.)
===== SR2 =====
 * Crane in SR2.
 * Move SR2 in-air cables.
 * Remove First Contact
 * Unlock and realign payload.

===== SRM =====
 *
===== Etc =====
 * Prepare for scheduled power outage on 9/10.

==== Plan for week of 9/10 ====
 * Monday 9/10 is scheduled power outage.
 * Mark, Hirata-san, Fabian, Kozu-kun, Panwei at Kamioka Tue-Fri.
 * Enzo at Kamioka Tue-Thu, then JPS Meeting Fri, then vacation.
 * Recover from power outage.

==== Plan for week of 9/17 ====
 * Monday 9/17 is holiday (Respect for the Aged Day).
 * Enzo on vacation.
 * Mark, Hirata-san, Fabian, Kozu-kun, Panwei at Kamioka Tue-Fri.

==== Plan for week of 9/24 ====
 * Monday 9/24 is holiday (Autumn Equinox).
 * Mark, Hirata-san, Fabian, Kozu-kun, Panwei at Kamioka Tue-Fri.

==== To-Do Lists, Schedule ====
 * [[KAGRA/Subgroups/VIS/TypeB/ToDoBS]]
 * [[KAGRA/Subgroups/VIS/TypeB/ToDoSR]]
 * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=7779|JGW-L1807779 Type B Schedule (SR)]]

==== Vacation Info ====
 * Mark: 8/13-16.
 * Hirata-san: 8/13-17
 * Terrence: 8/24-26 f2f, then returns to Hong Kong.
 * Enzo: 9/14 JPS, 9/15 through 10/8 vacation in Chile.
==== Vacation/Travel Info ====
 * Terrence's next visit from 4/18 to 7/27.
 * Fabian's vacation 4/25 to 5/10.
 * Mark's US vacation from 5/22 to 6/11.
 * Mark's final day 6/28.

Scraps of text for incorporation in the VIS Meeting Minutes

KAGRA/Subgroups/VIS/MeetingNAOJ

Type B (Mark)

Report for the week of 4/15

  • Fabian debugged a dead stepper on SR3 (broken driver channel) and a dead geophone on SRM (unplugged cable). He made another update to the table used by the Python script for the stepper driver MEDM screen to reflect the remapping.
  • Fabian monitored the pumpdown and he and Hirata-san did post-pumpdown checks of all the suspensions. They were all healthy.
  • Hirata-san participated in the health checks and learned about the computer systems.
  • Mark did major revisions to the MEDM menu on the OVERVIEW screen with scripts for making safe.snap files and snapshots of setpoints. He made the safe.snap files in directories under /opt/rtcds/kamioka/k1/target into symbolic links to files in /opt/rtcds/userapps/release/vis/k1/burtfiles, alongside the setpoint files, so that they could be backed up to the SVN (as at LIGO).

  • Mark did major updates to his vistools.py Python package for manipulating the suspensions (based on his LIGO sustools.py). He added entries for Type B suspensions to the internal database and added commands for manipulating SET and DCCTRL blocks. He also added commands to simulate pressing on the CLEAR HISTORY and LOAD COEFFICIENTS buttons.

  • Mark started updating the TYPEB.py Guardian definition file to use vistools.py. So far only the ENGAGING_IP_CONTROL state has been fully rewritten and tested, but other states will be simple adaptations. It should be easy to do Type A and other Guardians in the same style.

Report for the week of 4/22

  • Fabian debugged an anomaly he found in the SRM (klog 8672) and found it was OK if the BF was high enough (klog 8733).
  • Mark and Terrence worked on improvements to the Guardian and the vistools.py package.
    • We debugged a problem where vistools.py triggered channel access timeouts when a Vis object was created in a live Guardian (it worked fine in a plain iPython session or the interactive mode of the Guardian). It turns out that in the live mode of the Guardian, the Ezca instance used for accessing the suspension is not a global variable (contrary to the documentation) but is associated with the GuardState class. Worse, creating a second Ezca instance upsets things. We came up with a workaround to grab and reuse the Ezca object already defined.

    • Mark added many new functions to vistools.py, including one to read the BIO WD status, and a group to manipulate the OLSET and OLDCCTRL filter blocks.
    • Terrence rewrote the TYPEB.py Guardian from scratch in terms of functions from vistools.py.
    • We removed the RESET state.
    • We renamed the DCCTRL_ONLY state to FLOAT and reimplemented it to switch the DCCTRL INPUT switches off (instead of the HOLD switches on).
    • We revised the OL_DAMPING_ENGAGED and neighboring states (ALIGN, MISALIGN etc).
    • We changed the RTMs to remove the TM_OSEM_DAMP blocks and to have the SET blocks connect only to the DCCTRL blocks (not the DAMP blocks).
    • We updated the PAYLOAD and OVERVIEW screens to reflect the RTM changes. We also fixed some broken links and fields related to the BIO functions.

Plan for week of 4/29

  • Glorious 10-day break!

Vacation/Travel Info

  • Terrence's next visit from 4/18 to 7/27.
  • Fabian's vacation 4/25 to 5/10.
  • Mark's US vacation from 5/22 to 6/11.
  • Mark's final day 6/28.

KAGRA/Subgroups/VIS/TypeB/Minutes (last edited 2022-10-28 10:02:46 by fabian.arellano)