Another COS Dark Correction (ACDC) ⚡
Another dark correction?
COS spectroscopic science in the extreme UV regime is limited by detector
background noise. The COS pipeline,
CalCOS
performs a basic background subtraction, but for low signal-to-noise ratio (SNR)
observations, a more nuanced approach is necessary to fully capitalize on COS's
FUV capabilities. In order to achieve the maximum scientific value of
the COS instrument, we have a designed a custom
characterization and correction of the COS FUV dark rate, acdc.
With acdc, we can:
- create and maintain databases needed to measure the dark rate as a function of time, HST position, PHA, solar activity, and more
- create COS/FUV superdarks
- use superdarks to perform custom dark corrections
- analyze the efficacy of custom dark-corrected COS data
For full usage instructions, refer to the documentation on ReadTheDocs.
Installation
Create a conda environment
If you do not already have Conda installed, you need to download and install either Miniconda or Anaconda. Miniconda provides a bare minimum Conda environment. Anaconda provides a full Conda root environment along with many other tools, libraries, and utilities.
Create a conda enviornment to use acdc:
conda create -n <env_name> python=<version>
conda activate <env_name>
pip install .
where <env_name> is the name of the environment that will be created.
You need at least python version 3.9, so fill in <version> with whatever
version >=3.9 that you desire.
Install the latest stable version
The easiest way to install acdc is to use pip:
pip install acdc-hst
[!IMPORTANT]
The package name on PyPi and the name of this repo,
acdc-hst, are different than the imported package name,acdc. That is, you import the package asimport acdc.
Install the development version
First clone this repo. Then cd into the cloned repository and execute:
pip install .
Usage
For full usage instructions, refer to the documentation on ReadTheDocs.
Building the docs locally
To build the documentation locally, for testing, first clone this repository then navigate into the repo and follow these commands:
pip install ".[docs]"
cd docs/
make html
It will take a minute or two to build all the docs. Once finished, you can open the docs in your default web browser with the following command:
open _build/html/index.html
From there you can click and navigate the webpage as if it were hosted online normally.
Metadata
Release files for acdc-hst 1.1
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 |
|---|---|---|---|---|
| acdc_hst-1.1.tar.gz | 805.9 kB | Without provenance | Details for acdc_hst-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acdc_hst-1.1-py3-none-any.whl | Python 3 | none | any | Details for acdc_hst-1.1-py3-none-any.whl |
Total release size: 1.6 MB
Release files / acdc_hst-1.1.tar.gz
| Download URL | acdc_hst-1.1.tar.gz |
|---|---|
| Size | 805.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c92039b38dfa7a6c22930839460167bdd6eb3682dd4008c9acde1fcbf921b09
|
|
BLAKE2b-256 checksum How to use checksums |
9f88ce9c65e99f901b34462b0470bd0354cdab9c8c0125334d2109450a12fdb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / acdc_hst-1.1-py3-none-any.whl
| Download URL | acdc_hst-1.1-py3-none-any.whl |
|---|---|
| Size | 826.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46fb108b97966bea4dff9ee00a7a039a8eea53f9f0582e516de9b72e6baf69d7
|
|
BLAKE2b-256 checksum How to use checksums |
558ca5140284ddde4feabe1bf38a4fbad2a429e798cd66676dbccff2abe44667
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for acdc-hst 1.1
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.