|
Size: 2243
Comment:
|
Size: 5261
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| The polarimetric filtergram data are processed with the Milne-Eddington inversion code VFISV (Borrero et al. 2010) to produce full-disk vector magnetic field maps every 12 minutes (or 720 seconds). Data products are available, on average, a week after observation. We are retroactively processing data from 2010 onwards. Current processed database includes, at least, 2 full-disk images per day, with a more exhaustive coverage of particular time intervals (click here for link to coverage map: http://jsoc.stanford.edu/doc/data/hmi/coverage_maps/ then select the fd10/ folder). The inversion code is operating with a fixed magnetic filling factor of unity, and the azimuth has not been disambiguated (it ranges between 0 and 180 degrees). Recent updates to the inversion code include the addition of a regularization term to the merit function in order to bias the solution towards lower eta0 values. The aim of this modification is to reduce spatial discontinuities due to the presence of double minima in the chi-square surface. Other updates focus on the convergence criteria and speed optimization. | |
| Line 7: | Line 6: |
| Be aware that some magnetic field values in strong umbrae and complex regions are erroneous in HMI vector data. The dynamic range of the HMI measurements goes up to ~3500 Gauss. Strong magnetic fields leads to a complete split of the spectral line (Zeeman saturation). In our case, stronger values than 3500 Gauss extends the spectral line outside of the observed HMI spectral range. High Doppler velocities can also shift the spectral line partially outside of the HMI spectral range. When either one of these facts or their combination happens, the inversion code does not have enough information to constrain the field strength, and occasionally it hits the preset upper limit of 5000GThe dynamic range of the HMI measurements goes up to ~3500 Gauss. Only a very, very small fraction of the pixels exhibits such problems, which are easily seen 'by eye'. These and other minor issues will be described in detail at ReleaseNotes3 page. | == Release Notes for Initial Milne Eddington Inversion of HMI Magnetic Field Data (VFISV) == '''hmi.ME_720s_fd10''' ([http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.ME_720s_fd10 click here for data]), '''hmi.ME_720s_fd10_HARP''' ([http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.ME_720s_fd10_HARP click here for data]), and '''hmi.ME_720s_fd10_HARP_nrt''' ([http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.ME_720s_fd10_HARP_nrt click here for data]). These three data series contain ME inversion data processed using VFISV ([http://hmi.stanford.edu/doc/magnetic/section4.pdf details]) using the codes implemented on April 13, 2012. There are known issues with these versions of VFISV, but this remains the best ME release version as of the date of implementation. We consider this a beta-test version of the HMI vector field inversion. . The prime data products are field strength, inclination, and azimuth. Errors and other quantities are included. . No disambiguation has been performed, so azimuths are in the range 0-180, not 0-360. . fd10 in the series name is an index of the choice we think best among those we had tested, since [:ME720se15w1332: the last release]. Our efforts to optimize the VFISV for the HMI data pipeline are on going, and we will create the series to fill the data processed by the newer codes when ready. The eventual pipeline code for HMI vector inversions will be different. We will announce the release of the new data through Solar News. ==== Temporal Coverage for These Three Series ==== '''[http://jsoc.stanford.edu/doc/data/hmi/coverage_maps/fd10/ Monthly charts]''' show the 12-minute time slots for which the ME inversion data processed with the VFISV module are available. The coverage charts also contain the status flags of the HMI observation, thus the quality and availability of input [http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.S_720s Stokes] data. See [:ME720se15w1332CoverChart: details] for an explanation of the coverage charts (* the color and legends in the coverage charts are same as those for the [:ME720se15w1332: previous version of ME data]). * '''hmi.ME720s_fd10 - ''Full Disk'' ''' . Synoptic data, on twice per day basis at 7 and 19UT daily, are stored in this series. The latest version of VFISV is being used to extend this series using the latest definitive Stokes data, on the 2 per day basis, usually about a week after the observation. Data for scattered additional time intervals are also available. Checking the version of VFISV codes is strongly recommended. * '''hmi.ME720s_fd10_HARP - ''HMI Active Region Patches'' ''' . The latest version of VFISV has been used to generate the ME data stored in this series. Many of the active regions were recognized automatically by the [:HARPDataSeries:HARP module], while some were defined manually. This series includes 12-minute (720s) cadence data for several of the ARs that created X-class flares in 2011, including the one occurring on 2011 February 15 (at NOAA AR11158). * '''hmi.ME720s_fd10_HARP_nrt - ''Near-Real-Time HMI Active Region Patches'' ''' . The latest version of VFISV has been used to generate the ME data stored in this series. The input Stokes data and the HARP info. are of preliminary though the time lag between observation and ME process is minimized. Current setting is to start processing at 7AM (7PM) Pacific time for the first (second) half day in UT. (K.H.'s memo : does this sentence make sense?) ==== Versions of VFISV in the FITS files exported at JSOC database ==== * The VFISV version is stored as a string value in the keyword ''INVCODEV''. * The ME data for the series above were processed with the latest version, labeled with a date, "Apr 13, 2012". * In IDL, for example, if the exported data is read with [http://hmi.stanford.edu/doc/magnetic/fitsio.pdf fitsio_read_image()] then, the version keyword can be printed with sxpar(): . {{{ IDL> img=fitsio_read_image('img.fits',header) IDL> print, sxpar(header,'INVCODEV') }}} * '''Major differences between 2011-October-14 (or 2011-November-27) version and the current FD10 version''' * VFISV core part 1. A regularization term, whose purpose is to penalize high values of the parameter eta_0, was added to the merit function in order to tackle a double-minima problem. 2. The selection process that decides when the inversion of a given pixel needs to be re-started with a different (randomized or tailored) initial guess atmosphere, has been implemented and fine-tuned. 3. We have settled on a convergence criterion based on the value of the Levenberg-Marquardt Lambda parameter. The algorithm exits the iteration loop when Lambda becomes too large and no re-start of the inversion is enforced for any other reason. The average number of iterations per pixel is now about 30. * Misc., other part 1. Parallelism, by means of MPI, has been modified and optimized to allocate the tasks to each Process Element as evenly as possible. |
Description & Release Notes for hmi.ME_720s_fd10 Data
Definitive, science-grade, HMI vector magnetic field data are now (May, 2012) available via JSOC under the series name hmi.ME_720s_fd10.
Release Notes for Initial Milne Eddington Inversion of HMI Magnetic Field Data (VFISV)
hmi.ME_720s_fd10 ([http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.ME_720s_fd10 click here for data]), hmi.ME_720s_fd10_HARP ([http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.ME_720s_fd10_HARP click here for data]), and hmi.ME_720s_fd10_HARP_nrt ([http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.ME_720s_fd10_HARP_nrt click here for data]).
These three data series contain ME inversion data processed using VFISV ([http://hmi.stanford.edu/doc/magnetic/section4.pdf details]) using the codes implemented on April 13, 2012. There are known issues with these versions of VFISV, but this remains the best ME release version as of the date of implementation. We consider this a beta-test version of the HMI vector field inversion.
- The prime data products are field strength, inclination, and azimuth. Errors and other quantities are included.
- No disambiguation has been performed, so azimuths are in the range 0-180, not 0-360.
- fd10 in the series name is an index of the choice we think best among those we had tested, since [:ME720se15w1332: the last release].
Our efforts to optimize the VFISV for the HMI data pipeline are on going, and we will create the series to fill the data processed by the newer codes when ready. The eventual pipeline code for HMI vector inversions will be different. We will announce the release of the new data through Solar News.
Temporal Coverage for These Three Series
[http://jsoc.stanford.edu/doc/data/hmi/coverage_maps/fd10/ Monthly charts] show the 12-minute time slots for which the ME inversion data processed with the VFISV module are available. The coverage charts also contain the status flags of the HMI observation, thus the quality and availability of input [http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.S_720s Stokes] data. See [:ME720se15w1332CoverChart: details] for an explanation of the coverage charts (* the color and legends in the coverage charts are same as those for the [:ME720se15w1332: previous version of ME data]).
hmi.ME720s_fd10 - Full Disk
- Synoptic data, on twice per day basis at 7 and 19UT daily, are stored in this series. The latest version of VFISV is being used to extend this series using the latest definitive Stokes data, on the 2 per day basis, usually about a week after the observation. Data for scattered additional time intervals are also available. Checking the version of VFISV codes is strongly recommended.
hmi.ME720s_fd10_HARP - HMI Active Region Patches
The latest version of VFISV has been used to generate the ME data stored in this series. Many of the active regions were recognized automatically by the [:HARPDataSeries:HARP module], while some were defined manually. This series includes 12-minute (720s) cadence data for several of the ARs that created X-class flares in 2011, including the one occurring on 2011 February 15 (at NOAA AR11158).
hmi.ME720s_fd10_HARP_nrt - Near-Real-Time HMI Active Region Patches
- The latest version of VFISV has been used to generate the ME data stored in this series. The input Stokes data and the HARP info. are of preliminary though the time lag between observation and ME process is minimized. Current setting is to start processing at 7AM (7PM) Pacific time for the first (second) half day in UT. (K.H.'s memo : does this sentence make sense?)
Versions of VFISV in the FITS files exported at JSOC database
The VFISV version is stored as a string value in the keyword INVCODEV.
- The ME data for the series above were processed with the latest version, labeled with a date, "Apr 13, 2012".
In IDL, for example, if the exported data is read with [http://hmi.stanford.edu/doc/magnetic/fitsio.pdf fitsio_read_image()] then, the version keyword can be printed with sxpar():
IDL> img=fitsio_read_image('img.fits',header) IDL> print, sxpar(header,'INVCODEV')
Major differences between 2011-October-14 (or 2011-November-27) version and the current FD10 version
- VFISV core part
- A regularization term, whose purpose is to penalize high values of the parameter eta_0, was added to the merit function in order to tackle a double-minima problem.
- The selection process that decides when the inversion of a given pixel needs to be re-started with a different (randomized or tailored) initial guess atmosphere, has been implemented and fine-tuned.
- We have settled on a convergence criterion based on the value of the Levenberg-Marquardt Lambda parameter. The algorithm exits the iteration loop when Lambda becomes too large and no re-start of the inversion is enforced for any other reason. The average number of iterations per pixel is now about 30.
- Misc., other part
- Parallelism, by means of MPI, has been modified and optimized to allocate the tasks to each Process Element as evenly as possible.
- VFISV core part