“Tasks” section

The “Tasks” section contains two tabs:

• The “LUNA PLATFORM. Deferred tasks” tab (1) is intended for creating, deleting, and displaying tasks, downloading search results by events and persons. Export to a file is implemented in the Service in the form of a task;
• The “VL Timetracker. Time tracking. Generated Reports” tab (2) is intended for creating, displaying, and downloading reports on work activity for persons from the control list (for example, company employees).

General view of the “Tasks” section is shown in Figure 57.

Figure 57. “Tasks” section

“LUNA PLATFORM. Deferred tasks” tab

The “LUNA PLATFORM. Deferred tasks” tab contains the following elements:

• task counter (1);
• “Cross-matching” button — button for creating a task for cross-matching lists of faces;
• “Export” button — button for creating a task to export objects (events or faces) and information on them;
• “Batch processing” button — button for creating a task for batch processing of photo image archives according to a specific policy;
• “Batch import” button — button for creating a task for batch import of photo image archive into the list;
• “Batch identification” — 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” — button for creating a task for removing persons from the selected list;
• table of tasks:
• “ID” — task identifier;
• “Author” — 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;

• 
  

  Figure 59. Stop

— button to stop the task (appears if the task status is “In progress”); -

Figure 60. Download

— button for downloading the result of the task (3); -

Figure 57. Delete

— button for deleting a task (4); - 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 (5).

The status changes during the task execution. In total, 4 statuses are applied to tasks in the Service:

• 
  

  Figure 62. Process

— task is being performed; - “Collecting results” — collecting the results of the task; -

Figure 63. Done

— task completed; -

Figure 57. Error

— an error occurred while executing a task.

Creating a cross-matching task

To create a task for cross-matching lists of faces, click on the “Cross-matching” button (Figure 57). A general view of the form for creating a cross-matching task is shown in Figure 58.

Figure 65. Form for creating a cross-matching task

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.

Resource-intensive tasks can take a while. In the pop-up window (Figure 59), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.

Figure 66. Confirmation of the creation of a cross-matching task

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 60).

Figure 57. Confirmation of successful creation of a cross-matching task

Creating an export task

To create a task to export objects (events or faces) and information on them, click on the “Export” button (Figure 57). A general view of the form for creating an export task is shown in Figure 61.

Figure 68. Form for creating an export task

Description of the parameters of the “Export” form is given in Table 11.

Table 11.Export task parameters

Parameter	Description	Default value
Objects type	Faces;	Faces
	Events
Filters
List	Specifies the list for export (only for “Objects type — Faces”)	-
Source	Specifies the name of the event source (only for “Objects type — Events”)	-
User data	Indicates face data (up to 128 characters)	-
Age	Specifies age group (only for “Objects type — Events”)	-
Gender	Specifies female or male gender (only for “Objects type — Events”)	-
Emotions	Anger;	-
	Disgust;
	Fear;
	Happiness;
	Neutral;
	Sadness;
	Surprise.
	It’s possible to choose several values (only for “Objects type — Events”)
Medical mask	Detection of the presence/absence of a medical mask, mouth occlusion.	-
	Missing;
	Medical mask;
	Occluded.
	It’s possible to choose several values (only for “Objects type — Events”)
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	Specifies the values of the event identifiers in LUNA PLATFORM 5 in UUID format for performing an accurate search (only for “Objects type — Events”)	-
Comma-separated event external IDs	Specifies the values of third-party external identifiers (only for “Objects type — Events”)	-
Comma-separated Face IDs	Specifies the values of identifiers of faces in LUNA PLATFORM 5 in UUID format	-
Comma-separated face external IDs	Specifies the values of third-party external identifiers (only for “Objects type — Faces”)	-
Similarity	A value from 0 to 1 is specified (only for “Objects type — Events”)	-
Handling policies	Specifies policy name, it is possible to specify several values (only for “Objects type — Events”)	-
Comma-separated track IDs	Specifies the values of the track identifiers in LUNA PLATFORM 5 in the UUID format (only for “Objects type — Events”)	-
Comma-separated tags	Specifies a tag or tags (only for “Objects type — Events”)	-
Age by body image	Specifies the age range (only for “Objects type — Events”)	-
Gender by body image	Specifies the female, male or undefined gender (only for “Objects type — Events”)	-
Upper body colors	Specifies top clothing color (only for “Objects type — Events”)	-
Sleeve	Specifies sleeve length (only for “Objects type — Events”)	-
Headwear	Specifies headdress (only for “Objects type — Events”)	-
Headwear color	Specifies headdress color (only for “Objects type — Events”)	-
Backpack	Specifies backpack presence (only for “Objects type — Events”)	-
Lower body type	Specifies bottom clothing type (only for “Objects type — Events”)	-
Lower body colors	Specifies bottom clothing color (only for “Objects type — Events”)	-
Shoes color	Specifies shoe color (only for “Identify among events);
Location	Only for “Objects type — Events”
	“District”;
	“Area”;
	“City”;
	“Street”;
	“House number”;
	“Longitude (-180…180)”;
	“Accuracy (0…90)”;
	“Latitude (-90…90)”;
	“Accuracy (0…90)”
