Advanced Data Reduction Techniques for MUSE

Advanced Data Reduction Techniques for MUSE

Abstract

MUSE, a 2nd generation VLT instrument, will become the world’s largest integral field spectrograph. It will be an AO assisted instrument which, in a single exposure, covers the wavelength range from 465 to 930 nm with an average resolution of 3000 over a field of view of 1’1’ with 0.2” spatial sampling. Both the complexity and the rate of the data are a challenge for the data processing of this instrument.
We will give an overview of the data processing scheme that has been designed for MUSE. Specifically, we will use only a single resampling step from the raw data to the reduced data product. This allows us to improve data quality, accurately propagate variance, and minimize spreading of artifacts and correlated noise. This approach necessitates changes to the standard way in which reduction steps like wavelength calibration and sky subtraction are carried out, but can be expanded to include combination of multiple exposures.

\paperID

8B.3

\affil

Astrophysikalisches Institut Potsdam, An der Sternwarte 16, D-14482 Potsdam, Germany \affilCentre de Recherche Astronomique de Lyon, 9 Avenue Charles André, 69561 Saint Genis Laval, France

\contact

Peter Weilbacher \emailpweilbacher@aip.de

\paindex

Weilbacher, P. M. \aindexGerssen, J. \aindexRoth, M. M. \aindexBöhm, P. \aindexPécontal-Rousset, A.

\keywords

data!processing, data!reduction, methods!algorithms, datacube, instrumentation!pipeline

1 The Instrument

MUSE is planned to be a giant integral field spectrograph and going to be commissioned as a second generation VLT instrument starting in 2012. Its 1\arcmin1\arcminfield of view is sampled at 0\farcs2 resolution in wide-field mode. In the adaptive-optics supported mode, observing in a narrow-field mode with sampling at 0\farcs75 is possible. Each exposure delivers about 90000 spectra, using 24 slicer integral field units (IFUs), each equipped with a separate 4k CCD. The full wavelength range from 465 to 930 nm is covered with resolution between 2000 and 4000.

The light at the VLT focal plane is divided into 24 sub-fields, each of which has a size of 60\arcsec2\farcs5 on the sky. Within each IFU, the sub-field is then further decomposed into 48 slices. Each slice has a size of 15\arcsec0\farcs2 on the sky. The spectrograph in each IFU disperses the light and focuses the spectral pattern on a 4k4k CCD. This means that the data appears on the CCDs as 48 strips of spectra which are 75 px wide and 4096 px high. In between these strips of data, dark regions of 6 px width can be used to identify stray-light.

Each raw exposure has a size of roughly 800 MB; by using the full capabilities of the Euro3D format, a processed exposure can require about 4.5 GB of storage. Typical observing nights will have 50 GB of raw data per night (calibrations plus science exposures), but the data rate may be as high as 150 GB per night. Each exposure will contain approximately 350 million illuminated pixels.

2 The Data Processing Pipeline

The main goals of the MUSE data processing pipeline are to fully reduce all exposures into ready-to-use datacubes (Euro3D format or FITS with NAXIS=3) without creating a backlog (a requirement on scope of the reduction and the speed), to track bad pixels, propagate error information, and to minimize the rebinning steps. Especially the last two goals are connected and not yet commonly implemented in existing data reduction systems. We therefore discuss the details in the following sections.

2.1 Noise Propagation

We take the approach of Gössl & Riffeiser (2002) and estimate the variance from the raw data:

The terms describe the read-out noise, the error of the read-out noise estimate, and the photon noise of each pixel.

This variance is then tracked through all processing steps using Gaussian error propagation. This approach assumes that the CCD pixels are uncorrelated which should be true to first order. During data analysis, the variance, together with the data value itself, makes it possible to directly read off the S/N estimate at each position in the output datacube.

2.2 One-step Resampling

If we followed the classical approach to determine a calibration function for one type of distortion and applied it (requiring resampling), before determining the next one, MUSE data would have to be resampled four to five times. Every resampling step always adds noise to a dataset. To be able to display and analyze data one always needs a rectangular format, so at least one resampling step has to be carried out. Resampling more than once complicates the noise propagation, passing it through five steps is near impossible.

The approach we use for the one-step resampling is centered around what we call a “pixel table” (Davies 2007 describes a very similar approach that was developed for the KMOS instrument). This table contains a list of all illuminated pixels (the data value, the bad pixel status, and the variance) of one exposure together with the coordinates (, , and ). As soon as first estimates of the three coordinates are known, i. e. following tracing and wavelength calibration, the CCD-based data is transfered into such a pixel table.

Once the data are listed in the pixel table, each transformation that would classically require an interpolation step can then be carried out just by changing the coordinates of each table entry. Shifting the data (such as done when combining multiple exposures) just adds a constant to the column representing the spatial axis; tilting it (as needed to correct for differential atmospheric refraction) applies a function to both spatial axes. Astrometric calibration can be carried out by replacing pixel values in the two spatial axes with values of RA and DEC (using a function describing an astrometric solution).

