Skip to content
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

omission-aligned traces have 106 frames instead of 107 frames. #654

Open
farznaj opened this issue Jun 11, 2020 · 0 comments
Open

omission-aligned traces have 106 frames instead of 107 frames. #654

farznaj opened this issue Jun 11, 2020 · 0 comments

Comments

@farznaj
Copy link
Contributor

farznaj commented Jun 11, 2020

Session_id: 1000439105

Experiment_id:
1000744370
1000744376
1000744365

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"?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant