Closed
Conversation
…nlx_ncs_readfix
Member
|
Hi Mike, Gaps in nlx files are not supported by design in the high level code. The mapping of timestamps to samples becomes too inaccurate or too slow. Furthermore, different channels can have different gaps, which was especially observed in 256 channel systems. Did you look at http://www.fieldtriptoolbox.org/getting_started/neuralynx ? best |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I found a mismatch between timestamps and sample number while reading nlx event file in case of non-continuous (e.g. with pauses) data acquisition. The 8724696 commit is the issue. I think I managed to solve it using mapping from timestamp to sample number acquired from data file.
BR
Mike from KFU