This release is a pre-release and may not be stable for production use.
bilby antiglitch
This Python package extends the functionality in the bilby to additionally sample over glitch realisations
Installation
bilby_antiglitch is currently available via PyPI and can be installed with:
$ pip install bilby_antiglitch
Once bilby_antiglitch has been installed, a custom version of bilby_pipe needs to
be installed with:
$ pip install 'bilby_pipe @ git+https://git.ligo.org/charlie.hoy/bilby_pipe.git@input_class'
This version needs to be installed because we are waiting for required code to
be merged into the main bilby_pipe code base. Please see the following merge
request for details:
* `bilby_pipe!583 <https://git.ligo.org/lscsoft/bilby_pipe/-/merge_requests/583>`_
For full installation instructions, see our documentation.
Usage in bilby_pipe
The functionality in bilby_antiglitch can be used with bilby_pipe as you would with any other frequency domain source model. It simply requires the following options to be specified in your configuration file:
analysis_executable_parser=bilby_antiglitch.bilby_pipe.create_parser
likelihood-type=GravitationalWaveTransientPlusGlitch
glitch-frequency-domain-source-model = bilby_antiglitch.source.antiglitch
detectors-glitch = ['L1']
If you wish to perform an injection with a specific glitch model, this can be done with the following option in your configuration file:
injection-glitch-frequency-domain-source-model = bilby_antiglitch.source.antiglitch
Citing
If you find bilby_antiglitch useful in your work please cite the following papers:
@article{Hoy:2026dkr,
author = "Hoy, Charlie and Bondarescu, Ruxandra and Lundgren, Andrew and Nuttall, Laura K.",
title = "{A parametric signal plus noise inference framework for short duration non-Gaussian noise transients}",
eprint = "2606.31304",
archivePrefix = "arXiv",
primaryClass = "gr-qc",
reportNumber = "LIGO-P2600325",
month = "6",
year = "2026"
}
Metadata
Release files for bilby-antiglitch 0.1.0a1
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 |
|---|---|---|---|---|
| bilby_antiglitch-0.1.0a1.tar.gz | 17.1 kB | Without provenance | Details for bilby_antiglitch-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bilby_antiglitch-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for bilby_antiglitch-0.1.0a1-py3-none-any.whl |
Total release size: 32.0 kB
Release files / bilby_antiglitch-0.1.0a1.tar.gz
| Download URL | bilby_antiglitch-0.1.0a1.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a30691ffe05d776c3f658c14c908d7a03e483427887059a88585de247f020e33
|
|
BLAKE2b-256 checksum How to use checksums |
1e0a58ea03344fff767b26e9062fbbab0c8c7b14a8b5a33a0153bb558329b5b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Release files / bilby_antiglitch-0.1.0a1-py3-none-any.whl
| Download URL | bilby_antiglitch-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f3bfee2197bfd185776d3fd44e7229cc7fa5a188cc099c22c72f9b63f995672
|
|
BLAKE2b-256 checksum How to use checksums |
53b7cd9e60667f0e19982f8ec0307f31ebf458386121c469c71aa23cea5a3b26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Security for bilby-antiglitch 0.1.0a1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.