I resumed preparations for making effective use of the DetChar cluster, including k1detms0 and the computing nodes k1detcl[012]. (past log: klog31462, related slide)
I configured the computing environment to avoid potential issues with Conda and the system clocks.
I found that the wrong disk had been mounted via NFS, so I corrected the configuration to use the proper server.
I started testing the automatic production of segment files using HTCondor. I will continue monitoring the generated files and logs to confirm stable operation.
Details
- Conda environment
- I installed the IGWN Conda environment required for the DetChar tools. I used the receipe updated on 2026/08/14. I used the text-based recipe instead of the yaml one to avoid the newer glibc requirement.
- The conda environment is shared through NFS and is located at /users/DET/conda/miniforge3/envs/igwn-py311/. I confirmed that it works on all four nodes.
- System clocks on the computing nodes
- The system clocks on the computing nodes were not synchronized correctly.
- I enabled and started chronyd so that the system clocks are automatically synchronized.
- NFS mount configuration
- The storage storing frame files is mounted at /frame1 via NFS.
- I updated the NFS configuration to use the current server and confirmed that the frame data can be accessed correctly.
- Segment generation
- I manually tested the Segment production script using the new Conda environment.
- After fixing issues of system clock and NFS maount, the script successfully generated Segment files.
- Segment generation using HTCondor
- I set up an HTCondor job to run the Segment production automatically every 15 minutes. I also prepared a script and an HTCondor job to automatically copy the generated Segment files to the product directory at 9:23 every day.
- Working directory: /users/yuzu/work/20260818_cluster
- The jobs are currently being tested, and I am monitoring the output, log files, and memory usage to confirm stable operation.