This release is a pre-release and may not be stable for production use.
A.C.I.D (Accurate Continuum fItting and Deconvolution)
Since the original ACID code was developed for Lucy Dolan's PhD in 2024, it has had devlopment continued by Benjamin Cadell from October 2025. The version was originally forked from the original code and renamed (ACID_v2). The code has now been merged to the original and development will continue here. The ACID_v2 repository will continue to exist on GitHub and will be kept up for reference, but all new development will be on the merged codebase here.
Since 2024, the most signficant changes to ACID have been: - Updating packages and code to work with newer and stable versions of python. - Improving memory management so that ACID can be run on MacOS without crashes (ie extending compatibility to all POSIX systems) - Adding additional kwargs to ACID to tailor output, including verbosity settings, MCMC number of steps, multiprocessing switch, and more. - Utilising classes for both ACID and the result of ACID, allowing for analysis methods that can be found in the documentation. - Methods to extract fits formats for common instruments (e.g. ESPRESSO, HARPS, UVES) and to load them directly into ACID. - Updated documentation and examples
An more complete list of changes can be found in the CHANGELOG.md file in the repository.
The documentation will be kept up to date until at least 2029.
ACID is a technique that builds on traditional Least-Squares Deconvolution (LSD) by simultaneously fitting the stellar continuum and stellar line profile and performing LSD in effective optical depth.
In a basic sense, ACID simulatenously fits the stellar continuum and profile using a combination of LSD and MCMC techniques. The spectra are then continuum corrected using this continuum fit. LSD is then run on the continuum corrected spectra to return high-resolution line profiles for each spectrum.
Installation
See the ReadTheDocs for the instructions on installation.
Metadata
Release files for ACID-code 1.5.0a3.post13
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 |
|---|---|---|---|---|
| acid_code-1.5.0a3.post13.tar.gz | 79.8 MB | Without provenance | Details for acid_code-1.5.0a3.post13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acid_code-1.5.0a3.post13-py3-none-any.whl | Python 3 | none | any | Details for acid_code-1.5.0a3.post13-py3-none-any.whl |
Total release size: 79.9 MB
Release files / acid_code-1.5.0a3.post13.tar.gz
| Download URL | acid_code-1.5.0a3.post13.tar.gz |
|---|---|
| Size | 79.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9193d0e6e4ae5884a03dc9b9625bcbedd86c90af5302fb14da586a62847a7d4d
|
|
BLAKE2b-256 checksum How to use checksums |
2c7803766d6c72f3975ac5c389bda78dc13c34cc4556657b22f88f11b8b9b304
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / acid_code-1.5.0a3.post13-py3-none-any.whl
| Download URL | acid_code-1.5.0a3.post13-py3-none-any.whl |
|---|---|
| Size | 65.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1894591db8ac44af910274de2fdfc5d977f536983d7bd02b2a384cc0ce242b0
|
|
BLAKE2b-256 checksum How to use checksums |
bed470186f7f6c56fd56fd4a6f39f520ea3ee03805d4fd61e26f6840de6b3836
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for ACID-code 1.5.0a3.post13
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.