Skip to content

Refactor the sweep start time/capture repeat index in striqt.sensor #74

@dgkuester-nist

Description

@dgkuester-nist

Currently, the repeat index is tracked in a field in SensorCapture. This adds little new information but leads to buffer misses in helper functions that use lru_cache. Further, the logic for determining sweep_start_time, which depends on this index, is currently housed in SourceBase, which seems like the wrong scope.

Instead, we can special-case specs.Repeat.get_points to return some sentinel like None. Then, iter_sweep can implement the outer sweep loop, and set sweep_start_time (and maybe a sweep index?) itself.

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