source: trunk/CHANGES @ 404

Last change on this file since 404 was 404, checked in by MatthewWhiting, 16 years ago

Changes for new minor version.

File size: 18.4 KB
Line 
1Duchamp version 1.1.2.1 (2008/01/08)
2------------------------------------
3
4A minor update that just improves the build process. The location of
5the wcslib include files was not specified correctly, so that some
6machines were unable to find them. The configure script has been fixed
7so that the compilation should work in all cases.
8
9As this is the only change in this version, if you have a working
10version of Duchamp 1.1.2 there is probably no reason to update.
11
12Duchamp version 1.1.2 (2007/12/07)
13----------------------------------
14
15Compilation:
16
17* The compilation had problems working correctly when the cfitsio and
18  wcs libraries were not in standard locations. The configure script
19  has been tweaked to make sure the libraries are found.
20
21* Problems with compiling in the absence of pgplot have been fixed,
22  and it should now compile fine.
23
24* Improved the configure script for use with Mac OS X and gfortran.
25
26
27Bugfixing:
28
29* A major problem with the text-based output was fixed. The widths of
30  the columns were not being calculated correctly, and were running
31  together. This should no longer be the case.
32
33* There was a bug in the way Duchamp interpreted spectral axes,
34  particularly AIPS types such as FELO-HEL, leading to incorrect
35  scaling of the velocity axis. This has been fixed, so that
36  non-standard types are now dealt with appropriately and the velocity
37  scaling should be accurate.
38
39* Another bug meant the beam correction was always applied to the
40  integrated spectra, regardless of whether the flux units involved
41  the beam (e.g. Jy/beam). This has been fixed. Note that the values
42  of the integrated flux presented in the results table were always
43  calculated correctly.
44
45* Other minor changes to improve the speed and efficiency, especially
46  of the merging code.
47
48New user parameters:
49
50* There is now the possibility to save a FITS file that contains a
51  mask array, indicating where the detected objects are. This is
52  governed by the flagOutputMask parameter.
53
54* The header information that is printed at the start of the results
55  file -- that is, the list of parameters, the statistics of the cube,
56  and the number of detections -- can now be written to a separate
57  file. Set the flagSeparateHeader parameter to true or 1 and it will
58  go to the file indicated by the headerFile parameter (the default is
59  duchamp-Results.hdr).
60
61* A "scaleMax" parameter has been added, so that the wavelet
62  reconstruction can include only a specified range of scales (for
63  instance, if one wants to search just for narrow features such as
64  absorption lines).
65
66* A "flagRobustStats" parameter has been added. This allows the user
67  to elect to use robust statistics (median and median absolute
68  deviation from the median) to estimate the noise parameters. If set
69  to false, the mean and standard deviation will be used. The default
70  value is true.
71
72New Feature:
73
74* When Duchamp is run on a 2D image (i.e. with no spectral output), it
75  now produces a postscript file that shows information each
76  individual source plus the image cutout of the source. This is
77  similar to the spectral output file, but without the spectra. The
78  filename is given by the spectraFile parameter.
79
80* Ability to save a FITS file containing a mask array, with pixel
81  values of 1 for pixels in a detected object, and 0 elsewhere.
82
83
84Duchamp version 1.1.1 (2007/07/20)
85------------------------------------
86
87Minor update to the release, with just a few changes:
88
89* The verification script was generating diffs due to differences in
90  the precision of some calculations when done on different machines.
91  One of these was the integrated flux, and this has been corrected so
92  that the same value should appear on all machines.
93  The verification script has also changed so that just the number of
94  sources and their positions are tested, as well as the
95  logfiles. This should avoid the reporting of spurious differences.
96
97* The grey-scale used in the image cutouts (in the spectral plots) has
98  been inverted. This makes it consistent with the scale used in the
99  maps, and hopefully easier to see when printing.
100
101* The configure/make system has been altered to make it easier to
102  install, and to specify different external libraries. In particular,
103  it is now not necessary to have PGPLOT installed on your system to
104  run Duchamp. In the absence of PGPLOT, Duchamp will run as normal,
105  just without any graphical output. Some source code needed to be
106  restructured to make this work. Please read the README file, or the
107  Installation appendix in the User's Guide, for complete details.
108
109* The time of completion is now written to the log file, so that the
110  user can have some idea of how long the program took.
111
112
113Duchamp version 1.1 (2007/05/17)
114------------------------------------
115
116Changes made since the last numbered release:
117
118EFFICIENCY OF EXECUTION:
119
120* Major change to the way detections are stored. They are now recorded
121  via run-length encoding in the x-y plane, and stored as collections
122  of channel-maps. This improves the memory usage and the speed of
123  execution (particularly for routines such as the merging
124  routines). The memory usage has also been improved by changing the
125  way the list of detected objects is stored.
126
127SMOOTHING:
128
129* Addition of ability to spatially smooth the cube before
130  searching. This is done with a Gaussian kernel, the size and shape
131  of which can be specified by the user, using the parameters kernMaj
132  & kernMin (which are the FWHM for the major & minor axes -- if
133  kernMin is not given it is assumed to match kernMaj) and kernPA (the
134  position angle of the major axis).  There is a new parameter
135  smoothType that distinguishes this method from the spectral (Hanning)
136  smoothing already in use.
137
138DETECTIONS:
139
140* Changed the way detection is done -- now only search in 2D images,
141  keeping all detections (ie. no minimum-pixel requirement). This
142  should be the same as doing both the 1D and 2D searches with the
143  minimum pixel requirement in, but simpler. The rejection is done at
144  the end after all the merging and growing has been done. This leads
145  to a larger number of intermediate detections (ie.  the number
146  before merging), which may increase the run-time slightly, although
147  this is offset by the changes to the efficiency (see above).
148
149* Increased the range over which objects can be grown to match the
150  threshSpatial & threshVelocity parameters, as well as rejecting new
151  pixels based on the BLANK and MW tests.
152
153INPUTS:
154
155* There has been a subtle change in the way BLANK pixels are dealt
156  with. To enable trimming of BLANK pixels, users should use the new
157  parameter flagTrim. The parameters flagBlankPix and blankPixVal are
158  no longer accessible via the parameter file -- warning messages are
159  given if they are provided in the parameter file.
160
161* Added ability to specify a statsec, so that the statistics are only
162  calculated from a given subsection of the cube, rather than the full
163  cube.
164
165* The subsections can also specify the ability to remove a border of n
166  pixels from the edges of an axis (ie. n from the start and from the
167  end) -- as requested in Trac ticket #5.
168
169* Changed the default value of the reconDim parameter from 3 to 1, and
170  the default value of the flagATrous parameter to false.
171
172OUTPUTS:
173
174* The output now includes three different estimates of the "centre" of
175  the detection: peak location, centroid (flux-weighted), or average.
176
177* Some slight improvements to the user feedback during execution.
178
179* Spectral output now includes the baseline, if one was fitted. The
180  format of the plot headers is slightly changed, to stop information
181  falling off the edge of the page.
182
183* Added command-line option -x to directly disable the PGPLOT X-window
184  map plotting. This overrides the setting of flagXOutput in the
185  parameter file.
186
187* Fallback spectral units (in case the FITS header fails to record
188  them) changed to SPC, but code has been fixed so that any problem
189  should be caught before this becomes an issue.
190
191BUGFIXES:
192
193* Fixed bug (Trac ticket #4) that meant the velocity units were not
194  correctly dealt with. Duchamp should be more robust for different
195  velocity axis setups now.
196
197* Fixed bug (ticket #9) with the VOTable output, where the tags were
198  not closing.
199
200* Fixed a bug that meant the integrated fluxes were not calculated
201  properly -- no allowance was made for the number of spatial
202  pixels. This should also work properly for 2D images now as well.
203
204* Fixed minor bug in calculating the flux threshold from the p-value
205  threshold when the FDR method is used. This did not affect the
206  actual thresholding, merely the quoted flux threshold in the results
207  file. Also, the MW channels are kept out of the p-value threshold
208  determination if they are being flagged.
209
210
211
212Duchamp version 1.0.7 (2006/11/22)
213----------------------------------
214
215One new feature, and some improvements and bug-fixes.
216
217* The user can now elect to Hanning-smooth the spectral direction of
218  the cube before the searching is done. This can be done instead of the
219  wavelet reconstruction (although if both are selected, the
220  reconstruction takes precendence). This functionality is switched on
221  and off by the flagSmooth parameter, and the width of the Hanning
222  kernel is governed by the hanningWidth parameter.
223
224* The smoothed array can also be written to a FITS file and read in at
225  the start in the same manner as the reconstructed array.
226
227* Several improvements have been made to the memory
228  management. Several memory leaks were fixed, and the memory usage of
229  Duchamp is considerably less, which will be a help for running it on
230  large cubes. The speed of some routines has also been improved, by
231  removing unnecessarily repetitive loops.
232
233* The sorting routines have been changed, and should now be slightly quicker
234  (and a bit more robust).
235
236* Enabled the scale bar (plotted on the 0th moment map in the spectral
237  output file) to be able to deal with much finer spatial scales (as
238  may be expected from VLBI data).
239
240* Other minor changes to code and presentation.
241
242
243Duchamp version 1.0.6 (2006/11/01)
244----------------------------------
245
246Some incremental improvements and changes to the code:
247
248* The statistics used for the detection are now calculated once for
249  the entire cube, rather than being calculated separately for each
250  channel map and spectrum. This results in a uniform threshold value
251  across the entire cube. The way the statistics calculations are
252  implemented in the code was changed, using a new statistics class.
253
254* This means we can report a peak signal-to-noise value for each
255  detection. This is given in the text-based output, as well as in the
256  summary information above the spectral output for each source.
257
258* The user can now elect not to have the moment map displayed in a
259  PGPlot window, through the use of the new flagXOutput
260  parameter. This should help in cases of running Duchamp on a dumb
261  terminal (with no X-display capabilities), or as part of a batch
262  script where the continual popping-up of the PGPlot window might
263  become annoying.
264
265* There are different Flags reported for the case of an object lying on
266  the spatial edge and spectral edge of the cube (E and S respectively).
267
268* A few minor bug fixes:
269  - When providing a subsection, any axes with the range given by *
270    had the pixel values offset incorrectly. This has been fixed.
271  - Negative searches now correctly invert the reconstructed array
272    when it is read in from a file.
273
274* Other minor changes to the code, to improve memory handling and
275  remove redundant arrays and variables.
276
277
278Duchamp version 1.0.5 (2006/09/06)
279----------------------------------
280
281Since version 1.0, there have been a range of mostly minor
282changes. These are generally bug-fixes, thanks to feedback from a
283number of users, as well as a few extra features.
284
285Here is a summary of the changes since version 1.0:
286
287USER INTERFACE:
288
289* The user is now able to enter the value of flag parameters in the
290  parameter file as strings, as well as integers (so one can enter
291  true or 1 to give the same result).
292
293GRAPHICAL OUTPUT:
294
295* Added a new function that draws the edge of the blank region on the
296  maps and image cutouts. There is a new flag parameter --
297  drawBlankEdges -- that controls the use of this function (the
298  default is true).
299  Also, the edge of the field is plotted on the image cutouts as a
300  yellow line. This distinguishes it from the purple blank pixel
301  dividing line.
302
303* The size of the tick mark in the image cutout (indicating the
304  spatial scale of the image) is now adaptable, so that it shows the
305  scale that best fits the image (ranging from 1 arcsec to 15
306  degrees). (This is a change from the previous standard length of 15
307  arcmin.)
308
309* The zoomed spectrum had its flux scale determined by all points in
310  the zoom box,including those flagged by the Milky Way (MW)
311  range. This has been fixed so that any MW channels will not affect
312  the flux scaling, potentially improving the appearance of objects
313  detected close in velocity to strong MW emission or absorption.
314
315* Improved Karma Annotation file output, so that files without good
316  WCS are dealt with appropriately.
317
318TEXT-BASED OUTPUT:
319
320* The position resolution in the IAU-format names has been increased,
321  so that distinct objects close to one another are more readily
322  distinguished.  Overlapping sources at different velocities may
323  still have the same name, but this is a more general problem.
324
325* The presentation of the results in tabular format has been improved,
326  so that the precision of faint sources is sufficient to show their
327  flux, for instance, is not 0. This also applies to the information
328  presented above the spectral plots.
329
330* Improved error and warning reporting, so that the formatting and
331  presentation of information is clearer.
332
333FITS I/O RELATED:
334
335* The previous version was did not deal well with 4 (or greater)
336  dimensions in the FITS file -- the memory allocation was badly done,
337  and the axes needed to be in a particular order. This has been
338  fixed, so that the FITS I/O routines can now handle any sized FITS
339  file, with axes in any order (as long as there are two spatial and one
340  spectral axes).
341
342* When the FITS file does not have a rest frequency defined, there is
343  no way to transform the frequency axis into velocity. In this case,
344  the spectral axis is left as frequency, and put into units of MHz.
345
346* If the beam size is not indicated by the FITS header (through the
347  BMAJ and BMIN keywords), the user can manually specify the size
348  through the parameter file (using parameter beamSize).
349
350* The FITS I/O routines make use of the command fits_file_exists. This
351  was introduced into the CFITSIO package from version 2.5, so Duchamp
352  will only work with this version or higher. Version 3+ is preferred.
353
354OTHER BUG-FIXING:
355
356* Several bugs related to the blank-pixels were dealt with.
357  The correct values were not propagating through correctly, meaning
358  that the default values were being used. Also, there was the
359  potential for blank pixels to be detected when the FDR method was
360  used. Finally, the image cutout displays occasionally did not
361  obscure the blank pixels. All these problems should be fixed now.
362
363* The FDR setup routine was occasionally failing with a segmentation
364  fault, due to it accessing unallocated memory. This has been fixed.
365
366* Fixed bugs that affected the way 2D images (rather than 3D cubes)
367  were dealt with. The minChannels test failed when minChannels=0.
368
369* If there is no beam information in the FITS header, the user can now
370  enter a beam size as a parameter.
371
372* Other minor fixes to the code, to improve its structure and
373  robustness.
374
375
376Duchamp version 1.0 (2006/06/30)
377--------------------------------
378
379The first full release version.
380
381Several major changes compared to previous version:
382
383* Incorporated a FitsHeader class, to keep track of header information
384  (including WCS) from the FITS file. All units-related calculations
385  are done with this class, such as conversion to velocity, and
386  pixel-to-WCS conversion.  The main advantage of this is improved
387  speed of execution, more adaptable to different units, and improved
388  code (easier for me!).
389
390* Able to select the dimensionality of the reconstruction, rather than
391  just doing it in 3-D.
392
393* Robust text output, so that the columns are sized correctly given
394  the data being written, and the relevant units (derived from the
395  FITS header) are included in the output table.
396
397* Improved the way the reconstructed image is saved and read back in,
398  with a better naming scheme and a better set of new FITS header
399  keywords. The MW headers are now not written.
400
401Other, more minor changes include:
402
403* MW channels now not set to 0, but just ignored for searching
404  purposes (and for the scaling of the spectral output -- they are
405  plotted though and highlighted with a hashed box).
406
407* The scale bar in the moment map in the spectral output file has its
408  length indicated.
409
410* Improved VOTable output, with more information about the way Duchamp
411  was run.
412
413* Made sure all statistics calculations in the reconstruction are
414  based on robust (ie. median) methods.
415
416Also moved to an autoconf based configure/make compilation, for ease of use.
417
418
419Duchamp version 0.9.2 (2006/06/27)
420--------------------------------
421
422* Added the use of warning flags for detections: for either edge
423  location or negative enclosed flux.
424
425* A new command line option added so that the user can specify a FITS
426  file to be searched with the default parameters, rather than giving
427  a full parameter file.
428
429* The scale bar on the moment cutout now works in general case, using
430  an iterative process to get to the correct length.
431
432* RA axes are now done correctly on the full-scale maps.
433
434* Various coding fixes, improving the readability of the code,
435  particularly regarding the declaration of temporary variables.
436
437* Changed the way the time of execution is called : now using time.h
438  functions, rather than a system call.
439
440* Changed output in Detection/outputDetection.cc for the pixel
441  information of detected objects (the info printed above the spectral
442  plots) -- now print out number of voxels in object, and have
443  improved the formatting a little.
444
445* Improved the functionality of saving the FITS file containing the
446  reconstructed array. Added ability to save and read back in the MW
447  parameters when saving a reconstructed cube (if a reconstructed cube
448  has different MW range to that being considered, it would cause
449  problems). ReadRecon now just returns a FAILURE and will reconstruct
450  the cube anew.
451
452* Changed default value of flagGrowth to 0.
453
454
455
456Duchamp version 0.9 (2006/05/05)
457--------------------------------
458
459First public release version.
Note: See TracBrowser for help on using the repository browser.