1.02-3

	- [CLEANUP] Removed several development classes that were no longer
	in use.

	- [TUNE] Maximum-likelihood estimators are rehabilitated for 'faint'
	and 'deep' reductions.



1.02-2
	
	Summary
	=======

	This is a bug-fix re-release of 1.02. Unfortunately all but the
	'deep' mode reductions of the prior 1.02 release were broken. Sorry
	for that.


	- [BUG] Source removal had a nasty bug due to a typo. It was not
	functioning correctly at all, causing problems in all but 'deep'
	mode reductions. Very sorry for that.

	- [BUG] Calculating source weights could end up hanging in default
	and mode, or generally when 'sourcesize' was not expliticly specified.

	- [BUG] Erroneous behaviour when data file fell outside of the tau
	calibration scaling interpolator range. When this happened the 
	calibration value used was going wild...

	- [FIX] Individual scanmaps were written without casting into the
	desired mapping unit (i.e. as raw uV). This is now corrected.

	- [TUNE] extended filter now automatically applies filter corrections
	for point sources. Also, the correction is made smart to avoid double
	corrections.

1.02

	Overview
	========

	This release fixes a few critical bugs from prior versions. Most
	importantly, the noise whitening filter was not behaving as intended.
	Also, the He3 temperature correction for LABOCA was broken.
	This version builds more heavily on commonalities among instruments
	thus minimizing the possibility of some functions working for certain
	instruments but not for others.	
	There are a number of new convenience features introduced in this
	release also such adding external calibration support (via a
	calibration data file), and automatic pixel-flags and RCP determination
	based on MJD (as defined in 'flagging.dat' and 'rcps.dat' inside the
	instrument subdirectories. 
	The bundled 'crush.jar' file is updated to 1.63-1.
	All in all, this version brings many improvements, which at the end of
	the day should result in better images.
	
	Details
	=======

	- [NEW] Added option 'sourceweights' allowing to calculate separate
	pixel weights for source modeling. If not specified, then the usual
	pixel weight will be used. The two are equivalent if the pixel noise
	is white. However, in all other cases, it is a good idea to calculate
	source weights separately.

	- [NEW] Added option 'relative-pixel-noise' to give user control
	how pixels are flagged based on their derived noise properties. The
	range specifies acceptable noise levels relative to the median pixel
	noise. A range is specified by the minimum and maximum allowed values
	separated by any '-', ':', ',', or white space characters. E.g.,

		relative-noise-range 0.1--10

	will allow channels with noise up to a decade more or less than the
	median pixel noise.

	- [NEW] Introducing 'time-weighting' in the pipeline. The 
	time-weighting is performed on blocks of size equal to that used
	by the drift modeling (for now...)

	- [NEW] Added preliminary support for SABOCA.

	- [NEW] Added options 'spectrum' to write channel power spectra
	as an ascii table. Possible arguments are the name of the window
	function to use and the binning size (in powers of 2!), separated
	by a comma if both specified. The default window is 'Hamming' and
	the default binning is 512.
	
	- [NEW] Added option 'sources' to insert artificial sources in a
	real map. The argument is a filename to a standard CRUSH mask file.
	However, the peaks need to be specified in volts.

	- [NEW] Added key 'rcpgains', which when present forces MiniCRUSH to
	use the source gains directly from the RCP, rather than the gains
	that are calculated based on the correlated sky response. Don't forget
	to change the calibration factor to match BoA's (which is defined
	for exactly this case.)

	- [NEW] Added key 'maxHe3rms', which specifies (in mK) a maximum 
	allowed base temperature fluctuation rms. If the scan exceeds this
	limit, it is removed from the dataset under reduction. This helps
	getting rid of scans where temperature fluctuation was excessive.
	
	- [NEW] Automatic cross-talker flagging based on MJD ranges defined in
	'laboca/Laboca-cross.dat'.
	
	- [NEW] Added key 'uniform' to specify using uniform gains at start
	rather than the gains read from the pixel data file...

	- [NEW] Effective point source NEFD is added to console output for
	each scan as the last number in square brackets. As opposed to the
	round bracket values derived when weighting, this number take into
	account the point-source filtering corrections, thus providing the
	most reslistic average sensitivity estimate.

	- [BUG] Another noise whitening bug found and fixed: The time-series
	array that was used for the FFT calculation was not completely cleared
	from pixel-to-pixel, resulting in junk data remaining from one pixel
	to the next in the calculation.

	- [BUG] Weighted median was wrongly calculated. This is hopefully
	fixed now. Problems could have resulted when median estimators were
	used instead of the default maximum-likelihood ones. As a result of
	the fix, median estimators are now default for signal estimation
	except for 'deep' mode reductions... 
	(but not for gains and weighting)..

	- [BUG] Whitening did not work as intended, as median estimation
	has destroyed the order of the spectral array, thus applying the
	filtering at the low frequency end of the spectrum.

	- [BUG] Pixels that had no position definition in the RCP were not
	'placed far enough' to be flagged for impossible position later...

	- [BUG] He3 temperature correction was quite broken, in effect not
	doing anything (since the temperature gains were not read). There
	were several other issues as well, which are now fixed...
	
	- [CHANGE] Various changes to noise-whitening filter, to improve
	performace and calibration.

	- [CHANGE] Rehabilitated decorrelation on amplifier boxes. Some
	scans clearly show box-correlated signals, while this may not be
	so obvious with other scans. However, to get clean results, box
	decorrelation is now back...

	- [CHANGE] The individual scanmaps generated by the 'scanmaps' option
	now carry the MJD day as well as the scan number in their filenames
	to allow for duplicate scan numbers year after year...

	- [CHANGE] The output of "pixeldata=write" option now contains 
	weights derived with point-source filtering correction.

	- [CHANGE] Changed behaviour of 'tau' configuration key. It can
	now be used either to specify a numerical zenith tau value, or
	it can specify a file to a tau table, from which values can be
	interpolated.

	- [CHANGE] Similarly to above, the parsing of the 'scale' key is
	also changed. It can either specify a numerical scaling value, or
	values can be looked up from appropriate calibration tables by the
	ISO timestamp.

	- [CHANGE] Switched to 'differential' weighting scheme.

	- [CHANGE] Automatic rcp-file lookup for LABOCA, based on 
	MJD ranges defined in 'laboca/Laboca-rcps.dat'

	- [CHANGE] Gridding changed to ~1/5 beams. The finer grid results
	in better calibration.

	- [CHANGE] In 'deep' mode, now whitening first, before looking for
	time-stream spiky features. This makes better sense because spectral
	features are almost always present, and spikes tend to have a white
	spectrum anyway. Thus, the presense spikes does not distract the 
	whitening, but the spectral features may appear as time-stream 
	features... 
	
	- [CHANGE] Whitening is now applied to all pixels not just 'good'
	ones. Also, the method now scales excess spectral power to the
	excess limit, rather than to the median spectral power. This results
	in less discontinuous specral shapes/filtering -- meaning less
	artifacts in the map.

	- [CHANGE] Reading pixel data files adds pixels flags to those
	already defined. Previously, it set flags ignoring prior values.

	- [CHANGE] More shared code among instruments. Helps to keep things
	synchronized with changes :-).

	- [TUNE] Turned off 'scanweighting'. Weight estimation shuold be
	good enough to arrive at the fait weights. However, scanweighting
	is performed before smoothing/filtering, and thus will not be
	representative of the final map. For this reason scan-weighting is
	now only enabled in 'faint', 'extended' mode.

	- [TUNE] Despiking by the 'features' method has been removed from
	the 'deep' mode configuration ('deep.cfg'). It could go 'crazy' with
	certain whitening settings and time-weighting. Instead, 
	time-weighting and despiking should deal with the problem of wide 
	spikes. This is the approach taken from now... 	

	- [TUNE] Recalibrated LABOCA conversion factor and taufactor.

	- [TUNE] Small change in setting the non-flagging limit for 
	time-domain features.

	- [TUNE] Adjusted automatic filtering settings to try minimize 
	overfiltering of timestreams.  

	- [TUNE] Changed scan initialization order.

	- [TUNE] Raised clipping/blanking and scanmap despiking levels
	such as to minimize the unwanted scenario of noise peaks falling
	false casualty to these. The result is more reliable maps down to
	the detection limit.	

	- [FIX] Slight pixel weight normalization in beta release 1.02-b1,
	due to misaccounting of the degrees of freedom... 

	- [FIX] Whitening fixed s.t. it better cooperates with flagged data.
	This is achieved by the filter subtrating an excess noise signal rather
	than replacing signal with the filtered one, as before. The previous
	method overwrote all spikes and flagged data, thus the original 
	information (e.g. source) were lost in the flagged bits. The new method
	preserved information in the flagged parts, only modifying it as
	needed.

	- [FIX] Small discrepancies in the dependency accounting (used for
	proper weight normalization) were fixed.

	- [FIX] 'gains median' did not actually switch to median gain
	calculation for group correlated models due to a coding bug. This
	is now corrected...

	- [FIX] Median estimators could cause problem when a single data point
	diminates the data set. In such cases the median would be too heavily 
	dependent on that one point, causing it to be excessively cleaned and 
	overweighted. Thus a safety pin was introduced that checks to make sure
	that the data set on which the median is evaluated is not too heavily
	dependent on a single point. When it is, the estimate reverts to the
	usual maximum-likelihood one. In short, this is to say that medians are
	good estimators when there is lots of data, not just a few points...

	- [FIX] Gain normalization is followed by an appropriate renormalization
	of the correlated noise estimate. The lack of this before was not 
	necessarily a problem since initial gains were subject to the same
	normalization already, thus renormalizing factors very close to 1
	resulted. Nonetheless, this is all more proper now.

	- [FIX] A little more consistency over pixel flagging. Blind channels
	are now retained and used in correlated signal estimation. They are
	not used for source mapping (for obvious reasons).

	- [FIX] Adjusted the use of weights for mapping to avoid double
	counting the filtering effects...

	- [FIX] The effect of whitening is now icorporated in the channel
	weight estimates.

	- [FIX] Fixed noise whitening normalization in light of Parseval's
	theorem...

	- [FIX] Filtering of extended structures had blanking at 3-sigma. Thus
	several noise peaks in a typical map would be blanked, making the
	filter biased lower, and thus elevating some positive noise peaks
	to above detection threshold. Now the filter blanking has been
	raised to 5-sigma, which should minimize such undesired behaviour...

	- [FIX] Some instrument data file names were hardcoded with the
	UNIX style file separators '/', making these unusable under Windows
	environments...

 