Columns	Selecting table columns to be included in the file upon export
	Face ID	On
	User data	On
	Time	On
	Lists (only for “Objects type — Faces”)	Off
	External ID	On
	Avatar (only for “Objects type — Faces”)	On
	Event ID	On
	Source (only for “Objects type — Events”)	On
	Handling Policy ID (only for “Objects type — Events”)	On
	Tags (only for “Objects type — Events”)	Off
	Track ID (only for “Objects type — Events”)	On
	Metadata (only for “Objects type — Events”)	Off
	Geo position (only for “Objects type — Events”)	On
	City (only for “Objects type — Events”)	On
	Area (only for “Objects type — Events”)	On
	District (only for “Objects type — Events”)	On
	Street (only for “Objects type — Events”)	On
	House number (only for “Objects type — Events”)	On
	Face detections (only for “Objects type — Events”)	Off
	Medical mask; (only for “Objects type — Events”)	On
	Emotion (only for “Objects type — Events”)	On
	Gender (only for “Objects type — Events”)	On
	Age (only for “Objects type — Events”)	On
	Liveness (only for “Objects type — Events”)	Off
	Matches (only for “Objects type — Events”)	Off
	Top match (only for “Objects type — Events”)	On
	List (only for “Objects type — Events”)	Off
	Body detections (only for “Objects type — Events”)	Off
	Body basic attributes (only for “Objects type — Events”)	Off
	Upper body (only for “Objects type — Events”)	Off
	Lower body (only for “Objects type — Events”)	Off
	Accessories (only for “Objects type — Events”)	Off
Delimiter	A special character that will be used in the file with export results to divide text into columns	,
Add images	Adding face images or face images from events	Off

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 62), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.

Figure 69. Confirmation of the creation of an export task

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 63).

Figure 57. Confirmation of successful creation of an export task

Creating a batch processing task

Available only to a user with the administrator role.

The batch processing task allows user to process several photos using a specified policy.

To create a task for batch processing of photo image archives according to a specific policy, click on the “Batch processing” button (Figure 57). The general view of the form for creating a batch processing task is shown in Figure 64.

Figure 71. Form for creating a batch processing task

By default the “Batch Processing” form contains the following elements:

• “Data source type” — selection of the source type of the loaded data;
• “Description” — description of the task;
• “Handling policy”* — selection of a policy (required);

The resource can accept five types of sources with images for processing:

• File;
• ZIP;
• S3;
• Network disk;
• FTP;
• Samba.

Additional options appear depending on the selected data source type.

To quickly download a ZIP archive from your local machine without additional options, select “File” as the data source type. Then upload or drag-and-drop the archive with photo images in the field for uploading data.

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 or body;
• 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”).

When choosing a ZIP archive as image source for the batch processing task, the following parameters can be set:

• “File URL”* — URL address of the archive with images, the default archive size is 100 GB;;
• “Archive password” — a password for the transferred archive protection;
• “Input image type” — selection of the type of image that is input in the batch processing task — "Raw image", "Face warped image", "Body warped image".

When choosing an S3-like storage as an image source for the batch processing task, the following parameters can be set:

• “Storage endpoint” — only when specifying the bucket name;
• “Bucket name”* — Access Point ARN / Outpost ARN;
• “File key prefix” — file key prefix. It can also be used to load images from a specific folder, such as "2022/January";
• “Bucket region” — only when specifying the bucket name;
• “Public access key”* — public key for setting up authorization;
• “Secret access key”* — secret key for setting up authorization;
• “Signature version” — signature "s3v2" / "s3v4";
• “Whether to estimate images from bucket subdirectories recursively?” — possibility to recursively download images from nested bucket folders;
• “Whether to save image origin?” — saving original images in the LUNA PLATFORM 5 database.

It is also possible to select the type of transferred images. For more information about working with S3-like repositories, see AWS User Guide.

When choosing a network disk as an image source for the batch processing task, the following parameters can be set:

• “Path to directory with images”* — absolute path to the directory with images in the container (required);
• “File key prefix” — a file key prefix that can be used to load images from a specific directory;
• “File key postfix” — file key postfix that can be used to upload images with a specific extension;
• “Whether follow file system links?” — enable/disable of symbolic links processing.

