Skip to content

DigitalRFReader.get_bounds skips some of drf recording. #101

@Sponge166

Description

@Sponge166

Hi, I am processing some data in Digital RF format and when I call get_bounds drf will ignore some of the sub directories. For example, I have a subdir_cadence of one hour, a file_cadence of one second, a sampling rate of 10MHz, and my recording looks like this:

toplevel/
  chA/
    2025-07-10T17-00-00/
      rf@1752169412.000.h5
      ...
      rf@1752170399.000.h5
    2025-07-10T18-00-00/
      rf@1752170400.000.h5
      ...
      rf@1752173206.000.h5

A call to get_bounds("chA") gives (1752170400e7, 1752173206e7) but (1752169412e7, 1752173206e7) is expected. The ends up causing the entirety of 2025-07-10T17-00-00/ to be skipped during my processing of the data. However, I can manually specify the lower bound and drf is able to read data from 2025-07-10T17-00-00/.

I have another recording with the same parameters that looks like this:

toplevel/
  chA/
    2025-07-10T15-00-00/
      rf@1752163113.000.h5
      ...
    2025-07-10T16-00-00/
      ...
    2025-07-10T17-00-00/
      rf@1752166800.000.h5
      ...
    2025-07-10T18-00-00/
      ...
      rf@1752172224.000.h5

A call to get_bounds("chA") gives (1752166800e7, 1752172224e7) but (1752163113e7, 1752172224e7) is expected.

I have a third recording where this issue does not occur, and the expected bounds are produced by a call to get_bounds. Its structure is the following:

toplevel/
  chA/
    2025-07-10T16-00-00/
      rf@1752163253.000.h5
      ...
    2025-07-10T17-00-00/
      ...
    2025-07-10T18-00-00/
      ...
      rf@1752171838/.000.h5

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions