Skip to content

LUNA PLATFORM v.5.26.0#

Changes#

  • SDK was updated to version 5.8.0.

  • The mask state estimation was updated. In addition to the three main states, the following additional properties are now estimated:

    • "correct" - there is mask on the face, the mouth and nose are occluded by the mask
    • "mouth" - there is mask on the face that occludes only the mouth
    • "clear" - there is no mask on the face
    • "chin" - there is mask on the face and is located under the chin, without occluding the area from eyes to mouth
    • "partially" - the face is partially occluded, but not by medical mask and not by mask with full face occlusion
    • "full" - there is mask on the face, in which the face is completely occluded, for example, balaclava/ski mask

    Each basic mask state corresponds to one of two properties. The most likely property is returned in the "predominant_occlusion" field:

    • "medical_mask" state corresponds to the "correct" or "mouth" property
    • "missing" state corresponds to the "clear" or "chin" property
    • "occluded" state corresponds to the "partially" or "full" property

    For each of the properties, a probabilistic score is returned in the range [0..1].

    Additional mask properties are not saved to the database and no filtering is performed on them.

    Note: The presence of the chin mask from this version refers to the "missing" state. In previous versions, it referred to the "medical_mask" state. Additional properties are returned when estimating mask states in the "sdk" and "detect faces" resources, as well as when creating events ("save event" and "generate events" requests) and performing verification ("perform verification" request). Additional mask properties are also taken into account when sending events via web sockets ("ws handshake" request).

    Example of estimating the updated mask state in the "/sdk" resource:

    "mask": { "predominant_mask": "occluded", "estimations": {}, "face_occlusion": { "predominant_occlusion": "correct", "estimations": { "full": 0.019, "clear": 0.02, "correct": 0.6108324766, "partially": 0.31, "mouth": 0.0209, "chin": 0.019097 } } },

  • The body attribute columns "apparent_gender", "apparent_age", "headwear_state", "sleeve length", "upper_clothing_colors" and "backpack_state" were added to the report structure in CSV format (see "reporter" and "exporter task" tasks).

  • For the "num_threads" parameters from the "LUNA_HANDLERS_HUMAN_EXTRACTOR_RUNTIME_SETTINGS", "LUNA_HANDLERS_WARP_ESTIMATOR_RUNTIME_SETTINGS", "LUNA_HANDLERS_EXTRACTOR_RUNTIME_SETTINGS", "LUNA_HANDLERS_DETECTOR_RUNTIME_SETTINGS" and "LUNA_HANDLERS_HUMAN_DETECTOR_RUNTIME_SETTINGS" settings, the default value was changed from 4 to 6. This change improves the default performance for servers with a large number of CPU cores.

Fixed errors#

  • The error was fixed in which in tasks it was possible to set empty values for the filters "handler_ids", "masks", "face_ids", etc., which led to filtering by all relevant objects.

  • The absence of the error when entering an incorrect login/password in the Admin service user interface was fixed.

  • Now, in the absence of the licensed feature, the name of the missing feature is displayed in the Licenses service logs.