Reports 1-1 of 1 Clear search Modify search
DGS (General)
takahiro.yamamoto - 2:29 Wednesday 15 April 2026 (36747) Print this report
Comment to Migrating scripts from k1script1 to k1script0. (36519)
Migration of all on-demand scripts were completed to k1script0.
Now, we can stop k1script1 which is old server.
OS upgrade of k1script1 will be done tomorrow.

All systems and services are now summarized on JGW Wiki.

Please keep this page up to date whenever you add a new service or system.
This will reduce the effort required for future server updates.
In fact, with this update, identifying services for which we had no information was more challenging than ensuring compatibility with the new OS.

-----
Traverser script
I had already confirmed that traverser script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/traverser/traverser_start.py) was worked well on the new server. But server connection and environmental variables were hard-coded on shell command block of MEDM screen files. So migration required to modify several MEDM screens. So I prepared a wrapper script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/traverser/medm_traverser_start.sh) in which necessary information is set. Thanks to this implementation, we won't need to find related MEDM screens and to update them in future OS upgrade.

Rebooter script
In Python3.13, telnetlib which is used in the rebooter script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/picomotor/pico_power_control.py) is completely deprecated. So I rewrote a function derived from telnetlib as one derived from socket package. Due to differences in escape sequences and control codes, it has been modified quite a bit. And also, a wrapper script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/picomotor/medm_pico_power_control.sh) is also prepared to avoid hard-coding of various parameters on MEDM screens. I needed to modify hundreds of shell command blocks to migrate from k1script1 to k1script0 in this time. Identifying and fixing related MEDMs was the most tough task of the migration work of script server.

HWP script
I had prepared an HWP script to avoid hard-coding in the previous version, but I realized that it was difficult to avoid hard-coding due to bad implementation of the callback function. (And while it probably hasn’t caused any practical problems yet, the sudores configuration on the RaspPi is likely set up incorrectly.) So, I rewrote the hard-coded `k1script1` to `k1script0`. To eliminate hard-coding entirely, HWP script must be redesigned drastically.

Phytron script
Though I couldn't find any information about Phytron script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/phytron/phytron_start.py), I happened to discover that this script was running on k1script1. Implementation of this script is quite similar to traverser script. So I prepared a wrapper script (/opt/rtcds/userapps/release/cds/common/scripts/epics-motor-control/phytron/medm_phytron_start.sh) to avoid hard-coding on the shell command block of MEDM screens.
Search Help
×

Warning

×