October DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsSlow PC?RecommendedPC slow today? Run a repair scan before it gets worseResolve common Windows issues and optimize system performance.Scan NowOctober DealsAmazon USDeal season is back - check today's better picksAmazon US: current deals, useful picks and tech finds.See Picks×
Skip to content
World desk2 min

How CVAT Fixed Numeric Range Validation in Auto-Annotation

CVAT 2.35.0 documents a numeric range-validation correction for Nuclio outputs in whole-task and per-frame auto-annotation. The step rule checks increments relative to the configured minimum.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

CVAT’s numeric range-validation correction is documented in CVAT 2.35.0, released on April 29, 2025. It covers numeric outputs from Nuclio detector functions in both whole-task auto-annotation and per-frame interactive auto-annotation. The key step rule is that a value must be checked relative to the configured minimum: (value - min) % step = 0, not simply value % step = 0.

What was wrong with range validation?

CVAT pull request #9285 addressed how detector results are converted and validated when Nuclio functions return numeric attributes. The pull request describes duplicated conversion logic between whole-task server-side annotation and per-frame annotation. Its change moved most of that conversion work to shared server-side handling for both request paths.

As an Amazon Associate I earn from qualifying purchases.

During review, CVAT contributor bsekachev pointed out that the interactive request path had lost min, max, and step validation: the server was only checking whether a value was numeric. The pull-request author said range checking was added to server validation and corrected the step test.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How should the numeric step rule work?

A configured step defines valid increments starting from the minimum. Therefore, a value is on the permitted step grid when subtracting the minimum leaves a multiple of the step:

(value - min) % step = 0

Checking only whether the value itself is divisible by the step can reject valid values when the minimum is not a multiple of the step. For example, with a minimum of 3 and a step of 2, the valid sequence is 3, 5, 7, and so on. The value 5 is valid even though 5 is not divisible by 2; its offset from the minimum is.

This explains the specific step-checking correction described by the pull-request author. It should not be read as a broader statement about decimal precision or validation behavior for every CVAT attribute type.

Which auto-annotation flows does the correction cover?

Flow What the release notes establish
Whole-task auto-annotation Nuclio numeric outputs are checked against their acceptable range.
Per-frame interactive auto-annotation Range validation works when the configured minimum is not a multiple of the step.

These are two affected request paths, not alternative products. The shared server-side conversion described in pull request #9285 was intended to avoid maintaining separate detector-output conversion behavior for batch and interactive requests.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Which CVAT version includes the documented fix?

The official CVAT changelog records the changes under version 2.35.0, dated April 29, 2025. That release entry is evidence for inclusion in 2.35.0; it does not establish behavior in every later release. The pull request was developed against the develop branch, so the release note is the clearer version reference for users.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What testing was reported?

The pull-request author reported manual testing with three Nuclio functions: openvino-omz-intel-face-detection-0205, openvino-omz-public-mask-rcnn-inception-resnet-v2-atrous-coco, and pth-mmpose-hrnet32. This is the author’s account of project testing, not an independent reproduction or a guarantee for every detector function or deployment.

Rank #4
Sale
Computer Vision
  • Used Book in Good Condition

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

More from the Wire

  1. World desk4 min
    How to Spot an AI Voice Scam Before Sending MoneyDon’t rely on how a caller sounds. Pause, call back through a known number, and verify the emergency with another trusted person before sending money.
  2. Mountain View desk4 min
    Google’s SynthID Detector: How to Check AI-Generated Images, Video and AudioGoogle’s SynthID Detector looks for an embedded watermark in supported images, video and audio. Here is what its results do—and do not—show.
  3. Redmond desk20 min
    How to create a link to File or Folder in Windows 11Windows 11 gives you several ways to point to a file or folder without moving or duplicating it. You can create a desktop shortcut,…
Recommended PC Tool
Recommended PC Tool
PC Slower Than It Used to Be?Free scan - under a minute
Outdated Drivers Are Slowing You DownFree scan - exact matches

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.