source: trunk/CHANGES @ 328

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

Preparing for the new minor release 1.1.1

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