Release Notes mdi.fd_M_96m_lev182:

The data in the DRMS series mdi.fd_M_96m_lev182 do not exactly match the data
that was contained in dsds.mdi__lev1_5__fd_M_96m_0ld. 


The data in mdi.fd_M_96m_lev182 were processed as follows:

1. dsds.mdi__lev1_5__fd_M_96m_0ld were run through the dsds module /home/soi/CM/bin/_linux4/fixplatescale_v0 with the updated and final scale corrections table (available at mdi.scale_corrections) for the MDI mission. 
2. the output of fixplatescale_v0 were run through the dsds module /home/soi/CM/bin/_linux4/fdmagcal to perform the sensitivity correction, magnetic field strength correction, and a few other corrections, 
3. the output of fdmagcal were run through the ingest module ingest_dsds_to_drms (available in cvs) to calculate and populate the correct WCS keywords,
4. the output of ingest_dsds_to_drms were stored in mdi.fd_M_96m_lev182.

The input data to ingest_dsds_to_drms were in type floats; the output data were in type ints. The BSCALE for this operation is 0.01. However, the conversion does yield non-identical co-temporal images. Differencing co-temporal images of type float and type scaled ints yields a pattern of oblate concentric rings. This image is available in the same directory as these release notes and is called diffbetween1and2.png. 

In addition, the following known concerns exist:

1. Data that are not present in dsds.mdi__lev1_5__fd_M_96m_0ld but have an associated blank .rdb file. The 
   list of data that fall into this category are in SECTION 1, appended.

2. Data that are present in dsds.mdi__lev1_5__fd_M_96m_0ld but do not have an associated .rdb file. The 
   list of data that fall into this category are in SECTION 2, appended.


============== BEGIN SECTION 1 =================

2004.12.9

============== BEGIN SECTION 2 =================

1996.04.15_00_TAI (1200) : 12 of 0 expected
1996.04.16_00_TAI (1201) : 9 of 0 expected
1996.04.17_00_TAI (1202) : 8 of 0 expected
1996.04.18_00_TAI (1203) : 9 of 0 expected
1996.04.19_00_TAI (1204) : 11 of 0 expected
1996.04.20_00_TAI (1205) : 13 of 0 expected
1996.04.22_00_TAI (1207) : 2 of 0 expected