This page (revision-12) was last changed on 27-Nov-2017 16:52 by Peter Young

This page was created on 17-Mar-2010 21:30 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
12 27-Nov-2017 16:52 2 KB Peter Young to previous
11 27-Nov-2017 16:51 2 KB Peter Young to previous | to last
10 07-Dec-2016 14:14 2 KB PeterYoung to previous | to last
9 28-Jul-2010 16:12 2 KB SKamio to previous | to last
8 08-Jul-2010 00:49 2 KB PeterYoung to previous | to last
7 08-Jul-2010 00:16 2 KB PeterYoung to previous | to last
6 08-Jul-2010 00:05 1 KB PeterYoung to previous | to last
5 08-Jul-2010 00:04 1 KB PeterYoung to previous | to last
4 07-Jul-2010 23:49 1 KB PeterYoung to previous | to last
3 17-Mar-2010 21:51 1 KB PeterYoung to previous | to last
2 17-Mar-2010 21:43 1 KB PeterYoung to previous | to last
1 17-Mar-2010 21:30 2 KB PeterYoung to last

Page References

Incoming links Outgoing links
NarrowWorksheet6
NarrowWorksheet6

Version management

Difference between version and

At line 1 added 2 lines
[{ALLOW edit EISMainUsers}]
[{ALLOW view Anonymous}]
At line 3 changed one line
Generally the EIS emission lines have a Gaussian shape and, by fitting a Gaussian function to the spectrum, one can derive line intensity, line width and velocity maps. The high sensitivity of EIS means that for many lines it is possible to perform good quality fits at each pixel in the image. The routine eis_auto_fit in Solarsoft takes the output from eis_getwindata (Worksheet 5) and fits a single Gaussian to each pixel in the image. The calling procedure is:
Generally the EIS emission lines have a Gaussian shape and, by fitting a Gaussian function to the spectrum, one can derive line intensity, line width and velocity maps. The high sensitivity of EIS means that for many lines it is possible to perform good quality fits at each pixel in the image. The routine EIS_AUTO_FIT in Solarsoft takes the output from eis_getwindata (Worksheet 5) and fits a single Gaussian to each pixel in the image. The calling procedure is:
At line 5 changed 2 lines
IDL> eis_wave_corr, l1name, offset\\
IDL> eis_auto_fit, wd, fit, offset=offset
{{{
IDL> eis_auto_fit, wd, fit
}}}
At line 8 changed one line
The first command is used to determine the wavelength offset at each spatial pixel due to the tilt of the EIS slit and orbit variation of emission line centroids. Correcting for these effects yields a much more accurate velocity map.
The output from EIS_AUTO_FIT is an IDL structure called FIT. Intensity, velocity and line width arrays can be extracted from FIT by doing:
At line 10 changed one line
The output from eis_auto_fit is an IDL structure called 'fit'. Intensity, velocity and line width arrays can be extracted from fit by doing:
{{{
int=eis_get_fitdata(fit,/int,calib=calib)
vel=eis_get_fitdata(fit,/vel,calib=calib)
wid=eis_get_fitdata(fit,/wid,calib=calib)
}}}
At line 12 changed 3 lines
int=eis_get_fitdata(fit,/int)\\
vel=eis_get_fitdata(fit,/vel)\\
wid=eis_get_fitdata(fit,/wid)
The optional input 'calib' specifies which radiometric calibration to apply to the data. Please check the [calibration discussion page|EISCalibration] for more details. The recommended options are 1 or 3 for the Del Zanna (2013) or Warren et al. (2014) calibrations. Neglecting to specify calib means that the original laboratory calibration (as performed in the call to eis_prep) will be retained. Although 'calib' does not need to be specified for the velocity and line width arrays, it's good practice to always specify it.
At line 16 changed one line
Error arrays for each parameter can be obtained by adding the optional output 'error=error':
Error arrays for each parameter can be obtained by adding the optional output 'error=error'. Make sure that 'calib' takes the same value as it did when you extracted the intensity array.
At line 18 changed one line
int=eis_get_fitdata(fit,/int,error=int_error)
{{{
int=eis_get_fitdata(fit,/int,error=int_error,calib=calib)
}}}
At line 20 changed one line
This example shows the most simple use for eis_auto_fit. The routine can also be used to perform multiple Gaussian fits and a full description of the capabilities are given in two documents: '[Gaussian fitting for the Hinode/EIS mission|eis_auto_fit.pdf]' and '[Gaussian fitting examples using eis_auto_fit|eis_auto_fit_examples.pdf]'.
This example shows the most simple use for eis_auto_fit. The routine can also be used to perform multiple Gaussian fits and a full description of the capabilities are given in two documents: '[Gaussian fitting for the Hinode/EIS mission|ftp://sohoftp.nascom.nasa.gov/solarsoft/hinode/eis/doc/eis_notes/16_AUTO_FIT/eis_swnote_16.pdf]' and '[Gaussian fitting examples using eis_auto_fit|https://ftp://sohoftp.nascom.nasa.gov/solarsoft/hinode/eis/doc/eis_notes/17_AUTO_FIT_EXAMPLES/eis_swnote_17.pdf]'.
At line 29 added one line
Some points to note about the line fit parameters:
At line 23 changed 4 lines
!!Exercise
#Some horizontal stripes can be seen in the velocity and line width maps. What could be causing these?
#Use eis_fit_viewer to find the approximate variation in line centroid position caused by the orbital motion of Hinode.
# The velocity map has been calibrated such that the average velocity across the whole raster is set to zero. Alternative methods of calibrating the velocity map are described in the fitting documents listed above. If velocity maps are used in scientific analysis, then scientists should consider carefully how the maps are calibrated.
# When the line width array is extracted with eis_get_fitdata, it is automatically corrected for the instrumental line width. To keep the instrumental component, use the /keep_inst_width keyword. The thermal component of the line width can be removed by using the thermal_wid= optional input - see the routine header for details on how to use this keyword.
This page (revision-12) was last changed on 27-Nov-2017 16:52 by Peter YoungTop