| Q: | When using multiple frame queries in my job, I get unexpected failures. |
| A: | Preferred framequery syntax recommendation:
With the advent of support for NDAS frames in LDAS, and the deprecation of explicit interferometer specifications in -framequery options, there is a possibility for bad behaviour of complex/compound framequeries whose component parts are actually satisfied by a single set of frame files. For example, this request:
-framequery {
{ RDS_R_L1 H {} 730524100-730524982 Adc(H2:LSC-AS_Q!resample!8!) }
{ RDS_R_L1 L {} 730524100-730524982 Adc(L1:LSC-AS_Q!resample!8!) }
}
Will work "as expected" when the request is satisfied by two
sets of frame files, Hanford frames for the first part, and
Livingston frames for the second part.
However, when the request is satisfied by a single set of NDAS
(multiple interferometers represented in a single file) frames,
the request will fail to produce output from the second part.
The above query can be rewritten as:
-framequery {
RDS_R_L1 {} {} 730524100-730524982
Adc(H2:LSC-AS_Q!resample!8!,L1:LSC-AS_Q!resample!8!)
}
So that it will always work.
|