To determine the function that needs to be applied to the dataset for a given transformation one in most cases needs to resample the data already into a datacube. An example is the flux calibration where the standard star exposure needs to be concerted to a datacube before one can measure the flux for each wavelength to derive the response function. But as the intermediate datacubes are generated of auxiliary data and are not used after the measurement, this does not affect the data quality of the science data. Additionally, for some operations it is possible to generate the temporary datacube with coarse resolution, and should therefore not have a large impact on the speed of the operation when compared to the classical approach.

2.3 Final Resampling

The final resampling involves the transformation from the pixel table to the datacube. The problem here is that due to instrumental distortions the data are irregularly spaced. It is difficult to find neighboring pixels needed to interpolate.

A naive approach to this problem is to search through the table to find the closest point(s) to be interpolated onto the output grid point. This means to search millions of pixels repeatedly, to compute the distances to the output grid point. For the data of only one MUSE IFU (15 million pixels) this process takes more than a week. This method can be sped up to only take hours when using knowledge of the instrument geometry and a system of hierarchical lookup tables so that one can restrict the search to a few thousands of pixels for each output point.

Research of other existing algorithms that resample irregular data on an output grid shows that all of them use nested loops and so work efficiently only for sets of small size. Hence, we developed our own algorithm that only uses “flat” loops. In this scheme, which we call “grid cell” approach, we first sort all pixels into a three-dimensional array that represents the output grid. Each input pixel is assigned to the nearest output grid point. This means that while in some cases none or more than one pixel are located in each grid point, it is still easy and fast to find neighboring pixels. And if the grid is well chosen for the input data, every grid cell will on average contain one input pixel.

We plan to implement a few interpolation algorithms. The simplest one, nearest neighbor, is almost trivial to implement, and the fastest possible scheme. The whole conversion from the pixel table to the output datacube takes only about 30 s per MUSE IFU. Another interpolation to be implemented is a distance-based weighting method. For this, we will use a modified inverse square law for interpolation: . This function is taken from Renka (1988) and vanishes at a cutoff radius , so that interpolation can be restricted to the nearest 6 () or 26 () grid cells. Finally, Kriging (Krige 1951) and sinc interpolation are candidates for further resampling techniques, but at this point it is not clear if they are usable with MUSE data.

3 Pipeline Implementation

The MUSE data processing system will be implemented in the ESO context, as plugin (“recipes”) to esorex, Gasgano, or Reflex (Hook et al., 2008). The code will be written in C and use the Common Pipeline Library (CPL) provided by ESO.

The pipeline will consist of a basic level of data reduction (bias, dark, and flat-field combination, wavelength calibration, application of calibration to science data), handling data on the basis of each integral field unit, i.e. per CCD, separately. The second level is required to derive scientifically usable data and will work on data from all units (across all sub-fields) simultaneously. This part consists of a complex procedure to determine the relative position of each slice within the field of view (the “geometry”), and on-sky calibration procedures like standard star reduction, handling of separate sky and astrometric exposures, as well as combination of multiple exposures into the final output datacube.
The basic level of reduction can be trivially parallelized, running multiple reduction processes at the same time. The second level is designed to use OpenMP to run several processing threads in parallel while processing the data across all 24 sub-fields.

4 Summary

The combination of high data rate and the very complex structure makes it difficult and possibly very time consuming to handle MUSE data.

The “one-step resampling” approach presented here is conceptually simple. In this scheme it is necessary to carry out additional steps to be able to perform the same tasks as in the classical reduction approach. CPU and memory requirements are therefore higher, but the improved data quality and the knowledge of variance make this a suitable method for MUSE data processing.

The final design review of the MUSE instrument is going to take place in March 2009. Following this date, the data reduction system will be implemented to be ready for commissioning starting end of 2012.

\acknowledgments

PMW acknowledges support by the German Verbundforschung through the MUSE/D3Dnet project (grant 05A08BA1). Discussions with Richard Davies and Jarle Brinchmann were important to develop and improve the resampling algorithm.

{references}\reference

Davies, R., 2007, in: The 2007 ESO Instrument Calibration Workshop, in press \referenceGössl, C. A. & Riffeser, A., 2002, A&A 381, 1095 \referenceHook, R., Romaniello, M., Ullgrén, M., et al., 2008, The Messenger 131, 42 \referenceKrige, D. G., 1951, Master’s thesis, University of Witwatersrand \referenceRenka, R., 1998 ACM 14, 151

Comments 0
Request Comment
You are adding the first comment!
How to quickly get a good reply:
  • Give credit where it’s due by listing out the positive aspects of a paper before getting into which changes should be made.
  • Be specific in your critique, and provide supporting evidence with appropriate references to substantiate general statements.
  • Your comment should inspire ideas to flow and help the author improves the paper.

The better we are at sharing our knowledge with each other, the faster we move forward.
""
The feedback must be of minumum 40 characters
Add comment
Cancel
Loading ...
108110
This is a comment super asjknd jkasnjk adsnkj
Upvote
Downvote
""
The feedback must be of minumum 40 characters
The feedback must be of minumum 40 characters
Submit
Cancel

You are asking your first question!
How to quickly get a good answer:
  • Keep your question short and to the point
  • Check for grammar or spelling errors.
  • Phrase it like a question
Test
Test description