Q: In 0.9.0, my frame query worked just fine, but in 1.0.0 it fails
A: 1.0.0 has introduced a bug in the diskcacheAPI which prevents some framequeries not to work. The 0.9.0 functionality will be restored in the next version of LDAS. The work around described below should be used until the problem has been corrected. LDAS allows implied interferometer specs based on inspection of specified channel names in the -framequery option. In previous versions of LDAS, the implied ifo would be matched against exact matches in frame file names, and also against merged frame files whose names reflected the existence of channel data from multiple interferometers. In LDAS release 1.0, the ability to match merged files implicitly was lost. To match merged frame files using LDAS version 1.0.0, it is necessary to explicitly declare the ifo portion of the filenames intended to match. Example: formerly this framequery:
   -framequery { MY_TYPE {} {} 600000000-600000012 Adc(H1:LSC-AS_Q) }
   
could be matched by frames with names of the form:
   HL-MY_TYPE-600000000-16.gwf
   
but in version 1.0.0, it is necessary to specify the ifo part of the expected frame name specifically IF MERGED FRAMES ARE EXPECTED:
  -framequery { MY_TYPE HL {} 600000000-600000012 Adc(H1:LSC-AS_Q) }
  
if ifo specific frames with a single character ifo spec in their name are wanted, the ifo does not have to be specified.



Back to LDAS FAQ