Alex Piet

@danielsf Thank you for clarifying that the problem is due to `date_of_acquisition = NULL` on LIMS. I suspected something like that was the problem. Which is why I think `BehaviorSession`...

As I reflect on this, it seems like option (1) - making `BehaviorSession` support loading VBN sessions - should be reasonable. Are the behavioral streams (stimulus times, eye data, running,...

@yavorska-iryna encountered this problem as well. Down-grading to pymongo=3.10.1 resolved the problem

-`get_extended_stimulus_processing`

@matchings @dougollerenshaw @yavorska-iryna This bug scares me because it calls into question other fields in extended stimulus processing! Yikes!

Here is a minimal working example of the discrepancy for the "rewarded" column. Spot checking, it might only happen on some sessions. ``` oeid = 1010556662 session = loading.get_ophys_dataset(oeid, include_invalid_rois=False)...

yes, sorry I dropped the imports. My head is in a different codebase right now, and I was just flagging this issue for later

How come your code block has nice colors, and mine doesnt?

I'm always paranoid about convolutions. Should the mode be "valid" instead of "full" (default)? https://github.com/AllenInstitute/visual_behavior_analysis/blob/0b07d4657b80431b328122efc6ef60122306b654/visual_behavior/ophys/response_analysis/response_processing.py#L422 https://numpy.org/doc/stable/reference/generated/numpy.convolve.html

@jeromelecoq I'm not sure if this is what you meant, but the motion correction values in the ophys dataset object do not have NaNs. > np.sum(pd.isnull(dataset.motion_correction.x_corr)) >0 > np.sum(pd.isnull(dataset.motion_correction.y_corr)) >0