girder-flyer-studio
A girder dashboard developed for use with girder dashboards, girder jsonforms, and LightBurn Software.
Facilitates the specification, creation, and registration of Flyer Stacks, which are an array of small circular discs used in laser impact experiments. This is accomplished through automatic specification of templated LightBurn project files through a simplified JSON form, packaging and capture of experimentally relevant metadata, and IGSN registration per flyer stack on girder.
Features
- Draft → submitted → generated → registered lifecycle.
- LightBurn layout, inventory CSV, and JSON metadata generation.
- Scans girder for foil IGSNs (denoting base material) by contains alternative identifier
foil-igsn. - Registration creates
<foil IGSN>-<stack ID>as a child deposition using JSONForms. - Metadata and experiment invariants validated.
Admin settings and shared storage
See Configuration form validation for form requirements, acknowledgement rules, and downstream checks.
See Dashboard configuration for administrator setup instructions, a complete settings example, permissions, and the Complete Workflow module.
Offline drafts
Use Copy or Download in the JSON tab to export the current form, including
incomplete configurations. Upload a single configuration .json file per item
directly into the workspace's Drafts folder using Girder's file browser, then
refresh the studio's configuration list. The studio creates this folder when the
list is opened by an operator with workspace write access.
Matching JSON in either the current section format or the legacy builder format appears as an editable, unvalidated draft. Imported drafts must still be submitted through the form's normal validation before generating or registering a stack. Malformed or unrelated JSON remains in the upload folder. Files must be no larger than 256 KiB, and the operator must have write access to import them.
Authors and licence
Flyer Studio was written by Max Berner. The conversion to a conventional Girder 5 plugin is by Kacper Kowalik.
Released under the BSD 3-Clause licence.
Metadata
Release files for girder-flycut-studio 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| girder_flycut_studio-1.0.3.tar.gz | 206.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| girder_flycut_studio-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 356.9 kB
Release files / girder_flycut_studio-1.0.3.tar.gz
| Download URL | girder_flycut_studio-1.0.3.tar.gz |
|---|---|
| Size | 206.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9734a7a3003f51bab144a05e9c01b42f60ad91064314025e34de9c0eea23a84
|
|
BLAKE2b-256 checksum How to use checksums |
43177da34255036238e417a561c0c5c5a3768358d8e752d08be0c9adf4db0a10
|
| 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 14, 2026.
Transparency logRelease files / girder_flycut_studio-1.0.3-py3-none-any.whl
| Download URL | girder_flycut_studio-1.0.3-py3-none-any.whl |
|---|---|
| Size | 150.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
be4c628fe3814930f2d0f91e7879129f1d73d465ca6fa6fdbba94c245697d0b3
|
|
BLAKE2b-256 checksum How to use checksums |
d95b4e5629c1dc06219fa0ce3c1595b98a538ae18fc65456e187212e4f15da73
|
| 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 14, 2026.
Transparency log