Skip to main content

SimCADO - the instrument data simulator for MICADO

Documentation Status Testing Status

Documentation for SimCADO can be found here:

https://readthedocs.org/projects/simcado/

SimCADO in a nutshell

SimCADO is a python package designed to simulate the effects of the Atmosphere, E-ELT, and MICADO instrument on incoming light. The current version (v0.2) can simulate the MICADO imaging modi (4mas and 1.5mas per pixel in the wavelength range 0.7µm to 2.5µm).

Reference Material

Downloading and Installing

For more information, see the the documentation

SimCADO has only been tested in Python 3.x.

It is highly recommended to use Python 3, however the basics of generating images will still work in Python 2.7. We cannot guarantee this though. See the Features page for more info on which functions with which Python version.

The quick way:

$ pip install simcado

The first time in python

>>> import simcado
>>> simcado.get_extras()
>>>
>>> # !! Only works in Python 3 - See Downloads section
>>> simcado.install_noise_cube()

Keeping SimCADO updated

As MICADO developes, the data files that SimCADO uses will also be updated. Therefore before you do any major work with SimCADO we HIGHLY recommend calling:

>>> simcado.get_extras()

Running a simulation in 3 lines

the keyword OBS_EXPTIME has been replaced by OBS_DIT in the latest version of SimCADO

The easiest way to run a simulation is to create, or load, a Source object and then call the .run() command. If you specify a filename, the resulting image will be output to a FITS file under that name. If you do not specify a filename, the output will be returned to the console/notebook as an astropy.io.fits.HDUList object.

To begin, we will import the simcado module (assuming it is already installed).

>>> import simcado

At the very least, we need to create a Source object which contains both spatial and spectral information on our object of interest. Here we use the built-in command .source.source_1E4_Msun_cluster() to create a Source-object for a 10000-Msun stellar cluster. (See Creating Sources for more information).

>>> src = simcado.source.source_1E4_Msun_cluster()

We now pass the source object through SimCADO. This is as easy as calling .run(). If we specify a filename, SimCADO will write the output to disk in the form of a FITS file. If no filename is given, then SimCADO returns an astropy.io.fits object to the console/notebook.

>>> simcado.run(src, filename="my_first_sim.fits")

Changing simulation parameters

The sim.run() also takes any configuration keywords as parameters for running the simulation. For example, the default exposure time for the simulation is 60 seconds, however this can be increased of decreased by using the keyword OBS_DIT (and/or combining it with OBS_NDIT). A stacked 6x 10 minute observation sequence would look like:

>>> simcado.run(src, filename="my_first_sim.fits", OBS_DIT=600, OBS_NDIT=6)

That's it. Of course SimCADO can also go in the other direction, providing many more levels of complexity, but for that the reader is directed to the examples pages and/or the API documentation

SimCADO building blocks

For a brief explanation of how SimCADO works and which classes are relevant, please see either the Getting Started or SimCADO in depth section.

Bugs and Issues

We freely admit that there may still be several bugs that we have not found. If you come across an buggy part of SimCADO, please please tell us. We can't make SimCADO better if we don't know about things.

The preferable option is to open an issue on our Github page: astronomyk/SimCADO/issues, or you can contact either one of us directly.

Please always include the output of

>>> simcado.bug_report()

Contact

For questions and complaints alike, please contact the authors:

Developers (Vienna): Kieran Leschinski, Oliver Czoske, Miguel Verdugo

Data Flow Team Leader (Gronigen): Gijs Verdoes Kleijn

MICADO home office (MPE): http://www.mpe.mpg.de/ir/micado

Metadata

Release files for SimCADO 0.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for SimCADO 0.7
File Size Uploaded Provenance
SimCADO-0.7.tar.gz 15.4 MB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for SimCADO 0.7
File Interpreter ABI Platform
SimCADO-0.7-py3-none-any.whl Python 3 none any Details

Total release size: 15.5 MB

Release files / SimCADO-0.7.tar.gz

Download URL SimCADO-0.7.tar.gz
Size 15.4 MB
Tags Source
SHA-256 checksum
How to use checksums
0f7bc630646c6a74e97db6c6e903f66b7942b5314152ece6c99276303b3a0d67
BLAKE2b-256 checksum
How to use checksums
24ad0e2a267dfef9da5c6397c539ccf93b6024130251c9b9433dd8cf5cde4b0e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.6.8

Release files / SimCADO-0.7-py3-none-any.whl

Download URL SimCADO-0.7-py3-none-any.whl
Size 122.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3ce83cb4ee784f55e1d1014bb049a15e8c8e5de1df28141411ad96ac27cd9eec
BLAKE2b-256 checksum
How to use checksums
49827cb04c76e83d0b37299aa5a7044c6ae5bb810aaa57d5b3ff91a3779e3032
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.6.8

Security for SimCADO 0.7

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page