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