|
Size: 3540
Comment:
|
Size: 3503
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Line 6: | Line 5: |
| ==== Report for week of 11/19 ==== * BS * Fabian did some debugging on the BS and found that the calibration for the F0 LVDT was off due to an Excel error, and that the sag wasn't quite the 7 mm originally observed, but still enough to cause the suspension to touch down. Enzo tried applying LVDT actuation at the GAS filters and got it to lift off far enough to get sensible TFs, but the required BF offset was enough to put the IM OSEMs at the very edge of their usable range, so this is not a good long-term solution. We can probably raise the F0 keystone during the vent by removing mass and/or installing an auxiliary spring, which will then allow us to return the BF keystone to nominal height. * While working on the BS, Enzo noticed that one of the stepper drivers was not responding. It turned out to be water damaged from the rain issues earlier in the year. Enzo and Fujii-kun opened the rest of the BS chassises on the second floor but they seem to be OK. Tanaka-san had made a third driver chassis as a spare, so we reserved that and will install it in the week of 12/10. * SRM * The SRM-W optic arrived and we installed it in place of the SRM-M in the metal mass, taking care to use 1.4 mm shims as recommended by Hirose-san. The weight of the new assembly was within 1 g of the old and did not disturb the height of the payload. There was a very small change in pitch which we corrected with the IM picos. * We installed the shelf for the OL receiver. * We added the arc weights and geophones and went through several rounds of improving the centering of the IP and then realigning the security structure back to vertical. * We calibrated the F0 LVDT, and checked the F0 and IP actuation signs. * We adjusted the SF trim masses to set the SF pitch and roll, did an inventory of the trim mass and set the damper gap. * We did a final alignment of the whole chain and left the suspension ready for TFs during the f2f week. There is only a few hours of work left before we can install and we hope to do that on Monday 12/10. * SR2 * Enzo replaced the geophones and cables that had been borrowed for calibration and did several rounds of optimization of the IP frequency. He got as low as 46 mHz but with poor Q and so backed off a bit to 55 mHz and may back off a tiny bit more. * I derived updated IP matrices for the BS and SR, with more precise geometry data provided by Hirata-san, and published them as T1707205 and T1807663. * I created a CENTERING screen for the IP, with large panel meters for the LVDT signals and the derived L, T and Y signals. * Enzo confirmed that the fancy stepper control screen created by Shoda-san worked. * We installed a modified LPCD as IM-V for testing. * SR3 * We moved HPCDs from BS and SR2 to replace the ones that had been stolen from SR3, so as to create a working suspension with an OL for Kozu-kun. ==== 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)]] |
==== 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 30: | Line 13: |
| ==== 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 31: | Line 27: |
| ==== Plan for week of 12/3 ==== * f2f Meeting at NAOJ - no Kamioka work. ==== Plan for week of 12/10 ==== * Crane SRM into tank. * Install new F0 yaw mechanisms on SRs. * Remove First Contact from SRM, unlock and realign. * Move SRM in-air cables over. |
==== 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.