1.01

	Overview
	========

	This update fixes many of the outstanding bugs in the prior (1.00) 
	release, and adds some new features, such as support for the newly
	commissioned photometric observing modes for LABOCA. There has also
	been an overhaul of the scripting/configuration support, with slight
	changes to the syntax (see below and in the README).
	The README file has been updated, and the 'Quick start' section 
	has been expanded into a more detailed starter's cookbook.


	Details
	=======

	- [NEW] New option 'photometry' is introduced to allow reduction of
	data taken in the new photometry mode of LABOCA. Instead of making
	a map, a single point source flux is calculated and displayed at the
	end of the reduction process. A word of warning: this functionality is
	still in its experimental state. Expect it to evolve and finalize 
	some time later...	

	- [NEW] New option 'scanmaps' will write individual maps for each scan
	in the reduction as 'scan-<scanno>.fits' in the usual output directory.

	- [NEW] New key 'stability' can be used for defining the 1/f stability
	time scale in seconds. This value is used for determining optimal
	filtering parameters for the reduction (e.g. for 'drifts' option), 
	unless explicit values are specified.

	- [NEW] 'boards' is now defined for ASZCA as 10 horizontal stripes on 
	the array. Decorrelating on these helps to arrive at cleaner 
	timestreams.

	- [NEW] Added FITS keyword 'INTEGRTN' describing the total integration
	time (in seconds) for the map. 

	- [NEW] The option 'spikewidth' can now take 'auto' as value, which
	will look for features up to the time scale determined by the 1/f
	filter setting...

	- [NEW] Rough ASZCA calibration on Mars (single scan at 30 deg). 
	Peak 1.07uV for 65.57 Jy. Assuming 2mm water --> 58.3 Jy/uV.

	- [NEW] Multiple fixes and improvements in ASZCA reduction...

	- [BUG] Pixels in multiple subscans weren't correctly handled due to 
	a cloning bug...

	- [BUG] 'offsets' was not working due to a typo. In any case, 'drifts'
	was the default and preferred way of obtaining residual DC offsets.

	- [BUG] As frames were slimmed to the minimum necessary size, the 
	sample flags were erroneously copied. This did not have much maleffect
	in standard reductions...

	- [BUG] Noise whitening had an inverted scaling problem. Now fixed. 

	- [BUG] ASZCA reduction was broken. Now fixed...

	- [FEATURE] LABOCA option '-he3=thermistor' was not effective due to a
	bug in reading the monitor table (Actually, the bug was in the FITS
	library). A workaround now corrects this. 

	- [FEATURE] Median scanning speeds were off by a factor of 2, 
	resulting in a bit of overfiltering at times...

	- [CHANGE] Slight changes to syntax. The new syntax is more coherent
	and less error-prone. The bigger changes are:

	   * Key/value pairs can be separated by '=', ':' or white spaces
	     or any combination of these in all places. Restrictions on the
	     command line mean spaces cannot be used there.
	   * the old 'iteration:XXX' keys are replaced with 'iteration.XXX'. 
	   * 'forget=iteration' is replaced with 'iterations=clear' for 
	     clearing iteration-based settings.
	   * extendedopts -> extendedopt, and each settings compounds the 
	     previous one. The separator for shorthand listing is '|'.
	
	See README for complete details.

	- [CHANGE] Some renaming of the decorrelation groups, for better
	consistency between LABOCA and ASZCA. The following groups are now
	defined:

	  (1) Detector groups

		wafers		(ASZCA only -- was 'squidgroups')
		regions		(ASZCA only -- 12 horizontal strips)

	  (2) Electronic groups
		
		boxes		(LABOCA & ASZCA)
		cables		(LABOCA & ASZCA)
		amps		(LABOCA & ASZCA)

	In case of ASZCA, cables and amps are effectively the same 
	(1:1 mapping), so one should only use one of these, not both...
	
	- [CHANGE] The key 'whiten' for noise whitening now can take an
	optinal relative spectral amplitude (over the median) above which
	the whitening is performed. This is to accomodate settings other than
	the default value...

	- [CHANGE] LABOCA automatically loads the new RCP file for scans after
	the February 2008 alignment (from laboca/master-laboca-feb08.rcp). 
	(Otherwise laboca/master-laboca-oct07.rcp is used).

	- [CHANGE] Disabled decorrelating on amplifier boxes for LABOCA by 
	default. Instead decorrelating on 'cables' alone is encouraged. 

	- [CHANGE] Cable gains were added to laboca pixel data file. These
	are now loaded as initial values, increasing the speed of convergence.
	
	- [CHANGE] Removing atmospheric 'sky' gradients is no longer default.
	There was little evidence for these at 850um for LABOCA. Therefore
	this reduction feature is now disabled. To re-enable just specify
	the option 'sky' either in the relevant configuration file or on the
	command line.
	
	- [CHANGE] Further changes to MEM. The target model used to be a
        beam-smoothed version of the map. This means that the MEM solution 
	is subjected to very much the same artefacts (e.g. negative lobes) 
	that affect the maximum-likelihood maps.
        From now, a more extremely smoothed map is used (with 5 beam widths),
	which should provide more realistic behaviour for low signal-to-noise
	signals both when a faint extended emission is present or with flat
	(zero) backgrounds.

        - [CHANGE] MEM correction is now applied after all other
        post-processing steps. All steps are performed, including smoothing.
        The MEM target model is generated from the beam-smoothed processed map
        by enforcing positivity.

        - [CHANGE] Revisited MEM algorithm. Changed entropy deifintion from

           H = - sum_i (1+A_i/sigma_i) log((A_i+sigma_i) / (T_i+sigma_i) - 1)

	to

           H = - sum_i sqrt(1 + A_i^2 / sigma_i^2) * log(X_i - 1)

        where

           X_i = sqrt(A_i^2 + sigma_i^2)/sqrt(T_i^2 + sigma_i^2)

        This definition has the following advantages over the original one:

                * Works for both positive and negative signals and models
                * lambda > 0 assures convergence towards the model
                * No need for explicit positivity regularization

        A a result of the last property, the previously introduced
        mem-clip, mem-absolute and mem-square options to sourcemap have been
	abandoned, and instead only 'mem' is retained.

	- [CHANGE] Behaviour of 'extended' mode under the default configuration
	has changed. Instead of iterating longer, it now suppresses
	decorrelation of band cables (for laboca) and squids/squidgroups
	(for aszca) until the third iteration.

	- [FIX] Bi-directional gain normalization was slightly off in the
	way the weighted average was calculated. This should have had 
	imperceptible effect on prior reductions. :-)

	- [FIX] Source blanking stayed active in 'deep' mode. This is 
	unnecessary as the benefits of blanking are only reaped when the source
	map is iterated. However, in 'deep' mode, only a single source map
	is produced. Thus blanking is now turned off for deep reductions.

	- [FIX] Filter blanking was uncannily tied to the regular source 
	blanking setting, rather than using its own specification. This is now
	corrected...

	- [FIX] Syntax problem found in some configurations specifying 
	'extendedopts'. The configurations have been updated accordingly...

	- [FIX] Cross-talking channels weren't thrown out. They were flagged
	nevertheless, causing no harm...

	- [FIX] Changes to the usage of HIERARCH keys.

	- [FIX] Trimming after downsampling. Without it, the downsampled data
	could start or end with null frames, causing problems with some routines
	like logging.

	- [UPDATE] Updated 'laboca/pixel-12067.dat' and 'aszca/pixel-5700.dat'

	- [UPDATE] Updated configuration files.

