Skip to main content

Modules to determine telescope polarization parameters and compute instrument demodulation matrices at DKIST

Project description

Modules to both determine telescope polarization parameters and compute instrument demodulation matrices

It is primarily a library used by the DKIST automated processing pipelines

Deployment

dkist-processing-pac is deployed to PyPI

Development

git clone git@bitbucket.org:dkistdc/dkist-processing-pac.git
cd dkist-processing-pac
pre-commit install
pip install -e .[test]
pytest -v --cov dkist_processing_pac

Changelog

When you make any change to this repository it MUST be accompanied by a changelog file. The changelog for this repository uses the towncrier package. Entries in the changelog for the next release are added as individual files (one per change) to the changelog/ directory.

Writing a Changelog Entry

A changelog entry accompanying a change should be added to the changelog/ directory. The name of a file in this directory follows a specific template:

<PULL REQUEST NUMBER>.<TYPE>[.<COUNTER>].rst

The fields have the following meanings:

  • <PULL REQUEST NUMBER>: This is the number of the pull request, so people can jump from the changelog entry to the diff on BitBucket.

  • <TYPE>: This is the type of the change and must be one of the values described below.

  • <COUNTER>: This is an optional field, if you make more than one change of the same type you can append a counter to the subsequent changes, i.e. 100.bugfix.rst and 100.bugfix.1.rst for two bugfix changes in the same PR.

The list of possible types is defined the the towncrier section of pyproject.toml, the types are:

  • feature: This change is a new code feature.

  • bugfix: This is a change which fixes a bug.

  • doc: A documentation change.

  • removal: A deprecation or removal of public API.

  • misc: Any small change which doesn’t fit anywhere else, such as a change to the package infrastructure.

Rendering the Changelog at Release Time

When you are about to tag a release first you must run towncrier to render the changelog. The steps for this are as follows:

  • Run towncrier build –version vx.y.z using the version number you want to tag.

  • Agree to have towncrier remove the fragments.

  • Add and commit your changes.

  • Tag the release.

NOTE: If you forget to add a Changelog entry to a tagged release (either manually or automatically with towncrier) then the Bitbucket pipeline will fail. To be able to use the same tag you must delete it locally and on the remote branch:

# First, actually update the CHANGELOG and commit the update
git commit

# Delete tags
git tag -d vWHATEVER.THE.VERSION
git push --delete origin vWHATEVER.THE.VERSION

# Re-tag with the same version
git tag vWHATEVER.THE.VERSION
git push --tags origin main

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

dkist_processing_pac-3.0.3.tar.gz (551.8 kB view details)

Uploaded Source

Built Distribution

dkist_processing_pac-3.0.3-py3-none-any.whl (558.2 kB view details)

Uploaded Python 3

File details

Details for the file dkist_processing_pac-3.0.3.tar.gz.

File metadata

  • Download URL: dkist_processing_pac-3.0.3.tar.gz
  • Upload date:
  • Size: 551.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.11.10

File hashes

Hashes for dkist_processing_pac-3.0.3.tar.gz
Algorithm Hash digest
SHA256 27e4a3d7bd5a063af5d869a686f3f0e564010dc95de5807592e7e70cd89247a2
MD5 c2ced8c873f0f88a9aff09463d9d319b
BLAKE2b-256 cf05f3c123405bb0f3f7da5b297461e2d8c1d1a7a0f9edd3cb2c6e5fb7c099f8

See more details on using hashes here.

Provenance

File details

Details for the file dkist_processing_pac-3.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for dkist_processing_pac-3.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 4f988b81a9e4f857331ce977419e737822f2541a9e989b5a14efaed2595a188c
MD5 6fa5e119cd2050b19e0d37b07e24c1ea
BLAKE2b-256 01274fe78f5a6d811bf3acf57a5e16fd4a12aa47156cdecfbbf893c08cffffbe

See more details on using hashes here.

Provenance

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