Skip to content

Issue with omicron-print at the boundary between consecutive "five first digits segments"

  • Setup
conda activate /virgo/conda/envs/omicron-env
source /virgo/conda/envs/omicron-env/etc/omicron.env.sh
  • Working command
omicron-print channel=V1:Hrec_hoft_16384Hz gps-start=1397999999 gps-end=1398000224 print=clusters
# time-clustered triggers, dt = 0.10000s
# peak time [GPS]
# peak frequency [Hz]
# SNR [-]
1397999999.4590   720.01     5.04 
(...)
1398000222.0430    40.42   493.12
  • Command that does not work (incrementing the gps-start parameter by one second)
omicron-print channel=V1:Hrec_hoft_16384Hz gps-start=1398000000 gps-end=1398000224 print=clusters
No trigger files

In /data/prod/omicron/V1/Hrec_hoft_16384Hz_OMICRON we have

13979/V1-Hrec_hoft_16384Hz_OMICRON-1397906343-93962.root
13980/V1-Hrec_hoft_16384Hz_OMICRON-1398000305-99904.root

with 1397906343 + 93962 = 1398000305.

So the first Omicron data from the GPS segment with 5 first digits equal to 13980 are in the ROOT file located in the previous directory 13979/ and Omicron seems not to look for them when queried from 1398000000 onwards.