fruitloops
Agent-friendly CLI for offline-first olfactory connectome queries across hemibrain and FlyWire.
The repository keeps generated CSV products in a predictable layout:
data/
manifest.csv
hemibrain/
flywire/
comparison/
Quick Use
Choose one install method.
Install with Homebrew:
brew tap gumadeiras/tap
brew install fruitloops
Install from PyPI:
python -m pip install fruitloops
Both installs include:
- the generated CSV snapshot for
status,table,find, andpartners - Python dependencies for local CSV queries, bulk imports, live access, and plotting
Nothing else is required for local snapshot queries:
fruitloops status
fruitloops table --flywire --contains summary --csv
Run setup when you want the larger local offline stores and derived olfaction tables:
fruitloops setup
For the best labels/glomerulus coverage, fetch live annotations while setting up. This requires neuPrint/FlyWire tokens:
export NEUPRINT_AUTH_TOKEN=...
export CAVE_AUTH_TOKEN=...
fruitloops setup --cache-annotations
Setup is offline-first. Hemibrain compact adjacencies do not include most ORNs,
so hemibrain setup also builds the ORN->PN and annotation tables from the
pinned neuPrint neo4j bundle, without tokens. It reads about 750 MB of the
bundle by HTTP range requests. It also downloads the pinned hemibrain
transmitter predictions (46 MB) that neurons, paths, and reach use for
signs.
Run directly from the repository:
python -m fruitloops status
python -m fruitloops olf glomerulus DM1 --flywire --csv
python -m fruitloops olf inputs --target-class PN --source-class ORN --glomerulus DM1 --by-side --csv
python -m fruitloops table --flywire --contains summary --csv
python -m fruitloops table flywire:analysis_outputs/full_summary --head
python -m fruitloops table comparison:matched_ln_class_similarity --contains LN_class=il3LN6 --json
python -m fruitloops find il3LN6 --flywire --json
python -m fruitloops partners il3LN6 --flywire --orn --csv
python -m fruitloops examples
For editable installation:
python -m pip install -e .
fruitloops status
fruitloops setup
Fruitloops does not depend on the current working directory. Inspect the active paths with:
fruitloops status
Full install/setup details, flags, credentials, paths, bulk imports, and live cache behavior are documented in docs/setup.md.
Persistent bulk data and DuckDB state use the OS application-data directory;
disposable live-query results use the OS cache directory. fruitloops status
prints the active paths.
Table References
Tables can be referenced as:
dataset:relative/path/without_csvdataset:collection/file_stemfile_idfromdata/manifest.csv
Examples:
fruitloops table flywire:analysis_outputs/full_summary --schema --csv
fruitloops table hemibrain:analysis_outputs/full_summary --select bodyId,LN_type,input_preference
fruitloops table flywire:source_audit/ln_observations_by_hemisphere --where LN_type=il3LN6
fruitloops table flywire:source_audit/orn_partner_counts_by_hemisphere --where LN_type=il3LN6 --csv
fruitloops table comparison:matched_ln_class_similarity --path
Common Agent Queries
After fruitloops setup, use fruitloops olf for broad olfaction questions:
fruitloops olf classes --flywire --region AL --csv
fruitloops olf glomerulus DM1 --flywire --csv
fruitloops olf pns --glomerulus DM1 --hemibrain --csv
fruitloops olf inputs --target-class PN --source-class ORN --glomerulus DM1 --by-side --flywire --csv
fruitloops olf outputs --source-class PN --target-class KC --region MB --flywire --csv
fruitloops olf pathway ORN LN --region AL --flywire --csv
fruitloops olf pathway PN KC --region MB --flywire --csv
Usable olf vocabulary:
- Datasets:
--flywire,--hemibrain, or--dataset flywire|hemibrain - Regions:
AL,LH,MB - Neuron classes:
ORN,PN,LN,LHN,KC,MBON,APL,DAN - Formats:
--csv,--json,--jsonl, or--format table|csv|json|jsonl - Side breakdown:
--by-side - Body ids:
--pre-id,--post-id,--source-id,--target-id
Discover values present in the current store:
fruitloops olf classes --csv
fruitloops olf glomerulus --flywire --limit 1000 --csv
fruitloops olf glomerulus --hemibrain --limit 1000 --csv
fruitloops olf tables --csv
Full local stores typically expose roughly 60-80 glomerulus labels per dataset, depending on imported annotations and whether hemibrain ORN->PN edges have been cached.
Command shapes:
fruitloops olf neurons --class ORN --region AL --glomerulus DM1 --flywire --csv
fruitloops olf classes --region AL --flywire --csv
fruitloops olf glomerulus DM1 --flywire --csv
fruitloops olf pathway ORN PN --source-glomerulus DM1 --target-glomerulus DM1 --by-side --flywire --csv
fruitloops olf inputs --target-class PN --source-class ORN --glomerulus DM1 --by-side --flywire --csv
fruitloops olf outputs --source-class PN --target-class KC --region MB --by-side --flywire --csv
fruitloops olf edges --region AL --pre-id 720575940623636701 --min-synapses 5 --flywire --csv
fruitloops olf pns --glomerulus DM1 --hemibrain --csv
fruitloops olf orn-inputs --glomerulus DM1 --by-side --flywire --csv
Hemibrain compact adjacencies only include traced neurons, so most hemibrain ORNs are absent from the compact cache. Setup caches the full hemibrain ORN->PN edges from the neo4j bundle. To refresh them offline from the bundle, or live from neuPrint with a token:
fruitloops olf cache-annotations --hemibrain --source neo4j-inputs --csv
fruitloops olf cache-annotations --hemibrain --csv
Question recipes:
# Which PNs exist for one glomerulus?
fruitloops olf pns --flywire --glomerulus DA2 --csv
fruitloops olf pns --hemibrain --glomerulus DA2 --csv
# Which lateral horn neurons receive direct DA2 PN input?
fruitloops olf outputs --flywire --source-class PN --target-class LHN --glomerulus DA2 --region LH --by-side --csv
fruitloops olf outputs --hemibrain --source-class PN --target-class LHN --glomerulus DA2 --region LH --by-side --csv
# Which mushroom body neurons receive direct DA2 PN input?
fruitloops olf outputs --flywire --source-class PN --target-class KC --glomerulus DA2 --region MB --by-side --csv
fruitloops olf outputs --hemibrain --source-class PN --target-class KC --glomerulus DA2 --region MB --by-side --csv
# Same DA2 PN target search, without requiring target class annotations.
fruitloops olf outputs --flywire --source-class PN --glomerulus DA2 --region LH --by-side --csv
fruitloops olf outputs --flywire --source-class PN --glomerulus DA2 --region MB --by-side --csv
Use table aggregation when you need legacy generated CSV products:
fruitloops table flywire:source_audit/orn_partner_counts_by_hemisphere \
--where LN_type=il3LN6 \
--by LN_type,analysis_hemisphere,input_relation \
--sum n_synapses \
--csv
Specialized LN partner summaries are still available:
fruitloops partners il3LN6 --flywire --orn --csv
fruitloops partners il3LN6 --flywire --pn --csv
fruitloops partners il3LN6 --hemibrain --orn --csv
fruitloops partners il3LN6 --hemibrain --pn --csv
Pull the reconciled hemibrain/FlyWire comparison:
fruitloops table comparison:matched_ln_class_similarity --contains LN_class=il3LN6 --json
Useful LN workflow:
fruitloops find il3LN6 --csv
fruitloops table flywire:source_audit/ln_observations_by_hemisphere --where LN_type=il3LN6 --csv
fruitloops table flywire:source_audit/orn_partner_counts_by_hemisphere \
--where LN_type=il3LN6 \
--by analysis_hemisphere,input_relation \
--sum n_synapses \
--csv
fruitloops table comparison:matched_ln_class_similarity --contains LN_class=il3LN6 --jsonl
Legacy commands such as datasets, files, schema, head, query,
aggregate, and ln remain available for scripts. New interactive use should
prefer status, setup, olf, neurons, paths, reach, table, find,
partners, and examples.
Whole-Brain Paths and Reach
After fruitloops setup, neurons, paths, and reach query the whole
FlyWire v783 and hemibrain v1.2 graphs offline:
fruitloops neurons --flywire --type DNa02 --csv
fruitloops paths --flywire --source-class ALPN --target-type DNa02 --orn-family orco --via LH --top 1 --csv
fruitloops reach --flywire --source-class ALPN --target-super-class descending --orn-family orco --hops 2 --by-side --csv
fruitloops paths --hemibrain --source-type '*_*PN*' --target-type DNa02 --max-hops 2 --top 3 --csv
fruitloops paths --flywire --source-type DL5_adPN --target-type DNa02,DNa03 --by-type --max-hops 4 --top 5 --csv
paths ranks strongest paths (maximum product of input-fraction weights) and
reports the fewest hops; --by-type ranks routes grouped by cell-type
sequence instead. reach ranks targets by hop-k reach. Both split by
first-hop route (AL, LH, MB, other, kc). They can seed PNs by their
input from an ORN receptor family, glomerulus, or antenna side. Definitions,
selector vocabulary, output columns, and a worked DNa02 recipe are in
docs/paths.md.
Olfaction Offline Cache
Build/query derived AL/LH/MB tables:
fruitloops setup
fruitloops olf tables
fruitloops olf neurons --dataset flywire --region AL --class ORN --format csv
fruitloops olf classes --dataset flywire --region AL --format csv
fruitloops olf glomerulus DM1 --dataset flywire --format csv
fruitloops olf inputs --dataset hemibrain --target-class PN --source-class ORN --glomerulus DM3 --by-side --format csv
fruitloops olf outputs --dataset flywire --source-class PN --target-class KC --region MB --format csv
fruitloops olf pathway PN KC --dataset flywire --region MB --format csv
fruitloops olf edges --dataset flywire --region LH --min-synapses 5 --format csv
Full olfaction table details, live access, offline cache behavior, bulk imports, and plotting examples live in docs/setup.md.
Output Formats
Most commands support --format table, --format csv, --format json, or
--format jsonl. CSV and JSONL are intended for downstream agent pipelines.
Rebuilding the Data Snapshot
Fruitloops needs a generated CSV snapshot for status, table, find,
partners, and comparison commands. Release builds ship that snapshot. For a
source checkout or custom package without data/, point FRUITLOOPS_DATA_DIR
at a snapshot or rebuild it from the paper repository.
From the fruitloops repository root:
python scripts/build_data_snapshot.py \
--source "/path/to/widespread-direction-selectivity" \
--dest "$(fruitloops status --csv | awk -F, '$2=="data_dir"{print $4}')"
The script copies generated CSVs and rewrites data/manifest.csv.
Test
python -m unittest discover -s tests
Metadata
Release files for fruitloops 0.2.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 | |
|---|---|---|---|
| fruitloops-0.2.2.tar.gz | 5.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fruitloops-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.5 MB
Release files / fruitloops-0.2.2.tar.gz
| Download URL | fruitloops-0.2.2.tar.gz |
|---|---|
| Size | 5.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38cd5b9ba3b3f15e196273279abb193e743df04b8dee35ecb1897548bfb04779
|
|
BLAKE2b-256 checksum How to use checksums |
bd8f32d62ffaa9dbe0ab09b38af4c0e9446b9ad7a9d1f03416ddd3c51b4db6aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / fruitloops-0.2.2-py3-none-any.whl
| Download URL | fruitloops-0.2.2-py3-none-any.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33926f5086a7e4cde8ad64c5459971eecd81abc857da2ff2b6ad56eaa9af6fd3
|
|
BLAKE2b-256 checksum How to use checksums |
f38dbe41b5d84ba71b43f0a99be769852e4304755cb437758ca979cea91cdb2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency log