source: trunk/CHANGES @ 379

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

Info on the beam changes.

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