1.00

	- [NEW] Can now use non-default RCP files via the 'rcp=<filename>' 

	- [CHANGE] 'pixeldata' option changed s.t. it can both read and
	write pixel defaults (gains, weight and flags). Syntax is either
	
		pixeldata=write		Write the pixel data.
		pixeldata=<filename>	read from <filename>

	- [NEW] Can now specify a list of pixels to be flagged explicitly
	via the 'flag=ch1,ch2,...chn' option, which simply takes a comma-
	separated list of backend channel numbers. 

	- [NEW] Implemented MEM corrections to source map. The Maximum-Entropy
        mapping can be activated by selecting one of the options below for
        the 'sourcemap' keyword:

                mem-clip
                mem-absolute
                mem-squares

        These correspond to three approaches for ensuring positivity, itself
        a requirement of the MEM method. The first simply zeroes the negative
        parts of the map. The second uses absoulute values, while the third
        uses the squared-values in the MEM equation. The option 'mem' is
        identical to 'mem-clip'.
        Additionally, the "closeness" to the pure MEM solution can be chosen
        by lambda recommended to be in the range 0--1 (although higher values
        are admissible). The value zero applies essentially no MEM correction
        to the Maximum-Likelihood map, while higher numbers increase the
        importance of the Maximum-Entropy property relative to the Maximum-
        Likelihood property of the map.


	- [NEW] Subscans are merged for reduction. LABOCA should normally be
	operated in continuous mode, but sometimes that is not the case, 
	leaving one with many subscans for the same scan. Now these are all
	merged as if they were part of one continuous data set...

	- [NEW] Implemented point source flux corrections for the various
	filtering effects of auxillary signal models. This is mainly affects
	reduction in 'deep' mode where only one source generation is
	produced. In other modes, iterating of the source map with clipping
	and blanking settings makes such corrections unnecessary for 
	structures above the critical levels, but it may still help achieve 
	faster convergence, thus its not completely without use then either...
	For the faint structures, below clipping and blanking, a different
	method can be used, which is a little more approximate and can
	be activated by the 'scanmap-correction' key.
	Neither of these methods applies corrections for the explicit filtering
	of extended structures via 'filter'. This can be done manually or
	via 'imagetool', which is filtering aware...

	- [NEW] New key 'nefd-range' allows to specify an acceptable range for
	the derived NEFD. Only when the average scan noise level, as measured 
	from the data, falls within this range will it be used to contribute
	to the mapping. Syntax is either:

		nefd-range <min>, <max>
	
	or
	
		nefd-range <max>

	The values are to be supplied in Jy sqrt(s) units.	

	- [CHANGE] Changed laboca beam size from 18" to 19.5". This is more
	realistic given beams measured on point sources.

	- [CHANGE] Recalibrated LABOCA after the new filter corrections were 
	implemented. The calibration has been separated into aperture
	calibration which is found to be 5.33 Jy/uV (in laboca/default.cfg)
	and points-source or peak-flux calibration, which is measured at
	5.43 Jy/beam / uV (in laboca/deep.cfg). The aperture calibration is
	default for all but 'deep' reduction modes, while peak calibration
	is used for 'deep' reductions. Fluxes are generally expected to be
	accurate to 10%, without additional corrections.

	- [CHANGE] Filtering of extended structures now takes an optional
	second argument to specify the filter-blanking S/N level. When not
	explitictly specified, the regular 'blank' value is used. Thus
	the new syntax is:

		filter <fft|convolution> [blanking-S/N]  


	- [BUG] Median calculation was a little buggy. It's not a huge deal
	because medians were rarely really used. But now they can be used!!!
	Indeed, medians may be preferable to maximum-likelihood estimators for
	the various auxillary models as it has little or no filtering effect
	on the source signals...

	- [FIX] In some cases unrealistically large pixel weights could result
	when decorrelation happened on pixel groups that had all but one member
	flagged. By restricting decorrelation and gain measurement to groups
	that have more than a single useful pixel, this is hopefully corrected.

	- [FIX] Small changes in the way file names are processed that should
	enable running minicrush under Windows platforms. This is not however
	tested. If anyone is willing to try and report problems to me at
	<attila@submm.caltech.edu> then I promise to fix those quickly :-)

	- [FIX] The FITS key 'V2JY' in unfortunately defined inversely for
	SHARC-2. For compatibility reasons, the minicrush output is made
	to comply. Thus the value actually measures voltage response to 1 Jy
	flux in a detector pixel (not the other way around!).

	- [FIX] Small bug in discovering pixel neighbours. Some invalid
	neightbours may have been added. This caused no problems whatsoever
	but it was not the intended behaviour...

	- [TWEAK] Tweaked 'faint.cfg' to be more tolerant to the potential
	presence of brighter features.

	- [TWEAK] Median correlated noise removal speeded up, by recycling
	temprorary storages.	

