Here are the GPS times we've spent in the NEW DARM
state. This is primarily useful for Keita, Sheila, and I as we try to better understand why weren't able to stay in the state in early Jan.
Time based on Sheila's investigative work from earlier this month: LHO:75308 and LHO:75348. The table of NEW DARM periods below does not include failed attempts. Instead, I just included successful transitions to the NEW DARM state (GRD STATE 710) in hopes of following up on LHO:75432. In addition, I've check the CAL-CS filterbank and gain states for each of the NEW DARM transitions in the table below as well. All but the last entry contain at least 10 minutes of "undisturbed" time during which CAL-CS was not changed. During the last window (GPS 1387237749-1387239372), CAL-CS saw many changes.
1386536646 |
1386544194 |
02:06:09 |
more info in LHO:75348; no CAL-CS changes during stretch |
1386619903 |
1386623884 |
00:35:41 |
more info in LHO:75348; no CAL-CS changes during stretch |
1387033311 |
1387033995 |
00:11:10 |
successful transition, more info in LHO:75348; no CAL-CS changes during stretch |
1387140065 |
1387141308 |
00:20:51 |
more info in LHO:75348; no CAL-CS changes during stretch |
1387237749 |
1387239372 |
00:26:49 |
more info in LHO:75348, initially discussed in LHO:74977 CAL-CS changed throughout. see NEW_DARM_scope_1387237749.png |
==
I used the ndscope command below to check the CAL-CS pipeline for changes:
ndscope H1:GRD-ISC_LOCK_STATE_N . H1:CAL-CS_DARM_FE_ETMX_L1_LOCK_L_SWSTAT , H1:CAL-CS_DARM_FE_ETMX_L1_DRIVEALIGN_L2L_SWSTAT , H1:CAL-CS_DARM_FE_ETMX_L1_LOCK_L_GAIN H1:CAL-CS_DARM_FE_ETMX_L1_DRIVEALIGN_L2L_GAIN . H1:CAL-CS_DARM_FE_ETMX_L2_LOCK_L_SWSTAT , H1:CAL-CS_DARM_FE_ETMX_L2_DRIVEALIGN_L2L_SWSTAT , H1:CAL-CS_DARM_FE_ETMX_L2_LOCK_L_GAIN H1:CAL-CS_DARM_FE_ETMX_L2_DRIVEALIGN_L2L_GAIN . H1:CAL-CS_DARM_FE_ETMX_L3_LOCK_L_SWSTAT , H1:CAL-CS_DARM_FE_ETMX_L3_DRIVEALIGN_L2L_SWSTAT , H1:CAL-CS_DARM_FE_ETMX_L3_LOCK_L_GAIN H1:CAL-CS_DARM_FE_ETMX_L3_DRIVEALIGN_L2L_GAIN . H1:LSC-DARM1_SWSTAT , H1:LSC-DARM1_GAIN