You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find the user guide for perievent a bit confusing. It would be helpful for me if the documentation more explicitly points out which argument serves which role in the functions and example data types for that argument.
For instance, 'data' is the variable to be grouped and counted (Ts), and 'tref' are the events to which the data histograms are aligned (Ts). Example data - tref pairs are: 'spike' - 'stimulus', or 'stimulus' - 'spike' (for the continuous case).
The above is just a rough idea, but the main point is to give a more direct guidance on how to fill in the function without too much guessing and reasoning.
'The object perievent is now of shape (number of bins, (dimensions of input), number of events )'
I found it to be (number of bins, number of events, dimensions of data)?
I'm also curious why compute_event_trigger_average just completely switched the argument names, compared to the compute_perievent and compute_perievent_continuous. It would make sense to me if they share the same argument names?
The text was updated successfully, but these errors were encountered:
I find the user guide for perievent a bit confusing. It would be helpful for me if the documentation more explicitly points out which argument serves which role in the functions and example data types for that argument.
For instance, 'data' is the variable to be grouped and counted (Ts), and 'tref' are the events to which the data histograms are aligned (Ts). Example data - tref pairs are: 'spike' - 'stimulus', or 'stimulus' - 'spike' (for the continuous case).
The above is just a rough idea, but the main point is to give a more direct guidance on how to fill in the function without too much guessing and reasoning.
'The object perievent is now of shape (number of bins, (dimensions of input), number of events )'
I found it to be (number of bins, number of events, dimensions of data)?
I'm also curious why compute_event_trigger_average just completely switched the argument names, compared to the compute_perievent and compute_perievent_continuous. It would make sense to me if they share the same argument names?
The text was updated successfully, but these errors were encountered: