Release 1.17
  • 14 May 2024
  • 3 Minutes to read
  • Dark
    Light
  • PDF

Release 1.17

  • Dark
    Light
  • PDF

Article Summary

Release 1.17.140 (Maintenance release) - May 14,  2024

  1. Sequence search improvements 
    1. Frames per sequence increased from 10 to 30.
    2. Improved search procedure to provide better accuracy.
  2. Autolabel quality improvements.
  3. Support for Union Views for the following use case
    1. Suppose an image has 5 ground truths and 6 predictions that have been imported into 2 different tables, namely gt_tbl and pred_tbl.
    2. To visualize the ground truths and predictions, the above tables must be joined with a pipeline primary table. A view with (primary JOIN gt_tbl JOIN pred_tbl) will result in a view with 5x6 = 30 rows which is not the intent here.
    3. A Union View allows specifying a view that is (primary JOIN gt_tbl) UNION ALL (primary JOIN pred_tbl) that appends the rows of the first JOIN to the rows from the second JOIN resulting in 5+6 = 11 rows as intended.
  4. Support PyTorch-YOLO as an additional format in import catalog operation.

Release 1.17.118 (Bugfix release) - April 25,  2024

  1. Fix a bug where text search was not enabled on a job.
  2. Fix a bug where fetching details for a catalog view with an external catalog table fails.

Release 1.17.116 - April 24,  2024

  1. Visual catalog: Visual mode as an additional mode of presentation for catalog results


  2. Autolabel enhancements: Over the base feature described in Release 1.16, this release brings in the following enhancements.
    1. Labeling Spec enhancements
      1. Choose a spec-wide weightage for text prompts versus image prompts(samples).
      2. Override the spec-wide weightage for text prompts with a different value specific to a class.
      3. Organize the classes based on their approval status into different tabs for easier navigation and focus.
      4. Have a separate display name field different from the class name. The display name is an alias used for display purposes, and a typical scenario for usage is described below.
        1. Suppose speed20 refers to a class for speed signs of 20mph in your dataset.
        2. 'Speed sign 20' is better interpreted by LLM than speed20, so the class name for this case must be set to 'speed sign 20' while the display name must be set to 'speed20'.
      5. Up to 5 extra prompts describing the class's visual characteristics can be selected to convey additional information to the autolabel models and improve accuracy.
      6. Collapsed mode for each class to improve navigation and focus on one class at a time.
    2. Additional ways to provide image samples
      1. Picking from images uploaded to an image repository.
      2. Through text search
    3. Additional job submit parameters to tune autolabel behaviour
      1. A job description field to capture more descriptive information on the purpose of the job. This is commonly available for all jobs.
      2. Autolabelling a coreset sampled subset for quick experimentation runs.
      3. Nested object detection and automatic removal parameters
    4. Additional filtering and grouping fields in the labeling statistics panel.
    5. Accept/Reject single annotation in addition to bulk actions.
    6. Download the autolabel resultset in COCO format in addition to JSON.
  3. Other enhancements
    1. Apply a resultset filter on catalog query output enabling creating a new job with points in a resultset or some subset of points in a resultset
    2. The following additional formats are supported for Import catalog operation.
      1. Yolo Darknet
      2. Yolo V8(Ultralytics)
    3. Single button creation of (train, valid, test) splits within a job.
    4. Improved user experience on full-resolution image view, with the ability to navigate through all images in context, pagination, and lower latency due to pre-fetching of all images on a page.
    5. Verbose mode for thumbnails in a job that shows key information inline below the thumbnail
    6. Improved score calibration for text search results. In previous releases, the good Vs. bad results did not have discriminative scores due to underlying model behavior.
    7. Public dataset import enhancements
      1. 1 public dataset imported automatically for a new account signup.
      2. Jobs created with text search support
    8. Catalog view edit support to add new tables, add virtual columns etc.
    9. An additional description field is added to the resultset and jobs to capture more descriptive information that can be used for search.
    10. Basic support for DICOM format files.

Notes

  1. In 'Visual search', the 'Quick Search' option has been removed, and the 'full object' search is defaulted.

Was this article helpful?

What's Next