Skip to content

Clarification re. "partial" implementation of skew and multiple sample rates #29

@drewsilcock

Description

@drewsilcock

Hi David, thanks for the useful library!

Would you be able to clarify the status of the "partial" implementation of the analog channel-specific skew and the multiple sample rates?

It seems from the code that while the skew is being read in from the cfg file, it isn't being used anywhere to calculate channel-specific timestamps via the timestamp + (sample_number - 1) * skew equation. Is this what is meant by "partial" implementation? If so, are there any plans to include the channel-specific skews? (I imagine it would require moving the timestamps from a global property to a channel-specific property.)

In terms of the multiple sample rates, from the code it looks like this is fully implemented - I can't see what edge cases wouldn't be correctly handled by the logic in the DatReader._get_time() method according to my understanding. Is there something I'm missing here?

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions