Page 11
Camera Placement • The Camera must install parallel to the ground with max tilt 20 degrees. • The suggested installation height is 2.4 meters to 3.6 meters by default. • With Zoom-in Factor adjustments the camera can be installed up to 5 meters. •...
Page 12
Camera Placement • Hallway • Door avoid swing area Outside 1/3 Inside 2/3 Mind the Width Feature: Feature: Open area without obstacle on the route. Door or other obstacle may block the line of Installation: sight between camera and incoming people. Camera “Face down”...
Page 13
Camera Placement • Example - Avoid uneven floor FOV covered stairs caused Solution: Install the camera on even floor. unexpected result of height filter.
Page 14
Camera Placement • Example - Avoid Swing Door FOV cover swing doors Solution: Install the camera away from door. might cause false object and miscount.
Page 15
Camera Placement • Example - Utilize the HFOV VFOV is shorter then HFOV, Solution: Utilize the longer HFOV might leave gap in passage. to cover the passage.
Page 25
Analytics Settings • Find Analytics Setting Pages 1. From Index page click “1: Stereo Tracker” hyperlink. 2. From “Index” -> “Configuration” -> “Applications” -> “Package management”-> “Stereo Tracker”...
Page 26
Analytics Settings • Camera settings: Configure the installation height, algorithm settings, and exclusive area settings. • Rules: Draw the counting-lines, and set up the max./min. object height, and analytics event rules.
Page 27
Analytics Settings • Camera Settings 1. Installation Height: Set camera installation height manually. 2. Camera Tilt angle: In case you install the camera titled, you have to enter the right angle. Recommended tilt angle below 20 degrees. 3. Check detection height: Check camera’s detection height with internal algorithm. This Calibration is a reference for refining setting installation height.
Page 28
Analytics Settings • Camera Settings 1. People Detection Area: The feet area that camera provide the highest accuracy in people counting. Calculated based on camera installation height and optical zoom factor. 2. The counting rules should cover the whole passage and mostly fall into detection area. Detection area is based on feet projection position, SC8131doesn’t need the area to cover the whole body of the target person.
Page 29
Analytics Settings • Optical Zoom (optional) • During 2.4 meters to 3.6 meters height, the object’s pixels are sufficient and clear for people counting algorithm calculation. • While installing higher than 3.6 meters, higher Zoom-in factor value could provide clearer image for countin algorithm.
Page 30
Analytics Settings • Exclusive Area – The camera is tracking the “feet” of the person, not his head. So the excluded area should not be drawn on the area where people might walk though. If the body or the head of the person is inside the excluded area, the person will still be detected, since his feet are outside this area.
Page 33
Rules • Analytics Rules – Draw Flow Path within the counting area. • We recommend users to use Flow Path instead of counting line for better accuracy. Counting line is only for legacy usage.
Page 34
Rules • Analytics Rules – Example If the passage is slightly wider then the detection area, please extend the analytics rule to cover the whole passage with proper test on site to make sure the counting accuracy.
Page 35
Rules • Entering Leaving Map – Helps you to know where the object has been tracked by the camera. Always draw flow path between the entering and leaving points.
Page 36
Rules • Entering Leaving Map– Example The flow path is places between start/stop points. The flow path is places on the edge of object detection which might lead to miscount.
Page 37
Rules • Flow Path Counting • This rule consists of 7 parallel arrows. When passengers pass by along with these flow path, the stereo camera would count. • Users can move, rotate, adjust the angle, expand the range, and adjust the arrow’s length. Extend Bend Direction (In/Out)
Page 38
Rules • Flow Path Counting – How to Draw the Flow Path? • Width: Fully cover the whole passage with the arrow and tail. • Length: The arrow should be drawn between the Start/Stop points. The width need to cover The arrows should be set the whole passage.
Page 39
Rules • Flow Path Counting – Example Count Miss The arrow and tail didn’t cover the whole passage.
Page 40
Rules • Flow Path Counting – Example Count Count Count Both the arrow and the tail cover the whole passage, then check the detection area, and the start/stop map.
Page 41
Rules • Flow Path Counting – Counting Sensitivity • The distance a person needs to move along the arrow direction to be counted.
Page 42
Rules • Flow Path Counting – Example Counting Sensitivity = 6 Counting Sensitivity = 5 Miss Count Not been counted in default sensitivity. Increase the sensitivity Sensitivity 5 means people need will let the camera count this people. to travel 50% length along the flow path.
Page 46
Report • The counting report can be set as push or pull. • Pull: Customer can retrieve counting report via CGI. • Push: SC9131 can generate the counting report and deliver to customer server periodically. CGI Report Request Periodical Report Push...
Page 47
Report - CGI • Select “Stereo Tracker” from Camera Web Index page. • Select “Report” to view report on web or via CGI.
Page 48
1. Select the report start time and end time 2. Select the report type: 3. Select the report format: 4. Select the period of time does one record representing. 5. Choose whether to show the record with no people counted. 6.
Page 49
Report – Report Push • Set up the report push...
Page 50
Report – Report Push • Server Info 1. Type: Select the server type which SC8131 will deliver the report. Now we support EMAIL/FTP/HTTP/HTTPS/SD Card. 2. Test connection: User can press the button to test whether this server is accessible by these settings.
Page 51
Report – Report Push 1. VCA: Select Report type 2. Format: XML/CSV/JSON 3. Push Frequency: Set the time interval between two report delivery. Ex: 1 minute, 1 hour or 1 DI cycle. 4. Aggregation frequency: Set how much time does a record representing. Ex: 1 minute, 5 minutes or 1 DI cycle.
Page 54
Validator Video Upload Report as .csv File Validation Tools (Import the Video clip)
Page 55
Validator – Camera Setting High resolution: Better video quality. Low resolution: Less impact on network bandwidth. Side by Side: Data for algorithm improvement. Video will be always recorded in the time period. Video will be recorded only when the DI is ON (ex: Door is opened.) The job will only be performed once.
Page 56
Validator – User Interface Select the target rule. Display options Accumulated counting result. Concurrent counting result. (1 second) Export the result.
Page 58
Device Center Device Naming Group Naming Device Center VADP Package The camera must be installed the VADP package then Device Center ability connect to the camera The VADP package default will create the Device ID (By MAC Address) and Group ID (Fixed Name) These IDs is for user naming, memory and management.
Page 59
Device Center Store A Store B Device Center Device Center Client Server Office Store C Add Device Must install the Device Center Client in the camera site to add the camera to Device Center Server Device Center Client can easy add the single and multiple devices...
Page 60
Device Center Device Management Monitoring devices status via hierarchical structure. The hierarchical structure is like the logical tree design. User can create the folder to manage it. Double click the camera can open the camera webpage t set up t directly.
Page 61
Device Center Devices Maintain Support the feature of batch firmware upgrade, package upgrade, restore & restart.