This page (revision-13) was last changed on 07-Dec-2016 14:14 by Peter Young

This page was created on 24-Feb-2010 18:15 by PeterYoung

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
13 07-Dec-2016 14:14 2 KB Peter Young to previous
12 24-Aug-2012 22:18 2 KB Peter Young to previous | to last
11 24-Aug-2012 22:15 2 KB Peter Young to previous | to last
10 28-Jun-2011 19:17 2 KB Peter Young to previous | to last
9 04-Aug-2010 21:40 1 KB PeterYoung to previous | to last
8 07-Jul-2010 19:34 1 KB PeterYoung to previous | to last
7 17-Mar-2010 21:33 1 KB PeterYoung to previous | to last
6 24-Feb-2010 22:22 1 KB PeterYoung to previous | to last
5 24-Feb-2010 22:19 1 KB PeterYoung to previous | to last
4 24-Feb-2010 22:09 1 KB PeterYoung to previous | to last
3 24-Feb-2010 18:32 1 KB PeterYoung to previous | to last
2 24-Feb-2010 18:29 1 KB PeterYoung to previous | to last
1 24-Feb-2010 18:15 1 KB PeterYoung to last

Page References

Incoming links Outgoing links
NarrowWorksheet2
NarrowWorksheet2

Version management

Difference between version and

At line 1 changed 3 lines
[{ALLOW edit EISMainUsers}]
[{ALLOW view Anonymous}]
!!!Worksheet 2 - Calibrating EIS data (eis_prep)
!!!Worksheet 2 - Reading and browsing data
At line 5 changed one line
In general the user should calibrate EIS data before he/she attempts to look it. This is because EIS data are affected by warm pixels on the CCD which make it difficult to study the images. The EIS calibration routine is called 'eis_prep'.
The EIS FITS file to be used in all the worksheets is from 9-Dec-2007, 11:30 UT:
At line 7 changed one line
For the present worksheets we will analyze a data-set taken on 2006 December 9 at 11:30. Worksheet 1 described how to download this file. If it's still in your working directory, then do:
filename=’eis_l0_20061209_113031.fits’
At line 9 changed 3 lines
{{{
IDL> filename=’eis_l0_20061209_113031.fits’
}}}
(NOTE: you may need to add the path name, depending on where the file is located.)
At line 13 changed one line
If you defined the $HINODE_DATA directory and moved the file there, then you can do:
To read an EIS FITS file from the command line, type:
At line 15 changed 3 lines
{{{
IDL> filename=eis_find_file('9-dec-2006 11:30')
}}}
IDL> data=obj_new(‘eis_data’,filename)
At line 19 changed one line
The standard call to eis_prep is:
data is an IDL object. You can extract information from the object using various methods. E.g.,
At line 21 changed 3 lines
{{{
IDL> eis_prep, filename, /default, /save, /retain, /quiet
}}}
IDL> exp=data->getexp()\\
IDL> xpos=data->getxpos()\\
IDL> wd0=data->getvar(0)\\
At line 25 changed one line
The /save keyword results in two files being created in the user's directory which have the names:
wd0 is a 3D array containing the window data for the specified window (0 in this case). You can get a list of all methods by doing:
At line 27 changed 4 lines
{{{
eis_l1_20061209_113031.fits
eis_er_20061209_113031.fits
}}}
IDL> data->display_methods
At line 32 changed one line
TIP: it is a good idea to compress these files with gzip.
To extract the header into a string array, do:
At line 34 changed one line
(If you defined the $HINODE_DATA environment variable in Worksheet 1, then use the eis_ingest.pro routine to transfer the files into your data directory.)
IDL> hdr_obj=data->gethdr()\\
IDL> text=hdr_obj->getbte_hdr()
At line 36 changed one line
The first file is the level-1 EIS FITS file containing calibrated intensity arrays. The second file is the error file which contains the corresponding 1-sigma intensity errors for the arrays stored in the level-1 file.
A number of useful header tags can be sent to a structure by doing:
At line 38 changed one line
Full details of the various keyword inputs to eis_prep are given in [EIS Software Note #1|ftp://sohoftp.nascom.nasa.gov/solarsoft/hinode/eis/doc/eis_notes/01_EIS_PREP/eis_swnote_01.pdf], where detailed descriptions of the various steps performed by eis_prep are given.
IDL> eis_get_hdr_struc,data,hdrstr
At line 40 changed one line
One feature of eis_prep is that bad pixels in the data are flagged as 'missing'. These bad pixels can be due to cosmic ray hits, saturated pixels, dust particles on the detector, hot pixels and warm pixels. The latter are by far the most numerous, and are described in more detail in [EIS Software Note #6|ftp://sohoftp.nascom.nasa.gov/solarsoft/hinode/eis/doc/eis_notes/06_HOT_WARM_PIXELS/eis_swnote_06.pdf]. Bad pixels are flagged only in the error file and are assigned a value of -100. The bad pixels in the level-1 file are replaced by a value interpolated from neighbouring pixels. More details about the effect of missing data on EIS data analysis and interpolation methods are given in [EIS Software Note #13|ftp://sohoftp.nascom.nasa.gov/solarsoft/hinode/eis/doc/eis_notes/13_INTERPOLATION/eis_swnote_13.pdf].
To find which wavelength windows are contained in data, do:
IDL> wininfo=eis_get_wininfo(filename,/list)
!Exercise
#Using eis_get_wininfo and the getvar() object method, extract an image in Fe XII 195 by summing all wavelength pixels in the window. Plot the image. What do you have to do to the image to orient it correctly? (You may need to refer to XRT images from Day 1 of the workshop.)
#Using the following commands:
IDL> aux_data=data->getaux_data()\\
IDL> exptimes=data->sec_from_obs_start(*(aux_data.ti_1))\\
IDL> xpos=data->getxpos()\\
work out in which direction EIS rasters (east-west, or west-east).
This page (revision-13) was last changed on 07-Dec-2016 14:14 by Peter YoungTop