|
Size: 297
Comment:
|
Size: 910
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| The HMI full disk disambiguated vector field, [[http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.B_720s|hmi.B_720s]], are routinely available from Jan 15, 2014. Data from early times will be processed for campaign events and upon request. | The HMI full disk disambiguated vector field, [[http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.B_720s|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 ([[http://jsoc.stanford.edu/data/cov.html|coverage]]). The data is in definitive format only, thus becomes available a few days after the observation. These full-disk azimuthal disambiguation solutions are used to produce the definitive SHARP data ([[http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.sharp_720s|hmi.sharp_720s]], [[http://jsoc.stanford.edu/ajax/lookdata.html?ds=hmi.sharp_cea_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 with disambiguation done on AR patch). |
Full Disk Disambiguated Vector Field from HMI
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 is in definitive format only, thus becomes available a few days after the observation. These full-disk azimuthal disambiguation solutions are 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 with disambiguation done on AR patch).