"Task log" section#
The “Task log” section is intended for creating, deleting, and displaying tasks. General view of the “Task log” section is shown below (Figure 29).
“Task log” section contains the following elements:
- “Cross-matching” button—a button for creating a task for cross-matching lists of faces;
- “Export faces” button—a button for creating a task to export faces and information on them;
- “Export events” button—a button for creating a task to export events and information on them;
- “Batch import” button—a button for creating a task for batch import of photo image archive into the list;
- “Batch identification”—a button for creating a task for identifying an archive of photo images of references with candidates (faces or events with faces);
- “Deleting faces from the list”—a button for creating a task for removing persons from the selected list;
- “Verification”—a button for creating a task for verifying persons;
- table of tasks:
- “ID” — task identifier;
- “Description” — user who created the task;
- “Type” — task type (cross-matching, export, batch processing, batch import, batch identification);
- “Date created” — date and time of task creation;
- “Expiration date” — date and time of completion of the task;
- “Status” — task progress state;
- — button to stop the task (appears if the task status is “In progress”);
- — button for downloading the result of the task (1);
- — button for deleting a task (2);
- the number of tasks displayed on the page is set by the switch in the lower right corner of the page. There can be 10, 25, 50 or 100 tasks in total on one page (3).
The status changes during the task execution. In total, 4 statuses are applied to tasks in the Service:
- — task is being performed;
- “Collecting results” — collecting the results of the task;
- — task completed;
- — an error occurred while executing a task.
The process of creating tasks and the values of the specified parameters are described below. If you need to go back to the task list page during creating a task, press the Esc key on your keyboard.
Configure notifications about task status using the "callbacks" functionality. Notifications will be sent to the external system at the specified URL. The notification settings block opens after filling in the required fields to create a task (Table 13).
Table 13. Notification settings in the task creation form
Parameter |
Description |
Default value |
---|---|---|
Add callback |
||
Type |
Protocol type when creating a notification. Users can receive notifications in the interface via http and Telegram |
HTTP |
URL |
Address of the external system where the notification will be sent |
- |
Authorization type |
Selecting the type of authorization into an external system and setting up authorization data. The basic type of authorization requires specifying login and password to enter an external system |
Basic |
Timeout (seconds) |
Maximum time to wait for a request to complete |
60 |
Request body format |
Data interchange format: JSON or MessagePack |
application/json |
HTTP Headers |
HTTP Request Headers |
- |
Creating a cross-matching task#
To create a task for cross-matching lists of faces, click on the “Cross-matching” button (Figure 29). A general view of the form for creating a cross-matching task is shown below (Figure 30).
The “Cross-matching” form contains the following elements:
- “List”* — selection of a list for comparison;
- “Find matches in”* — selection of a list for comparison;
- “The maximum number of similar ones” — maximum number of similar candidates (the default is 3);
- “Minimum similarity threshold, %” — the lowest score of similarity in percentage between candidates that the Service accepts as a possible match (the default is 50).
* Required field
Fill in all the required parameters and click on the “Create task” button (or Enter key on your keyboard)..
Resource-intensive tasks can take a while. In the pop-up window (Figure 31), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button (Esc key on keyboard)..
After successfully creating a cross-matching task, the message “Task for cross-matching has been created” will appear in the upper right corner of the screen (Figure 32).
Creating an export faces task#
To create a task to export faces and information on them, click on the “Export faces” button (Figure 29). A general view of the form for creating an export task is shown below (Figure 33).
Description of the parameters of the “Export faces” form is given below (Table 14).
Table 14. Export task parameters
Parameter |
Description |
Default value |
---|---|---|
Data upload parameters |
||
List |
Specifies the list for export |
- |
User data |
Indicates face data (up to 128 characters) |
- |
Face IDs |
Specifies the values of identifiers of faces in LUNA PLATFORM 5 in UUID format |
- |
Face external IDs |
Specifies the values of third-party external identifiers |
- |
Date from |
Specifies the lower limit of the period of creation of faces or events in LUNA PLATFORM 5 |
- |
Date to |
Specifies the upper limit of the period of creation of faces or events in LUNA PLATFORM 5 |
- |
ID of the first face |
Specify the values of the identifier of the first face from the exported faces |
- |
ID of the last face |
Specify the values of the identifier of the last face from the exported faces |
- |
Additional parameters |
||
Selecting table columns to be included in the file upon export, and indication the order in which they are located |
Face ID User data External ID Time Avatar Event ID Lists |
On On On On On On Off |
Save face images |
Enabling this option allows you to upload face images into the archive with the .csv report |
Off |
Type of biometric template |
Specifies the biometric template of which objects will be exported—faces or bodies |
Faces |
Delimiter for .csv |
A special character that will be used in the file with export results to divide text into columns |
, |
Fill in all the required parameters and click on the “Create task” button.
Resource-intensive tasks can take a while. In the pop-up window (Figure 34), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button (Esc key on keyboard)..
After successfully creating an export task, the message “Export task has been successfully created” will appear in the upper right corner of the screen (Figure 35).
Creating an export events task#
To create a task to export objects events and information on them, click on the “Export events” button (Figure 29). A general view of the form for creating an export events task is shown below (Figure 36).
Description of the parameters of the “Export events” form is given in Table 14.
Table 14. Export task parameters
Parameter |
Description |
Default value |
---|---|---|
Data upload parameters |
||
General data about the event |
||
Source |
Specifies the name of the event source |
- |
User data |
Indicates face data (up to 128 characters) |
- |
Event IDs |
Specifies the values of the event identifiers in UUID format for performing an accurate search separated by commas |
- |
Event external IDs |
Specifies the values of third-party external identifiers separated by commas |
- |
Face IDs |
Specifies the values of identifiers of faces in UUID format separated by commas |
- |
Similarity |
A value from 0 to 1 is specified |
- |
Tags |
Specifies a tag or tags separated by commas |
- |
Handling policies |
Specifies policy name, it is possible to specify several values |
- |
Date from |
Specifies the lower limit of the period of creation of events |
- |
Date to |
Specifies the upper limit of the period of creation of events |
- |
Advanced event filters |
||
End date from |
Indicates the lower limit of the event end period |
- |
End date to |
Indicates the upper limit of the event end period |
- |
ID of the first event |
Indicate the value of the identifier of the first event from the exported events |
- |
ID of the last event |
Indicates the value of the identifier of the last event from the exported events |
- |
Track IDs |
Specifies the values of the track identifiers in the UUID format separated by commas |
- |
Face attributes |
||
Gender |
Specifies male/female gender |
- |
Age |
Specifies the age range |
- |
Emotions |
Specifies emotions |
- |
Medical mask |
Detection of the presence/absence of a medical mask, mouth occlusion |
- |
Liveness |
Specifies the result of checking for the presence of a living person in the frame |
|
Body attributes |
||
Gender by body image |
Specifies the female, male, undefined gender |
- |
Age by body image |
Specifies the age range |
- |
Headwear |
Specifies headdress |
- |
Upper body colors |
Specifies top clothing color |
- |
Sleeve |
Specifies sleeve length |
- |
Headwear color |
Specifies headdress color |
- |
Lower body colors |
Specifies bottom clothing color |
- |
Lower body type |
Specifies bottom clothing type |
- |
Shoes color |
Specifies shoe color (only for “Identify among events); |
|
Backpack |
Specifies backpack presence |
- |
Best match data |
||
Face IDs |
Specifies the values of identifiers of faces 5 in UUID format |
- |
Face external IDs |
Specifies the values of third-party external identifiers |
- |
Label |
Name of the label parameter (the rule by which comparison occurs); |
- |
Geoposition |
||
“District”; “Area”; “City”; “Street”; “House number”; |
||
Advanced geoposition filters |
||
“Longitude (-180…180)”; “Accuracy (0…90)”; “Latitude (-90…90)”; “Accuracy (0…90)” |
||
Other |
||
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:
|
|
Additional parameters |
||
Columns in the report |
Selecting table columns to be included in the file upon export Face ID User data Time External ID Event ID Source Handling Policy ID Tags Track ID Metadata Geo position |
On On On On On On On Off On Off On |
Order |
Indication the order in which parameters are located in the report Event ID Create time End time Source Handling Policy ID Face ID External ID User data Age Gender Emotion Medical mask; Track ID Top match District Area City Street House number Geo Position |
- - - - - - - - - - - - - - - - - - - - |
Save face images |
Enabling this option allows you to upload face images into the archive with the .csv report |
Off |
Type of biometric template |
Specifies the biometric template of which objects will be exported—faces or bodies |
Faces |
Delimiter for .csv |
A special character that will be used in the file with export results to divide text into columns |
, |
Fill in all the required parameters and click on the “Create task” button or the Enter key on your keyboard.
Resource-intensive tasks can take a while. In the pop-up window (Figure 34), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button (Esc key on keyboard).
After successfully creating an export task, the message “Export task has been successfully created” will appear in the upper right corner of the screen (Figure 35).
Creating a batch import task#
The batch import task allows you to batch import faces from photos into a specified list.
To create a task for batch import of photo image archive into the list, click on the “Batch import” button (Figure 29). The general view of the form for creating a batch import task is shown below (Figure 37).
The “Batch import” form contains the following elements:
- field for uploading an archive with photographs — it is possible to upload archives in *.ZIP format (required);
- “List” — selection of a list (required);
- “Add a photo to the list only if it complies with the ISO/IEC standard” — the photo will be added to the list only after passing the ISO/IEC 19794-5:2011 verification.
- — button for deleting the loaded archive — button for deleting the loaded archive.
Download file requirements:
- *.ZIP file format;
- there can be one or more people on the image (depends on policy settings);
- the image must contain a person's face;
- images must be located immediately inside the archive, and not in a folder inside the archive;
- the archive size is set using the ARCHIVE_MAX_SIZE parameter in the config.py configuration file of the Tasks component, the default size is 100 GB (for details, see “VisionLabs LUNA PLATFORM 5. Administrator manual”).
Fill in all the required parameters and click on the “Create task” button or the Enter key on your keyboard.
Resource-intensive tasks can take a while. In the pop-up window (Figure 38), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.
After successfully creating a batch import task, the message “Batch import task has been successfully created” will appear in the upper right corner of the screen (Figure 39).
Creating a batch identification task#
To create a task for identifying an archive of photo images (faces or events with faces), click on the “Batch identification” button (Figure 29). The general view of the form for creating a batch identification task is shown below (Figure 40).
The “Batch Identification” form contains the following elements:
- field for uploading an archive with photographs in *.ZIP format (required);
- —button for deleting the loaded archive;
- “Identify among”—look for matches among “Faces” or “Events”;
- “Filters” block—settings for user identification. A description of the parameters of the “Filters” block, depending on the selected object for identification, is presented in the tables (Table 15 and Table 16);
- “Additional filter parameters” block—general parameters for identification among faces and events:
- “Similarity threshold, %”—the lowest percentage similarity score between candidates that the Service accepts as a possible match (default: 80).
- “Number of records (from 1 to 100)”—the number of lines with matches with a limit of 100 lines (default: 3).
Table 15. “Filters” block parameters of the batch identification task when searching for a match among faces
Name |
Description |
---|---|
List |
List name |
Comma-separated Face IDs |
Face ID from the list |
User data |
Information linked to the person from the database |
Comma-separated external face IDs |
External ID of persons face |
Date from |
Specifies the lower limit of the period of creation of faces or events in LUNA PLATFORM 5 |
Date to |
Specifies the upper limit of the period of creation of faces or events in LUNA PLATFORM 5 |
Table 16. “Filters” block parameters of the batch identification task when searching for a match among events
Name |
Description |
---|---|
Source |
List of available event sources |
User data |
Information linked to the person from the database |
Age |
Age group: below 18; from 18 to 44; from 45 to 60; above 60 |
Gender |
Female; Male |
Emotion |
Anger; Sadness; Neutral; Disgust; Fear; Happiness; Surprise. Its possibly to select multiple emotions. |
Medical mask |
Detection of the presence/absence of a medical mask or mouth occlusion. Missing; Medical mask; Occluded. Its possibly to select multiple variants. |
Creation date from |
Specifies the lower limit of the period of creation of faces or events in LUNA PLATFORM 5 |
Creation date to |
Specifies the upper limit of the period of creation of faces or events in LUNA PLATFORM 5 |
Comma-separated event IDs |
Event ID of detection and attribute retrieval |
Comma-separated external event IDs |
External event ID |
Comma-separated Face IDs |
Face ID from events that are created in LUNA PLATFORM 5 as a result of a detection event and attribute extraction |
Similarity |
The lower threshold on the similarity if the person was identified |
Handling policies |
Handling Policy ID |
Comma-separated track IDs |
Specifies the values of the track identifiers in LUNA PLATFORM 5 in the UUID format |
Comma-separated tags |
Specifies a tag or tags |
Gender by body image |
Specifies the female, male, undefined gender |
Age by body image |
Specifies the age range |
Headwear |
Specifies headdress |
Upper body colors |
Specifies top clothing color |
Sleeve |
Specifies sleeve length |
Headwear color |
Specifies headdress color |
Lower body colors |
Specifies bottom clothing color |
Lower body type |
Specifies bottom clothing type |
Shoes color |
Specifies shoe color (only for “Identify among events); |
Backpack |
Specifies backpack presence |
Location |
“District”; “Area”; “City”; “Street”; “House number”; “Longitude (-180…180)”; “Accuracy (0…90)”; “Latitude (-90…90)”; “Accuracy (0…90)” |
To upload an archive with photo images of faces to be identified, click on in the “References” section and specify the path to the archive on the local computer.
Download file requirements:
- *.ZIP file format;
- there can be one or more people on the image (depends on policy settings);
- the image must contain a person's face; images must be located immediately inside the archive, and not in a folder inside the archive;
- the archive size is set using the ARCHIVE_MAX_SIZE parameter in the config.py configuration file of the Tasks component, the default size is 100 GB (for details, see “VisionLabs LUNA PLATFORM 5. Administrator manual”).
Fill in all the necessary parameters and click the “Create task” button or the Enter key on your keyboard..
Resource-intensive tasks can take a while. In the pop-up window (Figure 41), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.
After successfully creating a batch identification task, the message “Batch identification task has been successfully created” will appear in the upper right corner of the screen (Figure 42).
Creating a task for deleting faces from the list#
The task of removing persons from the list (Cleanup task) allows you to select faces based on specific parameters and then remove them from the selected list.
To create a Cleanup task, click on the “Deleting faces from the list” button (Figure 29). The general view of the window for creating a task for batch import is shown below (Figure 43).
The “Deleting faces from the list” window contains the following elements:
- “Description”—a field for adding an explanatory note to the task;
- “Store results” checkbox—if enabled, the results of the task will be saved in the Image Store service storage.
- “Delete samples” checkbox—if enabled, wrapped images obtained after detecting faces from the list will be deleted;
- “List”*—select a list from which faces will be removed;
- “Information”—a field for specifying information about persons from the list. Allows you to remove only a few people from the list, for example, those for whom the same information is provided.
- “Delete data after”—the lower included threshold value of the face creation time;
- “Delete data before”—the upper excluded threshold value of the face creation time.
* Required to be filled out.
Fill in all the required parameters and click on the “Create task” button or the Enter key on your keyboard.
Resource-intensive tasks may take some time to complete. Confirm the action in the pop-up window—click the “Ok” button or cancel the action using the “Cancel” button (Figure 44).
After successfully creating a task for removing persons from the list, the message “Cleanup task has been successfully created” appears on the screen (Figure 45).
Creating the verification task#
The verification task allows you to quickly compare two faces from photographs and find out the result of the comparison (percentage of facial similarity).
To create a verification task, click on the “Verification” button (Figure 29). The general view of the window for creating a verification task is shown below (Figure 46).
The “Verify” window contains two blocks for uploading photos. To verify faces, select images on your local computer or drag and drop images directly into the image upload windows.
Image file requirements:
- *.png , *.jpeg, or *.bmp format;
- image size no more than 15 MB and no more than 3840х2160 pixels;
- image may contain one or more people;
- image must have a person's face.
If there is more than one face in the photo, select which face to be added in the list/lists then after uploading—the selected face will be highlighted with a green frame. Click on the “Verify” button. The result of comparing faces will appear in the window—the value of the degree of similarity of faces as a percentage and with a color designation of similarity thresholds.
Viewing the results of a task#
Viewing the results of a task is performed by pressing the button in the line (3 in the Figure 29). For viewing the *.ZIP archive for export tasks, the *.csv file for cross-matching tasks, the *.json file for batch processing, batch import and batch identification tasks (where * is the task ID) will be loaded.
The downloaded *.csv file contains a table with the export parameters selected in "Creating an export task" section (Figure 47) or with the results of cross-matching (Figure 48).
Task deleting#
Deleting a task is performed by clicking the button in the line (4 in the Figure 29).
In the pop-up window (Figure 49), you must confirm the action — click on the “Delete” button or cancel the action by clicking on the “Cancel” button. After the successful deletion, a corresponding notification appears.