== ER200401~200407, OBS200407~200421 == * ER Time :''' From 2020/Apr/1(09:00) to 2020/Apr/7(09:00)''' * OBS Time :''' From 2020/Apr/7(17:00) to 2020/Apr/21(09:00)''' * Rough Schedule (time can be shifted by 1 or 2 hours according to the task progress and delay) || Mar/29 || Commissioning || || Mar/30 || Commissioning || || Mar/31 || Commissioning, ADS, BPC, IMC angular control, etc || || || || || Mar/31(pm5~) || ER start || || Apr/01 ||(am9-pm5) CAL Day 1, (rest time) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode || || Apr/02 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode for CAL2 || No JRPC meeting held, only LVEM call|| || Apr/03 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode for CAL2 || || Apr/04 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode for CAL2 || || Apr/05 ||(am9-am1) ADS, BPC, IMC angular control, FF adjustment, etc, (am1-am9) silent mode for CAL2 || || Apr/06 ||(am9-am1) Ocean Violence, (am1-am9) silent mode || || Apr/07(~am9) || ER end || || || || || Apr/07(am9-pm5) || Maintenance for observation || || Apr/07(pm5~) || Observation Start || || || || || Apr/09 || During Observation || If we got positive results, we hope to ask something about O3c in JRPC meeting || || || || || Apr/16 || During Observation || If we got positive results, we hope to ask something about O3c in JRPC meeting || || || || || Apr/21(~am9) || Observation End || || || || || Apr/21(am9 ~ ) || Post Observation Activities : OMC noise injection and so on || ---- === For shifts for ER and OBS === * [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=11578|Shift members]] ---- === Observation : Points to Remember === * Basic * Any problems during Observation will be discussed by Miyoki, Yamamoto, Ito and related group (and SEO members) and we decide the directions. Please report these 3 persons and in "klog" if you notice any problems. * If we encounter violent ocean conditions, temporal down of IFO will be selected. * Daily morning meeting won't be held during Observation to avoid dense situation. Daily necessary information including from office staffs will be sent via e-mail during 9am-10am. * Expected Improvements compared with the previous ER and OBS * CAL injection reliability * Injection failure is improved ? -> Still need to monitor whether cal line is injected or not. In the case of no cal line, we should apply cal line manually. The instruction manual will be prepared by CAL group * Initial oplev (mirror alignment) condition at the starting point of relock process * Alignment recorder is installed at proper timing during lock acquisition ? -> Alignment Recorder was applied. It works good ! * ADS/BPC situation * Which are effective, which should be postponed ? -> ADS for ETMs has need more adjustment. We try ASC by using QPDs on AS table, and try more adjustment about offset for BPC/ADS. * IMC angular control * It works. * ISS stability * Improved ? , applying timing is changed ? -> Control servo was improved. However, ISS system cannot follow the power up process. So ISS was set to applied at the final stage of the LSC_LOCK guardian. It now wrorks very well. * Expected kick at the unlock timing, and known annoying excitation of a suspension system. * Guardian is implemented -> It works very well. The kick was minimized. * Off load status for each suspension. * Done according to klog ? -> TypeA, TypeBp were done, while some of Type B will be checked. * How about OMC suspensions -> They should be checked because OMC ADS will push OMMTs that has small dynamic range. * Summary page reliability is enhanced ? * hardware trouble was fixed. However, software troubles still remain. We will keep improving. * SAL (monkey) Alignment reliability * Dewhitening for TM that might contributes a bit to sensitivity should be included or not ? -> No problem. Lock_loss during LSC_LOCK guardian due to not saturation but other reason. We will check later. * When should we try SAL (monkey) alignment ? -> if you cannot IFO for 1 hours, please try SAL alignment. The beam positions on mirrors, OMC direction are important as checking list. * How much IMC output power should be selected ? -> 5W. We have no confidence that 10W can improve the sensitivity. * Additional sound proof for bellows -> done. we hope some improvement in sensitivity. * Others * Actual tasks during OBS * Shift Member Duty and Manual : * Basic monitoring and recording (by Miyakawa) * Manual (important check points) *Please write klog by selecting a category of "Observation". *Please make a memo about SAL alignment by using [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=11596 |this memo style]] prepared in the control room. * LOCK_LSC guardian Process was changed *Assuming from "DOWN" state *(a) Down (as an initial condition) *(b) Push "PRFPMI_LSC_LOCKED_RF", not "OBSERVATIUON". *(c) If IFO reaches "PRFPMI_LSC_LOCKED_RF" state, wait until the TMSXY power seem to be maximized. *(d) If you judge TMSXY power is around max, push "OBSERVATION". *note: OMC hand off (PRFPMI_LSC_LOCKED) still has unstability, and tends to fail. We are still tweaking now. *(e) IF IFO reaches "OBSERVATION", ADS for ETMs will be off, and BPC will be ON. * Maintenance Day Activities (from CAL, DGS, FLC/SAF etc groups) * SAF/FCL: Weekly SAF/FCL check will be held in the morning on Tuesday (Furuta, Hayakawa, Yoshimura, Kamioka-mine company) * DGS: * CAL: * '''Restricted Remote Access (from T.Yamamoto)''' * We plan to stop the access to controls@k1gate again from 17:00 on 4/7. *If you face some emergency, please use your personal accounts in order to login DGS network. *> ssh firstname.lastname@172.16.33.11 *I ask you to use these personal accounts only for a emergency response. *If you need remote access to know the site situation, subsystem status, etc as a daily check, please join to develop remote access tools such as SummaryPage, Pastavi etc. *Unfortunately, some people probably used these accounts for daily monitoring not for a emergency response during previous run. But we need reliable observing data at least during the observing run. ---- === Post Observation Tasks : Items and necessary time === . 5/18,19 Kashiwa network stop-> no access to/form outside at Kamioka, but inside OK . 5/26 11AM~(30min?): 200V power down at Kamioka building. * Calibration (~1day) -> Yamamoto * Power recycling gain for sidebands (~ 1 day) -> * LSC and ASC sensing matrix (~ 2 days) -> Ushiba * ISS contribution, frequency noise contribution to DARM (2 days) -> Kokeyama, Miyakawa * Finesse/loss measurement for X/Y arm (~ 1 day) -> * MICH contrast defect with MICH locked and FPMI locked (~ 1 day) -> Nakano * Mode content of AS (OMC cavity scan) (~ 1 day) -> Aso, Kokeyama * Scattered light, swing test, IOO investigations (~5days) -> Yokozawa * PEM injections (~2day) -> Yokozawa * Type Bp measurement with some restricted IFO (~2days) -> Fabian * BS measurement with some restricted IFO like simple Michelson (~2days) -> Fabian * Type A measurement with some restricted IFO like Xarm (~2days) -> Lucia * Feasibility of locking DRFPMI (~ 3 week) -> Nakano * Damping the known Type-A suspension peaks by DARM -> Yokozawa * Targets are 46Hz and 180Hz. * Merit : We can learn how to damp those noises * Demerit1 : The damping filter would be change after cooling down and after fixing the local sensors. * Demerit2 : Can we use DARM signal for damping? * Fill the eigenfrequencies for Type-A suspension. -> Yokozawa * [[https://gwdoc.icrr.u-tokyo.ac.jp/DocDB/0111/T1911116/001/20191213tyamada_sumconCRYp20161025.pdf]] * Merit : Identification of the line noise sources for the sensitivity of this observation run. * (We can make following noise investigation [[https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/private/DocDB/ShowDocument?docid=11514]]) * Demerit : Those frequency may change in the future observation.