Documentation for Face PSIM 1.0.1.

Previous page General information on stored face types and related data  Configuring the face images, vectors and metadata storage depth Next page

The images of captured and recognized faces and vectors are stored in a folder, the path to which is specified in the FaceDB registry key. This data storage mode corresponds to the UseFaceDB = 2 mode and is set forcibly when Face PSIM starts (see Registry keys reference guide, for details about working with the registry, see Working with Windows OS registry).

Note

It is not recommended that the folder for storing face images and vectors be located on the same disk where the Axxon PSIM video archive is stored.

UseFaceDB = 2 mode provides maximum search speed and storage depth. The general algorithm of Face PSIM operation in this mode is as follows:

  • at startup, the Server reads all data from the folder into RAM. Then the received images and vectors are written to the RAM and to the folder, and the metadata is written to the database. This ensures the fastest possible search process;
  • all searches are carried out in RAM. However, this entails a high consumption of RAM and a longer start of the Server;
  • metadata is stored in the Fir database in the Hits table. Since the images and vectors are stored in a folder on disk, the database will fill up much more slowly. This ensures maximum storage depth.

The reference faces are stored in the <Axxon PSIM installation directory>\Bmp\<Person> folder.

Note

The reference face images from the <Axxon PSIM installation directory>\Bmp\<Person> folder can be used for automatic face verification using a script (see Examples of frequently used scripts). Also, with the help of the Event Manager module, which is a part of the ACFA PSIM, the operator controlling the Event Manager interface window can decide whether the face looking at the camera is to be verified or not. In this case, the operator compares this face with the reference face from the <Person> folder, which is displayed in the Event Manager interface window (for details about Event Manager, see Guide for configuring and working with the Event Manager integration module).

  • No labels