👨🏿💻👩🏽💻🌈🪴 Want to join the AI Institute for Food Systems team and help lead AgML development? 🪴🌈👩🏼💻👨🏻💻
We're looking to hire a postdoc with both Python library development and ML experience. Send your resume and GitHub profile link to jmearles@ucdavis.edu!
Overview
AgML is a comprehensive library for agricultural machine learning. Currently, AgML provides access to a wealth of public agricultural datasets for common agricultural deep learning tasks.
AgML supports both the TensorFlow and PyTorch machine learning frameworks.
To browse our latest datasets, view our full set of documentation, and compare model performance on your crops / tasks of interest, please visit project-agml.github.io.
Installation
To install the latest release of AgML, run the following command:
pip install agml
Quick Start
AgML datasets are hosted on the Hugging Face Hub under the Project-AgML
organization. You can start off by using the HuggingFaceDataLoader to download and load a dataset directly into a
native Hugging Face DatasetDict:
from agml.data import HuggingFaceDataLoader
# Load a dataset from the Hub
loader = HuggingFaceDataLoader("Project-AgML/apple_flower_segmentation")
# Load a specific config/subset (e.g. an augmented variant)
loader = HuggingFaceDataLoader("Project-AgML/apple_flower_segmentation", config="augmented")
HuggingFaceDataLoader automatically casts image-like columns (image, mask, and image-typed label columns) to
the Hugging Face Image type for decoded pixel access.
You can split the dataset into train/val/test sets, with optional stratification across one or more columns:
dataset = loader.split(val_size=0.1, test_size=0.1, stratify_cols="label")
# Returns a DatasetDict with 'train', 'val', and 'test' splits
# Access the underlying DatasetDict at any time
dataset = loader.dataset
For any preprocessing, inference, or training beyond loading and splitting, use the
datasets and transformers
libraries directly. Since loader.dataset is a native Hugging Face DatasetDict, it works out of the box with
datasets' map, filter, and with_transform methods for preprocessing, and with transformers' Trainer,
Pipeline, and model classes for training and inference — there's no separate AgML-specific processing API to learn.
from transformers import AutoImageProcessor, AutoModelForImageClassification, Trainer
processor = AutoImageProcessor.from_pretrained("google/vit-base-patch16-224")
model = AutoModelForImageClassification.from_pretrained(
"google/vit-base-patch16-224",
num_labels=dataset["train"].features["label"].num_classes,
)
def preprocess(batch):
batch["pixel_values"] = processor(batch["image"], return_tensors="pt")["pixel_values"]
return batch
dataset = dataset.with_transform(preprocess)
trainer = Trainer(model=model, train_dataset=dataset["train"], eval_dataset=dataset["val"])
trainer.train()
Image-Text-to-Text Datasets
Some AgML datasets (e.g. Project-AgML/AgroOmni) are too large to fit the standard load_dataset()
archive handling, which fully extracts every archive to disk before reading it. These datasets instead store images
as raw relative paths inside zip shards, alongside a single shared path -> shard index, so no extraction step is
needed and no per-archive metadata has to be duplicated. Because of that, they aren't load_dataset()-compatible,
and are loaded with loadImageTextToTextDataset instead:
from agml import loadImageTextToTextDataset
# Whole dataset, split-aware:
ds = loadImageTextToTextDataset(
"Project-AgML/AgroOmni",
token=HF_TOKEN
)
ds["train"][0] # {'id', 'messages', 'raw_metadata', 'images': [PIL.Image, ...]}
# Single split:
train_ds = loadImageTextToTextDataset(
"Project-AgML/AgroOmni",
split="train",
token=HF_TOKEN
)
# Multi-config repo (each config under its own folder): pass `config` to select one.
ds = loadImageTextToTextDataset(
"Project-AgML/MIRAGE",
config="MMST_Standard",
token=HF_TOKEN,
)
loadImageTextToTextDataset(repo_id, config=None, split=None, cache_dir=None, token=None, cache_max_bytes=...) returns a DatasetDict
when split is omitted, or a single Dataset when a split name is given. Splits are auto-discovered from the
metadata parquet filenames (e.g. train-0000-of-0001.parquet becomes train), the same convention load_dataset()
itself uses; if no split can be inferred, every row is placed under a single train split. For repos with multiple
configs, each living under its own folder, config is required, if it's omitted the error message lists the
configs available in that repo.
Image bytes are only read the first time a row is actually accessed (ds["train"][0], a slice, or a batch), never
eagerly over the whole dataset, and repeated access to the same image is cached. The ImageTextToTextShardStore
backing that lazy decoding is attached to the returned dataset as ds.store, in case you want to inspect its cache,
call ds.store.getBytes(path) directly, or free its open shard file handles and cached bytes (ds.store.close()).
The cache is bounded by total size, 256 MiB by default; pass cache_max_bytes= to change it, or 0 to disable it.
If you're using this with a PyTorch DataLoader, prefer num_workers > 0. Each worker process opens its
own shard handles (and keeps its own byte cache), whether workers are forked or spawned.
Public Datasets
AgML contains a wide variety of public datasets from various locations across the world:
Use the Dataset Search experience for filtering and previews. For programmatic filtering,
agml.data.public_data_sources(...) supports task and modality filters.
iNatAg and iNatAg-mini
AgML provides an API with direct access to iNatAg (and iNatAg-mini), one of the world's largest collections of agricultural images dedicated for the task of image classification. Collectively, this dataset contains over 4 million images along with detailed species classificaations and enables access to a variety of large-scale agricultural machine learning tasks. You can instantiate the iNatAg (or iNatAg-mini, a smaller variant of iNatAg for smaller-scale applications) dataset as follows:
# To select a collection of scientific family names.
loader = agml.data.AgMLDataLoader.from_parent("iNatAg", filters={"family_name": ["...", "..."]})
# To select common names.
loader = agml.data.AgMLDataLoader.from_parent("iNatAg", filters={"common_name": "..."})
Usage Information
Using Public Agricultural Data
AgML aims to provide easy access to a range of existing public agricultural datasets The core of AgML's public data pipeline is
AgMLDataLoader. You can use the AgMLDataLoader or agml.data.download_public_dataset() to download
the dataset locally from which point it will be automatically loaded from the disk on future runs.
From this point, the data within the loader can be split into train/val/test sets, batched, have augmentations and transforms
applied, and be converted into a training-ready dataset (including batching, tensor conversion, and image formatting).
Annotation Formats
A core aim of AgML is to provide datasets in a standardized format, enabling the synthesizing of multiple datasets
into a single training pipeline. Datasets on the Hugging Face Hub encode annotations as columns on the underlying
Dataset/DatasetDict:
- Image Classification: a
labelcolumn of typeClassLabel. - Object Detection: an
objectscolumn, holding COCO-style bounding boxes (un-normlized [x_min, y_min, width, height]) and corresponding category IDs as a ClassLabel per image. - Semantic Segmentation: a
maskcolumn, a single-channel (L-mode) image the same size as the corresponding image.
Contributions
We welcome contributions! If you would like to contribute a new feature, fix an issue that you've noticed, or even just mention a bug or feature that you would like to see implemented, please don't hesitate to use the Issues tab to bring it to our attention.
See the contributing guidelines for more information, or the guide to contributing leaderboard results if you have benchmark results to add.
Funding
This project is partly funded by the National AI Institute for Food Systems.
Metadata
Release files for agml 0.8.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agml-0.8.2.tar.gz | 6.2 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agml-0.8.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.0 MB
Release files / agml-0.8.2.tar.gz
| Download URL | agml-0.8.2.tar.gz |
|---|---|
| Size | 6.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf40913e0852b702978106c40a8a4b0eccaaa0adf36651545e5556640e8a13a1
|
|
BLAKE2b-256 checksum How to use checksums |
2d07d3c5e57a1b921417d499a90e66ab9ba7ddbe98bdd31a89871a222fb21d25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / agml-0.8.2-py3-none-any.whl
| Download URL | agml-0.8.2-py3-none-any.whl |
|---|---|
| Size | 784.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7568a88e943411aced87f4b7244c6b3009470d82137c1d277ecf0e00221b4979
|
|
BLAKE2b-256 checksum How to use checksums |
8fb250dcdb3035d588686537cb40812e9be7a1dcadcffcb92d06e6ba8e5bc0a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.14 {"installer":{"name":"uv","version":"0.11.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for agml 0.8.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.