source: tags/release-1.1.1/CHANGES @ 333

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

Minor updates to CHANGES.

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