Size: 1300
Comment:
|
Size: 1300
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 33: | Line 33: |
1. With intel Zion v2. Upgrading to v4 solved the problem. KAGRA will test it. | 1. With intel Xion v2. Upgrading to v4 solved the problem. KAGRA will test it. |
LIGO-KAGRA CDS meeting - 6/21 8am (JST), 6/20 6pm (LLO)
Connection Info
Teamspeak (password protected page. KAGRA wiki account is necessary to view.)
Participants
Osamu, Takahiro, Keiko, Keith, Rolf, Jamie
Agenda
Takahiro's slide https://gwdoc.icrr.u-tokyo.ac.jp/cgi-bin/DocDB/ShowDocument?docid=8403
- Solved issues in KAGRA
- Timing (IRIGB issue)
- Installation of the trend writers
- Dolphin disable script
- Remaining issues in KAGRA
- CPU Max issue
- LIGO's update
Minutes
(Trend writer) when data file is separated in multiple local SSD (?) the NDS server can read regardless of the separated files => Keith will send us his note.
- (Dolphin) There are two ways to kill the other models:
- Disable the links when FEs shutdown
- Disable the node ID to swith
=> Keith will send us a not too. LIGO's new Dolphin ---
- (CPU max) LIGO had the same experience when
- With intel Xion v2. Upgrading to v4 solved the problem. KAGRA will test it.
- When the fiber links between an FE and IO chassis age. Symptom was dropping communications.
- LIGO's new IO chassis is PCIE gen2. Regular LC-LC fibers.
Next meeting
TBD.