https://github.com/astarvienna/irdb
A database containing instrument data for infrared telescopes
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (14.1%) to scientific vocabulary
Repository
A database containing instrument data for infrared telescopes
Basic Info
Statistics
- Stars: 8
- Watchers: 11
- Forks: 9
- Open Issues: 45
- Releases: 0
Metadata Files
README.md
ScopeSim's Instrument reference database
This repository contains the data files needed by ScopeSim to create a model of
any given optical train.
The data is split in the following way:
- Primary observing packages
e.g. Instruments
Primary packages are complete packages which can be used by scopesim to
simulate the readout files from a full optical system
(i.e. atmosphere + telescope + relay optics + instrument + detector)
These packages contain all information regarding the internal working of the instrument, such as optics, detectors, properties (e.g. temperature), etc
- Support packages
e.g: Telescopes / Observing sites / Relay optics
These packages only contain information pertaining to the effects generated by the specific set of optics contained within the optical subsystem. These packages are used to support the Primary packages, and can be shared between multiple primary instrument package.
For example, the ELT package cannot be used to generate images on its own, however it is need by both the MICADO and METIS instument packages.
- PSFs
Currently PSFs are kept separately, simply due to their size
Packages kept here
- Armazones
- ELT
- MORFEO
- MICADO
- METIS (under construction)
Status of packages
Detailed information on the test suite can be found in the
Contributing
The IRDB is closely tied to ScopeSIM. The following development workflow is therefore used:
- The IRDB master branch should always work with the ScopeSIM master branch, similarly with the dev_master branches.
- The dev_master branch should always be ahead of the master branch.
- Feature branches are used to introduce new features and these are branched from devmaster, and merged into devmaster.
- Merging a feature branch into devmaster is only allowed if all tests against ScopeSIM devmaster succeed.
- Merging a feature branch into dev_master should preferably require a review from a second set of eyes to avoid accidents.
- devmaster is merged into master whenever ScopeSIM devmaster is merged into master.
Owner
- Name: A*Vienna
- Login: AstarVienna
- Kind: organization
- Location: Vienna. Austria
- Repositories: 10
- Profile: https://github.com/AstarVienna
GitHub Events
Total
- Create event: 44
- Release event: 1
- Issues event: 15
- Watch event: 1
- Delete event: 47
- Issue comment event: 75
- Push event: 118
- Pull request review comment event: 20
- Pull request review event: 45
- Pull request event: 85
- Fork event: 2
Last Year
- Create event: 44
- Release event: 1
- Issues event: 15
- Watch event: 1
- Delete event: 47
- Issue comment event: 75
- Push event: 118
- Pull request review comment event: 20
- Pull request review event: 45
- Pull request event: 85
- Fork event: 2
Dependencies
- actions/checkout v2 composite
- actions/setup-python v2 composite
- actions/checkout master composite
- gaurav-nelson/github-action-markdown-link-check v1 composite
- actions/checkout v4 composite
- actions/setup-python v5 composite
- actions/upload-artifact v4 composite
- actions/checkout v4 composite
- actions/setup-python v5 composite