Open rhuszar opened 5 years ago
I think at this level nothing exists. Feel free to add away.
That said I suggest EMGFromLFP... don't see why accelerometer is better.
It's the actual movement signal. Maybe it's redundant, but it's very fast to load.
On Fri, Jan 11, 2019, 12:47 PM Brendon Watson <notifications@github.com wrote:
I think at this level nothing exists. Feel free to add away. That said I suggest EMGFromLFP... don't see why accelerometer is better.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453599856, or mute the thread https://github.com/notifications/unsubscribe-auth/ANnfgLQ6x142Yg8oE9nmbTvQxWLVwnWqks5vCM4_gaJpZM4Z74Cu .
It would be good to have a buzcode function that extracts the accelerometer from auxiliary.dat and saves it in a buzcode file (say, accel.behavior.mat) for subsequent analysis.
TheStateEditor (and anything else) can then load from that the same as it does EMGfromLFP
I don't have time for this, but I welcome the idea
On Fri, Jan 11, 2019 at 12:56 PM Dan Levenstein notifications@github.com wrote:
It would be good to have a buzcode function that extracts the accelerometer from auxiliary.dat and saves it in a buzcode file (say, accel.behavior.mat) for subsequent analysis.
TheStateEditor (and anything else) can then load from that the same as it does EMGfromLFP
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453602604, or mute the thread https://github.com/notifications/unsubscribe-auth/ADXrTUHfMCXDC5nNA-_3fw5ApC7AoPq8ks5vCNBhgaJpZM4Z74Cu .
I already did it. Roman was just asking whether to push it back, which we will
On Fri, Jan 11, 2019, 1:01 PM Brendon Watson <notifications@github.com wrote:
I don't have time for this, but I welcome the idea
On Fri, Jan 11, 2019 at 12:56 PM Dan Levenstein notifications@github.com wrote:
It would be good to have a buzcode function that extracts the accelerometer from auxiliary.dat and saves it in a buzcode file (say, accel.behavior.mat) for subsequent analysis.
TheStateEditor (and anything else) can then load from that the same as it does EMGfromLFP
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453602604 , or mute the thread < https://github.com/notifications/unsubscribe-auth/ADXrTUHfMCXDC5nNA-_3fw5ApC7AoPq8ks5vCNBhgaJpZM4Z74Cu
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453603935, or mute the thread https://github.com/notifications/unsubscribe-auth/ANnfgLCrsYhsRjSMVzhK8YMsu_ilIRaMks5vCNFcgaJpZM4Z74Cu .
Great
On Fri, Jan 11, 2019 at 1:45 PM samamckenzie notifications@github.com wrote:
I already did it. Roman was just asking whether to push it back, which we will
On Fri, Jan 11, 2019, 1:01 PM Brendon Watson <notifications@github.com wrote:
I don't have time for this, but I welcome the idea
On Fri, Jan 11, 2019 at 12:56 PM Dan Levenstein < notifications@github.com> wrote:
It would be good to have a buzcode function that extracts the accelerometer from auxiliary.dat and saves it in a buzcode file (say, accel.behavior.mat) for subsequent analysis.
TheStateEditor (and anything else) can then load from that the same as it does EMGfromLFP
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub < https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453602604 , or mute the thread <
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453603935 , or mute the thread < https://github.com/notifications/unsubscribe-auth/ANnfgLCrsYhsRjSMVzhK8YMsu_ilIRaMks5vCNFcgaJpZM4Z74Cu
.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453617070, or mute the thread https://github.com/notifications/unsubscribe-auth/ADXrTQfwnAG812gt5dRWwTjBUxpxKMzNks5vCNuwgaJpZM4Z74Cu .
Thanks for the suggestions! I will wrap Sam's code into a buzcode function that generates the accel.behavior.mat file. Then TheStateEditor can simply load its contents or run the requisite function, given that the user has decided they want to state score using Intan's accelerometer data. Will send to @dlevenstein and @DavidTingley for verification.
Sounds good. Glad for the extra participation in the sleep scoring stuff. It's old code from Andres Grosmark, but pretty comprehensible I think/hope
Thanks for doing this
On Fri, Jan 11, 2019 at 3:12 PM rhuszar notifications@github.com wrote:
Thanks for the suggestions! I will wrap Sam's code into a buzcode function that generates the accel.behavior.mat file. Then TheStateEditor can simply load its contents or run the requisite function, given that the user has decided they want to state score using Intan's accelerometer data.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-453643134, or mute the thread https://github.com/notifications/unsubscribe-auth/ADXrTThVgcGOeJUGRCaIYiOYhQJ44byqks5vCPA5gaJpZM4Z74Cu .
Did anyone work out an implementation of using the accelerometer in SleepScoreMaster?
I am not aware of any such implementation yet
On Wed, Apr 21, 2021 at 2:48 PM Dan Levenstein @.***> wrote:
Did anyone work out an implementation of using the accelerometer in SleepScoreMaster?
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-824280670, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA26WTK55337JVT2VNDTTG3TJ4MYPANCNFSM4GPPQCXA .
I use the accelerometer for the GUI to curate state scoring (I don't think this code is pushed), I have no sense of SleepScoreMaster, so I didn't play around with that.
bz_getIntanAccel is the function that extracts the accelerometer, with outputs ready to work with the sleep scoring code (i.e., 1Hz sampling rate)
On Wed, Apr 21, 2021 at 9:39 PM Brendon Watson @.***> wrote:
I am not aware of any such implementation yet
On Wed, Apr 21, 2021 at 2:48 PM Dan Levenstein @.***> wrote:
Did anyone work out an implementation of using the accelerometer in SleepScoreMaster?
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <https://github.com/buzsakilab/buzcode/issues/278#issuecomment-824280670 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA26WTK55337JVT2VNDTTG3TJ4MYPANCNFSM4GPPQCXA
.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/buzsakilab/buzcode/issues/278#issuecomment-824308327, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC4QSPELKKY2LLIQ6V2A7E3TJ4SW5ANCNFSM4GPPQCXA .
Does the most recent version of
TheStateEditor
include functionality to load accelerometer data from the auxiliary.dat file that is generated by the Intan? Apparently it does provided that the xyz coordinates from auxiliary.dat are included as additional channels in the lfp file. That said,bz_GetLFP
does not have functionality to add these channels to the lfp file it generates - also, I am not sure it should given that these channels are not LFP. @samamckenzie has a workaround on his local machine that allowsTheStateEditor
to load motion data straight from the auxiliary.dat file when prompted to do so by the user. We thought this might be a nice addition to the program, but I am posting it here just in case a solution already exists and we're just not aware of it.