Full Disk Disambiguated Vector Field from HMI
The hmi.B_720s Data Series
The HMI full disk disambiguated vector field, hmi.B_720s, are routinely available from Jan 15, 2014. As currently planned, data from early times will be processed for campaign events and upon request (coverage). The data are in definitive version only, thus becomes available a few days after the observation.
The hmi.B_720s data series mostly inherits the content form the ME inversion (hmi.ME_720s_fd10), with added keywords and segments (images). For the ME data series, please refer to the pipeline overview paper and the ME inversion paper. The added keywords contain information of the disambiguation module parameters, and will be detailed in a forthcoming pipeline paper. The two added full-disk images are the results from disambiguation process: disambig and conf_disambig.
Algorithm and Added Images
The full-disk disambiguation differs from the AR patch version in that only the strong field pixels are subject to the minimum-energy algorithm, in order to speed up the processing. This information is retained in the conf_disambig image, where a value of 90 indicates pixels above the noise threshold, 60 indicates pixels peripheral to the strong field, 50 indicates weak field, and 0 off disk. The 90 and 60 pixels are "annealed" using the minimum-energy algorithm, whereas the 60 pixels are subsequently smoothed. The 50 pixels are not "annealed". Three solutions are provided: potential-acute; radial-acute; random.
The disambig image contains disambiguation solutions for each pixel. The lowest three bits are set, either to 1 or 0, based on three different algorithms.
Example of Using the Data
Miscellaneous
The full-disk azimuthal disambiguation solutions are now used to produce the definitive SHARP data (hmi.sharp_720s, hmi.sharp_cea_720s) starting from Jan 15, 2014, and can be identified through the AMBPATCH keyword (0 for full disk disambiguation, 1 for early data). NRT SHARP data are still disambiguated on the AR patches.