VMDET(7)

📦
version 4.1.7 · 2 versions
, in debian bookworm, ubuntu noble

💅 VMDET ✨ (the vmdet recipe, section 7 of the vimos recipes manual, bestie)

ok so. sit down. hydrate. we're doing detector physics today and honestly? it's giving iconic. 🎀

🌸 NAME 🌸

vmdet — Determine RON, gain, and bad pixels from a set of flat field exposures.

like. it figures out your detector's whole personality. no cap. 🔥

✨ SYNOPSIS ✨

esorex vmdet [OPTIONS] FILE.sof

that's it. that's the whole vibe. one recipe, one SOF file, a dream. 💫

🦋 DESCRIPTION 🦋

okay so bestie, this recipe is the one that estimates the read-out-noise (RON) and the gain of the CCD, and also figures out where all the bad pixels are hiding. three jobs. one recipe. main character energy fr fr.

Your input SOF needs to have at least five pairs of flat field exposures, and here's the important part — they all have to belong to the same quadrant, and each pair has to correspond to a different exposure time. Like a lil matching set. 🧚

The flat fields can be produced either in imaging or in MOS mode. In MOS mode a HR grism is used, so that the CCD gets illuminated also beyond the central region that direct imaging mode uses — but heads up, no mask is inserted at the telescope focal plane. (the way that grism just... does all that 😭)

ngl this type of exposure cannot really be considered a spectral flat field, because the CCD is exposed to white light — meaning there's no wavelength dependency along the dispersion direction. it's flat-flat. plain. unbothered. 💅

The flat fields generated for the purpose of determining the detector properties get assigned the DO category DETECTOR_PROPERTIES, so we can tell them apart from the more common IMG_SCREEN_FLAT or MOS_SCREEN_FLAT that are used to produce master calibrations. different flat, different job, iykyk. ✨

Input files:

  • DO category: DETECTOR_PROPERTIES — Type: Raw — Explanation: Flat field — Required: Y
  • DO category: MASTER_BIAS — Type: Calib — Explanation: Master bias — Required: Y

Output files:

  • DO category: CCD_TABLE — Data type: FITS table — Explanation: Bad pixel table
  • DO category: (none) — Data type: FITS image — Explanation: Bad pixel image
  • DO category: (none) — Data type: FITS image — Explanation: Error image

And here's the tea 🍓: only the primary product, the bad pixel table, is copied (or moved) to the product directory. The other products are generated only on request — typically for debug purposes — and they don't get assigned a DO category, because they wouldn't be used anywhere in further data processing steps. they're just there for the lore. 🙈

For more details, please refer to the VIMOS Pipeline User´s Guide. (yes bestie, actual documentation, go read it, it's good for you 💜)

💖 OPTIONS 💖

five options. all bangers. let's go. 🌈

  • --CreateBadPixelMap <bool> — Bad pixel map creation (bool; default: True). The full name of this option for the EsoRex configuration file is vimos.Parameters.map [default = True].
  • --CreateErrorImage <bool> — Response slope uncertainty map creation (bool; default: False). The full name of this option for the EsoRex configuration file is vimos.Parameters.error [default = False].
  • --DetectionThreshold <float> — Threshold in determination of bad pixels (float; default: 5.0). The full name of this option for the EsoRex configuration file is vimos.Parameters.threshold [default = 5.0].
  • --DetectionMode <str> — Bad pixel detection method (str; default: ´Intolerant´). The full name of this option for the EsoRex configuration file is vimos.Parameters.method [default = Intolerant].
  • --ComputeQC <bool> — Compute QC1 parameters. (bool; default: True). The full name of this option for the EsoRex configuration file is vimos.Parameters.quality.enable [default = True].
💡 note that it is possible to create a configuration file containing these options, along with suitable default values. Please refer to the details provided by the 'esorex --help' command. (go on, run it, it's free 🫶)

👀 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. (python girlies we are SO back 🐍✨)

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), vmifucalib(7), vmifucombine(7), vmifucombinecube(7), vmifuscience(7), vmifustandard(7), vmmoscalib(7), vmmosscience(7), vmspphot(7)

the whole squad. the friend group. every single one of them ate. 👑

⭐ VERSION ⭐

vmdet 4.1.7

🎀 AUTHOR 🎀

ESO VIMOS Pipeline Team <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>.

fr fr if something's broken, tell them. they wanna know. don't suffer in silence bestie 💜

📜 LICENSE 📜

This file is part of the VIMOS Instrument Pipeline Copyright (C) 2002-2005 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., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA

okay that's the whole page!! 💖 this was vmdet, version 4.1.7, from the vimos recipes collection — documented by the ESO VIMOS Pipeline Team, and the manual itself lives at the footer of VMDET(7). ty for coming to my ted talk, go determine some bad pixels, slay, periodt. 🦋✨👑

📦 where this page comes from