Release Notes mdi.fd_M_lev182:

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

The data in mdi.fd_M_lev182 were processed as follows:

1. dsds.mdi__lev1_5__fd_M_0lh 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_lev182. The '_lev182' suffix is temporary and uses a deprecated level-numbering scheme from dsds; once the definitive magnetic field strength correction is determined, a definitive series without such a suffix will be created.

The input data to ingest_dsds_to_drms were in type shorts; the output data are in type scaled ints. (There will be some difference, less than BSCALE, when converting data types in drms. For zero difference between the dsds and drms data, the dsds data should be ingested as type 32-bit single precision floating point.) The BSCALE for this operation is 0.01. Differencing co-temporal images of type shorts and 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 for which the value of T_OBS in the .rdb file does not match the vlaue of T_OBS associated with the data series number. These data are not present in mdi.fd_M_lev182. The list of data that fall into this category are in SECTION 1, appended.

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

2005.10.23_16:00:00(112288)