Skip to main content

Utility code to perform QAG and SV analysis

Project description


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


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 the main branch

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.

  1. On github click Fork. This creates a copy of wl_utilities for you to work on (WARNING: make sure your repo is called "wl_utilities" and not "utilities")
  2. Check that your machine can use ssh key authentication with github
  3. On the pc where you develop QAG tests, cd somewhere for development on this wl_utiltities repository. There is no need to create a wl_utilities directory.
  4. git clone (the link can be found under the green code button on your github page)
  5. cd wl_utilities on your local machine.
  6. Activate your development environment (maybe: conda activate weaveio or similar)
  7. Install helper aliases chmod +x && ./

To add/modify this repository with your own changes and improvements please use this workflow:

  1. Activate your development environment (maybe: conda activate weaveio or similar)
  2. Pull the latest updates: git sync-fork
  3. Create a new branch for your changes to live on: git fork-branch my-clever edit
  4. Make your changes on this branch
  5. View what has happened: git status
  6. Add your changes to be commited: git add <file1> <file2> ...
  7. View what has changed: git status
  8. Save your changes: git commit -m "description of changes"
  9. Wait for automated checks to complete (and then commit again if necessary: git commit -m "description of changes")
  10. Push changes to your fork only: git push
  11. Open a pull request on your github page (, 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.


The structure of this package will be:

  misc/  # for random short but useful snippets
  spectrum/  # for anything that processes spectra
  stats/  # for anything that looks like a statistical test

We will not use separate folders for individual's code since the objective is to put them together and not repeat.


  • This repo will be autoformatted according to black on server-side
  • No change is merged with the main branch until approved by "enough" people
  • Keep the code as modular as possible

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

wl_utilities-2022.0.4.tar.gz (16.5 kB view hashes)

Uploaded source

Built Distribution

wl_utilities-2022.0.4-py2.py3-none-any.whl (15.8 kB view hashes)

Uploaded py2 py3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page