Size: 4550
Comment:
|
Size: 4672
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
== O3GK log == Some report on O3GK data processing in detail. [[KAGRA/Subgroups/DET/Omicron/O3GKlog|O3GKlog]] |
Omicron
O3GK log
Some report on O3GK data processing in detail.
Installation
- The Omicron code is managed on the Virgo SVN and it should be able to be installed by CMT system.
- But when we use the CMT in order to install Omicron, dependency conflict is occurred and we cannot install it correctly.
F. Robinet helped us to install it on the k1sum0 and we can use copy of it on the another Debian 9 systems.
T. Yamamoto had already copied Omicron and the related packages on k1nfs0:/export/virgo/virgosoft.
- So Omicron can be used by mounting NFS area on the Debian 9 systems.
> grep virgsoft /etc/fstab 10.68.10.10:/export/virgo/virgosoft /home/controls/opt/virgosoft nfs rw,bf,soft 0 0
- So Omicron can be used by mounting NFS area on the Debian 9 systems.
How to use
- Before using omicron, we must set the environmental variables by
> source ~controls/opt/virgosoft/environment.sh
- Omicron is available as a command line tool on k1sum0, k1sum1, and another test system of Debian 9.
- There are three ways to use omicron
case1> omicron start_gps stop_gps option_file case2> omicron segment_file option_file ### TY don't know much about this way. case3> omicron central_gps option_file
Some examples of a form of option_file are shown in [1] and [2].
- There are three ways to use omicron
- Omicron is available as a GUI launched from MEDM on the client workstations.
Sitemap -> Commissioning -> Glitch pipeline -> Omicron
Trigger generation for DailySummary
DailySummaryPage uses the trigger files using gwtrigfind for constructing the Omicron summary page.
T. Yamamoto modified gwtrigfind because our computer environment is slightly different from LIGO's one.
In LIGO convention [3], trigger files should be generated in the /home/detchar/triggers
We have only controls user on k1sum0 and another computers.
--- /home/controls/opt/summary-2.7/lib/python2.7/site-packages/gwtrigfind/core.py.bak 2018-10-19 09:12:45.375654000 +0900 +++ /home/controls/opt/summary-2.7/lib/python2.7/site-packages/gwtrigfind/core.py 2019-01-23 18:29:06.224172322 +0900 @@ -161,12 +161,12 @@ def find_detchar_files(channel, start, e ifo, name = _format_channel_name(channel).split('-', 1) # find base path relative to O1 or O2 formatting if start >= OMICRON_O2_EPOCH: - base = os.path.join(os.path.sep, 'home', 'detchar', 'triggers') + base = os.path.join(os.path.sep, 'home', 'controls', 'triggers') tag = etg.upper() dirtag = '%s_%s' % (name, tag) else: epoch = '*' - base = os.path.join(os.path.sep, 'home', 'detchar', 'triggers', '*') + base = os.path.join(os.path.sep, 'home', 'controls', 'triggers', '*') tag = etg.title() dirtag = '%s_%s' % (str(channel).split(':', 1)[1], tag)
The Omicron job is automated using crontab on k1sum1.
> crontab -l | grep Omicron 5-59/15 * * * * env - `cat /users/DET/tools/Omicron/etc/sum1_cron-omicron.env` /users/DET/tools/Omicron/Script/automation.sh /users/DET/tools/Omicron/Parameter/summary_test.txt > /tmp/auto-omicron.log 2>&1
- When you want to add some channels for the Omicron search,
1) add channel name to DATA CHANNELS line of /users/DET/tools/Omicron/Parameter/summary_test.txt
or 2) add new job to crontab> crontab -e 5-59/15 * * * * env - `cat /users/DET/tools/Omicron/etc/sum1_cron-omicron.env` /users/DET/tools/Omicron/Script/automation.sh /users/DET/tools/Omicron/Parameter/summary_test.txt > /tmp/auto-omicron.log 2>&1 5-59/15 * * * * env - `cat /users/DET/tools/Omicron/etc/sum1_cron-omicron.env` /users/DET/tools/Omicron/Script/automation.sh /path/to/your_parameter.txt > /tmp/auto-omicron2.log 2>&1
In order to use trigger results on SummaryPage, use same OUTPUT parameters as
OUTPUT DIRECTORY /home/controls/triggers/tmp OUTPUT PRODUCTS triggers OUTPUT FORMAT xml OUTPUT VERBOSIT 0
Finally, we must modify the INI file of DailySummary.
Reference
[1] VIR-0135A-15, Omicron: a tool for detector characterization
[2] VIR-0545C-14, Omicron: an algorithm to detect and characterize transient events in gravitational-wave detectors
[3] LIGO-T1300468, DetChar Trigger Handling Conventions