KMOS Instrument KMOS Instrument Overview & Data Overview & Data

ProcessingProcessingRichard Davies

Max Planck Institute for Extraterrestrial Physics

What does KMOS do?

When will it do it?

What does the data look like?

How is the data processed?

What & When?What & When?

• Phase B start July 2004

• Preliminary Design Review May 2006

• Final Design Review July 2007

• Preliminary Acceptance Europe Spring 2010

• Preliminary Acceptance Chile Autumn 2010

2m

2800kg

Science DriversScience Drivers• Investigate the physical processes which drive galaxy formation and

evolution over redshift range 1<z<10• Map the variations in star formation histories, spatially resolved star-

formation properties, and merger rates• Obtain dynamical masses of well-defined samples of galaxies across a

wide range of environments at a series of progressively earlier epochs

need: multiplexing (large numbers of sources), NIR (optical diagnostics at z>1), moderate spectral resolution (kinematics), integral field (mergers vs disks)

Instrumental FeaturesInstrumental Features

• R~3500 spectroscopy at 0.8-2.5m

• 7.2arcmin patrol field• 24 robotic pickoff arms,

each with a 2.8”×2.8” FoV sampled at 0.2 arcsec

• IFUs are consolidated in groups of 8

• each set feeds one of 3 identical spectrographs

pick off mirror (covered)

roof mirror

to K-mirror & filter wheel

multiple-object cryogenic integral field spectrograph

Instrumental FeaturesInstrumental Features

• 24 arms in 2 layers, 20mm above & below focal plane

• positioning within 0.1” (<60μm)• mass ~4.5kg each• size ~30cm• each path has 45 optical surfaces• in total 1080 optical surfaces and 60 cryogenic motors

Fixed instrument configuration:

Non-configurable item Options available

Pixel scale 0.2arcsec x 0.2arcsec

Field of View 2.8arcsec x 2.8arcsec

Observing mode integral field spectroscopy

Spatial resolution mode seeing limited

Configurable item Options available

Filter (bandpass) KHYJIzHK

1.95-2.50μm1.45-1.85μm0.975-1.33μm0.80-1.15μm 1.5-2.38μm

R ~ 3700R ~ 3900R ~ 3300R ~ 2800R ~ 2200

Instrumental Configuration(s)Instrumental Configuration(s)

Instrument configuration options:

Raw Data FormatRaw Data Formatfirst RTD: raw data from the 3 2k×2k detectors

wav

elen

gth

spatial position

14 pixels per slitlet (plus a gap)14 slitlets per IFU8 IFUs per detector3 detectors

IFU 1 IFU 2

Reconstructed ImagesReconstructed Images

second RTD: reconstructed images for each of the 24 IFUs

either arrayed in a grid

Reconstructed ImagesReconstructed Images

second RTD: reconstructed images for each of the 24 IFUs

or positioned in the 7.2’ patrol field

Association MapAssociation Map

calibration templates & recipes:

kmo_darkkmo_flatkmo_illuminationkmo_spec_alignkmo_wave_calkmo_std_star

KMOS_spec_cal_darkKMOS_spec_cal_calunitKMOS_spec_cal_skyflatKMOS_spec_tec_verticalslitKMOS_spec_cal_waveKMOS_spec_cal_std

Templates & RecipesTemplates & Recipes

science templates & recipes:

kmo_rtd_image

kmo_sci_red

any acquisition frame

KMOS_spec_obs_nodtoskyKMOS_spec_obs_stareKMOS_spec_obs_mapping

note: reconstruction works on 1 IFU at a time (i.e. in effect recipe runs 24 times for each data set).

Basic Tools used in recipes:

kmo_create_cubekmo_set_valuekmo_arithmetickmo_statskmo_copykmo_rotatekmo_shiftkmo_flip_axiskmo_euro3D_convert

More Complex Tools used in recipes:

kmo_reconstructkmo_make_imagekmo_extract_speckmo_combinekmo_sky_mask*kmo_sky_tweak*kmo_bkg_sub*kmo_fit_profilekmo_cosmic*†

Additional (Advanced) Tools:

kmo_extract_pv*kmo_fit_continuumkmo_extract_moments*kmo_convolvekmo_mediankmo_voronoi*

* = prototype version in use for SINFONI data

† = based on ‘L.A.Cosmic’ by P. van Dokkum

other Recipesother Recipes

• Modular design also useful to observer when re-processing their data back home

Recipe HierarchyRecipe Hierarchy

What KMOS will & won’t doWhat KMOS will & won’t do

Things we will do (and think are a good idea)

keep everything modular so astronomers can add in their own extra processing steps or leave some out

provide basic tools so astronomer can manipulate their datacubes provide some more advanced tools to extract information from a datacube (e.g. emission line kinematics, Voronoi binning, etc)

Things we won’t be providing

a 3D data viewing tool (since there are already many good ones, e.g. QFitsView)

tools for deconvolution, line deblending, extracting stellar kinematics, etc (because they’re very user/data/model dependent) mosaicing tool – it will be possible to combine datacubes with the right offsets to make a larger field, but no scaling/background adjustments will be made