[!warning] This project is depreciated, use ptr-editor instead.
ESA Planning Timeline Request (PTR) Python package
Since the Rosetta mission,
ESA developed an XML-like syntax to create Planning Timeline Request (PTR) files.
These files allow the mission team member to design custom attitude spacecraft pointing.
It is readable by AGM and MAPPS softwares to detect spacecraft constrains violations,
power conception and surface coverage. It can also be used to compute custom spacecraft
attitude: quaterions, camera kernels (ck) and resolved PTR.
This format is used for the JUICE mission,
and can be tested on the JUICE pointing tool.
This python package implements an object oriented approach to help the creation and parsing of PTR files for the user, as well an interface to check JUICE PTR validity with AGM.
🚧 Disclaimer: This package is in beta stage and does not support all PTR implementations. Please, open an issue to report any issue you may accounter. ⚠️ Currently this tool in beta stage, do not use it in critical environments.
📚 Documentation
A detailed documentation can be found here: esa-ptr.readthedocs.io
🐍 Installation
This package is available on PyPI and could be installed with the python package manager pip:
python -m pip install esa-ptr
Even if this tool does not have any external dependencies, we recommend to use it in an isolated virtual environment (venv or conda env).
🐛 Development and testing
If you want to contribute to the development and tests your changes before submitting a merge request, you need to install Poetry and clone this repository:
git clone https://gitlab.esa.int/juice-soc-public/python/esa-ptr.git esa-ptr ;
cd esa-ptr/
Install the package and its dependencies:
poetry install
Then, after your edits, you need to check that both linters are happy:
poetry run flake8
poetry run pylint src tests
and all the tests passed:
poetry run pytest
🎓 Resources
- Rosetta Flight Dynamics:
RO-ESC-IF-5501_i3r4_RSGS_FD_ICD-2.pdf
Metadata
Release files for esa-ptr 2.0
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 | |
|---|---|---|---|---|
| esa_ptr-2.0.tar.gz | 28.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| esa_ptr-2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.6 kB
Release files / esa_ptr-2.0.tar.gz
| Download URL | esa_ptr-2.0.tar.gz |
|---|---|
| Size | 28.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
058d68de2178e8f8f111af63f1e53aa82f74e63dccf20e0e455c7a3ab5e70326
|
|
BLAKE2b-256 checksum How to use checksums |
5848d43f81da24688b370af89d5d6bbfcddf27ba5f084abbdb1847537907bb64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.9.25 Linux/6.1.0-44-amd64
|
Release files / esa_ptr-2.0-py3-none-any.whl
| Download URL | esa_ptr-2.0-py3-none-any.whl |
|---|---|
| Size | 37.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d6a10a9d3344a72797cccf131f9fe99853668697a1a9f4fbc623b1671e6a96b
|
|
BLAKE2b-256 checksum How to use checksums |
e60bfd5fe06a2f07552aa93a3edc80697bbcb4ebca770d458c732370ab8e39a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.2.1 CPython/3.9.25 Linux/6.1.0-44-amd64
|
Security for esa-ptr 2.0
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.