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 would like to calculate features in certain (configurable) time window after stim_end. I am attaching an example trace, where there are five spike after the end of the stimulus (stimulus ends at 3250 ms). rebound.txt
One obvious way would be to set stim_start and stim_end to 3250 and 3500 ms for the trace above for calculating the features. However, I don't think this would work during optimization, because stim_start and stim_end are used to create the stimulus (and in this case they should be 250 and 3250 ms).
What would be the best approach here? Should we just create new features, e.g. "Spikecount_rebound", "time_to_first_spike_rebound", etc...? Or maybe add an option to detect features between stim_end and stim_end + user_defined_time_after_stim_end?
The text was updated successfully, but these errors were encountered:
I wonder if it wouldn't be possible to create an eFELFeature object with the adapted stim_start/stim_end.
Adding all these new features for _rebound seems to be a bit overkill.
I would like to calculate features in certain (configurable) time window after stim_end. I am attaching an example trace, where there are five spike after the end of the stimulus (stimulus ends at 3250 ms).
rebound.txt
One obvious way would be to set stim_start and stim_end to 3250 and 3500 ms for the trace above for calculating the features. However, I don't think this would work during optimization, because stim_start and stim_end are used to create the stimulus (and in this case they should be 250 and 3250 ms).
What would be the best approach here? Should we just create new features, e.g. "Spikecount_rebound", "time_to_first_spike_rebound", etc...? Or maybe add an option to detect features between stim_end and stim_end + user_defined_time_after_stim_end?
The text was updated successfully, but these errors were encountered: