Skip to content

Don't check FrProcData's tRange when reading GWF

Duncan Macleod requested to merge github/fork/duncanmmacleod/framecpp-no-trange into master

This PR removes a check against the tRange attribute of an FrProcData structure when reading GWFs. According to the frame spec:

tRange, fShift, fRange are redundant with the axis information in the data Vector in some cases. If a redundancy exists, the data must be identical to that in the FrVect for the earliest time and/or lowest frequency dimension (e.g. for a t-Series tRange = dx[0]*nx[0]). If a discrepancy exists then the FrVect values take precedence

This would resolve the issues reading BayesWave-produced files, see https://git.ligo.org/computing/helpdesk/-/issues/1579 (IGWN credentials required).

Merge request reports