Frequently asked questions
Do I need an account to look at the data?
No, not to look. The public API returns the catalogue, per-dataset metadata and the table schema without a token:
curl https://api.syndb.xyz/v1/neurodata/datasets
curl https://api.syndb.xyz/v1/neurodata/schema/tables
You do need a free academic account to run a query, to use graph analysis or meta-analysis, and to upload. Creating one takes one click; see Authentication.
Why is there no email sign-up or password reset?
Accounts are created only through an identity provider — “Sign in with your institution” (CILogon) or GitHub — and the provider verifies you. There is therefore no SynDB password, no confirmation email and no reset link. If you lose access, sign in again with the same provider.
Why can’t I install the CLI or the Python client from PyPI or crates.io?
Neither is published yet. Both live in the private repository, so you need read access granted on request; Get help says how to ask. The web app and the HTTP API need no repository access, so you can do the worked example without installing anything.
Why does my query fail when I add a JOIN or a subquery?
SyQL accepts joins, CTEs and subqueries grammatically, and the SyQL reference documents them, but the public server currently rejects them before execution with:
joins and nested queries are not supported until dataset authorization covers every query scope
The restriction is an access-control gap, not a syntax problem: a nested query
could read a dataset you were not authorised for. Single-table queries with
WHERE, GROUP BY, ORDER BY and aggregates all work. To compare datasets,
either run one query per dataset and join the small results client-side, or use
UNION ALL, which is supported.
What units are the numbers in?
It depends on the dataset, and you have to check. SynDB keeps each importer’s
source convention instead of converting everything to one unit: FlyWire
morphometry is micrometres, mesh-connectomics morphometry is micrometres, and
MICrONS mitochondria record voxel counts. A column name that states its
unit wins (length_um, volume_um3, diameter_nm). For everything else,
Tables, columns and units lists the units
that have been verified per source and marks the rest unit: to be confirmed.
Do not assume nanometres, and convert before you compare datasets.