|
Size: 1630
Comment:
|
Size: 2580
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| * Time :''' From 2020/Apr/1(09: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 14: | Line 15: |
| || Apr/03 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode || || Apr/04 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode || || Apr/05 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode || || Apr/06 ||(am9-am1) ADS, BPC, IMC angular control, etc, (am1-am9) silent mode || |
|| 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 || |
| Line 29: | Line 30: |
| || Apr/21(am9 ~ ) || OMC noise injection and so on || | || Apr/21(am9 ~ ) || Post Observation Activities : OMC noise injection and so on || |
| Line 33: | Line 34: |
| === For shifts === | === For shifts for ER and OBS === |
| Line 35: | Line 36: |
---- === Observation : Points to Remember === * 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. |
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
- 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.