You can either try yourself with the instructions here for ghost counting issue from support portal or log a request in https://flir.custhelp.com/app/ask_PCT so our support team in suitable time zone can help to fine tune at our night time.

Credentials to FLIR Support


Link: https://flir.custhelp.com/app/ask_PCT 
Email: support@gotapway.com
Password: tapwayabc123#


ISSUE

You are seeing false tracks or random counts on a Brickstream 3D Gen 2 during a time when the site

has no one there.


SOLUTION

Note: The following methods describe how to disable tracking in low light conditions (i.e., lights off) and are not applicable for installations that have consistent lighting even during times of inactivity (i.e., lights on).


There are three tracking parameters that can be adjusted to avoid false counts.


Undefined Threshold


The Undefined Threshold is the percentage of undefined required for the camera to disable tracking. The

current Undefined (Pink) % can be found on the Calibration page and is represented by the pink number

in the top of the image. You will want to observe what this number is during the period of time the false

tracks are happening. Then compare it to the number during the operational hours. The idea is to find a

number that will keep the camera tracking while the store is open but shuts off when it's closed.

The Undefined Threshold parameter can be found on the Tracking page Quality tab and has a default

value of 50.


Some examples:

  1. Operational Undefined is 43-48 and your Night Undefined is 57-62. You will want to set your Undefined Threshold to 52.
  2. Operational Undefined is 13-18 and your Night Undefined is 34-39. You will want to set your Undefined Threshold to 26.

You don't want to get too close to your Operational Undefined or you'll stop counting during the day. It

is acceptable to lean closer to the Night Undefined as to not risk it.


If the Undefined Threshold barely changes between the two timings, please record a Debug AVI during

the time of the false tracks. Open a support ticket with <pct-support@flir.com > and transfer the Debug

DAT file to FLIR's FTP server or your own. It will likely be too large to send via email. Support will

analyze the track data from the Debug AVI to make suggestions.


Intensity


Minimum intensity is set on the Tracking page Quality tab. This defines the minimum level of

brightness in a scene, under which tracking is disabled. The default value is 40.


The average intensity can be viewed on the diagnostics page by clicking button in top right.


As with Undefined Threshold you don't want to increase this value too much or you may disable

tracking during the operational periods.



Example

For ghost counting at night, if it's constant light in daytime, we can adjust the min dynamic change, min intensity value and undefined threshold. either of these three condition is not fulfilled, camera will disable the 'tracking engine' so to not track and count anything.



In daytime as of now, we can find the current dynamic value and intensity value in 'diagnostics' page, for example 210 and 152


Then I come here to change the default value of these two parameter to a number about 20% lower than the current reading I get, for example, I put 180 for dyn range and 120 for intensity.


To ensure at daytime the camera tracking engine wont be disabled. and usually night time these two value will drop tremendously, so it will definitely lower than 180 or 120 here, and to ensure night time tracking engine will be disabled to eliminate ghost count


* side note - change the min dynamic range value to a number in between the daytime value and night time reading, change the min intensity to a number in between the daytime avg intensity value to night. By doing this, at night time, the tracking engine will be disabled and there will be no more ghost counts or tracks.



See attached document for more information