CLI reference¶
vibe-view --help and vibe-view COMMAND --help are authoritative for the
flags. This page groups the commands by what you are trying to do, names
the extra each one needs, and calls out the ones with a caveat.
vibe-view --version # version, codename, Python, PyVista and VTK
vibe-view --help
The product and the command are spelled vibe-view; the Python
distribution and import package are vibeview. Most commands run on the
core install. open, compare, serve, dashboard and desktop need the
browser stack ([viewer]); tui needs Textual ([tui]). Run a command
whose extra is missing and vibe-view names the extra and the exact install
command rather than failing obscurely.
Getting started¶
Command |
Needs |
What it does |
|---|---|---|
|
core |
Diagnose the installation and every optional mode. |
|
core |
Write and validate a bundled water-structure archive. |
|
core |
Show worked workflows. |
|
core |
List the built-in, optional and plugin importers this installation has, with their extensions and availability. |
|
vibe-qc |
Run a real calculation and open it. The only command on this page that requires vibe-qc in the same environment. |
Looking at a file¶
Command |
Needs |
What it does |
|---|---|---|
|
|
The interactive browser viewer. Loose structure files convert in memory. Several files give a Files dropdown; |
|
|
|
|
|
A native window; see The desktop app. |
|
|
The interactive terminal viewer. |
|
core |
One frame as terminal braille, then exit. |
|
|
A web file browser over a directory of archives. |
|
core |
A grid preview of many archives, as an image or, with |
Do not pass a directory to open. Use serve DIR for a browsable listing,
or import DIR to convert its contents.
Asking questions¶
Command |
Needs |
What it does |
|---|---|---|
|
core |
Metadata and section sizes. |
|
core |
Tabular sections as |
|
core |
Schema and SHA-256 check of every member. Run it before publishing or forwarding an archive. |
|
core |
Energy delta, section overlap, geometry RMSD. |
|
core |
The same across a set, against |
|
core |
Aggregate statistics over every archive in a directory. |
|
core |
Recently opened files. |
|
core |
Which visualizations a producer has to write what for. No queue needed; it is a static table. |
Figures, without a display¶
These are the core install: no [viewer] extra, no browser. They do want
an offscreen GL context; Figures without a display covers
setting one up, and show is the fallback when there is none.
Command |
What it does |
|---|---|
|
Render a section to PNG. |
|
A PNG gallery from many archives. |
|
A trajectory, reaction path, vibration, orbital sweep or turntable as MP4 or GIF. |
|
The structure as |
|
Prove the offscreen pipeline renders a non-blank image, and report the backend. |
Building and reshaping archives¶
Command |
What it does |
|---|---|
|
Convert loose files into persistent archives. One input writes a sibling |
|
Keep ( |
|
Combine sections from several archives. Structure and provenance come from the first; duplicate ids are renamed. |
|
Replicate a periodic structure |
|
Saturate open valences with hydrogens; writes |
Queue¶
Command |
Needs |
What it does |
|---|---|---|
|
|
Fetch finished jobs’ archives into |
Without the extra it prints the exact install remediation and exits 1. The queue panel inside the viewer is described in Jobs and live results, and the extra’s peculiarities in Queue integration.
Configuration¶
vibe-view config --path # where the file is
vibe-view config --init # write it with the defaults
The file is ~/.config/vibe-view/config.toml ($XDG_CONFIG_HOME is
honoured) and carries two tables:
[server]
port = 8080 # vibe-view open / serve / compare
host = "127.0.0.1" # localhost only
open_browser = true
[display]
size = "900x600" # vibe-view batch / capture
representation = "ball_and_stick" # ball_and_stick, space_filling, sticks_only, wireframe
Everything else the viewer remembers lives under the cache directory,
~/.cache/vibe-view/ ($XDG_CACHE_HOME): the browser settings and
per-element colour overrides in settings.json, the recent-files list in
recent.json, the server log in vibe-view.log, and the interpreter the
desktop app last launched from in interpreter.json. uninstall.sh leaves
all of it in place.
Exit codes¶
0 on success, non-zero on failure. A missing optional dependency is a
failure with a remediation message naming the extra to install, not a
silent degradation. capture-selftest is non-zero when the environment
cannot render, which is what makes it usable as a healthcheck.