source: trunk/CHANGES @ 542

Last change on this file since 542 was 542, checked in by MatthewWhiting, 15 years ago

Added changes since last version.

File size: 26.9 KB
Line 
1Duchamp version 1.1.8 (2009/??/??)
2----------------------------------
3
4Improvements:
5
6* Screen output now has more information on the growing threshold when
7  the cube statistics are printed.
8
9
10Bug fixes:
11
12* The function that grows objects had a major bug, that stopped it
13  working when flagAdjacent=false. This has been fixed and should work
14  fine.
15
16* All calls to uint were changed to unsigned int, as some compilers
17  had problems recognising that they were the same thing.
18
19* src/fitsHeader.cc was missing an include statement for stdlib.h,
20  again causing some compilers to fail.
21
22
23Duchamp version 1.1.7 (2009/01/16)
24----------------------------------
25
26Improvements:
27
28* The mask file that can be created with flagMask can now specify
29  which object a given detected pixel belongs to, by taking the object
30  ID as its value. This applies if you set flagMaskWithObjectNum=true
31  (it defaults to false, which means each detected pixel has the value
32  1). Non-detected pixels still have the value 0.
33
34* The names of the output FITS files are now able to be specified
35  directly by input parameters. These will override the default names
36  that Duchamp provides.
37
38* The Karma annotation file now specifies a font - previously it did
39  not and so was at the mercy of whatever was specified in other
40  annotation files being viewed at the same time. Please let me know
41  if the font I've chosen (lucidasans-12) is not suitable.
42
43* The default flag, used in the absence of 'E', 'S' or 'N', is now '-'
44  rather than blank. This will ensure that each column in the results
45  file has something in it.
46
47* The configure script is somewhat more robust to non-standard
48  systems, particularly when the X11 libraries are in unusual
49  places. It can also deal with the slightly different way that
50  wcslib-4.3 installs itself.
51
52* The installation part of the Makefile was altered so that the
53  symbolic link Duchamp that points to Duchamp-1.1.7 does not have the
54  absolute path encoded in it. This will enable the files to be moved
55  around at a later date.
56
57Bug Fixes:
58
59* Fixed a bug that caused problems when the flux units were less than
60  5 characters long (e.g. 'K')
61
62* The new velocity width values were not getting proper headers in the
63  VOTable output. This has been remedied.
64
65* Minor improvements to help non-pgplot use
66
67* Minor fix in WCS functionality.
68
69* Minor fixes to the FitsHeader class.
70
71* Improved FITS data reading, that doesn't require a nullarray
72  array. This will reduce memory usage.
73
74* Improved subsection parsing, particularly for non-standard WCS
75  systems.
76
77* Improving the memory allocation of the Cube class.
78
79* Fixed a bug that meant the growthThreshold values were sometimes
80  being lost.
81
82* Improving the way the growing and merging is done, particularly in
83  the case of non-adjacent merging.
84
85* Fixed a scaling bug in the GaussSmooth function.
86
87Other:
88
89* Numerous changes to the code that do not affect how Duchamp itself
90  runs, but were necessary for code development with the Duchamp
91  libraries (primarily as a part of the ASKAP code development).
92
93
94Duchamp version 1.1.6 (2008/09/08)
95----------------------------------
96
97New features:
98
99* The velocity widths can now be quoted in two additional ways: the
100  full width at 50% of the peak flux (ie. the FWHM) and the full width
101  at 20% of the peak flux (w_50 and w_20 respectively). The w_50
102  parameter is now quoted in the results printed to the screen
103  (instead of w_VEL), but all three are written to the results file.
104
105* The facility now exists to bypass the searching step and go straight
106  to the output stage using a list of previously detected objects. The
107  list is extracted from a previously-created log file. The user can
108  change the way the spectra are plotted (e.g. choose to plot
109  integrated rather than peak spectra), and select a subset of the
110  detected objects to be printed to individual postscript files. Use
111  the input parameter usePrevious (set to true) to use this facility,
112  and provide a list of objects using the objectList parameter
113  (eg. 1,2,4,7-10,15)
114
115* A new parameter "growthThreshold" has been created, that goes with
116  "threshold". If you manually specify a threshold, and you wish to
117  grow detections, you need to manually specify a growthThreshold (in
118  flux units).
119
120Bug fixes:
121
122* Cubes that do not have a spectral axis (such as Stokes cubes) were
123  causing memory leaks and crashing, due to some assumptions of the
124  existence of the spectral axis. These bugs have been fixed, so that
125  Duchamp will run on such cubes, although the WCS transforms may not
126  always work appropriately. Please let me know via bug reports of
127  difficulties you encounter!
128
129* The growing function has had a few bugs fixed and is now more
130  efficient.
131
132* The FDR method was previously overriding any manually-specified
133  threshold. This has been fixed so that if the user specifies
134  threshold=X, then the FDR method is not called.
135
136* Some undefined things were happening with textual output when no
137  objects were detected. This has been fixed.
138
139* Memory leaks caused by FITS WCS irregularities have been fixed
140  (specifically, if a FITS header had NAXIS=2 but more than two WCS
141  axes were defined).
142
143
144
145Duchamp version 1.1.5 (2008/03/20)
146----------------------------------
147
148Bug fixes:
149* A major bug was discovered in the calculation of integrated
150  fluxes. The flux was incorrectly being weighted by the spatial size
151  of the detection, resulting in a (often considerable) overestimation
152  of the integrated flux. This has been corrected.
153
154* The beam size calculation was also incorrect, being out by a factor
155  of 1/ln(2).
156
157* The "make install" command previously failed to work properly if the
158  library had not been created. This has been fixed so that the
159  installation works even if there is no library file.
160
161New Features:
162* You can now provide a new flux unit string, so that the pixel fluxes
163  will be converted to these new fluxes before any calculations are
164  done. This is done with the newFluxUnits input parameter. The new
165  units should be directly convertible from the old ones (given by the
166  BUNIT header -- e.g. if BUNIT = Jy/beam, you can give newFluxUnits
167  as mJy/beam, but not mJy).
168
169* You can now specify the precision used in the output files for flux,
170  velocity and S/N ratio columns, via new input parameters precFlux,
171  precVel and precSNR. These will apply to the VOTable output as well
172  as the text table and information on the spectral plots.
173
174* The Karma annotation files previously provided just a circle at the
175  spatial location of the detected object. You now have the option to
176  draw a border around the detected pixels (in a similar manner to the
177  PGPLOT moment maps). Karma does not do this perfectly, so the lines
178  may not line up exactly with the pixel borders, so the option
179  remains to keep using the circles. This is controlled by the
180  parameter "annotationType", with possible options being "borders"
181  (the default) or "circles".
182
183* There is a new function getMetadata() that loads the header and WCS
184  data, but no pixel information. This is only of interest if you are
185  doing code development with the Duchamp library -- it does not
186  affect the running of Duchamp itself.
187
188Duchamp version 1.1.4 (2008/02/15)
189----------------------------------
190
191Most of the changes incorporated in this update result from ASKAP code
192development (that makes use of some of the Duchamp functionality),
193but do not actually affect the way Duchamp runs (other than, in a
194couple of cases, making it a bit faster). Changes that are
195relevant for regular users of Duchamp are as follows:
196
197* A new option has been made available (thanks to Mary Putman et al
198  for the suggestion!) to save the spectra of all detected objects in
199  a text file. This has the form of one column for the spectral
200  coordinates and one column of fluxes for each object. This is
201  enabled by the input parameters flagTextSpectra and spectraTextFile.
202
203* Slight changes to the output include he formatting of the way the
204  detected objects are written to the log file. This meant the
205  verification files were also updated. Also the cube statistics are
206  not printed to the results file if a user threshold is specified (as
207  they are not calculated!).
208
209* The determination of beam size has been made more reliable, as has
210  the BUNIT determination.
211
212* Fixed a bug that meant source merging was not done for 2D images
213  (not usually a problem, as the source-finding takes care of this,
214  but came up in parallelisation development).
215
216Duchamp version 1.1.3 (2008/01/08)
217----------------------------------
218
219A minor update that just improves the build process. The location of
220the wcslib include files was not specified correctly, so that some
221machines were unable to find them. The configure script has been fixed
222so that the compilation should work in all cases.
223
224Some minor changes have also been made to the code in the PixelMap
225directory, and to param.cc, to fix warnings or errors that may appear
226in compilation.
227
228However, there are no changes to the actual workings of the code in
229this minor version, so if you have a working version of Duchamp 1.1.2
230there is probably no reason to update.
231
232Duchamp version 1.1.2 (2007/12/07)
233----------------------------------
234
235Compilation:
236
237* The compilation had problems working correctly when the cfitsio and
238  wcs libraries were not in standard locations. The configure script
239  has been tweaked to make sure the libraries are found.
240
241* Problems with compiling in the absence of pgplot have been fixed,
242  and it should now compile fine.
243
244* Improved the configure script for use with Mac OS X and gfortran.
245
246
247Bugfixing:
248
249* A major problem with the text-based output was fixed. The widths of
250  the columns were not being calculated correctly, and were running
251  together. This should no longer be the case.
252
253* There was a bug in the way Duchamp interpreted spectral axes,
254  particularly AIPS types such as FELO-HEL, leading to incorrect
255  scaling of the velocity axis. This has been fixed, so that
256  non-standard types are now dealt with appropriately and the velocity
257  scaling should be accurate.
258
259* Another bug meant the beam correction was always applied to the
260  integrated spectra, regardless of whether the flux units involved
261  the beam (e.g. Jy/beam). This has been fixed. Note that the values
262  of the integrated flux presented in the results table were always
263  calculated correctly.
264
265* Other minor changes to improve the speed and efficiency, especially
266  of the merging code.
267
268New user parameters:
269
270* There is now the possibility to save a FITS file that contains a
271  mask array, indicating where the detected objects are. This is
272  governed by the flagOutputMask parameter.
273
274* The header information that is printed at the start of the results
275  file -- that is, the list of parameters, the statistics of the cube,
276  and the number of detections -- can now be written to a separate
277  file. Set the flagSeparateHeader parameter to true or 1 and it will
278  go to the file indicated by the headerFile parameter (the default is
279  duchamp-Results.hdr).
280
281* A "scaleMax" parameter has been added, so that the wavelet
282  reconstruction can include only a specified range of scales (for
283  instance, if one wants to search just for narrow features such as
284  absorption lines).
285
286* A "flagRobustStats" parameter has been added. This allows the user
287  to elect to use robust statistics (median and median absolute
288  deviation from the median) to estimate the noise parameters. If set
289  to false, the mean and standard deviation will be used. The default
290  value is true.
291
292New Feature:
293
294* When Duchamp is run on a 2D image (i.e. with no spectral output), it
295  now produces a postscript file that shows information each
296  individual source plus the image cutout of the source. This is
297  similar to the spectral output file, but without the spectra. The
298  filename is given by the spectraFile parameter.
299
300* Ability to save a FITS file containing a mask array, with pixel
301  values of 1 for pixels in a detected object, and 0 elsewhere.
302
303
304Duchamp version 1.1.1 (2007/07/20)
305------------------------------------
306
307Minor update to the release, with just a few changes:
308
309* The verification script was generating diffs due to differences in
310  the precision of some calculations when done on different machines.
311  One of these was the integrated flux, and this has been corrected so
312  that the same value should appear on all machines.
313  The verification script has also changed so that just the number of
314  sources and their positions are tested, as well as the
315  logfiles. This should avoid the reporting of spurious differences.
316
317* The grey-scale used in the image cutouts (in the spectral plots) has
318  been inverted. This makes it consistent with the scale used in the
319  maps, and hopefully easier to see when printing.
320
321* The configure/make system has been altered to make it easier to
322  install, and to specify different external libraries. In particular,
323  it is now not necessary to have PGPLOT installed on your system to
324  run Duchamp. In the absence of PGPLOT, Duchamp will run as normal,
325  just without any graphical output. Some source code needed to be
326  restructured to make this work. Please read the README file, or the
327  Installation appendix in the User's Guide, for complete details.
328
329* The time of completion is now written to the log file, so that the
330  user can have some idea of how long the program took.
331
332
333Duchamp version 1.1 (2007/05/17)
334------------------------------------
335
336Changes made since the last numbered release:
337
338EFFICIENCY OF EXECUTION:
339
340* Major change to the way detections are stored. They are now recorded
341  via run-length encoding in the x-y plane, and stored as collections
342  of channel-maps. This improves the memory usage and the speed of
343  execution (particularly for routines such as the merging
344  routines). The memory usage has also been improved by changing the
345  way the list of detected objects is stored.
346
347SMOOTHING:
348
349* Addition of ability to spatially smooth the cube before
350  searching. This is done with a Gaussian kernel, the size and shape
351  of which can be specified by the user, using the parameters kernMaj
352  & kernMin (which are the FWHM for the major & minor axes -- if
353  kernMin is not given it is assumed to match kernMaj) and kernPA (the
354  position angle of the major axis).  There is a new parameter
355  smoothType that distinguishes this method from the spectral (Hanning)
356  smoothing already in use.
357
358DETECTIONS:
359
360* Changed the way detection is done -- now only search in 2D images,
361  keeping all detections (ie. no minimum-pixel requirement). This
362  should be the same as doing both the 1D and 2D searches with the
363  minimum pixel requirement in, but simpler. The rejection is done at
364  the end after all the merging and growing has been done. This leads
365  to a larger number of intermediate detections (ie.  the number
366  before merging), which may increase the run-time slightly, although
367  this is offset by the changes to the efficiency (see above).
368
369* Increased the range over which objects can be grown to match the
370  threshSpatial & threshVelocity parameters, as well as rejecting new
371  pixels based on the BLANK and MW tests.
372
373INPUTS:
374
375* There has been a subtle change in the way BLANK pixels are dealt
376  with. To enable trimming of BLANK pixels, users should use the new
377  parameter flagTrim. The parameters flagBlankPix and blankPixVal are
378  no longer accessible via the parameter file -- warning messages are
379  given if they are provided in the parameter file.
380
381* Added ability to specify a statsec, so that the statistics are only
382  calculated from a given subsection of the cube, rather than the full
383  cube.
384
385* The subsections can also specify the ability to remove a border of n
386  pixels from the edges of an axis (ie. n from the start and from the
387  end) -- as requested in Trac ticket #5.
388
389* Changed the default value of the reconDim parameter from 3 to 1, and
390  the default value of the flagATrous parameter to false.
391
392OUTPUTS:
393
394* The output now includes three different estimates of the "centre" of
395  the detection: peak location, centroid (flux-weighted), or average.
396
397* Some slight improvements to the user feedback during execution.
398
399* Spectral output now includes the baseline, if one was fitted. The
400  format of the plot headers is slightly changed, to stop information
401  falling off the edge of the page.
402
403* Added command-line option -x to directly disable the PGPLOT X-window
404  map plotting. This overrides the setting of flagXOutput in the
405  parameter file.
406
407* Fallback spectral units (in case the FITS header fails to record
408  them) changed to SPC, but code has been fixed so that any problem
409  should be caught before this becomes an issue.
410
411BUGFIXES:
412
413* Fixed bug (Trac ticket #4) that meant the velocity units were not
414  correctly dealt with. Duchamp should be more robust for different
415  velocity axis setups now.
416
417* Fixed bug (ticket #9) with the VOTable output, where the tags were
418  not closing.
419
420* Fixed a bug that meant the integrated fluxes were not calculated
421  properly -- no allowance was made for the number of spatial
422  pixels. This should also work properly for 2D images now as well.
423
424* Fixed minor bug in calculating the flux threshold from the p-value
425  threshold when the FDR method is used. This did not affect the
426  actual thresholding, merely the quoted flux threshold in the results
427  file. Also, the MW channels are kept out of the p-value threshold
428  determination if they are being flagged.
429
430
431
432Duchamp version 1.0.7 (2006/11/22)
433----------------------------------
434
435One new feature, and some improvements and bug-fixes.
436
437* The user can now elect to Hanning-smooth the spectral direction of
438  the cube before the searching is done. This can be done instead of the
439  wavelet reconstruction (although if both are selected, the
440  reconstruction takes precendence). This functionality is switched on
441  and off by the flagSmooth parameter, and the width of the Hanning
442  kernel is governed by the hanningWidth parameter.
443
444* The smoothed array can also be written to a FITS file and read in at
445  the start in the same manner as the reconstructed array.
446
447* Several improvements have been made to the memory
448  management. Several memory leaks were fixed, and the memory usage of
449  Duchamp is considerably less, which will be a help for running it on
450  large cubes. The speed of some routines has also been improved, by
451  removing unnecessarily repetitive loops.
452
453* The sorting routines have been changed, and should now be slightly quicker
454  (and a bit more robust).
455
456* Enabled the scale bar (plotted on the 0th moment map in the spectral
457  output file) to be able to deal with much finer spatial scales (as
458  may be expected from VLBI data).
459
460* Other minor changes to code and presentation.
461
462
463Duchamp version 1.0.6 (2006/11/01)
464----------------------------------
465
466Some incremental improvements and changes to the code:
467
468* The statistics used for the detection are now calculated once for
469  the entire cube, rather than being calculated separately for each
470  channel map and spectrum. This results in a uniform threshold value
471  across the entire cube. The way the statistics calculations are
472  implemented in the code was changed, using a new statistics class.
473
474* This means we can report a peak signal-to-noise value for each
475  detection. This is given in the text-based output, as well as in the
476  summary information above the spectral output for each source.
477
478* The user can now elect not to have the moment map displayed in a
479  PGPlot window, through the use of the new flagXOutput
480  parameter. This should help in cases of running Duchamp on a dumb
481  terminal (with no X-display capabilities), or as part of a batch
482  script where the continual popping-up of the PGPlot window might
483  become annoying.
484
485* There are different Flags reported for the case of an object lying on
486  the spatial edge and spectral edge of the cube (E and S respectively).
487
488* A few minor bug fixes:
489  - When providing a subsection, any axes with the range given by *
490    had the pixel values offset incorrectly. This has been fixed.
491  - Negative searches now correctly invert the reconstructed array
492    when it is read in from a file.
493
494* Other minor changes to the code, to improve memory handling and
495  remove redundant arrays and variables.
496
497
498Duchamp version 1.0.5 (2006/09/06)
499----------------------------------
500
501Since version 1.0, there have been a range of mostly minor
502changes. These are generally bug-fixes, thanks to feedback from a
503number of users, as well as a few extra features.
504
505Here is a summary of the changes since version 1.0:
506
507USER INTERFACE:
508
509* The user is now able to enter the value of flag parameters in the
510  parameter file as strings, as well as integers (so one can enter
511  true or 1 to give the same result).
512
513GRAPHICAL OUTPUT:
514
515* Added a new function that draws the edge of the blank region on the
516  maps and image cutouts. There is a new flag parameter --
517  drawBlankEdges -- that controls the use of this function (the
518  default is true).
519  Also, the edge of the field is plotted on the image cutouts as a
520  yellow line. This distinguishes it from the purple blank pixel
521  dividing line.
522
523* The size of the tick mark in the image cutout (indicating the
524  spatial scale of the image) is now adaptable, so that it shows the
525  scale that best fits the image (ranging from 1 arcsec to 15
526  degrees). (This is a change from the previous standard length of 15
527  arcmin.)
528
529* The zoomed spectrum had its flux scale determined by all points in
530  the zoom box,including those flagged by the Milky Way (MW)
531  range. This has been fixed so that any MW channels will not affect
532  the flux scaling, potentially improving the appearance of objects
533  detected close in velocity to strong MW emission or absorption.
534
535* Improved Karma Annotation file output, so that files without good
536  WCS are dealt with appropriately.
537
538TEXT-BASED OUTPUT:
539
540* The position resolution in the IAU-format names has been increased,
541  so that distinct objects close to one another are more readily
542  distinguished.  Overlapping sources at different velocities may
543  still have the same name, but this is a more general problem.
544
545* The presentation of the results in tabular format has been improved,
546  so that the precision of faint sources is sufficient to show their
547  flux, for instance, is not 0. This also applies to the information
548  presented above the spectral plots.
549
550* Improved error and warning reporting, so that the formatting and
551  presentation of information is clearer.
552
553FITS I/O RELATED:
554
555* The previous version was did not deal well with 4 (or greater)
556  dimensions in the FITS file -- the memory allocation was badly done,
557  and the axes needed to be in a particular order. This has been
558  fixed, so that the FITS I/O routines can now handle any sized FITS
559  file, with axes in any order (as long as there are two spatial and one
560  spectral axes).
561
562* When the FITS file does not have a rest frequency defined, there is
563  no way to transform the frequency axis into velocity. In this case,
564  the spectral axis is left as frequency, and put into units of MHz.
565
566* If the beam size is not indicated by the FITS header (through the
567  BMAJ and BMIN keywords), the user can manually specify the size
568  through the parameter file (using parameter beamSize).
569
570* The FITS I/O routines make use of the command fits_file_exists. This
571  was introduced into the CFITSIO package from version 2.5, so Duchamp
572  will only work with this version or higher. Version 3+ is preferred.
573
574OTHER BUG-FIXING:
575
576* Several bugs related to the blank-pixels were dealt with.
577  The correct values were not propagating through correctly, meaning
578  that the default values were being used. Also, there was the
579  potential for blank pixels to be detected when the FDR method was
580  used. Finally, the image cutout displays occasionally did not
581  obscure the blank pixels. All these problems should be fixed now.
582
583* The FDR setup routine was occasionally failing with a segmentation
584  fault, due to it accessing unallocated memory. This has been fixed.
585
586* Fixed bugs that affected the way 2D images (rather than 3D cubes)
587  were dealt with. The minChannels test failed when minChannels=0.
588
589* If there is no beam information in the FITS header, the user can now
590  enter a beam size as a parameter.
591
592* Other minor fixes to the code, to improve its structure and
593  robustness.
594
595
596Duchamp version 1.0 (2006/06/30)
597--------------------------------
598
599The first full release version.
600
601Several major changes compared to previous version:
602
603* Incorporated a FitsHeader class, to keep track of header information
604  (including WCS) from the FITS file. All units-related calculations
605  are done with this class, such as conversion to velocity, and
606  pixel-to-WCS conversion.  The main advantage of this is improved
607  speed of execution, more adaptable to different units, and improved
608  code (easier for me!).
609
610* Able to select the dimensionality of the reconstruction, rather than
611  just doing it in 3-D.
612
613* Robust text output, so that the columns are sized correctly given
614  the data being written, and the relevant units (derived from the
615  FITS header) are included in the output table.
616
617* Improved the way the reconstructed image is saved and read back in,
618  with a better naming scheme and a better set of new FITS header
619  keywords. The MW headers are now not written.
620
621Other, more minor changes include:
622
623* MW channels now not set to 0, but just ignored for searching
624  purposes (and for the scaling of the spectral output -- they are
625  plotted though and highlighted with a hashed box).
626
627* The scale bar in the moment map in the spectral output file has its
628  length indicated.
629
630* Improved VOTable output, with more information about the way Duchamp
631  was run.
632
633* Made sure all statistics calculations in the reconstruction are
634  based on robust (ie. median) methods.
635
636Also moved to an autoconf based configure/make compilation, for ease of use.
637
638
639Duchamp version 0.9.2 (2006/06/27)
640--------------------------------
641
642* Added the use of warning flags for detections: for either edge
643  location or negative enclosed flux.
644
645* A new command line option added so that the user can specify a FITS
646  file to be searched with the default parameters, rather than giving
647  a full parameter file.
648
649* The scale bar on the moment cutout now works in general case, using
650  an iterative process to get to the correct length.
651
652* RA axes are now done correctly on the full-scale maps.
653
654* Various coding fixes, improving the readability of the code,
655  particularly regarding the declaration of temporary variables.
656
657* Changed the way the time of execution is called : now using time.h
658  functions, rather than a system call.
659
660* Changed output in Detection/outputDetection.cc for the pixel
661  information of detected objects (the info printed above the spectral
662  plots) -- now print out number of voxels in object, and have
663  improved the formatting a little.
664
665* Improved the functionality of saving the FITS file containing the
666  reconstructed array. Added ability to save and read back in the MW
667  parameters when saving a reconstructed cube (if a reconstructed cube
668  has different MW range to that being considered, it would cause
669  problems). ReadRecon now just returns a FAILURE and will reconstruct
670  the cube anew.
671
672* Changed default value of flagGrowth to 0.
673
674
675
676Duchamp version 0.9 (2006/05/05)
677--------------------------------
678
679First public release version.
Note: See TracBrowser for help on using the repository browser.