CLI¶
TimeNet ships two console scripts, one for each side of the workflow:
| Command | Ships with | Role | Mirrors |
|---|---|---|---|
timenet |
timenet |
Consumer: browse a registry and download datasets. | The client SDK. |
timenet-curate |
timenet-connectors |
Producer: run a connector through the pipeline into a registry. | Curate & publish. |
Both are built with Typer and gate their heavier dependencies behind an
extra, so the core package stays small. timenet needs the cli extra (install coming soon);
run it without the extra and it prints a one-line install hint instead of a traceback.
Both split their output the same way: status lines on stderr, the machine-readable result (a path) on
stdout. --quiet/-q silences the status, and belongs to the tool rather than the subcommand, so it
goes first: timenet --quiet list, timenet-curate --quiet build <id>.
Every command reads the same configuration the SDK does. The registry to talk to is resolved as
--registry flag (or --out for timenet-curate build), then $TIMENET_REGISTRY, then the local
default at <home>/registry. See Configuration for the full set of
TIMENET_* variables.
Start with timenet if you want to use datasets, or timenet-curate if you
are building one.