source: trunk/CHANGES @ 211

Last change on this file since 211 was 211, checked in by Matthew Whiting, 18 years ago
  • Updated CHANGES ready for new version.
  • Updated InputComplete? with new parameters.
  • Added new scale bar lengths and fixed bugs in drawScaleBar.
  • Tried to fix problem with setCubeStats -- seems to be taking longer than it should. See ticket:3
File size: 9.6 KB
Line 
1Duchamp version 1.0.7 (2006/11/22)
2----------------------------------
3
4One new feature, and some improvements and bug-fixes.
5
6* The user can now elect to Hanning-smooth the spectral direction of the cube
7  before the searching is done. This can be done instead of the wavelet
8  reconstruction (although if both are selected, the reconstruction takes
9  precendence). The width of the Hanning kernel is governed by the hanningWidth
10  parameter.
11
12* The smoothed array can also be written to a FITS file and read in at the
13  start in the same manner as the reconstructed array.
14
15* Several improvements have been made to the memory management. Several
16  memory leaks were fixed, and the memory usage of Duchamp is considerably
17  less, which will be a help for running it on large cubes. The speed of
18  some routines has also been improved, by removing unnecessarily repetitive
19  loops.
20
21* Enabled the scale bar (plotted on the 0th moment map in the spectral output
22  file) to be able to deal with much finer spatial scales (as may be expected
23  from VLBI data).
24
25* Other minor changes.
26
27
28Duchamp version 1.0.6 (2006/11/01)
29----------------------------------
30
31Some incremental improvements and changes to the code:
32
33* The statistics used for the detection are now calculated once for
34  the entire cube, rather than being calculated separately for each
35  channel map and spectrum. This results in a uniform threshold value
36  across the entire cube. The way the statistics calculations are
37  implemented in the code was changed, using a new statistics class.
38
39* This means we can report a peak signal-to-noise value for each
40  detection. This is given in the text-based output, as well as in the
41  summary information above the spectral output for each source.
42
43* The user can now elect not to have the moment map displayed in a
44  PGPlot window, through the use of the new flagXOutput
45  parameter. This should help in cases of running Duchamp on a dumb
46  terminal (with no X-display capabilities), or as part of a batch
47  script where the continual popping-up of the PGPlot window might
48  become annoying.
49
50* There a different Flags reported for the case of an object lying on
51  the spatial edge and spectral edge of the cube (E and S respectively).
52
53* A few minor bug fixes:
54  - When providing a subsection, any axes with the range given by *
55    had the pixel values offset incorrectly. This has been fixed.
56  - Negative searches now correctly invert the reconstructed array
57    when it is read in from a file.
58
59* Other minor changes to the code, to improve memory handling and
60  remove redundant arrays and variables.
61
62
63Duchamp version 1.0.5 (2006/09/06)
64----------------------------------
65
66Since version 1.0, there have been a range of mostly minor
67changes. These are generally bug-fixes, thanks to feedback from a
68number of users, as well as a few extra features.
69
70Here is a summary of the changes since version 1.0:
71
72USER INTERFACE:
73
74* The user is now able to enter the value of flag parameters in the
75  parameter file as strings, as well as integers (so one can enter
76  true or 1 to give the same result).
77
78GRAPHICAL OUTPUT:
79
80* Added a new function that draws the edge of the blank region on the
81  maps and image cutouts. There is a new flag parameter --
82  drawBlankEdges -- that controls the use of this function (the
83  default is true).
84  Also, the edge of the field is plotted on the image cutouts as a
85  yellow line. This distinguishes it from the purple blank pixel
86  dividing line.
87
88* The size of the tick mark in the image cutout (indicating the
89  spatial scale of the image) is now adaptable, so that it shows the
90  scale that best fits the image (ranging from 1 arcsec to 15
91  degrees). (This is a change from the previous standard length of 15
92  arcmin.)
93
94* The zoomed spectrum had its flux scale determined by all points in
95  the zoom box,including those flagged by the Milky Way (MW)
96  range. This has been fixed so that any MW channels will not affect
97  the flux scaling, potentially improving the appearance of objects
98  detected close in velocity to strong MW emission or absorption.
99
100* Improved Karma Annotation file output, so that files without good
101  WCS are dealt with appropriately.
102
103TEXT-BASED OUTPUT:
104
105* The position resolution in the IAU-format names has been increased,
106  so that distinct objects close to one another are more readily
107  distinguished.  Overlapping sources at different velocities may
108  still have the same name, but this is a more general problem.
109
110* The presentation of the results in tabular format has been improved,
111  so that the precision of faint sources is sufficient to show their
112  flux, for instance, is not 0. This also applies to the information
113  presented above the spectral plots.
114
115* Improved error and warning reporting, so that the formatting and
116  presentation of information is clearer.
117
118FITS I/O RELATED:
119
120* The previous version was did not deal well with 4 (or greater)
121  dimensions in the FITS file -- the memory allocation was badly done,
122  and the axes needed to be in a particular order. This has been
123  fixed, so that the FITS I/O routines can now handle any sized FITS
124  file, with axes in any order (as long as there are two spatial and one
125  spectral axes).
126
127* When the FITS file does not have a rest frequency defined, there is
128  no way to transform the frequency axis into velocity. In this case,
129  the spectral axis is left as frequency, and put into units of MHz.
130
131* If the beam size is not indicated by the FITS header (through the
132  BMAJ and BMIN keywords), the user can manually specify the size
133  through the parameter file (using parameter beamSize).
134
135* The FITS I/O routines make use of the command fits_file_exists. This
136  was introduced into the CFITSIO package from version 2.5, so Duchamp
137  will only work with this version or higher. Version 3+ is preferred.
138
139OTHER BUG-FIXING:
140
141* Several bugs related to the blank-pixels were dealt with.
142  The correct values were not propagating through correctly, meaning
143  that the default values were being used. Also, there was the
144  potential for blank pixels to be detected when the FDR method was
145  used. Finally, the image cutout displays occasionally did not
146  obscure the blank pixels. All these problems should be fixed now.
147
148* The FDR setup routine was occasionally failing with a segmentation
149  fault, due to it accessing unallocated memory. This has been fixed.
150
151* Fixed bugs that affected the way 2D images (rather than 3D cubes)
152  were dealt with. The minChannels test failed when minChannels=0.
153
154* If there is no beam information in the FITS header, the user can now
155  enter a beam size as a parameter.
156
157* Other minor fixes to the code, to improve its structure and
158  robustness.
159
160
161Duchamp version 1.0 (2006/06/30)
162--------------------------------
163
164The first full release version.
165
166Several major changes compared to previous version:
167
168* Incorporated a FitsHeader class, to keep track of header information
169  (including WCS) from the FITS file. All units-related calculations
170  are done with this class, such as conversion to velocity, and
171  pixel-to-WCS conversion.  The main advantage of this is improved
172  speed of execution, more adaptable to different units, and improved
173  code (easier for me!).
174
175* Able to select the dimensionality of the reconstruction, rather than
176  just doing it in 3-D.
177
178* Robust text output, so that the columns are sized correctly given
179  the data being written, and the relevant units (derived from the
180  FITS header) are included in the output table.
181
182* Improved the way the reconstructed image is saved and read back in,
183  with a better naming scheme and a better set of new FITS header
184  keywords. The MW headers are now not written.
185
186Other, more minor changes include:
187
188* MW channels now not set to 0, but just ignored for searching
189  purposes (and for the scaling of the spectral output -- they are
190  plotted though and highlighted with a hashed box).
191
192* The scale bar in the moment map in the spectral output file has its
193  length indicated.
194
195* Improved VOTable output, with more information about the way Duchamp
196  was run.
197
198* Made sure all statistics calculations in the reconstruction are
199  based on robust (ie. median) methods.
200
201Also moved to an autoconf based configure/make compilation, for ease of use.
202
203
204Duchamp version 0.9.2 (2006/06/27)
205--------------------------------
206
207* Added the use of warning flags for detections: for either edge
208  location or negative enclosed flux.
209
210* A new command line option added so that the user can specify a FITS
211  file to be searched with the default parameters, rather than giving
212  a full parameter file.
213
214* The scale bar on the moment cutout now works in general case, using
215  an iterative process to get to the correct length.
216
217* RA axes are now done correctly on the full-scale maps.
218
219* Various coding fixes, improving the readability of the code,
220  particularly regarding the declaration of temporary variables.
221
222* Changed the way the time of execution is called : now using time.h
223  functions, rather than a system call.
224
225* Changed output in Detection/outputDetection.cc for the pixel
226  information of detected objects (the info printed above the spectral
227  plots) -- now print out number of voxels in object, and have
228  improved the formatting a little.
229
230* Improved the functionality of saving the FITS file containing the
231  reconstructed array. Added ability to save and read back in the MW
232  parameters when saving a reconstructed cube (if a reconstructed cube
233  has different MW range to that being considered, it would cause
234  problems). ReadRecon now just returns a FAILURE and will reconstruct
235  the cube anew.
236
237* Changed default value of flagGrowth to 0.
238
239
240
241Duchamp version 0.9 (2006/05/05)
242--------------------------------
243
244First public release version.
Note: See TracBrowser for help on using the repository browser.