Berk is a package for fetching and processing MeerKAT data on a compute cluster using Oxkat for calibration and imaging, and PyBDSF for generating object catalogs.
Documentation: https://berk.readthedocs.io
License: GPL v3
Authors: Matt Hilton
Installation: pip install berk
Support: Please use the GitHub issues page, and/or contact Matt Hilton.
Berk should run on any compute cluster that runs either Slurm or PBS as a workload manager. It is is being developed and deployed on Hippo, the High Performance Computing facility at the University of KwaZulu-Natal, and at the Centre for High Performance Computing, with the aim of using it to perform a serendipitous survey with MeerKAT, and in turn to generate useful high-level processed MeerKAT data (initially, continuum images and catalogs) for use by the community.
Berk is under active development, and not all documentation may be up to date. Not all needed features are implemented yet. However, at the moment, data can be fetched from the archive, processed to images and catalogs, and collected from multiple compute clusters using only a few shell commands.
Berk is named after the faithful servant of The Thing Upstairs.
Metadata
Release files for berk 0.1.2
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 |
|---|---|---|---|---|
| berk-0.1.2.tar.gz | 57.6 kB | Without provenance | Details for berk-0.1.2.tar.gz |
Release files / berk-0.1.2.tar.gz
| Download URL | berk-0.1.2.tar.gz |
|---|---|
| Size | 57.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b59d386b7874b7394a1eea2c3592a5db63cf4c717b12086e84c59fa9fbc2eb67
|
|
BLAKE2b-256 checksum How to use checksums |
d646b3764ffb52b685f1ca654e00d302fd8f0c612a1676f725a7845431a552fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for berk 0.1.2
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.