Reports 1-1 of 1 Clear search Modify search
DetChar (General)
hirotaka.yuzurihara - 12:22 Thursday 23 January 2025 (32432) Print this report
Running Omegascan at DetChar cluster

[Chia-Hsuan Hsiung (Tamkang university), Yuzurihara]
We tried to run the Omegascan at DetChar cluster and developed the script for that. We plan to apply the Omeca scan for the data before the lockloss time and upload the results at gwdet server.

Details

  • We developed the script to submit the job to HTCondor. The script is stored in /users/yuzu/lockloss/Omegascan/script_for_detchar-omega .
    • K-K1_C-selected_v6.ini : configuation file for the Omegascan.
    • script_for_detchar_omega.py : the script to submitt he job. Before the submission, edit the date, the output directory, and configuration file.
  • To run the Omegascan at detchar cluster, we needed to change several environmental variables: LIGO_DATAFIND_SERVER and NDSSERVER. It was implemented in the python script.
    • To read the recent data, we thought we can use LIGO_DATAFIND_SERVER. But, it failed due to some reason.
    • To read the past data which are unavailable at Kamioka, we use k1nds2.
  • We need ~30min to finish the job by using the current configuration file.
  • The latest results are stored in /users/yuzu/lockloss/Omegascan/output_SNR_3 . The iniail plan was to put the results in /mnt/GlitchPlot. But, this directory is unavailable on gwdet. We will consider the solution.
Search Help
×

Warning

×