Skip to main content

AI-POWERED DOCS

What do you want to know?

Library

The Library is every capture the camera has kept, with the tool results attached. It is where you go when someone asks why a specific part failed, and where you collect evidence for a recipe change.

OV Spark Library screen with capture grid and detail pane

Find the capture​

Ask in plain language​

At the top is a search box: Ask the library, with the example "failed parts in the last hour". Describe what you want and it fills in the filters below.

It will not guess

If it cannot read your request it says so and changes nothing, rather than silently applying a filter you did not ask for. The filters it does set are visible underneath, so you can always see what it actually searched.

Or filter directly​

FilterUse it to
Capture IDJump to one exact capture, when support or a report gives you the ID
Trigger IDTrace back to a specific PLC trigger
Captured betweenNarrow to a shift or an incident, with 5m to 1d quick-sets
RecipeLimit to one product
JudgmentPass, Fail, Indeterminate or Unspecified
Trigger IDs repeat

The trigger counter resets when the camera restarts, so the same trigger ID can appear more than once. Use the capture ID when you need something genuinely unique.

Advanced filters adds per-tool filtering, and it only shows the tools the selected recipe actually contains. Depending on the recipe you get aligner score ranges, classifier class and confidence, segmentation blob and area ranges, or count ranges. That is how you find, for instance, every capture where the classifier passed but only barely.

The filters live in the URL

Copy the address bar and you have sent a colleague the exact view you are looking at, not a description of it.

Read a capture​

Selecting a capture opens the detail pane: the image with tool overlays, a Heatmap toggle, and the metadata that matters, being Recipe, Captured at, Processing time, Triggered by and Dimensions. Below that, each tool's result with its score and processing time, plus Notes and Annotations.

Do something with the results​

Select several captures and a toolbar appears:

ActionNotes
Pin / UnpinPinned captures are never deleted automatically
DownloadPlain, or Download with labels, as one ZIP
DeletePermanent, and it warns you if any selection is pinned

Keyboard navigation is quicker than clicking once you have more than a screenful: arrow keys move and flip pages at the edge, Shift with arrows selects a range, Enter toggles selection.

Storage runs at capacity by design

The camera deletes the oldest unpinned captures automatically as new ones arrive. That is normal operation, not a fault. If a capture matters, whether it is evidence for a customer complaint or a training example, pin it, because pinned captures are never deleted.

A practical habit​

When a defect escapes to the customer, or a good part gets rejected:

  1. Find the capture here
  2. Pin it, so it survives
  3. Add a note saying what actually happened
  4. Use it as training data or as a backtest case

Over a few weeks that gives you a real set of the failures your line actually produces, which is worth far more than a synthetic test set.

Who can do what​

Every role can browse and download. Operators can also pin, annotate and delete, which is deliberate: those are factory-floor actions that should not need an engineer.

Where to go next​