Skip to content

LUNA PLATFORM v.5.67.0#

LP changes

  • The ability to perform video analytics on GPU has been added.

    GPU is enabled by specifying "gpu" in the "decoder_device_class" setting of the "LUNA_REMOTE_SDK_VIDEO_SETTINGS" section.

  • SDK has been updated to version 5.21.0.

    In this version LUNA PLATFORM:

    • HumanDetector has been updated to version v6.
    • DeepFakeDetector has been updated to v3.

    Important: The default threshold for redetection of FaceDetV3 detector has been updated from "0.3" to "0.5". When LUNA PLATFORM is updated, the threshold for redetection in the "redetect_score_threshold" setting of the "LUNA_REMOTE_SDK_FACE_DETECTOR_SETTINGS" section will not be updated automatically. You must manually update the threshold to "0.5" to use the default redetection logic. If a custom value was previously set, you must update the threshold value yourself.

    When installing LUNA PLATFORM from scratch, the "redetect_score_threshold" value will also default to "0.3". It is necessary to use the dump file "platform_settings.json" from the distribution package, or update the threshold value after installation. In the next release, when installing from scratch, the value will be automatically set to "0.5".

  • A mechanism for specifying trusted detections has been added, enabling you to explicitly specify which detections do not need to be redetected.

    It is assumed that trusted detections were obtained using VisionLabs algorithms. Marking a third-party detection as trusted may affect the evaluation results.

    You can indicate whether the detection is trusted using the "application/json" scheme (the "trusted_detections" parameter) or the "multipart/form-data" scheme (the "X-Luna-Trusted-Detections" header) in the following requests, where detections are explicitly specified instead of images:

  • In the "generate stream events (beta)" request with specifying the source image (sources > source_type > raw_image) an optional field origin_bounding_box has been added, enabling to specify the coordinates of a bbox with a face or body in the coordinate system of the source image, which will be saved in the generated event.

    Thus in the request you can specify both bbox coordinates in the Crop image coordinate system (bounding_box parameter) and bbox coordinates in the source image coordinate system (origin_bounding_box parameter).

    Also, the parameter sources > source > face/body > bounding_box, available when specifying detections in a request (sources > source_type > detections), has been renamed to origin_bounding_box.

  • The support for setting the DROI relative to the source frame has been added.

    DROI specifies a region of interest relative to the source frame. DROI, unlike ROI, is not an estimation parameter, but works as a filter after estimation has been performed in accordance with the "targets" field. In other words, ROI is for estimation and optimization, DROI is for implementing business logic. You can use DROI together with ROI or separately. For example, if after execution the estimate taking into account the ROI of the number of people in the frame was equal to M, then after performing an additional filter on the DROI area, the number of people in the frame can be reduced to N.

    The DROI on the source frame is specified by the following parameters:

    • "area" — Geometry of the region of interest. The parameter is represented as an array of polygons. Each polygon is represented by an array of objects, where each object contains the x and y coordinates of the polygon's vertex. For example, you can define a triangular area of interest.
    • "mode" – mode of specifying “x”, “y”. Two modes are available:
      • "abs" — Parameters "x", "y", "width" and "height" are set in pixels.
      • "percent" — Parameters "x", "y", "width" and "height" are set as percentages of the current frame size.
    • "form" — Format of the region of interest. In the current implementation there is only one possible value, "common". Future implementations will support other formats in addition to polygons.

  • The ability to set the time to live of task results has been added to all tasks.

    TTL is set in result_storage_policy > ttl parameter in task or schedule creation requests.

    It is not possible to add TTL of task results to already created and executed tasks.

    You can add the TTL of task results to an already created schedule by using the "replace tasks schedule" request. TTL of task results will not be applied to tasks created or running at the time of the request.

  • Added automatic sending of the header Set-Cookie: LUNA_AUTH_TOKEN=""; Path=/; Max-Age=0 to the client application when it receives a 401 error from the API service due to a rotten authorization token placed in the Cookie.

LP fixed errors