As in the batch processing task using S3-like storage as image source, it is possible to recursively receive images from nested directories, and to select the type of transferred images.

When choosing a FTP server as an image source for the batch processing task, the following parameters can be set:

• “Server host”* — FTP server IP address or hostname;
• “Port” — FTP server port;
• “FTP sessions” — maximum number of allowed sessions on the FTP server;
• “Server user” and “Server password” — authorization parameters.

* Required field

As in the batch processing task using network disk as image source, it is possible to set the path to the directory with images, recursively receive images from nested directories, select the type of transferred images, and specify the prefix and postfix.

When choosing a Samba as an image source for the batch processing task, the parameters are similar to those of an FTP server, except for the "max_sessions" parameter. Also, if authorization data is not specified, the connection to Samba will be performed as a guest.

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 65), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.

Figure 72. Confirmation of the creation of a batch processing task

After successfully creating a batch processing task, the message “Batch processing task has been successfully created” will appear in the upper right corner of the screen (Figure 66).

Figure 57. Confirmation of successful creation of a batch processing task

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 57). The general view of the form for creating a batch import task is shown in Figure 67.

Figure 73. Form for creating a batch import task

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.

Resource-intensive tasks can take a while. In the pop-up window (Figure 68), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.

Figure 74. Confirmation of the creation of a batch import task

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 69).

Figure 75. Confirmation of successful creation of a batch import task

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 57). The general view of the form for creating a batch identification task is shown in Figure 70.

Figure 77. Form for creating a batch identification task

The “Batch Identification” form contains the following elements:

• field for uploading an archive with photographs — it is possible to upload archives in *.ZIP format (required);
• — button for deleting the loaded archive;
• “Filters”.

The description of the parameters of the “Filters” block is presented in Table 12.

Table 12. “Filters” block parameters

Name	Description
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
Source (only for Events)	List of available event sources
Gender (only for Events)	Female;
	Male
Age (only for Events)	Age group:
	below 18;
	from 18 to 44;
	from 45 to 60;
	above 60
Emotion (only for Events)	Anger;
	Sadness;
	Neutral;
	Disgust;
	Fear;
	Happiness;
	Surprise.
	Its possibly to select multiple emotions.
Medical mask (only for Events)	Detection of the presence/absence of a medical mask or mouth occlusion.
	Missing;
	Medical mask;
	Occluded.
	Its possibly to select multiple variants.
Comma-separated event IDs (only for Events)	Event ID of detection and attribute retrieval
Comma-separated external event IDs (only for Events)	External event ID
Comma-separated Face IDs (only for Events)	Face ID from events that are created in LUNA PLATFORM 5 as a result of a detection event and attribute extraction
User data	Information linked to the person from the database
Comma-separated external face IDs (only for Faces)	External ID of persons face
Comma-separated Face IDs (only for Faces)	Face ID from the list
List (only for Faces)	List name
Similarity	The lower threshold on the similarity if the person was identified
Handling policies (only for Events)	Handling Policy ID
Comma-separated track IDs	Specifies the values of the track identifiers in LUNA PLATFORM 5 in the UUID format (only for “Objects type — Events”)
Comma-separated tags	Specifies a tag or tags (only for “Objects type — Events”)
Location (only for “Objects type — Events”)	“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

Figure 78. Plus

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.

Resource-intensive tasks can take a while. In the pop-up window (Figure 71), you must confirm the action — click on the “Ok” button or cancel the action by clicking on the “Cancel” button.

Figure 79. Confirmation of the creation of a batch identification task

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 72).

Figure 80. Confirmation of successful creation of a batch identification task

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 57). The general view of the window for creating a task for batch import is shown in the figure (Figure 73).

Figure 81. Window for creating a “Deleting faces from the list” task

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.

Resource-intensive tasks may take some time to complete. Confirm the action in the pop-up window (Figure 74)—click the “Ok” button or cancel the action using the “Cancel” button.

Figure 83. Confirmation of creating a “Deleting faces from the list” task

After successfully creating a task for removing persons from the list, the message “Cleanup task has been successfully created” appears on the screen (Figure 75).

Figure 81. Confirmation of successful creation of the “Deleting faces from the list” task

Stopping a task

The task can be stopped only when it is being executed; to do this, click on the

Figure 59. Stop

button (Figure 76, (1)).

A stopped task cannot be restarted or continued. The function of stopping the task execution is necessary in case the task turned out to be incorrectly formulated or not needed, so as not to waste resources on it.

Figure 81. Stopping the execution of a task

Confirm the action in the pop-up window (Figure 77)—click on the “Ok” button or cancel the action by clicking on the “Cancel” button.

Figure 83. Confirmation of stopping the execution of a task

Viewing the results of a task

Viewing the results of a task is performed by pressing the button

