|
Size: 615
Comment:
|
Size: 3302
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == ER200331~200407 == | == ER200401~200407, OBS200407~200421 == |
| Line 3: | Line 3: |
| * Time :''' From 2020/Mar/31(17:00) to 2020/Apr/7(09:00)''' | * 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)''' |
| Line 5: | Line 6: |
| * Rough Schedule | * Rough Schedule (time can be shifted by 1 or 2 hours according to the task progress and delay) |
| Line 7: | Line 8: |
| || Mar/31(~ 09:00) || Commissioning and preparation || || Mar/31(09:00 ~) || IFO stabilization || || Apr/01 || CAL Day 1 (??:00 - ??:00)|| || Apr/02 || CAL Day 2 (??:00 - ??:00)|| || Apr/03 || IFO stabilization || || Apr/04 || IFO stabilization || || Apr/05 || IFO stabilization || || Apr/06 || FF(??-??) || || Apr/07(~ 09:00) || ER End || || Apr/07(09:00 ~) || Observation Start || |
|| 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 || |
| Line 19: | Line 34: |
| === For shifts === * [[KAGRA/EngineeringRun//ER200331-0407/Shift|Shift manuals]] |
=== 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 we decide the directions. * 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. *Tasks during Obserbation * Shift Member Duty and Manual (from Miyakawa) : * * Maintenance Day Activities (from CAL, DGS, FLC/SAF group) * Saf/FAL: Weekly FCL check will be held in the morning on Tuesday (Furuta, Hayakawa, Yishimura, 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 <mailto: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 === * * * * * |
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
Observation : Points to Remember
- Basic
- Any problems during Observation will be discussed by Miyoki, Yamamoto, Ito and related group and we decide the directions.
- 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.
- Tasks during Obserbation
- Shift Member Duty and Manual (from Miyakawa) :
- Maintenance Day Activities (from CAL, DGS, FLC/SAF group)
- Saf/FAL: Weekly FCL check will be held in the morning on Tuesday (Furuta, Hayakawa, Yishimura, 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.
- 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.