jinwu-gw
jinwu-gw turns a public LIGO/Virgo/KAGRA alert or a local HEALPix
localization into a reproducible sky-coverage report. The first release is
deliberately focused on visualization: it combines the GW probability map
with Fermi/GBM geometry and optional EP/BAT footprints. It does not claim
that a geometric coverage result is a valid GBM exposure or spectral product.
jinwu-gw plot --notice alert.json --output results/
jinwu-gw plot --event S240422ed --output results/
jinwu-gw plot --skymap sky.multiorder.fits --time 2024-04-22T00:00:00Z \
--gbm-cache ~/.cache/jinwu-gw/gbm --output results/
--skymap may also be an HTTPS FITS URL. The output directory always
contains the all-sky and GBM diagnostic PNG/PDF (the latter is labelled
unknown when no POSHIST is available), coverage.json, and coverage.ecsv.
The CLI uses $GBM_POSHIST_DIR or ~/.cache/jinwu-gw/gbm for GBM
POSHIST products when --gbm-cache is omitted; use --no-download for a
strictly offline run.
The JSON records the alert/map checksum, credible-region areas, MOC-order
convergence, coverage status and the explicit spectral_analysis: "not_run"
state. A geometric GBM result is not a validated exposure or spectrum.
Metadata
Release files for jinwu-gw 0.3.1
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 | Actions |
|---|---|---|---|---|
| jinwu_gw-0.3.1.tar.gz | 34.6 kB | With provenance | Details for jinwu_gw-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jinwu_gw-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for jinwu_gw-0.3.1-py3-none-any.whl |
Total release size: 73.1 kB
Release files / jinwu_gw-0.3.1.tar.gz
| Download URL | jinwu_gw-0.3.1.tar.gz |
|---|---|
| Size | 34.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9cca44744bc7457c044c02aefb9f56450e25b642e7a8398876c3a7bcbd6d232
|
|
BLAKE2b-256 checksum How to use checksums |
a46f58551bf535b5ec60cb4c3ae1c07bcd69bc66e384b74f25074724ecc90b95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 16, 2026.
Transparency logRelease files / jinwu_gw-0.3.1-py3-none-any.whl
| Download URL | jinwu_gw-0.3.1-py3-none-any.whl |
|---|---|
| Size | 38.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0037421c5944c7abf538c084dde405f513e83efc38ba67b2565720ee3147ab93
|
|
BLAKE2b-256 checksum How to use checksums |
10ce488596661f7b5bfa678fea271b5e1c77ec3f5d9efdb5773ddc6d96ae4368
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 16, 2026.
Transparency logSecurity for jinwu-gw 0.3.1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for jinwu_gw-0.3.1.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 Nov 16, 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.