This page (revision-7) was last changed on 07-Dec-2016 14:14 by Terje Fredvik

This page was created on 14-Jun-2010 15:59 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
7 07-Dec-2016 14:14 4 KB Terje Fredvik to previous
6 31-Mar-2011 10:21 4 KB Terje Fredvik to previous | to last
5 31-Mar-2011 10:19 4 KB Terje Fredvik to previous | to last
4 15-Jun-2010 15:05 4 KB PeterYoung to previous | to last
3 15-Jun-2010 15:04 4 KB PeterYoung to previous | to last
2 14-Jun-2010 16:11 4 KB PeterYoung to previous | to last
1 14-Jun-2010 15:59 4 KB PeterYoung to last

Page References

Incoming links Outgoing links
HKmethod
HKmethod

Version management

Difference between version and

At line 1 changed one line
!Correction for EIS Line Centre Variations Due To Orbital Motion Using Instrument Temperatures
[{ALLOW edit EISMainUsers}]
[{ALLOW view Anonymous}]
!!!Correction for EIS Line Centre Variations Due To Orbital Motion Using Instrument Temperatures
At line 5 changed one line
(Click here to see a complete list of all new and modified SolarSoft routines)
(Click [here|http://folk.uio.no/tfredvik/astro/wavecorr/list.txt] to see a complete list of all new and modified SolarSoft routines)
At line 7 changed one line
The wavelength correction can be found using eis_wave_corr_hk.pro, the gethkwavecorr() method of the eis_data object or eis_prep.pro. All procedures use specially prepared house keeping data files that are distributed with SolarSoft in the directory $EIS_DATA/wave_corr. If the house keeping files that are needed for correcting a certain EIS raster are missing in your SolarSoft installation, the new routines will search for the files in $EIS_WAVE_CORR_HK_DATA (if this environment variable is set), and in the current working directory. If the files are not found, they will automatically be downloaded from the Oslo archive and saved in $EIS_WAVE_CORR_HK_DATA (if set) or to the current working directory (if not set).
The wavelength correction can be found using {{eis_wave_corr_hk.pro}}, the {{gethkwavecorr()}} method of the eis_data object or eis_prep.pro. All procedures use specially prepared house keeping data files that are distributed with SolarSoft in the directory {{$EIS_DATA/wave_corr}}. If the house keeping files that are needed for correcting a certain EIS raster are missing in your SolarSoft installation, the new routines will search for the files in {{$EIS_WAVE_CORR_HK_DATA}} (if this environment variable is set), and in the current working directory. If the files are not found, or if newer versions of the files exist in the Oslo archive, they will automatically be downloaded and saved in {{$EIS_WAVE_CORR_HK_DATA}} (if set) or to the current working directory (if not set). Note that the house keeping files for a specific month are updated every night on the Oslo servers until the month is passed, i.e. if you work with observations from the current month new house keeping files will be downloaded to your machine every day until the end of the month.
At line 11 added 8 lines
The following three examples demonstrate different methods to obtain the new wavelength correction. The example data-set is specified through
{{{
IDL> paths = '~/hinodedata/eis/mission/2007/12/11/eis_l0_20071211_162413.fits.gz'
}}}
(please modify the path to the location where your Hinode data are stored) and the data-file can be obtained [here|http://tinyurl.com/wavecorr-example].
At line 11 changed one line
This is simply a wrapper procedure calling the necessary methods of the eis_data object. It is called with the same parameters as the well known eis_wave_corr.pro:
This is simply a wrapper procedure calling the necessary methods of the {{eis_data}} object. It is called with the same parameters as the well known {{eis_wave_corr.pro}}:
At line 14 removed one line
IDL> paths = '~/hinodedata/eis/mission/2007/12/11/eis_l0_20071211_162413.fits.gz' ; This file can be downloaded here
At line 21 changed 3 lines
In addition eis_wave_corr_hk takes two keywords:
wvl_cube: If set to a named variable, wvl_cube will return a 3 dimensional wavelength cube in the format used by mk_analysis.pro of the Component Fitting System for IDL (cfit) package.
lam: the underlying methods of eis_data calculates the wavelength correction in pixels, and we assume that the shift in pixels is the same for all lines formed at any location on the two detectors. However, when measured in Angstroms the line centre variation and the slit tilt will vary slightly with wavelength. As default, eis_wave_corr_hk assumes that the corrections are to be calculated for the Fe XII 195 Å line, but the lam keyword may be set to the wavelength of the line you want to investigate.
In addition {{eis_wave_corr_hk}} takes two keywords:
At line 32 added 3 lines
* wvl_cube: If set to a named variable, wvl_cube will return a 3 dimensional wavelength cube in the format used by [mk_analysis.pro|http://www.astro.washington.edu/docs/idl/cgi-bin/getpro/library32.html?MK_ANALYSIS] of the [Component Fitting System for IDL (cfit)|http://solar.bnsc.rl.ac.uk/swnotes/cds_swnote_47.pdf] package.
* lam: the underlying methods of eis_data calculates the wavelength correction in pixels, and we assume that the shift in pixels is the same for all lines formed at any location on the two detectors. However, when measured in Angstroms the line centre variation and the slit tilt will vary slightly with wavelength. As default, eis_wave_corr_hk assumes that the corrections are to be calculated for the Fe XII 195 Å line, but the lam keyword may be set to the wavelength of the line you want to investigate.
At line 40 changed one line
When creating an eis_data object, the aux_data will contain two new null pointers, hkpixcorrtilt and hkpixcorrtime:
When creating an {{eis_data}} object, the aux_data will contain two new null pointers, {{hkpixcorrtilt}} and {{hkpixcorrtime}}:
At line 47 changed one line
The two pointers will become valid when the method gethkwavecorr() is called (i.e. when you try to access the contents of the pointers):
The two pointers will become valid when the method {{gethkwavecorr()}} is called (i.e. when you try to access the contents of the pointers):
At line 55 changed one line
The gethkwavecorr() may be called with a wavelength as input parameter, or with the keyword wvl_cube set, to get the same functionality as for the eis_wave_corr_hk wrapper as explained above.
The {{gethkwavecorr()}} may be called with a wavelength as input parameter, or with the keyword {{wvl_cube}} set, to get the same functionality as for the {{eis_wave_corr_hk}} wrapper as explained above.
At line 66 changed one line
eis_prep.pro now accepts the keyword hkwavecorr. If set, the resulting level 1 file will contain the wavelength correction information.
{{eis_prep.pro}} now accepts the keyword {{hkwavecorr}}. If set, the resulting level 1 file will contain the wavelength correction information.
At line 75 removed one line
This page (revision-7) was last changed on 07-Dec-2016 14:14 by Terje FredvikTop