hera_qm
is a python package for calculating quality metrics of HERA data.
It is integrated in the Real-Time Pipeline (RTP), automatically generating metrics
for all HERA data as it is taken. But hera_qm
can also be used offline for
further analysis.
Data quality metrics are useful and needed throughout the analysis of interferometric data.
This repository is a centralized place for the HERA team to develop metrics to 1)
run on data in the RTP and deliver to the wider collaboration; 2) store these metrics
in the Monitor and Control database for easy access; and 3) use offline in individual
analyses. As a consequence of the first two goals, contributions to hera_qm
will
be vetted by the community and require thorough unittests. However, the code base
will also be flexible to enable the third goal, and we welcome contributions (see below).
Preferred method of installation for users is simply pip install .
(or pip install git+https://github.com/HERA-Team/hera_qm
). This will install
required dependencies. See below for manual dependency management.
If you are using conda
, you may wish to install the following dependencies manually
to avoid them being installed automatically by pip
::
$ conda install -c conda-forge "numpy>=1.23" "astropy>=5.0.4" "h5py>=3.1" "pyuvdata>=2.3" pyyaml
If you are developing hera_qm
, it is preferred that you do so in a fresh conda
environment. The following commands will install all relevant development packages::
$ git clone https://github.com/HERA-Team/hera_qm.git
$ cd hera_qm
$ conda create -n hera_qm python=3
$ conda activate hera_qm
$ conda env update -n hera_qm -f environment.yml
$ pip install -e .
This will install extra dependencies required for testing/development as well as the standard ones.
Uses the pytest
package to execute test suite.
From the source hera_qm
directory run: pytest
or python -m pytest
.
There are currently five primary modules which drive HERA quality metrics.
A module to handle visibility-based metrics designed to identify misbehaving antennas.
The module includes methods to calculate several metrics to identify cross-polarized antennas
or dead antennas, based on either their redundancy with other antennas or their relative power.
The primary class, AntennaMetrics
, includes interfaces to these methods and functions for
loading data, iteratively running metrics and removing misbehaving antennas, and saving the
results of those metrics in a JSON. And example of using this moduleis in
scripts/ant_metrics_example_notebook.ipynb
.
A module to calculate metrics based on firstcal delay solutions. These metrics
identify large variations in delay solutions across time or across the array
for a given time. Included are functions for plotting firstcal delay solutions,
running the firstcal metrics, plotting the metrics, and writing them to file.
An example of using this module is in scripts/firstcal_metrics.ipynb
.
A module to calculate metrics based on omnical solutions. Currently, these metrics
aim to identify discontinuities in the phase solutions of the gains and model visibilities,
as well as outliers in the antenna-based chi-square output from omnical. Routines for
calculating the metrics, writing them to file, and plotting the metrics (as well as the
gain solutions and model visibilities) are included. For an example of how to use these
metrics see scripts/omnical_metrics_example.ipynb
. The metrics themselves are detailed
there as well as in the doc-strings of the source code in hera_qm.Omnical_Metrics.run_metrics()
.
This module contains the tools to for radio frequency interference (RFI) detection
and flagging. Low-level preprocessing functions act on 2D arrays to filter data
and/or calculate significance metrics. Flagging algorithms implement the low-level
functions or flag in other ways (e.g. "watershed" around existing flags). "Pipelines"
define the flagging strategy to apply to some data. For example, xrfi_h1c_pipe
shows
the flagging scheme we used for H1C observing season. Wrappers handle the file I/O,
and call pipelines. xrfi_h1c_run
is a wrapper we retroactively made to reflect
what we did for H1C.
UVFlag has been moved to pyuvdata.
Issues are tracked in the issue log. Major current issues and planned improvements include:
- A unified metric class structure
- Develop Tsys calculations into metrics (HERA Memos 16 and 34)
- Develop closure quantities into metrics (HERA Memo 15)
Contributions to this package to introduce new functionality or address any of the issues in the issue log are very welcome. Please submit improvements as pull requests against the repo after verifying that the existing tests pass and any new code is well covered by unit tests.
Bug reports or feature requests are also very welcome, please add them to the issue log after verifying that the issue does not already exist. Comments on existing issues are also welcome.