source: tags/release-1.1.1/CHANGES @ 334

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

Updated version of the configure and makefiles, along with better descriptions of how to install it.

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