dophot now can optionally output the full covariance matrix of a fit by choosing a file for COVARS_OUT in the parameter files
fixed memory bug in covar file output
fixed covariance matrix error causing extra step in covariance matrix update when switching fitting spaces.  covariance matrix diagonal elements in chisq are sqrt of autovariances.  additionally updated the covariance matrix updating and saving routine covarupd to save the true covariance matrix with correct autovariances rather than those with square roots.
chisq now heavily commented to explain that the output covariance matrix is NOT a covariance atrix but contains the sqrt variances and correlations.  OY.
Outputted covariance matrix should now be correct, contingent on further testing.
Covaraince outputs are now correct.  Output covariances are actuallt sqrt variances and correlation coeffieicnts so precision isn's lost in float math
onefit comments referring to working covariance matrix now are accurate
manual updated to include covariance matrix option
attempting to debug segfault on user's data set.  problem seemed to be related to insufficient memory allocated to empirical arrays for large FWHM stars.  I assumed that faulty centers on those stars meant that the program was trying to read/write to memory immediately outside of empirical arrays.  I created a memory buffer of a few cells per side on those arrays to try to alleviate the problem.  No avail.  Setting BUF memory buffer=0 and trying other solutions.  MAXFIL=2048 fixes large FWHM analytic case.
The problem seems to be that the empirical fitting is reading and FAR outside of the allocated memory space.  Must figure out why this is happening, specifically how the centers and other parts of the empirical array are determined.  This reading outside the array is happening during the fitcall in chisq.
I believe problem is fixed, but in perhaps an inelegant way.  If the improve chisq call to the empirical fit is moving the centroid more than 4.0 whole pixels, an error is written to the logfile and the offset is changed to a move of only 4.0 pixels.  SInce the empirical fit is only performed as an improve step, this should be an adequate movement size.  moreover, the movement truncation can only take place during a fitcall, not during an image adding or subtraction outside of a fit.  However the results are not fully tested as a set of empirical stars must be found for this image and fed as a warmstart
bug fixed.  more comments after cleanup
bestab now fixed so that a change of empirical star will not cause a bug.  specifically, the new empirical template is subtracted off as analytic in bestab so that the empirical template is already ready to be treated as such (added back analytically) in improve.  moreover, the designation for the old template is not updated until the next pass through bestab as the stars are still subtracted off using the old empirical template after leaving bestab and must be added back using that same old template.
empiricals receives a warning statement if improve's fitting cal is driving the fit out of the allocated memory bounds and urges the user to refit with proper constraints on the limitsfor x and y.
tuneup now outputs the psfsubraster if the psf file is asked for, not on the constraint that a template star is suggested.  former bug.
tuneable.h reset to default parameters in preparation for remerge with master
reverted Makefile in prep for merge with master