1.00-rc2

	Overview
	========
	
	Unfortunately, the prior release was extremely buggy, to the extent
	of being dysfunctional. Multi-threading especially was broken, 
	affecting those running on multiple CPUs. After a thorough bug-fixing, 
	minicrush was optimized for speed as well as for maximal image depths 
	(esp. in deep modes). Further problems have been fixed with ASZCA
	reduction, which was also broken. Hopefully, this version is worthy
	to be called a release candidate (unlike the previous one).
	
	Details:
	========

	- [CHANGE] The option 'vclip' now takes one or two arguments in the
	form:

		vclip minv [maxv]

	where 'minv' and 'maxv' are minimum and maximum admissible scanning 
	speeds in arcsec/s, and the second argument is optional.	

	- [BUG] Option 'blacklist' was not cumulative thanks to an incomplete
	code change at some earlier point. Sorry.

	- [BUG] ASZCA-processing was dysfunctional in several prior releases 
	due to an outdated initialization sequence, and a zenith tau that 
	defaulted to NaN. 

	- [BUG] More bugs in multi-threaded map-making. Some private variables
	that are meant to speed calculations, were shared among parallelized
	objects, causing them to 'crosstalk'. 

	- [BUG] Frame spiky flags were not properly revised in successive
	despiking rounds.

	- [BUG] Sky gradients gains were botched, resulting in unpredictable
	behaviour. Gains are 'shifted' such as to keep the expected gradient
	over a constant field zero (as it ought to be). Same adjustment made
	for LABOCA cable twisting estimation.

	- [BUG] Despiking method 'features' did not fully clear sample flags
	from prior rounds of despiking. May have resulted in overflagging...
	
	- [BUG] When source modeling was turned off for some iterations, like
	in faint.cfg in 1.00-rc1, the source map got completely reset, causing
	the features modeled that far to be be flushed....
	
	- [BUG] In prior version map sizes were wrongly calculated, often 
	resulting in an ArrayIndexOutOfBoundsException being thrown when
	trying to actually make the map. Sorry.

	- [BUG] 'whiten once' directive caused misbehavior when multiple scans
	were reduced...

	- [FEATURE] 'gains maximum-likelihood' had no effect in prior release.
	Gains were always solved with median estimators.

	- [FEATURE] 'scanmap-redundancy' in 'default.cfg' was not well defined
	and thus reverted to the default value of 3...

	- [FEATURE] Channel flagging following despiking is now essentially the
	same no matter what despiking method was used, with only a correction
	for increasing the allowance if 'features' method was used AT ANY POINT
	PRIOR. In the previous release, channels that have been flagged for
	spiky features could have become unflagged by another despiking method
	under certain circumstances. Now spiky channel flags stick like they
	should.

	- [FEATURE] Spikes were not marked for data that is excluded from 
	modeling. This is probably wrong, since the modeling flags can later
	be cleared, but the spike should stay active. It is another matter
	whether to count such as spike or not...

	- [FEATURE] 'gains median' had no effect except correlated noise model.
	This is now fixed. 

	- [IMPROVEMENT] Source blanking has been combined with synching, making
	it considerably faster. As a result blanking will not take place under
	'sourcemap nosync'. Another effect of the change is that blanking flags
	are cleared when blanking is disabled, which was not the case prior
	to this change. Clearly, this is the preferred behaviour.

	- [IMPROVEMENT] 'deep' configuration updated based on extensive
	testing with different settings.

	- [IMPROVEMENT] Speeded up map projection calculations by allowing
	compiler to inline most of the calls.

	- [NEW] Added 'Radio' (GLS) projection to the list of usable 
	projections. This is mainly to comform with BoA's updated output.
	(Careful, it isn't really tested, but what could possibbly go wrong...)

	- [NEW] Average (median really) scan speed is calculated and used to
	determine optimal 1/f filtering for given source sizes.

	- [CODE] Cleaned up code and removed a lot of unused functions.
	
	- [UPDATE] Updated files for ASZCA (configurations and pixel.dat). 

	- Small cosmetic changes...

1.00-rc1

	- All configurations files have been created anew from the ground up.
	
	- [***BIG BUG***] In 1.00 beta versions, things went awfully wrong
	in all but 'deep' reduction mode. Basically, whenever the source 
	map solution was iterated, garbage resulted. Extremely sorry if this
	affected you... 
	
	- [BUG] In prior 1.00 versions the reduction crashed when the number 
	of scans processed was smaller than the number of CPUs used. Sorry.

	- [NEW] Gave more control over what exatly the 'extended' flag does.
	Use the new key 'extendedopts' to specify a ;-separated list of
	options to set when 'extended' mode is selected. E.g.,
		
		extendedopts drifts 10.0; blacklist sky
	
	will set the 1/f filtering timescale to 10 seconds and will never
	solve for sky-gradients.

	- [NEW] key 'taufactor' can be used to multiply tau values from
	skydips (or equivalent). Axel's research into the calibration revealed 
	that skydip tau values are underestimated by a factor of 1.3 (+-0.1). 
	Thus setting 'taufactor 1.3' makes the skydip information 
	approximately correct. A possible explanation for the discrepancy is
	the optical loading dependence of bolometer gains, which can be
	effectively modeled as G ~ exp(-alpha * tau)...

	- [NEW] All configuration options, as effective during reduction, are
	written into the FITS header as HIERARCH keys + values. 

	- [NEW] Can now specify a minimum redundancy each map pixel should
	have in a map generated from single scans via the 'scanmap-redundancy' 
	keyword. This is useful to avoid using really underexposed mapping
	areas for each scan.

	- [NEW] 'weighting' can now take on options, specifying the method to
	be used. The following methods are available:

		rms		Use the standard 1/rms*2 weighting
		robust		Measure 'rms' using robust estimators
				(which are more resilient against spikes)
		differencial	Measure 'rms' based on differences between
				two data points separated by some time in
				the time stream. This method is not biased
				by long term variations, but may not be
				'fair' because it only measured noise in
				certain spectral locations rather than full
				band. 

	- [DEPRECATED] Removed initial gain iterations, thus the corresponding
	'gainrounds' and 'ordering:gains' configuration keywords no longer have
	any effect. 

	- [FEATURE] default configuration was too strict, resulting in 
	overflagging on bright sources. This has been relaxed. Now the default
	config ought to be good for up to a few hundred Jy... 

	- [FEATURE] In prior 1.00 versions the console output sometimes
	indicated that source was solved during gain iterations even though 
	it was not always true. This did not really affect the reduction, 
	only the reporting (thus it was a feature not a bug...)
	
	- [IMPROVEMENT] default reduction now proceeds more gradually. Maps
	are clipped in relation to subsequent despiking levels, allowing 
	fainter features to pass through additional despiking before recovered.

	- [IMPROVEMENT] Speeded up median offset removal routine, as well
	as allowed offset to be removed even if based on single datum.

	- [IMPROVEMENT] Further tweaks to despiking. 'neighbours' method now
	flags both suspect neighbouring frames as spikes. Critical spike
	fraction and count for channel flagging is accordingly adjusted to
	2x the normally tolerated value.

	- [IMPROVEMENT] Spiky frames and spiky channels are flagged after each
	round of despiking. Thus the 'despike frames' option is no longer
	necessary and is therefore removed. The number of tolerated spikes per
	frame is set by the 'framespikes' option.
	
	- [IMPROVEMENT] Flagging spikes has been diversified to distinguish
	between three different spike flags, depending on the algorithm used
	for despiking. This way the different despiking method do not reset
	each others flags, which should make despiking a little more 
	reliable...

	- [IMPROVEMENT] In 'deep' configuration, the default now is to iterate
	10 times. This should result in somewhat better deep fields. 

	- [IMPROVEMENT] Noise whitening algorithm smartened up. Will scale down
	excess power only, and renormalizes to keep median absolute spectral 
	amplitudes unchanged. It works only on pixels that carry 'recoverable'
	flags, and skips over flagged or blanked data like other models.
	
	- [TWEAK] sky-gradients and LABOCA 'twisting' cables modeling 
	tweaked to better complement correlated noise and correlated cable 
	modeling respectively when not all cable pins are active (or not 
	equally sensitive).

	- [TWEAK] Changed behaviour of 'gains' keyword. It now enables solving
	for gains for ALL signal models which have that possiblibity (
	decorrelate, cables, boxes, boards, squids, squidgroups), unless these
	have the 'nogains' option set otherwise. Also, 'gains' can take an
	additional argument 'median' to specify that these should be estimated
	using medians rather than maximu-likelihood estimates. The 'median' 
	method is more resilient against spikes, and it is therefore default.

	- [TWEAK] Gains are normalized over the average of pixels that 'see' 
	and have not been previously flagged for abnormal gain behaviour.

	- [TWEAK] Source maps are not synched to data with incremental gain
	changes. This should result is slightly increased speed and more robust
	behaviour in the presence of spikes...

	- [SMALL BUG] in the way of accounting lost degrees of freedom during
	mapmaking. Used entire map for the estimate rather than scanmap...

	- [SMALL BUG] Scanmap leveling only in first map generation.

	- Source map initialization and source synching to timestreams are now 
	also multithreaded making these operations faster when more than one 
	CPUs are available for the calculation.

	- Updated the way the arrays are projected onyto the sky, accounting
	for the the fact the BoA array parameter files use the same offsets
	as the control system, which itself is not quite GLS...

	- Relaxed despiking in 'faint' mode to allow for up to 10 Jy sources
	to pass unflagged. This is useful when one is looking for faint 
	structures around moderately bright centers (e.g. spirals around 
	the brightish galactic nuclei).
	
	- Adjusted calibration to taufactor=1.3. Some 40 Uranus scans
	from the technical run yield blind calibration accurate to 6-7%!!!.

	- Updated external crush utils ('crush.jar') to v1.61-1.


1.00-b1
	
	- Parallelized processing to use use multiple CPUs if available. In 
	multi-processor machines, one can specify the number of CPUs that are
	to be 'left-alone' by crush, via the 'reservecpus' key. E.g.
		
		reservecpus 2

	will instruct to use all but 2 CPUs available. Naturally, at least 1
	CPU will always be utilized, even if too many are put on reserve...
	The number of parallel threads will be the smaller of the allowed
	number of CPUs and the number of scans processed.

	- [BUG] 'estimator median' instruction was not fully implemented 
	earlier. This version corrects the omission.

	- [BUG] squid-groups decorrelation (ASZCA only!) was not active due 
	to a typo in the code. Apologies if this affected you.

	- Despiking setting sticktened up again to provide better image depth.

	- [FEATURE] 'default.cfg' erroneously had 'featurewidth' key instead of
	'spikewidth' specified.

	- [NEW] minicrush now checks for version updates and notifies when
	new versions are released (similarly to CRUSH).

0.99-5
	
	- Changed noise whitening algorithm to whiten to median power in the
	spectral band between the 1/f filter knee and f_c/2. Ideally this 
	part of the spectrum should be flat, as it is unaffected both the 1/f
	noise at low frequencies (provided the filter is well configured) and 
	by the roll-off of any anti-alias filtering at the higher frequencies.
	Note, whitening is not enabled by default, and it is not recommended
	except as an experimental feature.

	- Changed map despiking algorithm to make it a little more robust
	against the presence of faint point sources. This should minimize the
	chance of accidental 'despiking' of point sources in 'deep' mode. 

	- [BUG] 'tau' keyword, for specifying tau explicitly, was ignored when
	sky-dip data was also available.

	- [LABOCA] Disabled decorrelation on amplifier boards. The redundancy 
	here is small (<= 5 pixels per board) making gain fitting unreliable. 

	- [LABOCA] Fine-tuned configurations. Changed 'features' despiking
	parameters. 

	- "scramble" key was not functioning. Fixed.

	- Updated external crush utilities to 1.61-b1.

0.99-4
	
	- updated configuration files. Some more stringent despiking for
	deep fields...

	- updated crush.jar for external crush tools.

	- option 'featurewidth' renamed 'spikewidth' which was already the
	form used in the configuration file... 

	- [FEATURE] It looks like ESO archive merges the several APEX fits
	files into a single fits per scan (which makes sense). However,
	minicrush was not trained to deal with these yet. This has been patched
	so should work now...

	- [BUG] UNIX shorthand '~' for home dirs and environment variables did
	now work for the 'outpath' option. Now should be fine. 

	 - [UPDATE] Refreshed spherical coordinate classes from tested crush-2
        project (this should not affect the behaviour in minicrush).

0.99-3

	 - [BUG] In external tools (e.g. 'coadd' and 'imagetool'). Again, in 
	last version introduced some new bugs with the projection update. This
	one was a miscalculated precession and coordinate epoch when 
	precessing equatorial coordinates. All good now (hopefully)...

	- [BUG] writing equatorial maps using the external crush tools (e.g.
	'coadd' or 'imagetool') had the wrong reference position in FITS
        (it was inverted by mistake). This bug was introduced only in the last
        beta relase with the projection update...

        - [BUG] imagetool's '-clip=' option was slightly misbehaving for
        equatorial maps following the projection update. This was only
        introduced in the 1.60-b1 release, and affects no earlier releases.

0.99-2
	
	- [FIX] Updated 'faint.cfg' and 'deep.cfg'. Deep mode accidentally
	solved for source too early.

