"Last events" section#
The “Last events” section displays detection and object (faces, bodies) recognition events, and records identification events using lists (Figure 8).
The section displays the last 30 events within the settings of handling policy for processing incoming images of the video stream, terminals, REST requests, etc. Receiving and displaying events is performed with minimal delays in near real time.
At the bottom of the screen, there is a “View events archive” button which leads to “Events archive” section
If departments are created, and users and event sources are attached to the department, the user sees only those events that were recorded by the event sources of his department. In order for the user to see the events, the administrator creates a department in the "Departments" section, then adds the user and the selected event source to it.
The filter icon (1), which is located on the right, hides the block with filtering settings. The page shows the following event data (2):
- "Event image"
- a photo image of the face from the video stream;
- a photo image of the body from the video stream;
- "Top Match"—the column is shown if the “Display top match” checkbox is active (3). If no matches are found for a photo from an event, then the column with the top match for this event will remain empty. The "Top match" includes:
- reference photo images of the face and/or body;
- value of similarity of the identified face with the reference in percentage terms and with the color coding of similarity thresholds:
- similarity values below “low” will be marked in red;
- similarity values between “low” and “medium” will be marked in yellow;
- similarity values above “medium” will be marked in green.
Color coding of similarity thresholds is configured in the config.json configuration file (see Luna Clementine 2.0. Administration Manual);
- "Match type"—the type of object (face or event), according to which the similarity of the identified face/body with the reference was found;
- "External ID"—external identifier of the face, the field is shown if such an ID is available (for "Face" in "Match type"). The external ID is used to integrate LUNA CLEMENTINE 2.0 with external systems as well as to transfer data to other systems in order to analyze and quickly respond to an event;
- "User data"—information from the database, linked to a person from the control (for "Face" in "Match type");
- "List"—the name of the list to which the person is attached (for "Face" in "Match type");
- "Date created"—date and time of fixing the event (for "Event" in "Match type");
- "Source"—the name of the source that recorded the event at the time the event was created. Users can change the source name. Then the "Video stream" field will show the new name, and the "Source" field will show the original one (for "Event" in "Match type");
- "Video stream"—the current name of the source that recorded the event, with a link to the real-time image of the stream (for "Event" in "Match type");
- "Handling policy"—the name of the handler, according to which the reference photo image of the body was processed (for "Event" in "Match type").
- "Event details" shows the available event data:
- "Date of created"—date and time of event registration;
- "Source"—the name of the source that recorded the event at the time the event was created. Users can change the source name. Then the "Video stream" field will show the new name, and the "Source" field will show the original one;
- "Video stream"—the current name of the source that recorded the event, with a link to the real-time image of the stream;
- "Handling policy"—the name of the handler, according to which the reference photo images of the face/body were processed;
- "Metadata" 1—button for uploading arbitrary user data in JSON format, the filed is shown if such data was added to the event (for "Event" in "Match type").
- Face attribute, if found:
- "Gender"—gender based on face image;
- “Age category”—the age of the detected person;
- Deepfake check results, if such check was performed;
- Liveness check results, if such check was performed
- Body attributes, if found:
- "Upper body colors"—an indication of the color of the clothes of the human body upper part;
- "Lower body colors"—indicating the color of the human body upper part;
- "Headwear"—the presence or absence of a headdress, if it is defined.
- "Backpack"—the presence or absence of a backpack, if it is defined.
Last events filtering#
The Service allows you to filter last events (2 in Figure 8) to find and display necessary events (Figure 9).
User can quickly find an event among the last 30, as well as set a limit for displaying new events on the screen.
When a user clicks on the icon (1 in Figure 8) on the “Last events” page, a menu with settings and filters opens. The number next to the icon shows the number of applied filters. A short description of the elements and parameters of the filter block on the “Last events” page is presented below (Table 2).
Table 2. Filters available to the user to search for last events
Name |
Description |
---|---|
"Sound notification" toggle and "Similarity threshold" parameter |
Allows a user to configure sound alerts about detection of an object that is not below the specified value of the "Similarity threshold" field |
General |
|
Source |
Filter by original source names—select one or more sources from the list of available ones |
Video stream |
Filter by current source names—select one or more sources from the list of available ones |
Handling policies |
Select one or more handling policies, according to which the face or body in the image was processed; |
Tags |
Selection of one or more tags. For example, the "Temperature" tag, is intended for displaying information about the temperature of the human body, filtering events by temperature. "Temperature":
Color coding of temperature values:
See the LUNA Access documentation for more information on setting of temperature ranges; |
Labels |
|
Label |
Name of the label—rule by which the comparison occurred. Labels are specified when setting up the handling policy; |
Similarity,% |
Lower and/or upper limits of similarity for displaying faces identified by the lists; |
Face attributes and properties |
|
Gender |
Gender of a person to be detected, determined by the image of a face:
|
Age category |
Age range of a person to be detected, determined by the image of a face:
|
Emotion |
Emotion of a person to be detected:
A combination of several values is possible; |
Mask |
Indication of the presence of a mask:
A combination of several values is possible; |
Liveness |
Liveness status selection:
A combination of several values is possible; |
Deepfake (Deepfake license required) |
Liveness status selection:
A combination of several values is possible; |
Body attributes and properties |
|
Upper body colors |
Top clothing color specification:
A combination of several values is possible; |
Lower body type |
Bottom clothing type specification:
A combination of several values is possible; |
Lower body colors |
Bottom clothing color specification:
A combination of several values is possible; |
Shoes color |
Shoe color specification:
A combination of several values is possible; |
Headwear |
Headdress specification:
A combination of several values is possible; |
Headwear colors |
Headdress color specification:
A combination of several values is possible; |
Backpack |
Backpack presence specification:
A combination of several values is possible; |
Sleeve |
Sleeve length specification:
A combination of several values is possible; |
Gender by body |
Gender of a person to be detected, determined by the image of a body:
A combination of several values is possible; |
Age category by body |
Age range of a person to be detected, determined by the image of a body:
|
Location |
|
City Area District Street House number Longitude(-180…180); Accuracy (0…90); Latitude(-90…90); Accuracy (0…90); |
Event location |
Other |
|
Comma-separated track IDs |
Specifying event track IDs. Copy the track ID from the event details |
Add filter by meta |
Allows you to fill in a set of blocks to create a filter by the "meta" field. The number of meta filters is unlimited. The following blocks are required to be filled in when creating a filter by meta:
|
The user selects one filter or a combination of filters and clicks on the “Filter” button for the applied filters to be applied.
To reset the applied filters, click on the “Reset” button.
The applied filters will affect the appearance of new events on the screen.
To collapse “Filters”, click on the filter icon on the right side of the screen.
Event details#
Click on an arrow button on the face or body from the event image (Figure 8) to open a page with detailed event data (Figure 10).
When an event contains data on the detection of both a face and a body, you can switch between these data on the page with event details. If an event contains detection data for only one object, such as a face, then there will be no detection data for another object.
The the page with event details consists of four blocks. The description of the elements of the page is presented below (Table 3).
Table 3. Elements and parameters of the "Event details" page
Name |
Description |
---|---|
Event information |
Basic information about the event |
Date created |
Date and time of event recording |
Event |
“Event ID” — when clicked on , the value is copied to the clipboard |
Track |
“Track ID” — when clicked on , the value is copied to the clipboard |
Handling policy |
Name of the policy by which the image processing in the video stream is performed. Clicking on the name of the policy opens the form for editing its parameters |
Source |
The name of the source that recorded the event at the time the event was created. Users can change the source name. Then the "Video stream" field will show the new name, and the "Source" field will show the original one |
Video Stream |
The current name of the source that recorded the event, with a link to the real-time image of the stream |
Tags |
Name of tags by which the event is filtered |
Metadata |
Uploading arbitrary user data in JSON format, if available |
Location |
Event location data: “City”, “Area”, “District”, “Street”, “House number”, “Coordinates (latitude)”, “Coordinates (longitude)” |
Detection |
If equipped: face and/or body detection |
Find similar: events |
Clicking on opens a page in a new tab and searches for evens by the Event ID where the face/body was recorded |
Find similar: faces |
Clicking on opens the page in a new tab and searches for similar faces by the Face ID For face detection only |
Photo image of a face and/or body from a video stream |
Normalized image. When clicked on:
|
Attributes |
Face attributes:
If Liveness and Deepfake checks were performed:
|
Body attributes:
|
|
Additional properties |
Face properties:
|
Best match: Event or Person |
Similarity value of identified face/body with the face/body from control list/event (in percentage); |
Find similar: events |
Clicking on opens a page in a new tab and searches for evens by the Event ID where the face/body was recorded |
Find similar: faces |
Clicking on opens the page in a new tab and searches for similar faces by the Face ID For face detection only |
Additional information |
“Face” type — “Information”, “Lists”, “External ID”. “Event” type — “Handling policy”, “Source” with the ability to go to the handling policy editing page and view the stream from the source in real time |
Photo image of a face and/or body |
Reference photo image of the face or body (sample) or no photo. When clicked on
|
Attributes |
Face attributes:
Body attributes:
|
Additional properties |
Face properties:
|
"Matches" |
List of matches with a detected face and/or body |
Event photo |
“Face” type—an avatar, sample, or no photo image. Similarity value of identified face with the face from control list (in percentage) “Event” type—detection (photo image of a face from a video stream). Similarity value of identified face or body with the face or body from the event (in percentage) |
Type |
|
Date created |
Date and time of the biometric sample of the face or body creation from the identification event |
Label |
Name of the label—rule by which the comparison occurred |
Additional information |
“Face” type — “Information”, “Lists”, “External ID”. “Event” type — “Handling policy”, “Source”, “Video stream” with the ability to go to the handling policy editing page and view the stream from the source in real time |
When clicked, the face or event details opens |
-
All detailed capabilities and limitations of the "Metadata" field are specified in the "Administrator Manual" of LUNA PLATFORM 5 in the paragraph 6.9.4 "Events meta-information". ↩