KAGRA Logbook

DGS (General)

satoru.ikeda - 18:40 Friday 07 February 2025 (32617)

Update model files

Request from Ushiba-san

Separate the Payload model into 16KHz and 2KHz models.

[K1EX1,K1EY1,K1IX1,K1IY1]
model: k1vis{etmx,etmy,itmx,itmy}{p,lsc<New>}
detail:

EPICS Channel Changes
CHANGE
K1:VIS-{ETMX,ETMY,ITEMX,ITMY}_HIERSWITCH => K1:VIS-{ETMX,ETMY,ITEMX,ITMY}_HIERSWITCH_L
Add
K1:VIS-{ETMX,ETMY,ITEMX,ITMY}_HIERSWITCH_{P,Y}

Model file changes
Separated LSC processing (k1visetmxlsc) and Payload processing (k1visetmxp) at the input of the ADD module for MN, IM, and TM in the Payload model (k1visetmxp).
　Change so that values added only by the Payload model are sent and added on the LSC processing (k1visetmxlsc) side.

The separated Payload model is changed to 2KHZ, and the separated LSC-related processing is changed to 16KHZ.

Combine the NBDAMP model (k1visetmxnb) with the Payload model and delete it.
Reuse dcuid and specific_cpu used in NBDAMP in the LSC-related model (k1visetmxp).
The output of NBDAMP combined with the Payload model was delayed by one sample by adding a unit delay due to the model configuration.

HIERSWITCH in the modified EPICS channel was separated into HIERSWITCH_{l,P,Y} from only L before the modification.

LOCAL_INF was added before ADD in the LSC model.

Non-image files attached to this report

japanese.txt

Comments to this report:

takahiro.yamamoto - 12:44 Sunday 09 February 2025 (32620)

I heard that the local dump part would be moved to the NB side, but it appears that the ISC part was actually moved to the DCUID which was used for NB.

Now many scripts and pipelines are unavailable due to the update of Type-A models.
Just ones I am currently aware are as following.
- Online state vector by k1detdq
- Segment file related to overflows
- Lockloss guardian
- DARM calibration scripts

In addition to that, I found some incomplete build as follows.
- Confusion of sender/receiver on ITMX as shown in Fig.1
- Wrong IPC rate for NBDAMP on ITMY as shown in Fig.2
- Remaining old info. about NBDAMP on ETMY as shown in Fig.3
- Mixing of old and new sender info about NBDAMP on ETMY as shown in Fig.4
- Wrong IPC rate for {PF,MN,TM}OPLEVs for all 4 type-As as shown in Fig.5-7
- Remaining old sender info. on CALCS as shown in Fig.8

I'm not sure the control signals can be sent/received among real-time models properly.
The only way to get back reliable IPC communications is to rebuild and restart them after cleaning up K1.ipc.
I think removing these chaos and unreliable situation is the most urgent task in next (a couple of?) weeks.

Images attached to this comment

satoru.ikeda - 21:29 Monday 10 February 2025 (32627)

[YamaT-san, Ikeda]
All models were rebuilt and restarted.
This time, we proceeded with the policy of not replacing the DCUIDs of the models on the Payload and LSC sides.

[Procedure]
1. make a copy of K1.ipc.
=> K1.ipc.20250210
2. delete the contents of K1.ipc and make the file size 0 bytes
3. make1st time for all models
4. second make of all models
5. install of all models
6. restart all models
k1vispr3p hung on restart. Recovered

[Confirmation]
> - Confusion of sender/receiver on ITMX as shown in Fig.1
=> I checked medm in step 4 and it was resolved, so I forgot to build twice.
> - Wrong IPC rate for NBDAMP on ITMY as shown in Fig.2
> Remaining old info. about NBDAMP on ETMY as shown in Fig.3
> - Mixing of old and new sender info. about NBDAMP on ETMY as shown in Fig.4
> - Wrong IPC rate for {PF,MN,TM}OPLEVs for all 4 type-As as shown in Fig.5-7
=> needed to delete from K1.ipc before build.
> - Remaining old sender info. on CALCS as shown in Fig.8
=> CALCS needed to be built.

Non-image files attached to this comment

japanese.txt