Mees Vector Magnetic Field Ambiguity Resolution Codes

	Barry LaBonte   August 16, 2000



   The following procedures are designed to handle the Mees
   data formats.  They can be replaced by appropriate local
   versions.


	BFITS		Reads a multi-plane FITS file with vector
			field data in scaled integer format into
			an IDL structure.

   The following procedures may be eligible for replacement by
   more standard codes.  A test of actual performance should
   be done to verify function.

	BICUBIC		Bicublic spline interpolator.  Can this 
                        be replaced by INTERPOLATE or one of the
                        SPLINE procedures from IDL?


	BICUBIC2D	Bicublic spline interpolator.  Can this
			be replaced by INTERPOLATE or one of the
			SPLINE procedures from IDL?


   The following procedures are very old.  They have direct
   replacements in the IDL release or the SolarSoft tree.
   They should be purged from the code.
   

	ADD2STR         Adds a tag to a structure.  Should be replaced
                        with ADD_TAG from SolarSoft.

	BILINXY		Binlinear interpolation.  Should be replaced with
			BILINEAR from IDL.

	INHEADER	Finds location of a keyword in a FITS header.
			Used only by WKEY (see below).

	RKEY		Reads a value from a FITS header.  Should
			be replaced with SXPAR, or FITSHEAD2STRUCT
			from SolarSoft.

	STRSTAT		Checks to see if a structure name exists.
			Should be replaced by CHK_STRUCT_NAME from
			SolarSoft.

	TAG_INDEX	Finds location of tag in a structure.
			Should use the TAG_INDEX in SolarSoft.

	TRMVECT		Plots a field of vectors.  Should be
                        replaced by VELOVECT from IDL.

	VECTORFIELD	Plots a field of vectors.  Should be 
			replaced by VELOVECT from IDL.

	VFIELD2		Plots a field of vectors.  Should be
                        replaced by VELOVECT from IDL.

	WKEY		Adds a line to a FITS header.  Should be
			replaced with SXADDPAR from SolarSoft.


   The following procedures are beyond belief.

	LPRINT		Somewhere in the depths of IDL codes there
			is a reference to a DEC LA printer, and
			this procedure.  Shows up when using
			RESOLVE_ALL.

	SETLOG		Somewhere deep in the bowels of IDL codes
			there is a reference to this which crashes
			if you do a RESOLVE_ALL.  It may be that
			this is unneeded if you just let the code
			compile at runtime.