Skip to content

LUNA PLATFORM v.5.38.3#

Changes

  • SDK was updated to version 5.13.0. Major SDK changes affecting LUNA PLATFORM:

    • updated body detector
    • updated FishEye estimator

    The default value of the score_threshold setting in the "LUNA_HANDLERS_BODY_DETECTOR_SETTINGS" section of the Handlers service settings was changed from 0.3 to 0.5 . Migrating settings automatically update this value (see the section "Configurator database migration" in the upgrade manual). Check the body recognition logic if you use a score_threshold value other than the default value.

    The default value of the redetect_face_target_size setting in the "LUNA_HANDLERS_FACE_DETECTOR_SETTINGS" section of the Handlers service settings was changed from 45 to 64 . Migrating the settings will automatically update this value (see the section "Configurator database migration" in the upgrade manual). Check the face recognition logic if you use a value redetect_face_target_size other than the default value.

  • Now, during the initial license check, only the license expiration time is checked, instead of all license checks. The remaining checks are now performed when the Licenses service receives requests.

    This change speeds up the loading of the Licenses service.

Fixed errors

  • The missing description for the msgpack format was added to the OpenAPI specification in the matching requests "matching faces" and "matching bodies".

  • The error was fixed, in which not all date and time formats were read in the monitoring. If an unintended format was transferred, then a reading error occurred.

    Now the ability to read all date formats from the Influxdb was added.

  • The Accounts service error was fixed, in which some errors related to processing requests to the Accounts database were not processed properly and were not output to the service logs.

  • The error was fixed where some data could be missing from tasks when the parameter tasks_to_faces_requests_concurrency of the Tasks service was set to 1.

  • If the matching request contains the value of the target field, which the plugin does not support, the service adds a key value for the target field to the request (face_id for matching by faces and event_id for matching by events).

    Previously, the plugin did not support the face_id or event_id field as the value of the target field and the request could fail or return an empty list of candidates. Now the Python Matcher Proxy service will not redirect such requests to the matching plugin.

    For more information, see the section "Matching targets" in the administrator manual.