1.44-4

	 - Beam size was not read back by ReducedData, defaulting to 8.5 arcsec
        size at all times.

	- Better reductions on a larger range of sources resulting from new
        stricter chi^2 requirements for despiking and temporal pixel analysis.
	
	- Crush -correct= (FLUX_CORRECTING_FWHM) still misbehaved if
        'none' was argumented. Now fixed.

1.44-3

	- The crush -correct= option did not work as desired. It was rather
	botched. FLUXES FROM PRIOR 1.44 RELEASES ARE NOT RELIABLE.
	
	- Corrected MUX variance calculation.

        - MUXOffsets and now revise the model and will only keep model for 
	rows which do appear to have detectable model levels. This is good 
	because MUX offsets seem to come ang go and affect only a few rows
	at once...

        - Windows .bat batch files added for easier Windows usage. Simply
        unzip windows.zip, then run 'cleanup' (cleanup.bat). The UNIX scripts
        will be replaced with Windows batch files to the same effect!!!

	- Deconvolution now makes the replacement beam size as the image
	beam size, and recalculates the necessary constants.

1.44-2
	- MUX RMS is estimated only for rows that have a detectable MUX
        term.

	- Changed pixel weighting frequency band to 0.7-0.9 times the 
	available range of frequencies. This way any high frequency trouble
	(like filtering or 13Hz noise will not bias pixel weights.

	- Console flux summary now in incident Jy/beam unit instead of detector
	nV. This way the numbers are more physically meaningful. Also shown
	the estimated residual source pollution (Jy/detector) by interfering
	models(!).	

	- More intelligent pipeline ordering based on estimated source
	pollution effects of various models. Does not use source diameter any 
	longer.

	- Map weights no longer displayed for scans that were did not
	contribute to the composite map. Instead '[--]' is displayed to
	indicate the scan was not used. Those scans are also assigned
	zero weights.		

	- A wrong normalization found in determining whether it is safe or not
	to solve for row polynomials and MUX offsets for extended sources. 
	This deteriorated the reductions of faint extended sources. Now 
	corrected. 

	- Relaxed flagging and map clipping directives for faint and deep
	reductions (faint.cfg & deep.cfg).

	- Deep reductions (deep.cfg) no longer filter large scale structures.
	However, such filtering will occur on the maps themselves until
	faithful source extraction is required (-Ifidel= flag). Normally,
	this will only affect the first few map generations but not the final
	output. Occasionally one may want to enable the RegionalCorrelations
	model to perform such filtering.

	- Faint and deep reductions (faint.cfg and deep.cfg) no longer
        exclude array edges. Though in some cases the user may want to
        re-enable the edge clipping (e.g. -edge=4:4:0:0)

	- -faint and -deep (faint.cfg, deep.cfg) now fit second order sky
	polynomials.

	- AccelerationResponse re-activated in pipeline for -faint and -deep
	reductions (faint.cfg, deep.cfg). Activation condition chi^2 
	requirement relaxed to < 2 for 'auto' activation.

	- Altered MUX Offset modelling. While the previous modelling was
        technically correct, it did not perform well on non-intact rows.
        The new estimator measures half row offsets separately first and
        estimates the MUX offset with the difference over the two halfs,
        rather than getting the MUX offset directly with a single estimator
        as done before. The result is expected to be more reliability for
        this model.

	- Improved error function integral estimation to use with significance
        estimation in 'detect' tool.

	- [Some more FFT cleanup. Does not affect functionality.]

1.44-1

	- Bug found with some of the FFT code (unsecureBackFFT). This only
	affected the 13Hz filter on 4 pixels per row, if the filtering option
	was set. The code is now fixed. Furthermore, the 13Hz filter now 
	applies to all pixels (since the 13Hz noise is not unique to that 
	subset of distinctly noisy pixels).

1.44	
	
	- Ambient temperature added to log tables generated by the -log=
	option. 

1.44-a4

	- Changed 'detect' behaviour to comply with built-in corrections.

	- FLUX_CORRECTING_FWHM key and -correct= flag introduced for crush
	itself controlling the flux correction during the reduction itself.
	Argument is either FWHM source size in arcsec or 'point' for point 
	sources, else 'none' if no correction is desired.

	- Took account of the effect of field rotation on the flux correction.
	RowPolynomials and MUXOffsets are now better corrected. This will not
	affect single scans really. Only sets of scans reduced together will
	have different correction factors from the prior test version.

	- Improved the way position angle range is calculated for a set of 
	scans. This is mainly used for deciding whether row or mux models are
	allowed to precede source under 'auto' activation rules for extended
	sources. Also, source diameter (or beam size) is taken into account
	in making that decision for more robust default functionality.

1.44-a3

	- Image FITS headers are now fully preseved under imagetool.

	- An error was found with the Regional Correlation correction, both
	in the way it was calculated and then applied. Both have been fixed.
	Only affected corrections on -deep reductions.

	- Problem from previous version with applying correction (leaving blank
	images) is now fixed.

1.44-a2

	- Applied Smoothing now appears on image info.
	
	- Further improved flux corrections. Corrections are calculated more
	exactly, and scans that are not contributing to maps are ignored.
	The source size (FWHM) for which fluxes are corrected for is recorded
	under the 'CORRECTN' FITS key in the image.
	The flux correction is also printed with the image info whenever
	images are opened with the crush utilities.
	Corrections can be applied multiple times via the crush utilities, 
	with the new correction overriding the previous.

	- Point flux corrections will be taken into account for -compact
	reductions to produce better composite maps. However, the output
	will remain an essentially uncorrected image, i.e. corrections
	are to be applied as usual, e.g. via imagetool or calibrate.

1.44-a1	

	- In an effort to aid calibration corrections, correction factors
	calculated for flux filtering models are now stored in the FITS
	output image for point sources. These numbers can be used to estimate
	the correction factor for any size source.

	- 'calibrate' updated to automatically apply the necessary source 
	flux corrections for calibration sources.

	- 'imagetool' new option -correct= added to apply flux corrections
	to the specified source size. The argument is either a FWHM in 
	arcsec, or "point" for point source corrections.

	- 'calibrate' headers updated. Behaviour on non Alt/Az images was
	also improved (FAZO and FZAO fields have strike-out entries.)

