Open leoscholl opened 1 year ago
also applies to any other tabulate function like in #432
tabulate_behavior_data() now tells you which file couldn't be loaded, and returns a df without any trials from the problematic entry. But wrappers around tabulate_behavior_data() break when a problematic entry is included in the ids to tabulate
if an exception happens during tabulate_behavior_data, there's no way of knowing which file generated the error. we should include a try/catch to print out the file that caused the error to make debugging easier