matiasandina
commented
12 months ago Related, but not exactly a Jam. It is possible that crumbs and dust interfere with the pellet detection. We should consider adding a "animal has not eaten for x hours" Say x = 3, it's unlikely for an animal to take 0 pellets in 3 hours, points to either: 1) Wrong functioning of the FED 2) Animal has not learnt yet 3) Animal needs attention (e.g., not habituated to arena? experimental condition? other?)
Practically speaking, we could just reduce notification frequency to 2 hours and get the event_summary more often.
[ ] adding
jamAlertIntervalto the jam message on the cpp side and printing it on the python side Unsure how useful this is...we put jamAlertInterval = 300 seconds so that FEDs don't spam the notification system when jammed. In fact, you end up getting a substantial amount of messages whenjamAlertInterval = 300. If people decide to increase it, it might become a problem at some point (e.g., FEDs are clogged but no message has been sent).[x] adding information about a cleared jam Because the users might put the notification to be several hours, they might get the jam alert but not the info about whether it resolved or not. The message that comes after n hours might also only contain info before the jam. Having a "jam was cleared" might be a good idea. Practically, it is evident that you stopped receiving the jam notification, and then you assume the jam has been cleared