visualdynamics.io.native¶
native
¶
Native .vdyn file format: HDF5.
A single object is one group named for its kind at the root. A whole test
is an objects/ container of numbered groups — number for order, name
and kind as attributes, so a user's name is free to contain anything
h5py would read as structure — plus the test's own name and active
geometry as root attributes. Ragged connectivity is stored as a flat
array plus offsets.
Functions:
| Name | Description |
|---|---|
save_sine_specification |
One subgroup per tone, the file's own shape: breakpoints with |
save_sine_levels |
One subgroup per tone, each the ordinary data layout — the set |
save |
Save a visualdynamics object to a .vdyn (HDF5) file. |
save_test |
Save a whole test — every named object — to one .vdyn file. |
load |
Load a .vdyn file: the object it contains, or a whole test. |
Classes¶
Functions:¶
save_sine_specification
¶
One subgroup per tone, the file's own shape: breakpoints with the per-segment sweep law, bands where they exist.
Source code in src/visualdynamics/io/native.py
save_sine_levels
¶
One subgroup per tone, each the ordinary data layout — the set is grouping, not a new format.
Source code in src/visualdynamics/io/native.py
save
¶
Save a visualdynamics object to a .vdyn (HDF5) file.
Source code in src/visualdynamics/io/native.py
save_test
¶
save_test(
path: str | PathLike,
name: str,
objects: Mapping[str, Any],
active_geometry: str | None = None,
project_type: str | None = None,
links: Sequence[Mapping[str, Any]] | None = None,
provenance: Mapping[str, Any] | None = None,
) -> None
Save a whole test — every named object — to one .vdyn file.
Objects go in numbered groups with the name as an attribute, so a name
is free to contain anything h5py would read as structure. links is
the explicit association groups, lists of object names.
Source code in src/visualdynamics/io/native.py
load
¶
Load a .vdyn file: the object it contains, or a whole test.
progress is called as (objects loaded, objects in the file) —
once up front with 0 and once per object — because a project file
is minutes of someone's day and the reader is the only thing that
knows how far along it is. A single-object file reports nothing:
one object is one step, and a bar with one step is a light bulb.