UPV
3.2.0
An algorithm to measure noise correlations for gravitational-wave detectors
|
Program to run the upv production at CCIN2P3. More...
Functions | |
int | main (int argc, char *argv[]) |
Main program. More... | |
void | PrintUsage (void) |
Prints the program usage message. More... | |
Program to run the upv production at CCIN2P3.
This script must be run twice. The first time, it prepares job scripts to run UPV in a standard mode, where channels are analyzed separately. The second time, it prepares a job script to run UPV in a hierarchical mode to only select non-redundant veto channels.
At CCIN2P3, source the local UPV environment. Moreover, UPV will have to access Omicron triggers. They are accessed in the directories pointed by $OMICRON_TRIGGERS
and $OMICRON_TRIGGERS_ONLINE
. The offline trigger files ($OMICRON_TRIGGERS
) will be searched first. If you are only interested in trigger files in $OMICRON_TRIGGERS_ONLINE
, you can de-activate the offline area: unset OMICRON_TRIGGERS
.
Run the script a first time:
upv-workflow-ccin2p3 segment-file=/sps/virgo/USERS/prod_virgo_omicron/production/1379030500.1380239448/segments.txt channel-file=/sps/virgo/USERS/prod_virgo_omicron/production/channels.o4 outdir=. channel-target="V1:Hrec_hoft_16384Hz"
segment-file=
points to a text file listing the segments to process, with two columns: GPS start and GPS end.channel-file=
points to a text file listing the channels to process, with two columns: the channel name and the sampling frequency. Note that the channel sampling frequency is not used. Only the channels for which Omicron triggers can be found will be considered.outdir=
points to an output directory. A production directory will be created there.channel-target=
provides the name of the target channel.Additionally, you can add the following options
email=
provides and email address where to send job reports.n-per-job=
provides the number of source channels to process in one UPV job (100 by default).In the newly-created production directory, you will find:
prod/parameters/
prod/jobs/
Run the jobs with:
for file in ./jobs/*.sh; do sbatch $file; done
In a second step, when all the standard UPV jobs are complete, you must run UPV in a hierarchical mode. For this analysis, only channels which gave a non-zero veto efficiency are considered. Moreover, unsafe channels are excluded.
Run the script again, pointing to your production directory:
upv-workflow-ccin2p3 prod-dir=./1379030500.1380239448 unsafe-eff=20
This script makes the following actions:
./1379030500.1380239448/channels_zero.txt
. They will not be considered../1379030500.1380239448/channels_unsafe.txt
. If the list does not make sense, adjust the efficiency threshold option. Unsafe channels are discarded../1379030500.1380239448/parameters
./1379030500.1380239448/jobs
Run the UPV script:
sbatch 1379030500.1380239448/jobs/job.upv.57.sh
int main | ( | int | argc, |
char * | argv[] | ||
) |
Main program.
void PrintUsage | ( | void | ) |
Prints the program usage message.
[upv-workflow-ccin2p3-usage]
[upv-workflow-ccin2p3-usage]