starccato_lvk
Tools to help work with LVK data. The project covers two primary workflows:
- Data acquisition – fetching GWOSC/OzSTAR strain segments and preparing analysis-ready chunks/PSDs.
- Data analysis – running Starccato signal inference (supernova, blip, noise models) on prepared data.
Typical usage:
# Acquire 100 segments (noise + blip) into ./lvk_data
collect_lvk_data 100
# Run Starccato analysis on a bundled strain/PSD file
python -m starccato_lvk.cli run analysis_bundle.hdf5 ./outdir
# (Optional) run with separate strain/PSD files
python -m starccato_lvk.cli run analysis_chunk.hdf5 ./outdir --psd-path psd.hdf5
# Generate prior diagnostics (time/PSD overlays) before sampling
python -m starccato_lvk.cli run analysis_bundle.hdf5 ./outdir --diagnostics
The diagnostics PNG overlays the analysis data with prior samples in both time and frequency domains so you can tune priors before expensive runs.
See docs/ and src/starccato_lvk/acquisition/README.md for more details on configuration and advanced options.
1 maintainer
Metadata
1 maintainer
Release files for starccato-lvk 0.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 | Provenance | |
|---|---|---|---|---|
| starccato_lvk-0.0.3.tar.gz | 1.5 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| starccato_lvk-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 MB
Release files / starccato_lvk-0.0.3.tar.gz
| Download URL | starccato_lvk-0.0.3.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb6b4492a2459df03dabd76919702788ba1144c5adb763095bf89f12824fffdb
|
|
BLAKE2b-256 checksum How to use checksums |
95e9eeeefbbe13c39438509d3fa59cdd7f21f4e58e150cdbbed0afb32e27d559
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Jul 1, 2026.
Transparency logRelease files / starccato_lvk-0.0.3-py3-none-any.whl
| Download URL | starccato_lvk-0.0.3-py3-none-any.whl |
|---|---|
| Size | 115.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
691625cac514f1c7d94954c7d96d7775ba2aebd0b3e113e50027b26addf691c9
|
|
BLAKE2b-256 checksum How to use checksums |
e8ae823bbd250bce49081f94f4e6a426c421b1ebe31307a70b0be033a6cca231
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Jul 1, 2026.
Transparency logSecurity for starccato-lvk 0.0.3
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for starccato_lvk-0.0.3.tar.gz
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 Jul 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
