General.....

The file glintdates_m1 (ascii) associates every day from 941130 to 961231
with a glint map identifier, which is the date for which the glint map was made.

The glint map identifier is the file name identifier <yymmdd> for a procedure
dglint_m1_<yymmdd>.pro (ex: dglint_m1_941130.pro) which idl-restores the 
appropriate glint map and/or explicitly defines glint map elements.

Glint maps have the form 19<yymmdd>*_m1.glntmap.

The file glintdates_m1 is created and updated using procedure glintdates.pro.

How to update the set of glint masks....

For each new "19<yymmdd>*_m1.glntmap", create a "dglint_m1_<yymmdd>.pro" and 
run procedure "glintdates.pro". The procedure "glintdates.pro" updates the
glintdates_m1 table.

Same as above for mode2 (m2).


How to use..... 

In the WGGS analysis tool, procedure lzinput.pro is executed once for the given
level zero data date, lzdate. Procedure lzinput.pro reads file glintdates_m1 
and finds glintdate corresponding to lzdate. 
Using glintdate as file identifier, the approriate dglint_m1_<lzdate>.pro is executed which in turns reads and stores
the glint map to be used, ex: 19960715_std2.0_m1.glntmap.

Similarly for mode2 (m2).
