Skip to content

Move laser parameters to config yaml - #369

Draft
oczoske wants to merge 3 commits into
dev_masterfrom
oc/metis_lasers
Draft

Move laser parameters to config yaml#369
oczoske wants to merge 3 commits into
dev_masterfrom
oc/metis_lasers

Conversation

@oczoske

@oczoske oczoske commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Laser wavelengths and powers are now in metis_wcu_config.yaml instead of hard-coded in ScopeSim. N-band lasers still to be added. Also documentation in notebook to be done.

@oczoske
oczoske requested a review from janusbrink August 11, 2026 16:22
@oczoske oczoske self-assigned this Aug 11, 2026
@oczoske oczoske added documentation Improvements or additions to documentation instrument-specific Limited to a certain IRDB instrument package instrument definition Addition or modification of instrument YAMLs METIS AIT Issues related to METIS AIT simulations labels Aug 11, 2026
Comment thread METIS/metis_wcu_config.yaml Outdated
# ------------- Available lasers
laser_l_wave: 3.39 # [um]
laser_l_power: 5e-3 # [W]
laser_t_wave: [4.70] # [um], array

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we could keep the default tuneable laser line list as it was in ScopeSim that would help:
laser_t_wave: [4.68 4.69 4.7 4.71 4.72 4.73 4.74 4.75 4.76 4.77 4.78]

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made it a round 10 lines, so 4.77 is the bluest, if that's alright.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation instrument definition Addition or modification of instrument YAMLs instrument-specific Limited to a certain IRDB instrument package METIS AIT Issues related to METIS AIT simulations

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants