FAQ

Owned by Padmashri Gargesa
Last updated: May 27, 2022
2 min read

 

Nimble

How to make sure the Nimble container has come up and running?

On installing the package, all docker containers for the VAS Suite/SDK are brought up in the background. To make sure the Nimble container is running you can run the following command at the terminal:

docker ps

In the list of running containers displayed, make sure that the Nimble container is listed and its corresponding STATUS column shows that the container is up

Run the following command

docker logs <name of the container> -f --tail 100

This prints out the Nimble container console logs. Stage wise logs are displayed for all configured pipelines as shown.

Make sure the configured sources and sinks (only if configured) are listing a non-zero value against the Frames Per Second metric

How to map the pipeline configs to the right use case names (relevant only to release packages v0.12/v0.13)?

Each supported use case needs to be accompanied by the right use case name in the config file. All sample use-case files are maintained in the deploy/samples/cpu in the package deploy folder, the below table shows the mapping between the sample config file for a use case and the use case property that needs to be populated for the pipeline.

Note: If there are multiple pipelines of the same use case, we will need to ensure that the use case name is mentioned in the format:

usecase: <use case name>|<unique id int>

Use case

Config mapping of use case name

Sample file

Comments

Use case

Config mapping of use case name

Sample file

Comments

People Counting

people-counting

c1_person-detection_privacy.yaml

The blur item pipeline element allows to blur faces for privacy. This can be removed for a normal people counting pipeline commissioning

Social Distancing

physical-distancing

c1_person-detection.yaml

 

Intrusion Detection

intrusion-detection

c1_intrusion-detection.yaml

 

People Occupancy

line-crossing

c1_line-crossing.yaml

 

Loiter Detection

loiter-detection

c1_loiter-detection.yaml

 

Intrusion + Loiter Detection

loiter-detection

c1_intrusion-loiter.yaml

This use case keeps a measure of dwell time on subjects only when they have violated a pre-defined intrusion zone

Fire/Smoke Detection

fire-detection

c1_fire-detection.yaml

 

Collision Detection

collision-detection

c1_collision-detection.yaml

 

Mask Detection

mask-detection

c1_mask-detection.yaml

 

Pose Detection

pose-detection

c1_pose-estimation.yaml

 

PPE Compliance

ppe-compliance

c1_ppe-compliance.yaml

 

 

Â