Figure 60. Download

in the line (Figure 57, (3)). 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 78) or with the results of cross-matching (Figure 79).

Export results table

Cross-matching results table

Task deleting

Deleting a task is performed by clicking the button in the line (Figure 57, (4)).

In the pop-up window (Figure 80), you must confirm the action — click on the “Delete” button or cancel the action by clicking on the “Cancel” button.

Confirmation of deletion of the task

“VL Timetracker. Time tracking. Reports” tab

The “VL Timetracker. Time tracking. Reports” tab is displayed in the interface only if there is a connection to the VL TimeTracker component (connection setup is described in the LUNA CLEMENTINE 2.0 administration manual).

In the “VL Timetracker. Time tracking. Reports” tab, you can create three types of reports:

• “Clock in” — the first recorded event per day for each person from the control list;
• “Clock out” — the last recorded event per day for each person from the control list;
• “Activity tracking” — the first and last recorded event per day for each person from the control list, number of events during working hours and number of working hours.

The general view of the “VL Timetracker. Time tracking. Reports” tab is shown in Figure 81.

The “VL Timetracker. Time tracking. Reports” tab

The “VL Timetracker. Time tracking. Reports” tab contains the following elements:

• task counter (1);
• “Clock in” button — button for creating clock in reports;
• “Clock out” button — button for creating clock out reports;
• “Activity tracking” button — button for creating reports on work activity;
• table of reports:
• “Author” — user who created the report;
• “Type” — report type (“Clock in”, “Clock out”, “Activity tracking”);
• “Policy name” — the name of the used policy;
• “Date” — date and time of report creation;
• “Status” — status of the report creation process;

• 
  

  Figure 60. Download

— button for downloading the report (2); - The number of reports 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 reports in total on one page (3).

In the process of creating a report, the status changes. In total, two statuses are applied to reports in the Service:

• — an error occurred while creating the report;

• 
  

  Ok

— the report has been created.

Creating a clock in report

To create a report on clock ins, click on the “Clock in” button (Figure 81).

The general view of the form for creating clock in report is shown in Figure 82.

Form for creating clock in report

“Clock in” form contains the following elements:

• “Handling policy”* — policy selection;
• “Creation date from”* — the lower limit of the period of creation of events in LP5;
• “Creation date to”* — the upper limit of the period of creation of events in LP5;
• “List”* — list selection;
• “Source”* — event source selection;
• “Medical mask” — specifies the detection of the presence/absence of a medical mask;
• “Create report” button — button for creating a report;
• “Reset” button — button for resetting the set parameters.

* Required field

Fill in all the required parameters and click on the “Create report” button.

After the successful formation of a request to create a report, the message “Report is being generated” will appear in the upper right corner of the screen (Figure 83).

Confirmation of the formation of a request to create a report

Creating a clock out report

To create a report on clock outs, click on the “Clock out” button (Figure 81).

The general view of the form for creating clock out report is shown in Figure 84.

Form for creating clock out report

“Clock out” form contains the following elements:

• “Handling policy”* — policy selection;
• “Creation date from”* — the lower limit of the period of creation of events in LP5;
• “Creation date to”* — the upper limit of the period of creation of events in LP5;
• “List”* — list selection;
• “Source”* — source selection;
• “Medical mask” — specifies the detection of the presence/absence of a medical mask;
• “Create report” button — button for creating a report;
• “Reset” button — button for resetting the set parameters.

* Required field

Fill in all the required parameters and click on the “Create report” button.

After the successful formation of a request to create a report, the message “Report is being generated” will appear in the upper right corner of the screen (Figure 83).

Creating a work activity report

To create a report on work activity, click on the “Activity tracking” button (Figure 81).

The general view of the form for creating work activity report is shown in Figure 85.

Form for creating work activity report

“Activity tracking” form contains the following elements:

• “Handling policy”* — policy selection;
• “Creation date from”* — the lower limit of the period of creation of events in LP5;
• “Creation date to”* — the upper limit of the period of creation of events in LP5;
• “List”* — list selection;
• “Source”* — source selection;
• “Number of clock ins” — minimum number of clock ins for a person;
• “Create report” button — button for creating a report;
• “Reset” button — button for resetting the set parameters.

* Required field

Fill in all the required parameters and click on the “Create report” button.

After the successful formation of a request to create a report, the message “Report is being generated” will appear in the upper right corner of the screen (Figure 83).

Viewing a report

Downloading and viewing the report is performed by pressing the

Figure 60. Download

button in the line (Figure 81, (2)). A *.csv file will be loaded (where * is the date and time of creation, the type of report).

The downloaded *.csv file contains a table with the results of the report creation (Figure 86).

Figure 1. Work activity report