This page (revision-11) was last changed on 07-Dec-2016 14:14 by PeterYoung

This page was created on 14-May-2007 13:16 by Louise Harra

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
11 07-Dec-2016 14:14 2 KB PeterYoung to previous
10 14-Jun-2010 15:54 3 KB PeterYoung to previous | to last
9 26-Jan-2009 05:53 1 KB David R Williams to previous | to last
8 26-Jan-2009 05:53 1 KB David R Williams to previous | to last Deleted the current-time stamp which gave the wrong date for David's contribution.
7 20-Sep-2007 19:36 2 KB David Pérez-Suárez to previous | to last
6 31-Aug-2007 14:15 888 bytes LouiseHarra to previous | to last
5 31-Aug-2007 14:14 1 KB LouiseHarra to previous | to last
4 14-May-2007 16:45 900 bytes Louise Harra to previous | to last
3 14-May-2007 16:18 828 bytes Louise Harra to previous | to last
2 14-May-2007 13:42 829 bytes Louise Harra to previous | to last
1 14-May-2007 13:16 828 bytes Louise Harra to last

Page References

Incoming links Outgoing links
OrbitalVariationLinePosition
OrbitalVariationLinePosition

Version management

Difference between version and

At line 1 changed 3 lines
[{ALLOW edit EISMainUsers}]
[{ALLOW view Anonymous}]
!!!Orbital drift of the EIS wavelength scale
!Orbital drift of the EIS wavelength scale
At line 5 changed one line
There is a shift of the spectral line position during the 98.5 minute Hinode orbit that is due to the thermal changes occuring across the instrument during the orbit. The effect is clearly seen if a velocity map is made from an EIS raster, such as the example below.
There is a shift of the spectral line position during the 98.5 minute Hinode orbit that is due to the thermal changes occuring across the instrument during the orbit and was expected before launch.
At line 5 added 2 lines
The effect is clearly seen if a velocity map is made from an EIS raster, such as the example below.
At line 13 changed one line
Two methods are available to users for correcting the orbital drift: one uses instrument housekeeping data, while the other uses the spectral data themselves. Tests are being performed to compare the two methods but generally inexperienced users should use the housekeeping data method.
Two methods are available to users for correcting the orbital drift: one uses instrument housekeeping data, while the other uses the spectral data themselves. Both have drawbacks, and a general rule of thumb is that EIS absolute velocities are accurate to no better than 4 km/s.
At line 15 removed 3 lines
NOTE: the ''accuracy'' of EIS absolute velocities obtained with these methods is no better than 4 km/s.
At line 26 removed one line
This method uses line centroid positions measured from a single raster to define the orbit correction for that same raster. It is somewhat risky since it requires an assumption about large-scale velocity flows within the raster. E.g., often one makes an assumption that a quiet Sun region within the raster is at rest.
At line 28 changed one line
The method is implemented through the process of performing Gaussian fits to the emission lines in a data-set, and so the reader is referred to the documents listed below:
We are currently collecting data that will allow us to model this accurately for correction. As well as orbital variation, there will be seasonal variation as well. In the meantime, especially when dealing with rasters, you must correct for this. An uncorrected velocity map looks like the attachment, where you can clearly see the change in red and blue shift during the orbit. Software is being produced to correct for this but is not within eis_prep. It is now released to SSW (eis_orbit_correction). You can correct for the variation by modelling the line position along the time direction and subtracting that component which is sinusiodal in shape.
At line 30 removed 2 lines
[Gaussian fitting for the Hinode/EIS mission|https://hyperion.nascom.nasa.gov/svn/eis/release/doc/fitting/eis_auto_fit.pdf]\\
[Fitting examples using the eis_auto_fit|https://hyperion.nascom.nasa.gov/svn/eis/release/doc/fitting/eis_auto_fit_examples.pdf]
At line 33 changed one line
The method essentially requires an initial guess to be made for the orbit variation using the routine {{eis_wave_corr}}, and then refinements are made using Gaussian fits to the line of interest.
I've been working with the 2" slit. I took different data from different days (13/April 17-22h and 19/April 18-22h) and I've plot the mean value of the position of the Fe XII 195.12 line. As you can see in both days there is a kink (marked with a blue circle).
I've been looking for the best way to solve it, and the dashed line that is in the plot is a sinusoidal fit that I've tried but that is not perfect.
In my opinion that kink is produced by thermal effects, since it is repeated in the other day and. The best way I've found to fix that is using splines every 5 time-steps as it is used in EIS_ORBIT_CORRECTION.PRO for 1" slit. But in that program it uses as reference wavelength the mean value between the maximum and minimum of the file, whereas I used the min and max of the all dataset ( I think that's important because if you have different files they will be corrected with different reference wavelength).
[Orbitfiles | OrbitalVariationLinePosition/FeXII195a2_thermal.jpg]
[Orbitfiles | OrbitalVariationLinePosition/FeXII195b2_thermal.jpg]
-[David Pérez-Suárez|DavidPS],
2007-Sep-21
This page (revision-11) was last changed on 07-Dec-2016 14:14 by PeterYoungTop