Differences between revisions 397 and 413 (spanning 16 versions)
Revision 397 as of 2019-03-01 16:42:06
Size: 2605
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 5: Line 5:
==== Report for the week of 2/25 ==== ==== 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 7: Line 13:
 * Fabian monitored suspensions during the vent.
 * Terrence and Mark made lots of changes to the Guardians and RTMs:
  * Added UI to take snapshots with ALIGNED/MISALIGNED channels (for late use by Guardian).
  * Changed "IM1" and "IM2" in channel names to "IMV" and "IMH"; also "DIO" and "BO" -> "BIO".
  * Created library blocks for BIO and made all the Type B models use them.
  * Tweaked the control topology to be more LIGO-style: the error signal for DC control is sensor-setpoint (not setpoint-sensor as in many controls textbooks); the input to the damping block is the uninverted sensor signal(s); there is a hard-wired -1 after the damping block representing default negative gain.
 * Fabian went inside the SRM chamber and diagnosed the problem that had appeared shortly before vent. It turned out to be yaw of the IP causing a payload cable to touch. He fixed it with the F0 yaw stepper. (He had tried this earlier without success but it turned out the problem was another dead output on the stepper driver.)
 * Terrence traced the geophone issue to a group of dead channels (#20-23) on the AA chassis. We tried replacing the chassis and it fixed not only the geophone issue but an issue in the TILT OL path (#24-27) that we had planned to debug next.
 * We retested the BIO for stepper remote enable system and this time it was working (probably due to the refactoring of the BIO stuff in the model and/or all the restarts).
 * We rebuilt all the IOP models after removing an unneeded ADC1 block (corresponding to hardware that Yoshizawa-san had removed).
 * Enzo and Terrence wrote Python scripts to automate the process of adapting the control filters to the new topology (where the DAMP and DCCTRL functions are in parallel instead of series).
==== Plan for week of 3/4 ====
 * Enzo at Mitaka.
 * Mark, Fabian Mon-Wed (Thu is farewell party).
 * Final tweaks of SRM?
 * Monitor (re-)pumpdown.
 * Tests of new Guardian.
 * Final test of stepper remote enable system (someone in cleanroom checks the lights go on/off).
 * Continue monitoring SRM yaw drift.
 * Setup SRM and SR3 LEN OLs.
 * Work on Type B paper.
==== 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 29: Line 27:
==== Plan for week of 3/11 =====
 * Mark at Kamioka full week?
 * Enzo at Kamioka Mon, Tue, then JPS.
 *
Line 34: Line 28:
 * Enzo vacation, 3/5 and 3/6.
 * Enzo et al. Farewell Party, 3/7.
 * Enzo at JPS then final vacation, 3/13-29
 * Terrence's last day, 3/29.
 * 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)