Allow reading timestamps as raw TDMS timestamps #200
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #200 +/- ##
==========================================
- Coverage 94.59% 94.58% -0.02%
==========================================
Files 17 18 +1
Lines 2164 2252 +88
==========================================
+ Hits 2047 2130 +83
- Misses 117 122 +5
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #198
Adds a new
raw_timestampsoption when opening a TDMS file that controls whether timestamps are read as numpy datetime64 objects or raw TDMS timestamps. This includes timestamp data in channels, which use a new TimestampArray type that wraps np.ndarray and provides conversion to datetime64 arrays of different resolution.