baseline_dependent_averaging
This is code for applying baseline-dependent averaging to a radio astronomy interferometric dataset. It applies the principles and formulas presented in Wijnholds et al. (2018) to average high-cadence data to a lower cadence while introducing a maximum amount of decorrelation specified by the user. In brief, short baselines of an interferometer do not decorrelate as rapidly as long baselines, and so data from shorter baselines can be averaged together without losing as much coherent sky information. The code and routines in this repo are designed to work on already-recorded data (which is typically written at a common cadence for all baselines) and averages together consecutive time samples until a specific threshold. A forthcoming memo will describe the operation in more detail.
Installation
The code can be installed by invoking
pip install .
from the top level of the repo. This will install a module called bda which
can be imported. The main user-facing function is bda.apply_bda, which is
designed to work on a pyuvdata UVData
object. It also provides a script, apply_bda.py, which can be called from the
command line for applying BDA to an existing dataset on disk.
Dependencies
The following packages are required:
- astropy
- setuptools_scm
- pyuvdata
pyuvdata can be installed from conda (preferred), or from pip. It is
available on the conda-forge channel. To install:
conda install -c conda-forge pyuvdata
Tests
The testing requirements can be installed by invoking
pip install .[testing]
from the top level of the repo. This will install the package and all
dependencies for running tests. The test suite can be run by running pytest
after installation.
Dependencies
In addition to the main package dependencies above, the following packages are required for running tests:
- pytest >= 6.0
Metadata
Release files for bda 0.1.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 |
|---|---|---|---|---|
| bda-0.1.1.tar.gz | 17.6 kB | Without provenance | Details for bda-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bda-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for bda-0.1.1-py3-none-any.whl |
Total release size: 30.1 kB
Release files / bda-0.1.1.tar.gz
| Download URL | bda-0.1.1.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
236db7565238d93ad3030d1020a1ec83e25aefd2bb470d0bf23a0e21cd1380f6
|
|
BLAKE2b-256 checksum How to use checksums |
4beccd1c03a8cf1807adbf1e654bf54a32678e40d24451da0404434b9f0a3a69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Release files / bda-0.1.1-py3-none-any.whl
| Download URL | bda-0.1.1-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f16909b1cddfc6a4c943b59c7f7a4d5916281f012766da98c81347a6504a3dc1
|
|
BLAKE2b-256 checksum How to use checksums |
802dc0cb370a864c0840ed6d45f37cd909c56b8df7d81a5f4af123c0e3e54c4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Security for bda 0.1.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.
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.