mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-12 23:02:28 +00:00
Move the public website pages into `docs/web` beside the SDK, with
shared navigation and executable example sources in `docs/web-tests`.
The combined website is assembled by
[lancedb/docs#355](https://github.com/lancedb/docs/pull/355), with six
Enterprise replacements from
[lancedb/sophon#7681](https://github.com/lancedb/sophon/pull/7681).
This includes Function guidance, runnable Quickstarts, regenerated
snippets, production contact/demo fixes, the legacy SQL route, and the
LeRobot redirect. LeRobot remains attributed to Geneva; all 34 Geneva
pages remain in the docs repository until Function officially launches.
Materialized-view guidance follows the full rebuild refresh introduced
by #4373: local refresh writes the complete result, has no `full`
argument, supports `source_version`, and no longer requires stable row
IDs. Deployment SQL refresh options and stable-ID setup are qualified by
version/configuration. Function input guidance distinguishes ordinary
stored columns from computed inputs supported by newer deployments.
**Validation:** independently accepted local checks include 95 Python
tests (real Enterprise excluded), eight TypeScript tests, Rust
Quickstart, snippet parity, typos, deterministic assembly, Mint
validation and links/anchors/redirects. The combined baseline retains
all 181 production routes and 17 legacy redirects. Examples ran locally
against source-built Python SDK 0.40.0b13; existing GitHub workflows do
not run `docs/web-tests`. New main at `069b2f7d` is 0.41.0b0 and adds
computed Function inputs; that SDK was not exercised by the accepted
tests. Latest prose corrections receive focused site validation.
**Merge/rollout:** merge this and #7681 before #355's combined CI, which
reads producer `main`. This is migration infrastructure: section
overlays, source-owned skills and automatic versioned paired releases
remain follow-ups. The current manual publisher is transitional. Hosted
validation, a supported SDK/Enterprise release pair and a real
Enterprise walkthrough remain pending.
Production Mintlify watches `lancedb/docs:deploy-freeze`, directory
`docs`; preserve that source through review. The separate SDK GitHub
Pages reference workflow rebuilds on main merges.
**Updated-head CI (9a50f8db):**
[Typos](https://github.com/lancedb/lancedb/actions/runs/37654185443/job/112904990558),
[PR
title](https://github.com/lancedb/lancedb/actions/runs/37654179507/job/112904974595)
and
[Aikido](https://app.aikido.dev/featurebranch/scan/215386145?groupId=74229)
pass. Critical findings in the example lockfiles were patched: all Sharp
copies use 0.35.5, protobufjs 7.6.6, tar 7.5.22, quinn-proto 0.11.19,
zerovec 0.11.8 and zerovec-derive 0.11.6. The SDK's product dependencies
are unchanged. The revised lockfiles pass eight TypeScript examples,
HuggingFace decode/resize/crop/rescale/normalize plus AVIF roundtrip,
and Rust Quickstart. Aikido passing does not mean every advisory is
cleared; npm still reports 29 high and five moderate advisories in the
example dependency graph. No scanner bypass or suppression was added.
The Function prose correction passes combined/standalone Mint,
deterministic assembly, routes and assets. The revised 325-file site
checksum is
`175bec06864abb400dd292e667ba93448c0479b8359fd7bf6146afabf9040647`. This
PR remains open for independent review; further merges are on hold.
---------
Co-authored-by: Brendan Clement <brendan.clement@lancedb.com>
213 lines
9.0 KiB
Plaintext
213 lines
9.0 KiB
Plaintext
---
|
|
title: "Voxel51"
|
|
sidebarTitle: "Voxel51"
|
|
---
|
|
|
|
import {
|
|
PyPlatformsVoxel51BackendFlag,
|
|
PyPlatformsVoxel51BackendParams,
|
|
PyPlatformsVoxel51BrainConfig,
|
|
PyPlatformsVoxel51Cleanup,
|
|
PyPlatformsVoxel51ComputeSimilarity,
|
|
PyPlatformsVoxel51LoadDataset,
|
|
PyPlatformsVoxel51SortBySimilarity,
|
|
} from '/snippets/integrations.mdx';
|
|
|
|
# FiftyOne
|
|
|
|
[FiftyOne](https://docs.voxel51.com/) is an open source toolkit that enables users to curate better data and build better models. It includes tools for data exploration, visualization, and management, as well as features for collaboration and sharing.
|
|
|
|
Any developers, data scientists, and researchers who work with computer vision and machine learning can use FiftyOne to improve the quality of their datasets and deliver insights about their models.
|
|
|
|

|
|
|
|
**FiftyOne** provides an API to create LanceDB tables and run similarity queries, both **programmatically in Python** and via **point-and-click in the App**.
|
|
|
|
Let's get started and see how to use **LanceDB** to create a **similarity index** on your FiftyOne datasets.
|
|
|
|
## Overview {#overview}
|
|
|
|
[Embeddings](/embedding/) are foundational to all of the **vector search** features. In FiftyOne, embeddings are managed by the [**FiftyOne Brain**](https://docs.voxel51.com/user_guide/brain.html) that provides powerful machine learning techniques designed to transform how you curate your data from an art into a measurable science.
|
|
|
|
> _Have you ever wanted to find the images most similar to an image in your dataset?_
|
|
|
|
The **FiftyOne Brain** makes computing **visual similarity** really easy. You can compute the similarity of samples in your dataset using an embedding model and store the results in the **brain key**.
|
|
You can then sort your samples by similarity or use this information to find potential duplicate images.
|
|
|
|
|
|
We'll be doing the following :
|
|
|
|
1. **Create Index** - In order to run similarity queries against our media, we need to **index** the data. We can do this via the `compute_similarity()` function.
|
|
- In the function, specify the **model** you want to use to generate the embedding vectors, and what **vector search engine** you want to use on the **backend** (here LanceDB).
|
|
<Tip>
|
|
You can also give the similarity index a name(`brain_key`), which is useful if you want to run vector searches against multiple indexes.
|
|
</Tip>
|
|
|
|
2. **Query** - Once you have generated your similarity index, you can query your dataset with `sort_by_similarity()`. The query can be any of the following:
|
|
|
|
- An ID (sample or patch)
|
|
- A query vector of same dimension as the index
|
|
- A list of IDs (samples or patches)
|
|
- A text prompt (search semantically)
|
|
|
|
## Prerequisites: install necessary dependencies {#prerequisites-install-necessary-dependencies}
|
|
|
|
1. **Create and activate a virtual environment**
|
|
|
|
Install virtualenv package and run the following command in your project directory.
|
|
<CodeBlock filename="bash" language="bash" icon="terminal">
|
|
python -m venv fiftyone_
|
|
</CodeBlock>
|
|
From inside the project directory run the following to activate the virtual environment.
|
|
|
|
<CodeGroup>
|
|
<CodeBlock filename="macOS/Linux" language="bash" icon="linux">
|
|
source fiftyone_/Scripts/activate
|
|
</CodeBlock>
|
|
<CodeBlock filename="Windows" language="bash" icon="windows">
|
|
fiftyone_/Scripts/activate
|
|
</CodeBlock>
|
|
</CodeGroup>
|
|
|
|
2. **Install the following packages in the virtual environment**
|
|
|
|
To install FiftyOne, ensure you have activated any virtual environment that you are using, then run
|
|
<CodeBlock filename="bash" language="bash" icon="terminal">
|
|
pip install fiftyone
|
|
</CodeBlock>
|
|
|
|
|
|
## Understand basic workflow {#understand-basic-workflow}
|
|
|
|
The basic workflow shown below uses LanceDB to create a similarity index on your FiftyOne datasets:
|
|
|
|
1. Load a dataset into FiftyOne.
|
|
|
|
2. Compute embedding vectors for samples or patches in your dataset, or select a model to use to generate embeddings.
|
|
|
|
3. Use the `compute_similarity()` method to generate a LanceDB table for the samples or object patches embeddings in a dataset by setting the parameter `backend="lancedb"` and specifying a `brain_key` of your choice.
|
|
|
|
4. Use this LanceDB table to query your data with `sort_by_similarity()`.
|
|
|
|
5. If desired, delete the table.
|
|
|
|
## Quick Example {#quick-example}
|
|
|
|
Let's jump on a quick example that demonstrates this workflow.
|
|
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51LoadDataset}
|
|
</CodeBlock>
|
|
Make sure you install torch ([guide here](https://pytorch.org/get-started/locally/)) before proceeding.
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51ComputeSimilarity}
|
|
</CodeBlock>
|
|
|
|
!!! note
|
|
Running the code above will download the clip model (2.6Gb)
|
|
|
|
Once the similarity index has been generated, we can query our data in FiftyOne by specifying the `brain_key`:
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51SortBySimilarity}
|
|
</CodeBlock>
|
|
|
|
The returned result are of type - `DatasetView`.
|
|
|
|
<Note>
|
|
`DatasetView` does not hold its contents in-memory. Views simply store the rule(s) that are applied to extract the content of interest from the underlying Dataset when the view is iterated/aggregated on.
|
|
|
|
This means, for example, that the contents of a `DatasetView` may change as the underlying Dataset is modified.
|
|
</Note>
|
|
|
|
> _Can you query a view instead of dataset?_
|
|
|
|
Yes, you can also query a view.
|
|
|
|
Performing a similarity search on a `DatasetView` will only return results from the view; if the view contains samples that were not included in the index, they will never be included in the result.
|
|
|
|
This means that you can index an entire Dataset once and then perform searches on subsets of the dataset by constructing views that contain the images of interest.
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51Cleanup}
|
|
</CodeBlock>
|
|
|
|
|
|
## Using LanceDB backend {#using-lancedb-backend}
|
|
By default, calling `compute_similarity()` or `sort_by_similarity()` will use an sklearn backend.
|
|
|
|
To use the LanceDB backend, simply set the optional `backend` parameter of `compute_similarity()` to `"lancedb"`:
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51BackendFlag}
|
|
</CodeBlock>
|
|
|
|
Alternatively, you can configure FiftyOne to use the LanceDB backend by setting the following environment variable.
|
|
|
|
In your terminal, set the environment variable using:
|
|
|
|
<CodeGroup>
|
|
<CodeBlock filename="macOS/Linux" language="bash" icon="linux">
|
|
export FIFTYONE_BRAIN_DEFAULT_SIMILARITY_BACKEND=lancedb
|
|
</CodeBlock>
|
|
|
|
<CodeBlock filename="Windows" language="powershell" icon="windows">
|
|
$Env:FIFTYONE_BRAIN_DEFAULT_SIMILARITY_BACKEND="lancedb" //powershell
|
|
|
|
set FIFTYONE_BRAIN_DEFAULT_SIMILARITY_BACKEND=lancedb //cmd
|
|
</CodeBlock>
|
|
</CodeGroup>
|
|
|
|
<Warning>
|
|
This will only run during the terminal session. Once terminal is closed, environment variable is deleted.
|
|
</Warning>
|
|
|
|
Alternatively, you can **permanently** configure FiftyOne to use the LanceDB backend creating a `brain_config.json` at `~/.fiftyone/brain_config.json`. The JSON file may contain any desired subset of config fields that you wish to customize.
|
|
|
|
```json
|
|
{
|
|
"default_similarity_backend": "lancedb"
|
|
}
|
|
```
|
|
This will override the default `brain_config` and will set it according to your customization. You can check the configuration by running the following code :
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51BrainConfig}
|
|
</CodeBlock>
|
|
|
|
## LanceDB config parameters {#lancedb-config-parameters}
|
|
|
|
The LanceDB backend supports query parameters that can be used to customize your similarity queries. These parameters include:
|
|
|
|
| Name | Purpose | Default |
|
|
| :------------- | :--------------------------------------------------------------------------------------------------------------- | :--------------- |
|
|
| **table_name** | The name of the LanceDB table to use. If none is provided, a new table will be created | `None` |
|
|
| **metric** | The embedding distance metric to use when creating a new table. The supported values are ("cosine", "euclidean") | `"cosine"` |
|
|
| **uri** | The database URI to use. In this Database URI, tables will be created. | `"/tmp/lancedb"` |
|
|
|
|
There are two ways to specify/customize the parameters:
|
|
|
|
1. **Using `brain_config.json` file**
|
|
|
|
```json
|
|
{
|
|
"similarity_backends": {
|
|
"lancedb": {
|
|
"table_name": "your-table",
|
|
"metric": "euclidean",
|
|
"uri": "/tmp/lancedb"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
2. **Directly passing to `compute_similarity()` to configure a specific new index** :
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsVoxel51BackendParams}
|
|
</CodeBlock>
|
|
|
|
For a much more in depth walkthrough of the integration, visit the LanceDB x Voxel51 [docs page](https://docs.voxel51.com/integrations/lancedb.html).
|