Long frame stimulus events can happen in clusters (e.g. 20 long frames in a row where the cluster happens at a set interval). This can indicate a background process taking up CPU during an acquisition. This is something we should automatically detect and flag to notify engineering to check procs running on the OS.
Session where this happens: mouse-seeks/qc/ophys/session/1303184169
The work around right now is that users will manually look for these events and mouse-qc will give a controlled language tag for these events.
Long frame stimulus events can happen in clusters (e.g. 20 long frames in a row where the cluster happens at a set interval). This can indicate a background process taking up CPU during an acquisition. This is something we should automatically detect and flag to notify engineering to check procs running on the OS.
Session where this happens: mouse-seeks/qc/ophys/session/1303184169
The work around right now is that users will manually look for these events and mouse-qc will give a controlled language tag for these events.