MAVISIM
Image simulating tool for the next generation ESO instrument MAVIS. If you use MAVISIM please cite Monty et al. 2021.
Getting started
For full documentation, see mavisim.readthedocs.io. To get started, install via pip:
pip install mavisim
and use the CLI:
mavisim --help
which should output something like:
usage: mavisim [-h] [-o OUTPUT] [-d DISTS] [--static STATIC] [--header HEADER] field psfs
mavis image simulator
positional arguments:
field file containing source field to simulate
psfs specify PSFs fits file on disk to use in simulation
options:
-h, --help show this help message and exit
-o OUTPUT, --output OUTPUT
specify name for output fits file
-d DISTS, --dists DISTS
specify distortion file on disk to pre-distort sources with
--static STATIC, -s STATIC
use only 1 psf (not field varying), at the given psf fits hdu index
--header HEADER dict to be parsed as header for saved fits file
Current Version
1.1 - EtE PSF - more accurate representation of the PSF, suitable for photometric and astrometric science cases
Documentation can be found here
Past Versions
1.0 - Fourier PSF - fast, most flexibility for astrometric modeling
Documentation can be found here
General Features
- Can simulate full stellar field (eg. Milky Way Globular Cluster) from an input catalogue
- Models three major sources of astrometric error introduced by the AO system:
- Tip-tilt residuals originating from uncorrected LO aberrations (dependent on the NGS constellation brightness and geometry) field variable
- HO aberrations originating from the LGS constellation and characteristics field variable
- Static field distortion originating from the AO module optics
Current Limitations
- Monochromatic images only
- Only compatible with input point source catalogues only
Future Versions
MAVISIM 1.2: Broadband End-to-End PSF
Broadband images! Starting with the V band
MAVISIM 2.0
Extended object version, not yet in development.
Metadata
Release files for mavisim 1.1.20
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 |
|---|---|---|---|---|
| mavisim-1.1.20.tar.gz | 42.0 kB | Without provenance | Details for mavisim-1.1.20.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mavisim-1.1.20-py3-none-any.whl | Python 3 | none | any | Details for mavisim-1.1.20-py3-none-any.whl |
Total release size: 77.9 kB
Release files / mavisim-1.1.20.tar.gz
| Download URL | mavisim-1.1.20.tar.gz |
|---|---|
| Size | 42.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b6390764cce1eb1fcf3b9d3d3cbb6e1cff3ad17fac933949d43e74edc51b2311
|
|
BLAKE2b-256 checksum How to use checksums |
87759b7705e948dbfec1b5bccdf0fc03929e9de0b8addd4be82525eb12d364f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.2
|
Release files / mavisim-1.1.20-py3-none-any.whl
| Download URL | mavisim-1.1.20-py3-none-any.whl |
|---|---|
| Size | 35.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9096f7615f8578ca771a9de12783f5a1c00a374dccfb7c7602bada3cd306504
|
|
BLAKE2b-256 checksum How to use checksums |
36453ac86aa1920d67840a74a4be699ae70649da2a46995a8246571da205b190
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.2
|
Security for mavisim 1.1.20
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.