-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regular timestamps calculated #109
Comments
Also, more importantly, is this the first stream? I couldn't find any logic to synchronize this with other streams in the conversion code. |
Yes, this should be using starting time and sampling rate -- looks like a mistake made in all the confusion of temporal alignment. We ended up adding the raw fiber photometry response data without temporal alignment, but with a comment warning that the raw data was not aligned. This is because the datta lab was unable to come up with the alignment information that we needed. All the other data streams (processed photometry, keypoints, moseq-extract output, etc.) are already aligned. |
ok got it, thanks! |
@pauladkisson did you want to regenerate the files with starting time + rate or just accept the less efficient timestamps and close the issue? |
I can go ahead and regenerate the files, it should be an easy fix. |
datta-lab-to-nwb/src/datta_lab_to_nwb/markowitz_gillis_nature_2023_keypoint/keypointinterface.py
Line 53 in 7540d94
@pauladkisson why are we computing the timestamps here? Seems like we should be using starting time and sampling rate
The text was updated successfully, but these errors were encountered: