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.

Sign up for GitHub

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

Jump to bottom

image_false_alarm and image_correct_reject treat lick_bouts differently #336

Open
2 tasks
alexpiet opened this issue Aug 31, 2022 · 0 comments
Open
2 tasks

image_false_alarm and image_correct_reject treat lick_bouts differently #336

alexpiet opened this issue Aug 31, 2022 · 0 comments

Comments

@alexpiet
Copy link
Owner

In two places

  • psy_metrics_tools.annotate_image_rolling_metrics()
  • psy_output_tools.session_df_backwards_compatability()

Inside a licking bout, image_correct_reject is NaN, while image_false_alarm is 0. NaN makes more sense because whether we had a false alarm or a correct reject is ill-defined inside of a licking bout.

  • Fix code
  • Re-run session_dfs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexpiet