-
Notifications
You must be signed in to change notification settings - Fork 128
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
bz_LoadPhy, npy package and several function updates #250
Closed
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
# Conflicts: # io/bz_LoadPhy.m
# Conflicts: # io/bz_LoadPhy.m
Is bz_LoadPhy in good working order now? |
yes, now it should work fine. I at least record at 30k
…On Thu, Oct 18, 2018 at 5:28 PM Brendon Watson ***@***.***> wrote:
Is bz_LoadPhy in good working order now?
Also can I ask why fs default is 30000Hz... is that how you guys are
recording now by default?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#250 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AM8oQ6_3whCpr70ogtDBIT98geT4Km_Yks5umPKRgaJpZM4XYSx5>
.
--
Antonio Fernandez-Ruiz, PhD
Sir Henry Wellcome Post-doctoral fellow
Buzsaki Lab. NYU Neuroscience Institute
New York University, Langone Medical Center
East River Science Park, 450 East 29th Street, 9th Floor
New York, NY 10016
|
Thanks Antonio
Do you find that 30Khz makes a notable difference? I've thought about it
and wasn't sure.
…On Thu, Oct 18, 2018 at 6:16 PM AntonioFR ***@***.***> wrote:
yes, now it should work fine. I at least record at 30k
On Thu, Oct 18, 2018 at 5:28 PM Brendon Watson ***@***.***>
wrote:
> Is bz_LoadPhy in good working order now?
> Also can I ask why fs default is 30000Hz... is that how you guys are
> recording now by default?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#250 (comment)>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AM8oQ6_3whCpr70ogtDBIT98geT4Km_Yks5umPKRgaJpZM4XYSx5
>
> .
>
--
Antonio Fernandez-Ruiz, PhD
Sir Henry Wellcome Post-doctoral fellow
Buzsaki Lab. NYU Neuroscience Institute
New York University, Langone Medical Center
East River Science Park, 450 East 29th Street, 9th Floor
New York, NY 10016
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#250 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADXrTbgr_9ERJJ3qLkAof9CPBsqEQfKFks5umP29gaJpZM4XYSx5>
.
|
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.
No description provided.