Reports 1-1 of 1 Clear search Modify search
MIF (General)
dan.chen - 7:48 Thursday 11 June 2026 (37059) Print this report
Initial alignment 260611

With Yokozawa-san

We performed the initial alignment for Xarm, Yarm, OMC and PRMI.

Comments to this report:
dan.chen - 12:15 Thursday 11 June 2026 (37060) Print this report

Detailed report.

Before starting the alignment work, we confirmed that all Type-A suspensions went to LOCK_ACQUISITION.

Xarm alignment

We followed the MEDM procedure for the Xarm alignment. First, we requested IRX_LOCKED, and then requested GRX_LOCKED_WITH_IRX. At this step, it took some time to lock the arm. Therefore, PR3 was slightly moved to improve the locking condition.

After that, we requested ALIGNING_XARM. Since the GRX transmitted power was not good enough, we manually adjusted ETMX and ITMX. As a result, the transmitted powers became approximately GRX ~ 0.96 and IRX ~ 0.95.

Then, we requested RECORD_GOOD_VALUES_XARM and performed OFFLOAD.

Yarm alignment

We also followed the MEDM procedure for the Yarm alignment. We requested IRY_LOCKED, GRY_LOCKED_WITH_IRY, and then ALIGNING_YARM. The alignment condition was already not bad, so we did not perform any manual adjustment.

Then, we requested RECORD_GOOD_VALUES_YARM and performed OFFLOAD.

OMC alignment

For the OMC alignment, we followed the MEDM procedure as well. We requested IRY_LOCKED_FOR_OMC and then INCREASE_LAS_POW_FOR_OMC. We waited until the Guardian comment showed READY.

Then, we requested ALIGNING_TO_OMC. We monitored K1:OMC-TRANS_DC_SUM_OUT16. The value was around 30, which was acceptable. We note that a value larger than about 60 may be dangerous for the OMC DC PD.

Finally, we requested RECORD_GOOD_VALUES_OMC. After recording the good values, the OMC alignment state automatically went down.

PRMI alignment

For the PRMI alignment, we requested ALIGNING_PRMI following the MEDM procedure. At this step, ADS was engaged for IMMT2, PRM, and BS.

After the alignment became stable, we requested RECORD_GOOD_VALUES_PRMI and then performed OFFLOAD.

Search Help
×

Warning

×