VMMOSSCIENCE(7)

πŸ“¦
version 4.1.7 Β· 2 versions
, in debian bookworm, ubuntu noble

πŸ’– NAME πŸ’–

vmmosscience β€” extraction of scientific spectra ✨

(yes bestie, that's the whole name β€” this page is VMMOSSCIENCE(7) from the vimos recipes collection, iykyk 🫢)


✨ SYNOPSIS ✨

esorex vmmosscience [OPTIONS] FILE.sof

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this recipe is the one that reduces your scientific spectra, and it does it using the extraction mask plus all the products that the recipe vimos_calib made for you. The spectra get bias subtracted, flat fielded (only if a normalised flat field is specified, bestie β€” otherwise no), and then remapped so all those optical distortions get eliminated. The wavelength calibration can optionally be upgraded using a bunch of sky lines, and here's the cute part: if you don't specify a sky lines catalog of wavelengths, an internal one gets used instead. built-in backup, we love to see it πŸ’…

If the alignment to the sky lines is performed, then the input dispersion coefficients table gets upgraded and saved to disk, and a brand new CCD wavelengths map is created. You may also specify a configuration table (typically it depends on the grism in use): this table holds a default recipe parameter setting that controls the way spectra are extracted for a specific instrument mode, and it's literally what's used for the automatic run of the pipeline on Paranal and in Garching. If you do specify this table, it will modify the default recipe parameter setting β€” with the exception of those parameters which have been explicitly modifyed on the command line, because command line said it first, periodt. And if you don't specify a configuration table? Then the input recipe parameter values will always be read from the command line, or from an esorex configuration file if present, or from their generic default values (which are rarely meaningful πŸ™ˆ so like… specify your stuff).

Either a scientific or a standard star exposure can be specified in input β€” dealer's choice, both are valid πŸ’–

Only in case of a standard star exposure input, the atmospheric extinction table and a table with the physical fluxes of the observed standard star must be specified in input, and a spectro-photometric table is created in output. That table can then be input again to this recipe β€” always with an atmospheric extinction table β€” and if a photometric calibration is requested, then flux calibrated spectra (in units of erg/cm/cm/s/Angstrom) are also written in output. iconic behaviour, no cap 🌈


πŸ“₯ Input files πŸ“₯

the vibe check on what you're feeding it:

  • MOS_SCIENCE β€” Type: Raw β€” Scientific exposure β€” Required: Y
  • or MOS_STANDARD β€” Type: Raw β€” Standard star exposure β€” Required: Y
  • MASTER_BIAS β€” Type: Calib β€” Master bias β€” Required: Y
  • SKY_LINE_CATALOG β€” Type: Calib β€” Sky lines catalog β€” Required: . (so, not required)
  • MOS_MASTER_SCREEN_FLAT β€” Type: Calib β€” Normalised flat field β€” Required: . (not required)
  • MOS_DISP_COEFF β€” Type: Calib β€” Inverse dispersion β€” Required: Y
  • MOS_CURV_COEFF β€” Type: Calib β€” Spectral curvature β€” Required: Y
  • MOS_SLIT_LOCATION β€” Type: Calib β€” Slits positions table β€” Required: Y
  • CONFIG_TABLE β€” Type: Calib β€” Configuration table β€” Required: . (not required)

🌟 In case MOS_STANDARD is specified in input,

these three join the group chat:

  • EXTINCT_TABLE β€” Type: Calib β€” Atmospheric extinction β€” Required: Y
  • STD_FLUX_TABLE β€” Type: Calib β€” Standard star flux β€” Required: Y
  • TELLURIC_CONTAMINATION β€” Type: Calib β€” Telluric regions list β€” Required: . (not required)

πŸ”₯ In case a photometric calibration is requested for scientific data,

the following inputs are mandatory, no skipping:

  • EXTINCT_TABLE β€” Type: Calib β€” Atmospheric extinction β€” Required: Y
  • MOS_SPECPHOT_TABLE β€” Type: Calib β€” Response curves β€” Required: Y
If requested for standard star data, the SPECPHOT_TABLE can be dropped: in this case the correction is applied using the SPECPHOT_TABLE produced in the same run. convenient much? πŸ’…

πŸ“€ Output files πŸ“€

quick note before the list, because it matters: the acronym _STD_ replaces _SCI_ and _STANDARD_ replaces _SCIENCE_ in case the input is MOS_STANDARD rather than MOS_SCIENCE πŸŽ€

  • MOS_SCIENCE_REDUCED β€” Data type: Image β€” Extracted scientific spectra
  • MOS_SCI_SKY_REDUCED β€” Data type: Image β€” Extracted sky spectra
  • MOS_SCI_ERROR_REDUCED β€” Data type: Image β€” Errors on extracted spectra
  • MOS_UNMAPPED_SCIENCE β€” Data type: Image β€” Sky subtracted scientific spectra
  • MOS_SCIENCE_EXTRACTED β€” Data type: Image β€” Rectified scientific spectra
  • MOS_SCIENCE_SKY_EXTRACTED β€” Data type: Image β€” Rectified science spectra with sky
  • MOS_SCIENCE_SKY β€” Data type: Image β€” Rectified sky spectra
  • MOS_SCI_UNMAPPED_SKY β€” Data type: Image β€” Sky on CCD
  • MOS_SCI_GLOBAL_SKY_SPECTRUM β€” Data type: Table β€” Global sky spectrum
  • OBJECT_SCI_TABLE β€” Data type: Table β€” Positions of detected objects

🧚 Only if fringing correction is requested (dithered exposures):

  • MOS_SCI_FRINGES β€” Data type: Image β€” Fringe map

⭐ Only if the sky-alignment of the wavelength solution is requested:

  • MOS_SCI_SKYLINES_OFFSETS_SLIT β€” Data type: Table β€” Sky lines offsets
  • MOS_SCI_DISP_COEFF_SKY β€” Data type: Table β€” Upgraded dispersion coefficients
  • MOS_SCI_WAVELENGTH_MAP_SKY β€” Data type: Image β€” Upgraded wavelength map

πŸ‘‘ Only if a MOS_STANDARD is specified in input:

  • MOS_SPECPHOT_TABLE β€” Data type: Table β€” Efficiency and response curves

πŸ’œ Only if MOS_SPECPHOT_TABLE or MOS_MASTER_RESPONSE are specified in input:

  • MOS_SCIENCE_FLUX_REDUCED β€” Data type: Image β€” Flux calibrated scientific spectra
  • MOS_SCI_ERROR_FLUX_REDUCED β€” Data type: Image β€” Errors on flux calibrated spectra
  • MOS_SCIENCE_FLUX_EXTRACTED β€” Data type: Image β€” Flux calibrated slit spectra

✨ OPTIONS ✨

okay bestie this is the part where you customise everything, so grab a snack πŸ“ every single one of these has an EsoRex config-file name too, so you can also just write it in a config file instead of typing it every time. slay.

  • --skyalign <int> β€” polynomial order for aligning those sky lines, or -1 to just... not align them at all (int; default: -1). EsoRex config name: vimos.vmmosscience.skyalign [default = -1].
  • --flatfield <bool> β€” apply flat field (bool; default: True). EsoRex config name: vimos.vmmosscience.flatfield [default = True].
  • --skyglobal <bool> β€” subtract the global sky spectrum from the CCD (bool; default: False). EsoRex config name: vimos.vmmosscience.skyglobal [default = False].
  • --skymedian <bool> β€” sky subtraction from the extracted slit spectra (bool; default: False). EsoRex config name: vimos.vmmosscience.skymedian [default = False].
  • --skylocal <bool> β€” sky subtraction from the CCD slit spectra (bool; default: True). EsoRex config name: vimos.vmmosscience.skylocal [default = True].
  • --cosmics <bool> β€” eliminate cosmic ray hits, and heads up: this only works if global or local sky subtraction is also requested (bool; default: True). EsoRex config name: vimos.vmmosscience.cosmics [default = True].
  • --slit_margin <int> β€” number of pixels to exclude at each slit when doing object detection and extraction (int; default: 3). EsoRex config name: vimos.vmmosscience.slit_margin [default = 3].
  • --ext_radius <int> β€” maximum extraction radius for detected objects, in pixels (int; default: 6). EsoRex config name: vimos.vmmosscience.ext_radius [default = 6].
  • --cont_radius <int> β€” the minimum distance at which two objects of equal luminosity stop contaminating each other, in pixels (int; default: 0). EsoRex config name: vimos.vmmosscience.cont_radius [default = 0].
  • --ext_mode <int> β€” which object extraction method you want: 0 = aperture, 1 = Horne optimal extraction (int; default: 1). EsoRex config name: vimos.vmmosscience.ext_mode [default = 1].
  • --detection <float> β€” object detection threshold, in ADU (float; default: 2.0). EsoRex config name: vimos.vmmosscience.detection [default = 2.0].
  • --resp_fit_nknots <int> β€” number of knots in the spline fitting of the instrument response. (-1: no fitting. -2: read from the grism table) (int; default: -2). EsoRex config name: vimos.vmmosscience.resp_fit_nknots [default = -2].
  • --resp_fit_degree <int> β€” degree of the polynomial when fitting the instrument response. (-1: no fitting. -2: read from the grism table) (int; default: -2). EsoRex config name: vimos.vmmosscience.resp_fit_degree [default = -2].
  • --resp_ignore_mode <str> β€” which types of lines/regions to ignore in the response. Valid ones are Β΄stellar_absorptionΒ΄, Β΄telluricΒ΄ and Β΄command_lineΒ΄ (from the parameter resp_ignore_lines) (str; default: Β΄stellar_absorption,telluric,command_lineΒ΄). EsoRex config name: vimos.vmmosscience.resp_ignore_mode [default = stellar_absorption,telluric,command_line].
  • --resp_ignore_points <str> β€” extra lines/regions to ignore in the response. Give it a comma separated list of values. You can also specify a range like 4500.0-4600.0 (str; default: ´´). EsoRex config name: vimos.vmmosscience.resp_ignore_points [default = ].
  • --resp_use_flat_sed <str> β€” use the flat SED to normalise the observed spectra. Values are true, false, grism_table. (str; default: Β΄grism_tableΒ΄). EsoRex config name: vimos.vmmosscience.resp_use_flat_sed [default = grism_table].
  • --resp_shift <float> β€” the extracted standard star gets shifted by this many angstroms before it's used to compute the response. this one's for when your observed std stars aren't centered in the slits, we've all been there πŸ™ˆ positive values shift the spectrum to the red. The shift is given in Angstroms but no fraction of pixels will be shifted (float; default: 0.0). EsoRex config name: vimos.vmmosscience.resp_shift [default = 0.0].
  • --time_normalise <bool> β€” normalise the output spectra by the exposure time (bool; default: True). EsoRex config name: vimos.vmmosscience.time_normalise [default = True].
  • --anyframe <bool> β€” look for a standard star in any frame classified as MOS_STANDARD (bool; default: False). EsoRex config name: vimos.vmmosscience.anyframe [default = False].
  • --alignment <str> β€” type of alignment of dithered frames, either to the nearest neighbour pixel or to fractions of pixel (str; default: Β΄integerΒ΄). EsoRex config name: vimos.vmmosscience.alignment [default = integer].
  • --stack_method <str> β€” frames combination method (str; default: Β΄averageΒ΄). EsoRex config name: vimos.vmmosscience.stack_method [default = average].
  • --minrejection <int> β€” number of lowest values to be rejected (int; default: 1). EsoRex config name: vimos.vmmosscience.minrejection [default = 1].
  • --maxrejection <int> β€” number of highest values to be rejected (int; default: 1). EsoRex config name: vimos.vmmosscience.maxrejection [default = 1].
  • --klow <float> β€” low threshold in the ksigma method (float; default: 3.0). EsoRex config name: vimos.vmmosscience.klow [default = 3.0].
  • --khigh <float> β€” high threshold in the ksigma method (float; default: 3.0). EsoRex config name: vimos.vmmosscience.khigh [default = 3.0].
  • --kiter <int> β€” max number of iterations in the ksigma method (int; default: 999). EsoRex config name: vimos.vmmosscience.kiter [default = 999].
  • --dither <bool> β€” align dithered frames before stacking (for multiple input frames) (bool; default: True). EsoRex config name: vimos.vmmosscience.dither [default = True].
  • --compute <bool> β€” compute offsets of dithered images from detected objects (true), or read the offsets from the header (false) (bool; default: False). EsoRex config name: vimos.vmmosscience.dither.compute [default = False].
  • --fringing <bool> β€” apply fringing correction, and no cap this one is only for dithered observations (bool; default: True). EsoRex config name: vimos.vmmosscience.fringing [default = True].
  • --offset <float> β€” minimum required offset between exposures for applying the sky fringing correction (float; default: 3.0). EsoRex config name: vimos.vmmosscience.fringing.offset [default = 3.0].
  • --generate_idp <bool> β€” generate IDP products (bool; default: False). EsoRex config name: vimos.vmmosscience.generate_idp [default = False].
πŸ’‘ psst β€” you can totally make a configuration file holding all of these options plus suitable default values, so you never have to type them again. go check the details from the esorex --help command. iykyk.

πŸ‘€ SEE ALSO πŸ‘€

The full documentation for the vimos pipeline can be downloaded as a PDF file using the following URL:

ftp://ftp.eso.org/pub/dfs/pipelines/vimos/vimos-pipeline-manual-6.9.pdf

An overview over the existing ESO pipelines can be found on the web page https://www.eso.org/sci/software/pipelines/.

Basic documentation about the EsoRex program can be found at the esorex (1) man page.

It is possible to call the pipelines from python using the python-cpl package. See https://packages.python.org/python-cpl/index.html for further information.

The other recipes of the vimos pipeline are vimos_ima_bias(7), vimos_ima_dark(7), vimos_ima_det_noise(7), vimos_ima_fringe(7), vimos_ima_science(7), vimos_ima_standard(7), vimos_ima_twilight_flat(7), vmbias(7), vmdark(7), vmdet(7), vmifucalib(7), vmifucombine(7), vmifucombinecube(7), vmifuscience(7), vmifustandard(7), vmmoscalib(7), vmspphot(7) β€” the whole friend group fr fr πŸ’–


🌈 VERSION 🌈

vmmosscience 4.1.7

🫢 AUTHOR 🫢

Carlo Izzo <https://support.eso.org>

😭 BUG REPORTS 😭

Please report any problems to https://support.eso.org. Alternatively, you may send a report to the ESO User Support Department <usd-help@eso.org>.

πŸ‘‘ LICENSE πŸ‘‘

This file is part of the VIMOS Instrument Pipeline Copyright (C) 2019 European Southern Observatory

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA


and that's the whole thing bestie πŸ’… this is vmmosscience version 4.1.7, living its life as the VMMOSSCIENCE(7) page β€” go forth and reduce some spectra, you absolute icon βœ¨πŸ¦‹

πŸ“¦ where this page comes from