Differences between revisions 20 and 21
⇤ ← Revision 20 as of 2021-10-06 22:12:22 →
Size: 1952
Editor: HirotakaYuzurihara
Comment:
← Revision 21 as of 2021-10-06 22:15:45 → ⇥
Size: 2539
Editor: HirotakaYuzurihara
Comment:
Deletions are marked like this. Additions are marked like this.
Line 55: Line 55:
  * ini files were edited to fit KAGRA environment.
   {{{
cd /users/yuzu/work/DQR/Script/o4-dqr-configuration
dqr-create-dag -vvv --config-files O4dev/ja-ub-tst.ini --config-dir /users/yuzu/work/DQR/Script/o4-dqr-configuration/etc S190930ak S190427ba S190816v
   }}}

 * The generated DAG files are located in {{{/home/controls/public_html/events/}}}
   {{{
ls /home/controls/public_html/events/
   }}}


== Submit DAG jobs ==

* For example on k1det1

{{{
cd /home/controls/public_html/events/
condor_submit_dag S190924h/data_quality_report_S190924h.dag
}}}

*

Task Manager

Installation

  • Yuzurihara prepared the virtual environment o4_dqr_proto on k1det1.

  • DQR tasks are supported by python 3.8

  • This procedure will require the authentication of git.ligo.org. 

    • conda create --name o4_dqr_proto python=3.8 -y
conda activate o4_dqr_proto -y
conda install M2Crypto -y
pip install git+https://git.ligo.org/o4-dqr/o4-dqr-configuration.git
pip install git+https://github.com/gwdetchar/gwdetchar.git
pip install git+https://git.ligo.org/detchar/dqrtasks.git
conda install ciecplib -y

  • install ligo-proxy-init, from the LDG Client package 

    • wget http://www.lsc-group.phys.uwm.edu/lscdatagrid/doc/ldg-client.sh -O /tmp/ldg-client.sh && sudo bash /tmp/ldg-client.sh
  • X.509 certification
    • For the additional permission to access GraceDB, we need to ask LIGO+Virgo colleague.

    • There are two options for KAGRA account. Here Yuzurihara used ligo-proxy-init. 

      ligo-proxy-init -i shibbi.pki.itc.u-tokyo.ac.jp albert.einstein
    • To test the certification, 
      gracedb ping
      grid-proxy-info

Generate DAG files

  • By following instruction, prepare ini files for DQR task manager.

    • This procedure will NOT require the access GraceDB, because the public alert will be used.

    • For test code, see /users/yuzu/work/DQR/Script/o4-dqr-configuration:k1det1 

      mkdir ~/public_html/event
dqr-create-dag S190924h -v -c ex_configs/defaults.ini ex_configs/condor.ini ex_configs/stationarity.ini ex_configs/omega.ini
  • This procedure will require the access GraceDB.
    • ini files were edited to fit KAGRA environment. 
      • cd /users/yuzu/work/DQR/Script/o4-dqr-configuration
dqr-create-dag -vvv --config-files O4dev/ja-ub-tst.ini --config-dir /users/yuzu/work/DQR/Script/o4-dqr-configuration/etc S190930ak S190427ba S190816v

  • The generated DAG files are located in /home/controls/public_html/events/ 

    • ls /home/controls/public_html/events/

Submit DAG jobs

* For example on k1det1 

cd /home/controls/public_html/events/
condor_submit_dag S190924h/data_quality_report_S190924h.dag

*

KAGRA/Subgroups/DET/DQR/TaskManager (last edited 2022-12-21 15:09:51 by HirotakaYuzurihara)