P2 Execution Sequence Merger
This tool allows to merge the execution sequence of two (or more) ESO instruments (e.g., HARPS and NIRPS) and to visualize the observability of the targets over the night. It also keeps track of already observed targets.
Installation
The p2esm package can be installed using pip with the following command:
pip install p2esm
Settings
You first need to create a p2esm.toml config file.
The p2esm application looks for this file either in the current folder or in the ~/.config folder.
A sample p2esm.toml is provided here.
Default parameters are set for observing with HARPS and NIRPS at La Silla.
The user and password should be the same as the ones used to login on the ESO P2 website.
Usage
- Launch
p2esmand login on P2 with your navigator. - Add OBs in the execution sequences (in the navigator). You should see them appear in
p2esm's plot. - Right click on the plot to set the observations starting time.
- Once the observations have started,
p2esmkeeps track of the currently running OB and the starting time should be updated automatically. - Left click on an OB to switch instruments just after this OB.
- Black vertical lines highlight instrument changes.
- The red vertical line shows the current time.
- Already exectuted OBs are shown with pale colors. It may happen from time to time that an executed OB disappears (ticket open at ESO Helpdesk), it does not mean that the OB failed.
- Scheduled OBs that do not fulfill the airmass or moon separation constraints or cross the zenith are highlighted with dotted lines.
p2esmis only a visualization tool. It does not affect the execution sequences in any way and it does not warn the TO of the instrument changes you schedule.- You can close
p2esm, reopoen it at any time. The execution sequences will be reloaded, but you will lose the scheduled instrument changes.
Contribute
Everyone is welcome to open issues and/or contribute code via pull-requests. A SWITCH edu-ID account is necessary to sign in to https://gitlab.unige.ch. If you don't have an account, you can easily create one at https://eduid.ch. Then you can sign in to https://gitlab.unige.ch by selecting "SWITCH edu-ID" as your organisation.
Metadata
Release files for p2esm 0.1.5
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 |
|---|---|---|---|---|
| p2esm-0.1.5.tar.gz | 22.6 kB | Without provenance | Details for p2esm-0.1.5.tar.gz |
Release files / p2esm-0.1.5.tar.gz
| Download URL | p2esm-0.1.5.tar.gz |
|---|---|
| Size | 22.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
954158c331f846356bd28c1bee2478f34e5d24c3fc281f77d17cf112a81d8f8a
|
|
BLAKE2b-256 checksum How to use checksums |
ce12d68df0954372d1e52e0a9c2f0b487824027b90080a9effff20b2d07cd819
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for p2esm 0.1.5
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.