Skip to content

Filtering enforces double precision #13738

@smalltimer

Description

@smalltimer

Hi, the filtering pipeline strictly enforces double-precision (filtering.py >_check_filterable).

When dealing with long recordings at high sampling rates, people often reduce precision to suit their storage and computational needs. I feel enforcing this datatype might be an overkill. Was there a specific computational reason for this?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions