Closed yiran25 closed 11 months ago
Is that fixed?
Not yet
Get Outlook for iOShttps://aka.ms/o0ukef
From: Antonin Blot @.> Sent: Thursday, November 30, 2023 3:00:59 PM To: znamlab/cottage_analysis @.> Cc: Yiran He @.>; Author @.> Subject: Re: [znamlab/cottage_analysis] Last imaging frame time later than last found monitor frame? (Issue #42)
External Sender: Use caution.
Is that fixed?
— Reply to this email directly, view it on GitHubhttps://github.com/znamlab/cottage_analysis/issues/42#issuecomment-1833950781, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARXNWVIVDOB2SL5UF3DHJFLYHCNSXAVCNFSM6AAAAAA74NMJG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTHE2TANZYGE. You are receiving this because you authored the thread.Message ID: @.***>
The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 1 Midland Road London NW1 1AT
This issue is likely a result of weird bonsai crashes by looking at a few sessions that crashed with this error. Tolerate this problem with this commit ab8345559bf531b4e98b7957141df9fa77202020
https://github.com/znamlab/cottage_analysis/blob/e9cef8d55dba16480c7af2fab11712bf67aeff00/cottage_analysis/analysis/spheres.py#L124
Last imaging frame time is slightly later than last photodiode-found monitor frame time.