This guide describes how to access, calibrate and derive scientific results from the EIS instrument on Hinode. For a description of EIS and its observing modes please consult the instrument paper, Culhane et al. (2007), and the MSSL Science Centre webpage.
If you are new to Hinode and EIS, please check our guide to Hinode and EIS terminology.
The following sections describe individual steps in going from finding data to deriving scientific results. Below we provide tutorials that take users through these steps for example data-sets.
Tutorial for narrow slit data (1", 2" slits)
Tutorial for slot data (40", 266" slits)
Each country contributing to the Hinode mission provides access to the data through web portals. Each one offers different capabilities and so it is recommended that you try each to familiarize yourself with the methods for searching for data. Web links to the four sites are given below.
In addition, it is possible to download EIS data directly from IDL:NEW! The EIS Mapper site allows you to quickly see where EIS was pointed on a given day, by overplotting on a full disk EUV image.
The large quantity of EIS data coupled with the large number of free parameters (raster size, wavelength windows, slit choice) means that it can be quite difficult to find the perfect data-set if you don't already know which study you want. Check out Tips for finding the perfect data-set to get some hints on searching for data. Also take a look at NEW!the list of most commonly-used EIS studies.
How to find data from the EIS response studies (e.g., flare triggers).
For information about where to store EIS data files on your computer after you've downloaded them, please check EIS Software Note No. 18.
What was EIS doing yesterday? How to find out what EIS observations were being performed yesterday, last week or anytime.
Important dates during the EIS mission. This gives a timeline of significant events during the EIS mission that may affect your data analysis.
Calibration of EIS data is performed with a single IDL routine, EIS_PREP, which converts a level-0 FITS file (raw data) to a level-1 FITS file (calibrated data). Note that the data archives listed above do not distribute level-1 files, so the user needs to perform the calibration. It is highly recommended that the user perform calibration before browsing the data as detector artifacts called warm pixels make browsing the raw data difficult.
The standard call for eis_prep is:
IDL> eis_prep, filename, /quiet, /retain, /default, /saveIMPORTANT NOTE: the /correct_sensitivity keyword is no longer recommended as of 8 October 2013. The recommendation for all EIS files is to use the call above, and then apply a calibration correction factor as a post-processing step. Please check the calibration discussion page for more details. NOTE FOR SLOT DATA: please check calibrating slot data.
An explanation of the eis_prep keywords and a description of the calibration steps performed by eis_prep are available in EIS Software Note No. 1.
eis_prep can take a long time to process a data-set, but it can be speeded up by using a dynamically-loadable module (DLM). Please check out setting up a DLM for eis_prep for more details.UPDATE, 12-Dec-2019: A significant change to EIS_PREP has been made, relating to the removal of residual warm pixels and cosmic rays. Please check out EIS Software Note No. 24 for more details.
For browsing a data-set there are several 'quicklook' tools available that can be accessed by first calling a single IDL widget called XFILES:
The widget allows you to choose an EIS file by manually typing in the path to the EIS file. Make sure to change 'eis_l0_*' to 'eis_l1_*' in the 'Set search filter' box to look for level-1 files rather than level-0 files. After confirming your selection a new widget called XCONTROL pops up which allows the user to access the five quicklook tools:
Control - find basic info on your data, run eis_prep, access QL tools.
Detector - displays detector images.
Browser - allows user to browse the 3D data cubes (wavelength-X-Y) obtained from narrow slit observations.
Spectroheliogram - for a specified line shows a solar-Y vs. wavelength plot for each exposure.
Whisker - for a specified line shows a solar-X vs. wavelength plot for each exposure.
Intensity map - for a specified line shows an intensity image.
A complete data-set is read into IDL as an object as follows:
where 'filename' is the name of the level-1 file (a level-0 file can be read in the same way). The contents of the object can be read and manipulated through a large number of methods and an overview of some of the most useful methods is given below.
The routine EIS_GETWINDATA is also available if you want to extract a single EIS data window into an IDL structure. Some routines (e.g., EIS_AUTO_FIT) require as input the structures produced by EIS_GETWINDATA.
The 1" and 2" slits return emission line spectra and a basic task for such data-sets is to fit Gaussians to the emission lines to return intensity, centroid and width information. Gaussian fitting routines available to EIS users are described below. The routines correct for most instrumental effects, but users should familiarize themselves with some of these effects through the software notes listed below:
There is one important instrumental effect that potentially can affect Doppler shift studies, but for which there is not a software fix at present:
Fitting a Gaussian function to an emission line yields measures of the line intensity, centroid (velocity) and width. Single Gaussian fits to individual lines are possible using EIS object methods, while more sophisticated fitting options are available through the EIS_AUTO_FIT and SPEC_GAUSS_EIS routines available in Solarsoft. Documents describing these routines and giving examples are listed below.
Some emission line ratios are sensitive to the electron density, and software is available to take the line fit structures output by EIS_AUTO_FIT and convert them to electron density maps. The density then allows the emitting column depth of the plasma to be determined which in turn allows the filling factor of the plasma to be estimated. The document below describes how this done, making use of atomic data from the CHIANTI database.
EIS Software Note #15 - Deriving densities from Hinode/EIS data
When line intensities are available from several different ions, then an emission measure (EM) or differential emission measure (DEM) distribution can be constructed. No specific EIS software is available for doing this and so users are referred to software in the CHIANTI database, in particular:
integral_calc.pro: computes an EM value from a single line intensity
chianti_dem.pro: computes a DEM distribution from multiple line intensities
Another popular DEM code is available within the PINTofALE software package.
The EIS slots produce images rather than spectra, and the most common application will be to produce movies from the slot rasters in a range of emission lines.
The data should be calibrated with eis_prep in the same way as narrow slit data. If you're working with slot rasters, then you can assemble the data into a single 2D image within a 'windata' structure with
(see also the slot tutorial).
To create an IDL map from slot rasters, do:
where you'll be asked to choose a wavelength window.
Most EIS users will be analyzing data-sets from multiple instruments and so it is necessary to determine where an EIS raster is positioned relative to the other instruments. Usually the pointing information within an EIS file will not be good enough to accurately co-align data-sets and so cross-correlation will be necessary.
A series of Software Notes have been written that give details about various technical aspects related to the EIS mission. Some of these documents are published are Zenodo and so have a citable DOI. Please use this if you reference the documents in a paper.
Software Note No. 1 - Calibrating EIS data: the EIS_PREP routine (Peter Young) [Zenodo]
Software Note No. 2 - Radiometric calibration (John Mariska)
Software Note No. 3 - Spatial Y-offsets between different wavelengths (spectrum tilt and CCD offset) (Peter Young)
Software Note No. 4 - Slit tilts (Peter Young)
Software Note No. 5 - Orbital variation of EIS wavelength scale (Sugura Kamio, Terje Fredvik, Peter Young)
Software Note No. 6 - Hot and Warm pixels (Louisa Kennedy, Peter Young)
Software Note No. 7 - Instrumental line widths for the narrow slits of EIS (Peter Young)
Software Note No. 8 - EIS Point Spread function (Ignacio Ugarte-Urra)
Software Note No. 9 - EIS Pointing (John Mariska)
Software Note No. 10 - Dark Current (Paul Bryans)
Software Note No. 11 - JPEG Compression (Harry Warren)
Software Note No. 12 - Stray Light (Ignacio Ugarte)
Software Note No. 13 - Interpolation of missing EIS data (Peter Young)
Software Note No. 14 - The EIS Bright Point Trigger (Peter Young, Khalid Al-Janabi)
Software Note No. 15 - Deriving densities, column depths and filling factors from Hinode/EIS data (Peter Young)
Software Note No. 16 - EIS_AUTO_FIT and SPEC_GAUSS_EIS: Gaussian fitting routines for the Hinode/EIS mission (Peter Young) [Zenodo]
Software Note No. 17 - Gaussian fitting examples using the EIS_AUTO_FIT routine (Peter Young)
Software Note No. 18 - EIS data files and directory structure (Peter Young)
Software Note No. 19 - How to access and use the EIS databases (Peter Young)
Software Note No. 20 - EIS/AIA coalignment (John Mariska)
Software Note No. 21 - The WINDATA routines for EIS data analysis (Peter Young)
Software Note No. 22 - EIS Quicklook Data Processing and Timeline Database Retrieval (John Mariska)
Software Note No. 23 - In preparation
Software Note No. 24 - EIS_PREP: removing residual warm pixels and cosmic rays (Peter Young)
Software Note No. 25 - How to search for and download EIS files from IDL (Peter Young)
These documents are also available in the EIS Solarsoft distribution, in $SSW/hinode/eis/doc/eis_notes.