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
{{ message }}
Repository navigation
omission-aligned traces have 106 frames instead of 107 frames. #654
import visual_behavior.data_access.loading as loading
from visual_behavior.ophys.response_analysis.response_analysis import ResponseAnalysis
ophys_experiment_id = 1000744365
dataset = loading.get_ophys_dataset(ophys_experiment_id)
analysis = ResponseAnalysis(dataset)
print('shape of omission_response trace: {}'.format(analysis.omission_response_df.iloc[0]['trace'].shape))
print('')
print('trace timestamps: \n{}'.format(analysis.omission_response_df.iloc[0]['trace_timestamps']))
As per my conversation with @dougollerenshaw and my further checking of data, this problem appears to be due to a longer frame duration for these 3 experiments, and that "start_ind_offset and end_ind_offset are both cast to integers".
It would be helpful to have consistent number of frames for the omission aligned traces of all experiments.
Can you please help fix this problem? Would it not make more sense to use np.round instead of "int"?
Activity