Object attribute display order problem.

Answered

Follow

Jason Shim

• April 20, 2022 00:24

We distinguish a person's top and bottom colors and transmit(using addAttribute method) them as metadata. In version 4.2, the metadata is displayed in the order it is sent, so in VMS, the top color is displayed above and the bottom color is displayed below.

In version 5.0 beta, the metadata is sorted alphabetically. We did some experiments, and we confirmed this. The problem is that when you sort alphabetically, the bottom color is displayed at the top and the top color is displayed at the bottom. This is contrary to human cognitive habits. There are also plans to send detailed characteristics of the detected object as metadata. We plan to write the main attributes first and the detailed attributes later. For example, Gender: Male, Top: white, Bottom: black, Hair: blonde, Sunglasses: no, Mask: on. If you sort this in alphabetical order, it will look ridiculous like Bottom: black, Gender: Male, Hair: blonde, Mask: on, Top: white, Sunglasses: no .

0

• 

  Sergey Yuldashev

  • April 20, 2022 15:46

  Hi Jason,

  I have requested our UI/UX team the info about this behavior change.
  To me personally that does look like a bug though.

  I will update you with some news shortly.

  JIRA-VMS-30459

  0

  Comment actions Permalink
• 

  Sergey Yuldashev

  • April 20, 2022 15:57

  By any chance, could you also provide us with the screenshots from 4.2 and 5.0 server receiving the same metadata sample where this behavior change is noticeable? As well as the JSON sample.

  Thank you in advance.

  0

  Comment actions Permalink
• 

  Jason Shim

  • April 21, 2022 22:24

  Hi Sergey,

  I'm actually use following order code to add attributes.

  auto attr = nx::sdk::makePtr<nx::sdk::Attribute>(nx::sdk::IAttribute::Type::string, "top color", topcolo);
  objectMetadata->addAttribute(attr);
  auto attr = nx::sdk::makePtr<nx::sdk::Attribute>(nx::sdk::IAttribute::Type::string, "bottom color", btmcolor);
  objectMetadata->addAttribute(attr);

  And I got different results depending on VMS version.

  Version:4.2.0.32842

  

   

  Version:5.0.0.34326

  

  I put attributes in the order with the intension. As you can see, the result in VMS 5.0 can cause confusion.

  0

  Comment actions Permalink
• 

  Sergey Yuldashev

  • April 25, 2022 14:08

  Hi Jason,

  Thank you for the provided details.
  I managed to replicate the issue in the lab.

  It will be fixed before the 5.0 release. Please follow the patch notes.

  0

  Comment actions Permalink
• 

  Andrey Terentyev

  • June 02, 2022 10:56

  The issue has been fixed.

  0

  Comment actions Permalink

Please sign in to leave a comment.