search

lastralab / ABISSMAL

Github repository for ABISSMAL behavioral tracking platform
https://github.com/lastralab/ABISSMAL
Other
3 stars 2 forks source link

[Log] Strange debug lines printed to log #423

Closed gsvidaurre closed 1 year ago

gsvidaurre commented 1 year ago

Describe the bug There is some strange debug information written to the log file.

To Reproduce Steps to reproduce the behavior:

  1. Remove the current version of Abissmal on the given Pi
  2. Clone Abissmal from GitHub
  3. Execute run_install.sh (select Y for updating packages and cron)
  4. Run the tracking system
  5. See the DEBUG lines written to the log file as soon as Abissmal starts

Expected behavior I don't expect these DEBUG lines to pop up in the log file. I'm not sure if this is a real bug that needs to be fixed, or some issue related to dependencies being updated since the last time I set up Abissmal

Screenshots This is an example of lines written to the log file:

2023-06-22 13:57:26 DEBUG Video: sensitivity = 9000 < 440119 pixels 2023-06-22 13:57:26 INFO Motion detected. Starting video recordings 2023-06-22 13:57:30 INFO IRBB activity detected in sensor: Outer Beam Breaker 2023-06-22 13:57:31 INFO IRBB activity detected in sensor: Inner Beam Breaker 2023-06-22 13:57:31 INFO IRBB activity detected in sensor: Inner Beam Breaker 2023-06-22 13:57:32 INFO IRBB activity detected in sensor: Inner Beam Breaker 2023-06-22 13:57:33 INFO IRBB activity detected in sensor: Inner Beam Breaker 2023-06-22 13:57:35 DEBUG tag: ImageWidth (256) - type: long (4) - value: b'\x00\x00\x05\x00' 2023-06-22 13:57:35 DEBUG tag: ImageLength (257) - type: long (4) - value: b'\x00\x00\x02\xd0' 2023-06-22 13:57:35 DEBUG tag: Make (271) - type: string (2) Tag Location: 46 - Data Location: 134 - value: b'RaspberryPi\x00' 2023-06-22 13:57:35 DEBUG tag: Model (272) - type: string (2) Tag Location: 58 - Data Location: 146 - value: b'RP_ov5647\x00' 2023-06-22 13:57:35 DEBUG tag: XResolution (282) - type: rational (5) Tag Location: 70 - Data Location: 156 - value: b'\x00\x00\x00H\x00\x00\x00\x01' 2023-06-22 13:57:35 DEBUG tag: YResolution (283) - type: rational (5) Tag Location: 82 - Data Location: 164 - value: b'\x00\x00\x00H\x00\x00\x00\x01' 2023-06-22 13:57:35 DEBUG tag: ResolutionUnit (296) - type: short (3) - value: b'\x00\x02' 2023-06-22 13:57:35 DEBUG tag: DateTime (306) - type: string (2) Tag Location: 106 - Data Location: 172 - value: b'2023:06:22 13:57:35\x00' 2023-06-22 13:57:35 DEBUG tag: YCbCrPositioning (531) - type: short (3) - value: b'\x00\x01' 2023-06-22 13:57:35 DEBUG tag: ExifIFD (34665) - type: long (4) - value: b'\x00\x00\x00\xc0' 2023-06-22 13:57:35 INFO Videos recorded

Raspberry Pi information (please complete the following information):

Additional context This has happened for 2 PIs that I set up today and yesterday to run Abissmal. I checked other files generated, and the tracking system does save videos and all data spreadsheets without any issues

gsvidaurre commented 1 year ago

Just figured out some more info: I think this is related to concatenating the pre- and post videos. On the Pi that I just set up, I can see the video recording events spreadsheet that has 1 entry each for 1 pre and 1 post video I can also see the pre- and post .mp4 video files (called Box_02_2023-6-22_13-57-26_pre.mp4 and Box_02_2023-6-22_13-57-26.mp4, 3.3Mb and 4Mb). But there is another .mp4 file called 2023-6-22_13-57-26.mp4 that must be the concatenated video. This file is only 256.0 kB and doesn't play when opened