Utility code to be used in the WEAVE-QAG/SV environment
This package is called wl-utilities on PyPI and can be installed with pip install wl-utilities and then imported with import wl_utilities
This package is a collaborative effort and will comprise the scientific code that allows the QAG tests and SV to run. wl_utilities will be a dependency of those projects. wl_utilities should not use weaveio or qag packages.
Please see setup for setting up github
Workflow
There will be 2 branches in use on this repository:
main- where the production-ready version exists and which is uploaded automatically to PyPI for use by everyone.develop- where changes and merges all take place before merging into themainbranch
Setup git
To setup git to deal with collaboration. This will allow you to use our custom git aliases, shortcuts that make your life easier.
- On github click
Fork. This creates a copy ofwl_utilitiesfor you to work on (WARNING: make sure your repo is called "wl_utilities" and not "utilities") - Check that your machine can use ssh key authentication with github
- On the pc where you develop QAG tests,
cdsomewhere for development on thiswl_utiltitiesrepository. There is no need to create awl_utilitiesdirectory. - git clone
git@github.com:YOURUSERNAME/wl-utilities.git(the link can be found under the greencodebutton on your github page) cd wl_utilitieson your local machine.- Activate your development environment (maybe:
conda activate weaveioor similar) - Install helper aliases
chmod +x setup.sh && ./setup.sh
To add/modify this repository with your own changes and improvements please use this workflow:
- Activate your development environment (maybe:
conda activate weaveioor similar) - Pull the latest updates:
git sync-fork - Create a new branch for your changes to live on:
git fork-branch my-clever edit - Make your changes on this branch
- View what has happened:
git status - Add your changes to be commited:
git add <file1> <file2> ... - View what has changed:
git status - Save your changes:
git commit -m "description of changes" - Wait for automated checks to complete (and then commit again if necessary:
git commit -m "description of changes") - Push changes to your fork only:
git push - Open a pull request on your github page (https://github.com/USERNAME/wl-utilities), click contribute->open pull request, and check "allow edits by maintainer"
You can also use gh pr create --fill to open a pull request on command line. This requires the github cli utility which can be installed with apt-get or conda
In general we should be writing code like this:
* Play with code in jupyter notebook (all weaveio queries, new functions, plotting)
* Refactor this notebook and the wl_utilities module to move new functions/plotting to wl_utilities
* Run notebook to make sure its still doing what you want
All changes therefore end up in the develop branch of the weave-lofar shared repo.
All pull requests will be reviewed before merging, so we can limit mistakes.
Structure
The structure of this package will be:
wl_utilities/
misc/ # for random short but useful snippets
spectrum/ # for anything that processes spectra
e.g. cross-correlation.py
e.g. reduction.py
stats/ # for anything that looks like a statistical test
e.g. zscores.py
We will not use separate folders for individual's code since the objective is to put them together and not repeat.
Rules:
- This repo will be autoformatted according to
blackon server-side - No change is merged with the
mainbranch until approved by "enough" people - Keep the code as modular as possible
Metadata
Release files for wl-utilities 2022.0.4
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 |
|---|---|---|---|---|
| wl_utilities-2022.0.4.tar.gz | 16.5 kB | Without provenance | Details for wl_utilities-2022.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wl_utilities-2022.0.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for wl_utilities-2022.0.4-py2.py3-none-any.whl |
Total release size: 32.3 kB
Release files / wl_utilities-2022.0.4.tar.gz
| Download URL | wl_utilities-2022.0.4.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed22a6a0084699643c5f5a6f3fbac11153dc0452c33e6eacd70b87b90e0c2491
|
|
BLAKE2b-256 checksum How to use checksums |
e682073af634c7cf8c9499bc7502fa39d992f49670103ff6cdd8ba61d0d1abb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / wl_utilities-2022.0.4-py2.py3-none-any.whl
| Download URL | wl_utilities-2022.0.4-py2.py3-none-any.whl |
|---|---|
| Size | 15.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7428726f11a2423407314e548dd232381b8682562c1924900bbe89d56c44bb3f
|
|
BLAKE2b-256 checksum How to use checksums |
a0ac46fbbb55d0ea5e57c4e10902b81888415c39fdbd8c66ca524c67904f9927
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for wl-utilities 2022.0.4
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.