-
Notifications
You must be signed in to change notification settings - Fork 129
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
Basic pipeline script #345
Comments
add ipshita as well |
Do we already have something like this? I have my own for example. Problem is everyone will want different things. I suggest the following: create a script that pretty much offers all currently - available functions and then people can make their own copy and comment out certain functions. But If we do it my way it can serve as an almost advertisement or communication about the current buzcode capaxities... which often people don’t know (I didn’t knew there was a bz_getwaveform). I can submit my version if people like this idea and then others can modify |
Yes, this is a good idea. Manu is working in a script like that but it will be good to compare it with yours.
The idea we discussed was to have a general script that launch all the basic analysis from the raw data and that can be customize for each person.
… On Oct 29, 2019, at 6:56 AM, Brendon Watson ***@***.***> wrote:
Do we already have something like this? I have my own for example. Problem is everyone will want different things. I suggest the following: create a script that pretty much offers all currently - available functions and then people can make their own copy and comment out certain functions. But If we do it my way it can serve as an almost advertisement or communication about the current buzcode capaxities... which often people don’t know (I didn’t knew there was a bz_getwaveform). I can submit my version if people like this idea and then others can modify
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#345?email_source=notifications&email_token=ADHSQQ4LA7KSJRZ75PJTPGTQRAJFVA5CNFSM4JF4WYTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECQCBSA#issuecomment-547365064>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADHSQQ3JHOE6YTRS426QUMLQRAJFVANCNFSM4JF4WYTA>.
|
We could do this different ways, but I'll just start by pasting mine in... or we can do this via google doc? function BWPreprocessing(basepath,noPrompts) warning off if ~exist('basepath','var') if ~exist('noPrompts','var') %% copying xml if needed sessionInfo = bz_getSessionInfo(basepath,'editGUI',true); %% Handling dat %% Handling some dat metadata %% Make LFP file %% Sleep Scoring %% Spike sorting if goodGPU
else |
You could also work on the a script on a separate branch that everyone can contribute to, and then pull it into dev when it's ready. |
I think it might be much faster to do it this way initially before putting in buzcode after initial agreement about elements: Feel free to edit this: |
Should go from after recording to basic set of buzcode files
The text was updated successfully, but these errors were encountered: