source: trunk/CHANGES @ 362

Last change on this file since 362 was 362, checked in by MatthewWhiting, 17 years ago

Updated the CHANGES and README for inclusion with the beta version.
Also updated the version number to 1.1.2.

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