stereoid
Stereoid packages together a set of software tools that are used in the design and analysis of the Harmony satellite mission.
Setting up your development environment to run stereoid
To be able to run the Jupyter Notebooks and use the modules defined in the library you will need to install a few dependencies. Setting up a virtual environment and running “pip install .” should automatically fetch and install the necessary packages. Detailed instructions on how to do so follow:
You will need a recent version of Python installed on your system. We suggest 3.9 or later but 3.8 is also know to work. Once you have Python, you can create a virtual environment so that you can install packages in isolation. You can do this by running the following command on Unix/macOS:
python3 -m venv drama-env
or on Windows:
py -m venv drama-env
This will create a folder called “drama-env” in the folder where the previous command was ran. All packages will be installed in this folder. Now to activate this environment run this on Unix/macOS:
source drama-env/bin/activate
or on Windows:
.\drama-env\Scripts\activate
Now change to the directory where you have downloaded the stereoid package to and execute: git switch develop pip install -e .
The first command switches to the develop branch and the second installs the package. Make sure that “pip install -e .” is ran from the root level of the git repository, ie from the directory where the setup.py and README.rst files are.
After this you can install Jupyter Lab (if you don’t already have it) and start running the Jupyter Notebooks.
Running the Harmony scientific workbench
The package provides a cli program that sets up a simulation scenario, reads the wave spectra from the SWAN model and runs the ocean scientific workbench for the Harmony mission. To run, execute: harmulator_fwd [--debug] /path/to/params_scientific_workbench.py The –debug flag provides additional information in the console log. A sample params_scientific_workbench.py is provided in the PAR directory of this repository.
Metadata
Release files for stereoid 0.4
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 |
|---|---|---|---|---|
| stereoid-0.4.tar.gz | 319.0 kB | Without provenance | Details for stereoid-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stereoid-0.4-py3-none-any.whl | Python 3 | none | any | Details for stereoid-0.4-py3-none-any.whl |
Total release size: 680.4 kB
Release files / stereoid-0.4.tar.gz
| Download URL | stereoid-0.4.tar.gz |
|---|---|
| Size | 319.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
858c16078609914e2b944727bb6d3beee1d8b9db229d1ed54a04a3ef27f7b74a
|
|
BLAKE2b-256 checksum How to use checksums |
9a4cbebf0adb3f0b89a52b0ab9ec210b8c55cdfc2b7cb105debe173f68083a1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Release files / stereoid-0.4-py3-none-any.whl
| Download URL | stereoid-0.4-py3-none-any.whl |
|---|---|
| Size | 361.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0633ceda3cd7f35e678b0bbcb12a59edca11ca1c2f1f71bd027c155012a837f5
|
|
BLAKE2b-256 checksum How to use checksums |
c9b6eca050b76db50ac1038eae1476b86a657660109750195011537b80b79562
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Security for stereoid 0.4
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.