Differences between revisions 1 and 2
Revision 1 as of 2017-09-01 04:50:26
Size: 1326
Editor: ToddHoeksema
Comment:
Revision 2 as of 2017-09-01 05:39:15
Size: 2238
Editor: ToddHoeksema
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
== Bug discovered in HMI Vector Field Data Processed Since 13 April 2016 == == Bug Discovered in HMI Vector Field Data Processed Since 13 April 2016 ==
Line 5: Line 5:
On 13 April 2016 HMI changed the vector field observations to use data from two cameras. Despite careful
testing, a bug has recently been discovered such that the filtergrams from the two cameras were not
properly aligned. The 0.08 degree offset in image rotation results in a displacement of a couple pixels at
the solar limb. The offset is most apparent in the Stokes Q and U components relative to Stokes V. The
error affects all of the data products that depend on the HMI Stokes data product, HMI.S_720s. In
particular the vector magnetic field provided in hmi.B_720s and hmi.sharp_720s deteriorate away from disk
center. The error was first noticed in measurements of the radial magnetic field component near the poles
derived from the vector data. The HMI 45-second data products are not affected. The bug has been corrected
starting with data processed on 1 September, 2017 and we will reprocess the data since 13 April 2016 over
the next several months. Data products with keyword CAMERA=3 and keyword DATE_S prior to 1 September 2017
should be replaced. Please contact a member of the HMI team if you have questions.
On 13 April 2016 HMI changed the vector field observations to use data from two cameras. Despite careful testing, a bug has recently been discovered such that the filtergrams from the two cameras were not properly aligned in the computation of the Stokes parameters in hmi.S_720s. A 0.08 degree offset in image rotation results in a displacement of about three pixels at the solar limb. The offset is most apparent in the Stokes Q and U components relative to Stokes V; Stokes I is a blend.

The misalignment affects all of the data products that depend on the HMI Stokes data product, HMI.S_720s. In particular the vector magnetic field provided in hmi.B_720s and hmi.sharp_720s deteriorate away from disk center. The error was first noticed in measurements of the radial magnetic field component near the poles derived from the vector data.

The bug has been corrected in data processed after 1 September, 2017 and we plan to reprocess the affected data over the next several months. Data products with keyword CAMERA=3 and keyword DATE prior to 1 September 2017 should be replaced.

Please contact a member of the HMI team if you have questions.

'''The HMI 45-second data products are not affected.'''
Line 17: Line 16:
Data series affected include the following.

 * hmi.S_720s
 * hmi.ME_720s_fd10
 * hmi.ME_720s_fd10_nrt
 * hmi.B_720s
 * hmi.sharp_720s
 * hmi.sharp_720s_nrt
 * hmi.sharp_cea_720s
 * hmi.sharp_cea_720s_nrt
 * hmi.bmap_lowres_latlon_720s
 * hmi.b_synoptic
 * hmi.b_synoptic_small
 * hmi.lookup_ChebyCoef_BNoise (MASKID = 7)

The (0x080) bit in the QUALITY keyword will be set in data that are affected by the problem.
The bit will be cleared when data reprocessed and the value of the keyword.

In addition bits 16-19 in the keyword CALVER64 will be set to 0x03000 instead of 0x02000 in reprocessed data.
 
All data that depend on hmi.S_720s collected after the switch to the Mod-L frame list at 2016.04.13_19:12:55 UT will be reprocessed.

Line 18: Line 40:
 '''[[http://jsoc.stanford.edu/jsocwiki/Production|Production]]'''

Recalibration of 720s HMI Data Products Obtained with Two Cameras

Bug Discovered in HMI Vector Field Data Processed Since 13 April 2016

On 13 April 2016 HMI changed the vector field observations to use data from two cameras. Despite careful testing, a bug has recently been discovered such that the filtergrams from the two cameras were not properly aligned in the computation of the Stokes parameters in hmi.S_720s. A 0.08 degree offset in image rotation results in a displacement of about three pixels at the solar limb. The offset is most apparent in the Stokes Q and U components relative to Stokes V; Stokes I is a blend.

The misalignment affects all of the data products that depend on the HMI Stokes data product, HMI.S_720s. In particular the vector magnetic field provided in hmi.B_720s and hmi.sharp_720s deteriorate away from disk center. The error was first noticed in measurements of the radial magnetic field component near the poles derived from the vector data.

The bug has been corrected in data processed after 1 September, 2017 and we plan to reprocess the affected data over the next several months. Data products with keyword CAMERA=3 and keyword DATE prior to 1 September 2017 should be replaced.

Please contact a member of the HMI team if you have questions.

The HMI 45-second data products are not affected.

Details

Data series affected include the following.

  • hmi.S_720s
  • hmi.ME_720s_fd10
  • hmi.ME_720s_fd10_nrt
  • hmi.B_720s
  • hmi.sharp_720s
  • hmi.sharp_720s_nrt
  • hmi.sharp_cea_720s
  • hmi.sharp_cea_720s_nrt
  • hmi.bmap_lowres_latlon_720s
  • hmi.b_synoptic
  • hmi.b_synoptic_small
  • hmi.lookup_ChebyCoef_BNoise (MASKID = 7)

The (0x080) bit in the QUALITY keyword will be set in data that are affected by the problem. The bit will be cleared when data reprocessed and the value of the keyword.

In addition bits 16-19 in the keyword CALVER64 will be set to 0x03000 instead of 0x02000 in reprocessed data.

All data that depend on hmi.S_720s collected after the switch to the Mod-L frame list at 2016.04.13_19:12:55 UT will be reprocessed.

JsocWiki: ModLRecalibration (last edited 2020-04-11 00:45:10 by PhilScherrer)