v.5.112.0#
Changes
-
The resource
/sdk
has been extended to include image modification estimation —estimate_image_modification
(see the section Face Image Modification).The system will consider the image to have been modified if the received score (a value from 0 to 1) is below the set threshold.
The default threshold is 0.5 (50%).If necessary, the threshold value can be set in the
LUNA_REMOTE_SDK_IMAGE_MODIFICATION_ESTIMATOR_SETTINGS.estimator_settings.threshold
setting of the Remote SDK service.This functionality is disabled by default.
-
Now the Accounts service has been classified as optional and is regulated within the group of parameters "ADDITIONAL_SERVICE_USAGE".
If the Accounts service is disabled, the functionality for creating/updating/deleting accounts and tokens will be unavailable, and the response to the "get system info" request to the Admin service in the "services_versions" section will not display information about this service.
Important: To launch LUNA PLATFORM with the Accounts service disabled, you must specify a list of accounts and their tokens that can be used to authorize requests in the
CONFIG_AUTHORIZATION_USERS
setting. An account and its tokens can be created inside the Admin service container using thecreate_account
command. For more details, see Accounts service disabling consequences.Also, a new resource
/generator
has been added to the Accounts service, allowing you to generate accounts and their tokens in advance (before disabling the service - if the user needs it). This data can be saved in theCONFIG_AUTHORIZATION_USERS
setting for further use. -
In the Remote SDK service, the size of the image queue for processing has been limited. This prevents uncontrolled growth of RAM consumption, which previously occurred when the request execution time was exceeded and led to performance problems.
Fixed errors
-
Fixed a bug that caused the
match_result
field to be incorrectly formed in responses to matching requests ("matching faces", "human body matching", "general events matching") when using events as candidates.Now the
stream_id
field is correctly added to thematch_result
content (previously, the value "None" was always set for this field in responses). -
Fixed incorrect behavior when working with empty matching results.
Previously, if the
similarity__lte
filter was set for matching results in the handler policies (for example, in the policy "storage_policy" > "face_policy" > "filters" > "match" > "similarity__lte"), then if there were no matches, filtering was not performed, and accordingly, all actions that were supposed to be performed when checking this condition were not performed (for example, saving a face/event/attributes, etc.).Now, with empty matching results and the
similarity__lte
value, filtering is performed successfully, which corresponds to the logic of "no candidate is similar to the reference".Note: If the filter
similarity__gte
is set and an empty result is returned, filtering is not performed, since this does not meet the condition "there is at least one candidate similar to the reference".See request create handler.
-
Fixed an issue in the Remote SDK service that caused a hang when processing images.