source: trunk/CHANGES @ 295

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