Create Synthetic Data Products from a 3D Stellar Corona Magnetic Field
Developer Documentation
Installation
From pip
$ pip install corona_lab
From source
$ git clone https://github.com/St-andrews-cool-stars/CoronaLab.git
$ cd CoronaLab
$ pip install .
For active developement intall in develop mode
$ pip install -e .
Testing
Testing is run with tox (pip install tox). Tests can be found in corona_lab/tests/.
$ tox -e test
Tests can also be run directly with pytest:
$ pip install -e .[test]
$ pytest
You can specify a single directory or file to test as:
$ pytest corona_lab/tests/test_radio.py
Codestyle can be checked with:
$ tox -e codestyle
Documentation
Documentation files are found in docs/.
We build the documentation with tox (pip install tox):
$ tox -e build-docs
You can also build the documentation with Sphinx directly using:
$ pip install -e .[docs]
$ cd docs
$ make html
The built docs will be in docs/_build/html/, to view them go to file:///path/to/corona_lab/repo/docs/_build/html/index.html in the browser of your choice.
License
This project is Copyright (c) St Andrews Cool Stars Group and licensed under the terms of the BSD 3-Clause license. This package is based upon the Openastronomy packaging guide which is licensed under the BSD 3-clause licence. See the docs/LICENSE.rst file. more information.
Contributing
We love contributions! CoronaLab is open source, built on open source, and we’d love to have you hang out in our community.
Imposter syndrome disclaimer: We want your help. No, really.
There may be a little voice inside your head that is telling you that you’re not ready to be an open source contributor; that your skills aren’t nearly good enough to contribute. What could you possibly offer a project like this one?
We assure you - the little voice in your head is wrong. If you can write code at all, you can contribute code to open source. Contributing to open source projects is a fantastic way to advance one’s coding skills. Writing perfect code isn’t the measure of a good developer (that would disqualify all of us!); it’s trying to create something, making mistakes, and learning from those mistakes. That’s how we all improve, and we are happy to help others learn.
Being an open source contributor doesn’t just mean writing code, either. You can help out by writing documentation, tests, or even giving feedback about the project (and yes - that includes giving feedback about the contribution process). Some of these contributions may be the most valuable to the project as a whole, because you’re coming to the project with fresh eyes, so you can see the errors and assumptions that seasoned contributors have glossed over.
Note: This disclaimer was originally written by Adrienne Lowe for a PyCon talk, and was adapted by model_corona based on its use in the README file for the MetPy project.
Metadata
Release files for corona-lab 0.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 | |
|---|---|---|---|---|
| corona_lab-0.1.1.tar.gz | 765.0 kB | Without provenance | Details |
Release files / corona_lab-0.1.1.tar.gz
| Download URL | corona_lab-0.1.1.tar.gz |
|---|---|
| Size | 765.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c245bc7f118cf11da9407de7a8e6092d12c08a0da6d17a49f2965e14f109f818
|
|
BLAKE2b-256 checksum How to use checksums |
5a32cf80646de691144ce881596c8b37237837e0812c7becbe4537aad1571a23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.4
|
Security for corona-lab 0.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.