[482] | 1 | Duchamp version 1.1.6 (2008/09/08) |
---|
[480] | 2 | ---------------------------------- |
---|
| 3 | |
---|
| 4 | New features: |
---|
| 5 | |
---|
| 6 | * The velocity widths can now be quoted in two additional ways: the |
---|
| 7 | full width at 50% of the peak flux (ie. the FWHM) and the full width |
---|
| 8 | at 20% of the peak flux (w_50 and w_20 respectively). The w_50 |
---|
| 9 | parameter is now quoted in the results printed to the screen |
---|
| 10 | (instead of w_VEL), but all three are written to the results file. |
---|
| 11 | |
---|
| 12 | * The facility now exists to bypass the searching step and go straight |
---|
| 13 | to the output stage using a list of previously detected objects. The |
---|
| 14 | list is extracted from a previously-created log file. The user can |
---|
| 15 | change the way the spectra are plotted (e.g. choose to plot |
---|
| 16 | integrated rather than peak spectra), and select a subset of the |
---|
| 17 | detected objects to be printed to individual postscript files. Use |
---|
| 18 | the input parameter usePrevious (set to true) to use this facility, |
---|
| 19 | and provide a list of objects using the objectList parameter |
---|
| 20 | (eg. 1,2,4,7-10,15) |
---|
| 21 | |
---|
[482] | 22 | * A new parameter "growthThreshold" has been created, that goes with |
---|
| 23 | "threshold". If you manually specify a threshold, and you wish to |
---|
| 24 | grow detections, you need to manually specify a growthThreshold (in |
---|
| 25 | flux units). |
---|
| 26 | |
---|
[480] | 27 | Bug fixes: |
---|
| 28 | |
---|
[482] | 29 | * Cubes that do not have a spectral axis (such as Stokes cubes) were |
---|
| 30 | causing memory leaks and crashing, due to some assumptions of the |
---|
| 31 | existence of the spectral axis. These bugs have been fixed, so that |
---|
| 32 | Duchamp will run on such cubes, although the WCS transforms may not |
---|
| 33 | always work appropriately. Please let me know via bug reports of |
---|
| 34 | difficulties you encounter! |
---|
[480] | 35 | |
---|
[482] | 36 | * The growing function has had a few bugs fixed and is now more |
---|
| 37 | efficient. |
---|
| 38 | |
---|
| 39 | * The FDR method was previously overriding any manually-specified |
---|
| 40 | threshold. This has been fixed so that if the user specifies |
---|
| 41 | threshold=X, then the FDR method is not called. |
---|
| 42 | |
---|
| 43 | * Some undefined things were happening with textual output when no |
---|
| 44 | objects were detected. This has been fixed. |
---|
| 45 | |
---|
| 46 | * Memory leaks caused by FITS WCS irregularities have been fixed |
---|
| 47 | (specifically, if a FITS header had NAXIS=2 but more than two WCS |
---|
| 48 | axes were defined). |
---|
| 49 | |
---|
| 50 | |
---|
| 51 | |
---|
[438] | 52 | Duchamp version 1.1.5 (2008/03/20) |
---|
| 53 | ---------------------------------- |
---|
| 54 | |
---|
| 55 | Bug fixes: |
---|
| 56 | * A major bug was discovered in the calculation of integrated |
---|
| 57 | fluxes. The flux was incorrectly being weighted by the spatial size |
---|
| 58 | of the detection, resulting in a (often considerable) overestimation |
---|
[447] | 59 | of the integrated flux. This has been corrected. |
---|
[438] | 60 | |
---|
[447] | 61 | * The beam size calculation was also incorrect, being out by a factor |
---|
| 62 | of 1/ln(2). |
---|
[438] | 63 | |
---|
[447] | 64 | * The "make install" command previously failed to work properly if the |
---|
| 65 | library had not been created. This has been fixed so that the |
---|
| 66 | installation works even if there is no library file. |
---|
| 67 | |
---|
| 68 | New Features: |
---|
| 69 | * You can now provide a new flux unit string, so that the pixel fluxes |
---|
| 70 | will be converted to these new fluxes before any calculations are |
---|
| 71 | done. This is done with the newFluxUnits input parameter. The new |
---|
| 72 | units should be directly convertible from the old ones (given by the |
---|
| 73 | BUNIT header -- e.g. if BUNIT = Jy/beam, you can give newFluxUnits |
---|
| 74 | as mJy/beam, but not mJy). |
---|
| 75 | |
---|
| 76 | * You can now specify the precision used in the output files for flux, |
---|
| 77 | velocity and S/N ratio columns, via new input parameters precFlux, |
---|
| 78 | precVel and precSNR. These will apply to the VOTable output as well |
---|
| 79 | as the text table and information on the spectral plots. |
---|
| 80 | |
---|
| 81 | * The Karma annotation files previously provided just a circle at the |
---|
| 82 | spatial location of the detected object. You now have the option to |
---|
| 83 | draw a border around the detected pixels (in a similar manner to the |
---|
| 84 | PGPLOT moment maps). Karma does not do this perfectly, so the lines |
---|
| 85 | may not line up exactly with the pixel borders, so the option |
---|
| 86 | remains to keep using the circles. This is controlled by the |
---|
| 87 | parameter "annotationType", with possible options being "borders" |
---|
| 88 | (the default) or "circles". |
---|
| 89 | |
---|
| 90 | * There is a new function getMetadata() that loads the header and WCS |
---|
| 91 | data, but no pixel information. This is only of interest if you are |
---|
| 92 | doing code development with the Duchamp library -- it does not |
---|
| 93 | affect the running of Duchamp itself. |
---|
| 94 | |
---|
[425] | 95 | Duchamp version 1.1.4 (2008/02/15) |
---|
| 96 | ---------------------------------- |
---|
| 97 | |
---|
| 98 | Most of the changes incorporated in this update result from ASKAP code |
---|
| 99 | development (that makes use of some of the Duchamp functionality), |
---|
| 100 | but do not actually affect the way Duchamp runs (other than, in a |
---|
| 101 | couple of cases, making it a bit faster). Changes that are |
---|
| 102 | relevant for regular users of Duchamp are as follows: |
---|
| 103 | |
---|
| 104 | * A new option has been made available (thanks to Mary Putman et al |
---|
| 105 | for the suggestion!) to save the spectra of all detected objects in |
---|
| 106 | a text file. This has the form of one column for the spectral |
---|
| 107 | coordinates and one column of fluxes for each object. This is |
---|
| 108 | enabled by the input parameters flagTextSpectra and spectraTextFile. |
---|
| 109 | |
---|
| 110 | * Slight changes to the output include he formatting of the way the |
---|
| 111 | detected objects are written to the log file. This meant the |
---|
| 112 | verification files were also updated. Also the cube statistics are |
---|
| 113 | not printed to the results file if a user threshold is specified (as |
---|
| 114 | they are not calculated!). |
---|
| 115 | |
---|
| 116 | * The determination of beam size has been made more reliable, as has |
---|
| 117 | the BUNIT determination. |
---|
| 118 | |
---|
| 119 | * Fixed a bug that meant source merging was not done for 2D images |
---|
| 120 | (not usually a problem, as the source-finding takes care of this, |
---|
| 121 | but came up in parallelisation development). |
---|
| 122 | |
---|
[406] | 123 | Duchamp version 1.1.3 (2008/01/08) |
---|
| 124 | ---------------------------------- |
---|
[404] | 125 | |
---|
| 126 | A minor update that just improves the build process. The location of |
---|
| 127 | the wcslib include files was not specified correctly, so that some |
---|
| 128 | machines were unable to find them. The configure script has been fixed |
---|
| 129 | so that the compilation should work in all cases. |
---|
| 130 | |
---|
[405] | 131 | Some minor changes have also been made to the code in the PixelMap |
---|
[412] | 132 | directory, and to param.cc, to fix warnings or errors that may appear |
---|
| 133 | in compilation. |
---|
[404] | 134 | |
---|
[405] | 135 | However, there are no changes to the actual workings of the code in |
---|
| 136 | this minor version, so if you have a working version of Duchamp 1.1.2 |
---|
| 137 | there is probably no reason to update. |
---|
| 138 | |
---|
[389] | 139 | Duchamp version 1.1.2 (2007/12/07) |
---|
| 140 | ---------------------------------- |
---|
[349] | 141 | |
---|
[363] | 142 | Compilation: |
---|
| 143 | |
---|
[349] | 144 | * The compilation had problems working correctly when the cfitsio and |
---|
[373] | 145 | wcs libraries were not in standard locations. The configure script |
---|
[349] | 146 | has been tweaked to make sure the libraries are found. |
---|
| 147 | |
---|
| 148 | * Problems with compiling in the absence of pgplot have been fixed, |
---|
| 149 | and it should now compile fine. |
---|
| 150 | |
---|
[362] | 151 | * Improved the configure script for use with Mac OS X and gfortran. |
---|
[349] | 152 | |
---|
[363] | 153 | |
---|
| 154 | Bugfixing: |
---|
| 155 | |
---|
[362] | 156 | * A major problem with the text-based output was fixed. The widths of |
---|
| 157 | the columns were not being calculated correctly, and were running |
---|
[373] | 158 | together. This should no longer be the case. |
---|
[349] | 159 | |
---|
[374] | 160 | * There was a bug in the way Duchamp interpreted spectral axes, |
---|
| 161 | particularly AIPS types such as FELO-HEL, leading to incorrect |
---|
| 162 | scaling of the velocity axis. This has been fixed, so that |
---|
| 163 | non-standard types are now dealt with appropriately and the velocity |
---|
| 164 | scaling should be accurate. |
---|
[362] | 165 | |
---|
[376] | 166 | * Another bug meant the beam correction was always applied to the |
---|
| 167 | integrated spectra, regardless of whether the flux units involved |
---|
| 168 | the beam (e.g. Jy/beam). This has been fixed. Note that the values |
---|
| 169 | of the integrated flux presented in the results table were always |
---|
| 170 | calculated correctly. |
---|
| 171 | |
---|
[389] | 172 | * Other minor changes to improve the speed and efficiency, especially |
---|
| 173 | of the merging code. |
---|
| 174 | |
---|
[363] | 175 | New user parameters: |
---|
| 176 | |
---|
[381] | 177 | * There is now the possibility to save a FITS file that contains a |
---|
| 178 | mask array, indicating where the detected objects are. This is |
---|
| 179 | governed by the flagOutputMask parameter. |
---|
| 180 | |
---|
[363] | 181 | * The header information that is printed at the start of the results |
---|
| 182 | file -- that is, the list of parameters, the statistics of the cube, |
---|
| 183 | and the number of detections -- can now be written to a separate |
---|
| 184 | file. Set the flagSeparateHeader parameter to true or 1 and it will |
---|
| 185 | go to the file indicated by the headerFile parameter (the default is |
---|
| 186 | duchamp-Results.hdr). |
---|
| 187 | |
---|
[362] | 188 | * A "scaleMax" parameter has been added, so that the wavelet |
---|
| 189 | reconstruction can include only a specified range of scales (for |
---|
[373] | 190 | instance, if one wants to search just for narrow features such as |
---|
[362] | 191 | absorption lines). |
---|
| 192 | |
---|
[389] | 193 | * A "flagRobustStats" parameter has been added. This allows the user |
---|
| 194 | to elect to use robust statistics (median and median absolute |
---|
| 195 | deviation from the median) to estimate the noise parameters. If set |
---|
| 196 | to false, the mean and standard deviation will be used. The default |
---|
| 197 | value is true. |
---|
[362] | 198 | |
---|
[369] | 199 | New Feature: |
---|
[362] | 200 | |
---|
[369] | 201 | * When Duchamp is run on a 2D image (i.e. with no spectral output), it |
---|
| 202 | now produces a postscript file that shows information each |
---|
| 203 | individual source plus the image cutout of the source. This is |
---|
| 204 | similar to the spectral output file, but without the spectra. The |
---|
| 205 | filename is given by the spectraFile parameter. |
---|
| 206 | |
---|
[381] | 207 | * Ability to save a FITS file containing a mask array, with pixel |
---|
| 208 | values of 1 for pixels in a detected object, and 0 elsewhere. |
---|
[369] | 209 | |
---|
[381] | 210 | |
---|
[328] | 211 | Duchamp version 1.1.1 (2007/07/20) |
---|
| 212 | ------------------------------------ |
---|
| 213 | |
---|
[329] | 214 | Minor update to the release, with just a few changes: |
---|
[328] | 215 | |
---|
| 216 | * The verification script was generating diffs due to differences in |
---|
| 217 | the precision of some calculations when done on different machines. |
---|
| 218 | One of these was the integrated flux, and this has been corrected so |
---|
| 219 | that the same value should appear on all machines. |
---|
| 220 | The verification script has also changed so that just the number of |
---|
| 221 | sources and their positions are tested, as well as the |
---|
| 222 | logfiles. This should avoid the reporting of spurious differences. |
---|
| 223 | |
---|
| 224 | * The grey-scale used in the image cutouts (in the spectral plots) has |
---|
| 225 | been inverted. This makes it consistent with the scale used in the |
---|
| 226 | maps, and hopefully easier to see when printing. |
---|
| 227 | |
---|
[338] | 228 | * The configure/make system has been altered to make it easier to |
---|
| 229 | install, and to specify different external libraries. In particular, |
---|
| 230 | it is now not necessary to have PGPLOT installed on your system to |
---|
| 231 | run Duchamp. In the absence of PGPLOT, Duchamp will run as normal, |
---|
| 232 | just without any graphical output. Some source code needed to be |
---|
[344] | 233 | restructured to make this work. Please read the README file, or the |
---|
| 234 | Installation appendix in the User's Guide, for complete details. |
---|
[328] | 235 | |
---|
[329] | 236 | * The time of completion is now written to the log file, so that the |
---|
| 237 | user can have some idea of how long the program took. |
---|
[328] | 238 | |
---|
| 239 | |
---|
[310] | 240 | Duchamp version 1.1 (2007/05/17) |
---|
[259] | 241 | ------------------------------------ |
---|
| 242 | |
---|
| 243 | Changes made since the last numbered release: |
---|
| 244 | |
---|
[295] | 245 | EFFICIENCY OF EXECUTION: |
---|
| 246 | |
---|
[259] | 247 | * Major change to the way detections are stored. They are now recorded |
---|
| 248 | via run-length encoding in the x-y plane, and stored as collections |
---|
| 249 | of channel-maps. This improves the memory usage and the speed of |
---|
[298] | 250 | execution (particularly for routines such as the merging |
---|
| 251 | routines). The memory usage has also been improved by changing the |
---|
| 252 | way the list of detected objects is stored. |
---|
[259] | 253 | |
---|
[295] | 254 | SMOOTHING: |
---|
| 255 | |
---|
[279] | 256 | * Addition of ability to spatially smooth the cube before |
---|
| 257 | searching. This is done with a Gaussian kernel, the size and shape |
---|
[287] | 258 | of which can be specified by the user, using the parameters kernMaj |
---|
| 259 | & kernMin (which are the FWHM for the major & minor axes -- if |
---|
| 260 | kernMin is not given it is assumed to match kernMaj) and kernPA (the |
---|
| 261 | position angle of the major axis). There is a new parameter |
---|
[279] | 262 | smoothType that distinguishes this method from the spectral (Hanning) |
---|
| 263 | smoothing already in use. |
---|
| 264 | |
---|
[295] | 265 | DETECTIONS: |
---|
| 266 | |
---|
[264] | 267 | * Changed the way detection is done -- now only search in 2D images, |
---|
| 268 | keeping all detections (ie. no minimum-pixel requirement). This |
---|
| 269 | should be the same as doing both the 1D and 2D searches with the |
---|
| 270 | minimum pixel requirement in, but simpler. The rejection is done at |
---|
[295] | 271 | the end after all the merging and growing has been done. This leads |
---|
| 272 | to a larger number of intermediate detections (ie. the number |
---|
| 273 | before merging), which may increase the run-time slightly, although |
---|
| 274 | this is offset by the changes to the efficiency (see above). |
---|
[264] | 275 | |
---|
| 276 | * Increased the range over which objects can be grown to match the |
---|
| 277 | threshSpatial & threshVelocity parameters, as well as rejecting new |
---|
| 278 | pixels based on the BLANK and MW tests. |
---|
| 279 | |
---|
[295] | 280 | INPUTS: |
---|
[259] | 281 | |
---|
[287] | 282 | * There has been a subtle change in the way BLANK pixels are dealt |
---|
| 283 | with. To enable trimming of BLANK pixels, users should use the new |
---|
| 284 | parameter flagTrim. The parameters flagBlankPix and blankPixVal are |
---|
[295] | 285 | no longer accessible via the parameter file -- warning messages are |
---|
| 286 | given if they are provided in the parameter file. |
---|
[287] | 287 | |
---|
[295] | 288 | * Added ability to specify a statsec, so that the statistics are only |
---|
| 289 | calculated from a given subsection of the cube, rather than the full |
---|
| 290 | cube. |
---|
| 291 | |
---|
| 292 | * The subsections can also specify the ability to remove a border of n |
---|
| 293 | pixels from the edges of an axis (ie. n from the start and from the |
---|
| 294 | end) -- as requested in Trac ticket #5. |
---|
| 295 | |
---|
| 296 | * Changed the default value of the reconDim parameter from 3 to 1, and |
---|
| 297 | the default value of the flagATrous parameter to false. |
---|
| 298 | |
---|
| 299 | OUTPUTS: |
---|
| 300 | |
---|
[279] | 301 | * The output now includes three different estimates of the "centre" of |
---|
| 302 | the detection: peak location, centroid (flux-weighted), or average. |
---|
| 303 | |
---|
[295] | 304 | * Some slight improvements to the user feedback during execution. |
---|
| 305 | |
---|
[282] | 306 | * Spectral output now includes the baseline, if one was fitted. The |
---|
| 307 | format of the plot headers is slightly changed, to stop information |
---|
| 308 | falling off the edge of the page. |
---|
[279] | 309 | |
---|
[295] | 310 | * Added command-line option -x to directly disable the PGPLOT X-window |
---|
| 311 | map plotting. This overrides the setting of flagXOutput in the |
---|
| 312 | parameter file. |
---|
[259] | 313 | |
---|
[295] | 314 | * Fallback spectral units (in case the FITS header fails to record |
---|
| 315 | them) changed to SPC, but code has been fixed so that any problem |
---|
| 316 | should be caught before this becomes an issue. |
---|
| 317 | |
---|
| 318 | BUGFIXES: |
---|
| 319 | |
---|
[259] | 320 | * Fixed bug (Trac ticket #4) that meant the velocity units were not |
---|
| 321 | correctly dealt with. Duchamp should be more robust for different |
---|
| 322 | velocity axis setups now. |
---|
| 323 | |
---|
| 324 | * Fixed bug (ticket #9) with the VOTable output, where the tags were |
---|
| 325 | not closing. |
---|
| 326 | |
---|
[305] | 327 | * Fixed a bug that meant the integrated fluxes were not calculated |
---|
| 328 | properly -- no allowance was made for the number of spatial |
---|
| 329 | pixels. This should also work properly for 2D images now as well. |
---|
| 330 | |
---|
[264] | 331 | * Fixed minor bug in calculating the flux threshold from the p-value |
---|
| 332 | threshold when the FDR method is used. This did not affect the |
---|
| 333 | actual thresholding, merely the quoted flux threshold in the results |
---|
| 334 | file. Also, the MW channels are kept out of the p-value threshold |
---|
| 335 | determination if they are being flagged. |
---|
| 336 | |
---|
[259] | 337 | |
---|
| 338 | |
---|
[211] | 339 | Duchamp version 1.0.7 (2006/11/22) |
---|
| 340 | ---------------------------------- |
---|
| 341 | |
---|
| 342 | One new feature, and some improvements and bug-fixes. |
---|
| 343 | |
---|
[264] | 344 | * The user can now elect to Hanning-smooth the spectral direction of |
---|
| 345 | the cube before the searching is done. This can be done instead of the |
---|
| 346 | wavelet reconstruction (although if both are selected, the |
---|
| 347 | reconstruction takes precendence). This functionality is switched on |
---|
| 348 | and off by the flagSmooth parameter, and the width of the Hanning |
---|
| 349 | kernel is governed by the hanningWidth parameter. |
---|
[211] | 350 | |
---|
[264] | 351 | * The smoothed array can also be written to a FITS file and read in at |
---|
| 352 | the start in the same manner as the reconstructed array. |
---|
[211] | 353 | |
---|
[264] | 354 | * Several improvements have been made to the memory |
---|
| 355 | management. Several memory leaks were fixed, and the memory usage of |
---|
| 356 | Duchamp is considerably less, which will be a help for running it on |
---|
| 357 | large cubes. The speed of some routines has also been improved, by |
---|
| 358 | removing unnecessarily repetitive loops. |
---|
[211] | 359 | |
---|
[287] | 360 | * The sorting routines have been changed, and should now be slightly quicker |
---|
[215] | 361 | (and a bit more robust). |
---|
| 362 | |
---|
[287] | 363 | * Enabled the scale bar (plotted on the 0th moment map in the spectral |
---|
| 364 | output file) to be able to deal with much finer spatial scales (as |
---|
| 365 | may be expected from VLBI data). |
---|
[211] | 366 | |
---|
[215] | 367 | * Other minor changes to code and presentation. |
---|
[211] | 368 | |
---|
| 369 | |
---|
[194] | 370 | Duchamp version 1.0.6 (2006/11/01) |
---|
| 371 | ---------------------------------- |
---|
| 372 | |
---|
| 373 | Some incremental improvements and changes to the code: |
---|
| 374 | |
---|
| 375 | * The statistics used for the detection are now calculated once for |
---|
| 376 | the entire cube, rather than being calculated separately for each |
---|
| 377 | channel map and spectrum. This results in a uniform threshold value |
---|
| 378 | across the entire cube. The way the statistics calculations are |
---|
| 379 | implemented in the code was changed, using a new statistics class. |
---|
| 380 | |
---|
| 381 | * This means we can report a peak signal-to-noise value for each |
---|
| 382 | detection. This is given in the text-based output, as well as in the |
---|
| 383 | summary information above the spectral output for each source. |
---|
| 384 | |
---|
[195] | 385 | * The user can now elect not to have the moment map displayed in a |
---|
| 386 | PGPlot window, through the use of the new flagXOutput |
---|
| 387 | parameter. This should help in cases of running Duchamp on a dumb |
---|
| 388 | terminal (with no X-display capabilities), or as part of a batch |
---|
| 389 | script where the continual popping-up of the PGPlot window might |
---|
| 390 | become annoying. |
---|
| 391 | |
---|
[265] | 392 | * There are different Flags reported for the case of an object lying on |
---|
[194] | 393 | the spatial edge and spectral edge of the cube (E and S respectively). |
---|
| 394 | |
---|
| 395 | * A few minor bug fixes: |
---|
| 396 | - When providing a subsection, any axes with the range given by * |
---|
| 397 | had the pixel values offset incorrectly. This has been fixed. |
---|
| 398 | - Negative searches now correctly invert the reconstructed array |
---|
| 399 | when it is read in from a file. |
---|
| 400 | |
---|
| 401 | * Other minor changes to the code, to improve memory handling and |
---|
| 402 | remove redundant arrays and variables. |
---|
| 403 | |
---|
| 404 | |
---|
[146] | 405 | Duchamp version 1.0.5 (2006/09/06) |
---|
[142] | 406 | ---------------------------------- |
---|
| 407 | |
---|
[146] | 408 | Since version 1.0, there have been a range of mostly minor |
---|
| 409 | changes. These are generally bug-fixes, thanks to feedback from a |
---|
[157] | 410 | number of users, as well as a few extra features. |
---|
[146] | 411 | |
---|
[157] | 412 | Here is a summary of the changes since version 1.0: |
---|
[142] | 413 | |
---|
[157] | 414 | USER INTERFACE: |
---|
[146] | 415 | |
---|
[142] | 416 | * The user is now able to enter the value of flag parameters in the |
---|
| 417 | parameter file as strings, as well as integers (so one can enter |
---|
| 418 | true or 1 to give the same result). |
---|
| 419 | |
---|
[157] | 420 | GRAPHICAL OUTPUT: |
---|
| 421 | |
---|
[142] | 422 | * Added a new function that draws the edge of the blank region on the |
---|
[146] | 423 | maps and image cutouts. There is a new flag parameter -- |
---|
| 424 | drawBlankEdges -- that controls the use of this function (the |
---|
| 425 | default is true). |
---|
| 426 | Also, the edge of the field is plotted on the image cutouts as a |
---|
| 427 | yellow line. This distinguishes it from the purple blank pixel |
---|
| 428 | dividing line. |
---|
[142] | 429 | |
---|
[146] | 430 | * The size of the tick mark in the image cutout (indicating the |
---|
| 431 | spatial scale of the image) is now adaptable, so that it shows the |
---|
| 432 | scale that best fits the image (ranging from 1 arcsec to 15 |
---|
| 433 | degrees). (This is a change from the previous standard length of 15 |
---|
| 434 | arcmin.) |
---|
[142] | 435 | |
---|
[113] | 436 | * The zoomed spectrum had its flux scale determined by all points in |
---|
[146] | 437 | the zoom box,including those flagged by the Milky Way (MW) |
---|
| 438 | range. This has been fixed so that any MW channels will not affect |
---|
| 439 | the flux scaling, potentially improving the appearance of objects |
---|
| 440 | detected close in velocity to strong MW emission or absorption. |
---|
[112] | 441 | |
---|
[157] | 442 | * Improved Karma Annotation file output, so that files without good |
---|
| 443 | WCS are dealt with appropriately. |
---|
| 444 | |
---|
| 445 | TEXT-BASED OUTPUT: |
---|
| 446 | |
---|
[113] | 447 | * The position resolution in the IAU-format names has been increased, |
---|
| 448 | so that distinct objects close to one another are more readily |
---|
| 449 | distinguished. Overlapping sources at different velocities may |
---|
| 450 | still have the same name, but this is a more general problem. |
---|
[112] | 451 | |
---|
[146] | 452 | * The presentation of the results in tabular format has been improved, |
---|
| 453 | so that the precision of faint sources is sufficient to show their |
---|
| 454 | flux, for instance, is not 0. This also applies to the information |
---|
| 455 | presented above the spectral plots. |
---|
[112] | 456 | |
---|
[146] | 457 | * Improved error and warning reporting, so that the formatting and |
---|
| 458 | presentation of information is clearer. |
---|
| 459 | |
---|
[157] | 460 | FITS I/O RELATED: |
---|
| 461 | |
---|
[172] | 462 | * The previous version was did not deal well with 4 (or greater) |
---|
| 463 | dimensions in the FITS file -- the memory allocation was badly done, |
---|
| 464 | and the axes needed to be in a particular order. This has been |
---|
| 465 | fixed, so that the FITS I/O routines can now handle any sized FITS |
---|
| 466 | file, with axes in any order (as long as there are two spatial and one |
---|
| 467 | spectral axes). |
---|
[157] | 468 | |
---|
| 469 | * When the FITS file does not have a rest frequency defined, there is |
---|
| 470 | no way to transform the frequency axis into velocity. In this case, |
---|
| 471 | the spectral axis is left as frequency, and put into units of MHz. |
---|
| 472 | |
---|
[172] | 473 | * If the beam size is not indicated by the FITS header (through the |
---|
| 474 | BMAJ and BMIN keywords), the user can manually specify the size |
---|
| 475 | through the parameter file (using parameter beamSize). |
---|
| 476 | |
---|
| 477 | * The FITS I/O routines make use of the command fits_file_exists. This |
---|
| 478 | was introduced into the CFITSIO package from version 2.5, so Duchamp |
---|
| 479 | will only work with this version or higher. Version 3+ is preferred. |
---|
| 480 | |
---|
[157] | 481 | OTHER BUG-FIXING: |
---|
| 482 | |
---|
| 483 | * Several bugs related to the blank-pixels were dealt with. |
---|
| 484 | The correct values were not propagating through correctly, meaning |
---|
| 485 | that the default values were being used. Also, there was the |
---|
| 486 | potential for blank pixels to be detected when the FDR method was |
---|
| 487 | used. Finally, the image cutout displays occasionally did not |
---|
| 488 | obscure the blank pixels. All these problems should be fixed now. |
---|
| 489 | |
---|
| 490 | * The FDR setup routine was occasionally failing with a segmentation |
---|
| 491 | fault, due to it accessing unallocated memory. This has been fixed. |
---|
| 492 | |
---|
| 493 | * Fixed bugs that affected the way 2D images (rather than 3D cubes) |
---|
| 494 | were dealt with. The minChannels test failed when minChannels=0. |
---|
| 495 | |
---|
[165] | 496 | * If there is no beam information in the FITS header, the user can now |
---|
| 497 | enter a beam size as a parameter. |
---|
| 498 | |
---|
[146] | 499 | * Other minor fixes to the code, to improve its structure and |
---|
| 500 | robustness. |
---|
| 501 | |
---|
| 502 | |
---|
[112] | 503 | Duchamp version 1.0 (2006/06/30) |
---|
| 504 | -------------------------------- |
---|
| 505 | |
---|
[113] | 506 | The first full release version. |
---|
| 507 | |
---|
| 508 | Several major changes compared to previous version: |
---|
| 509 | |
---|
| 510 | * Incorporated a FitsHeader class, to keep track of header information |
---|
| 511 | (including WCS) from the FITS file. All units-related calculations |
---|
| 512 | are done with this class, such as conversion to velocity, and |
---|
| 513 | pixel-to-WCS conversion. The main advantage of this is improved |
---|
| 514 | speed of execution, more adaptable to different units, and improved |
---|
| 515 | code (easier for me!). |
---|
| 516 | |
---|
| 517 | * Able to select the dimensionality of the reconstruction, rather than |
---|
| 518 | just doing it in 3-D. |
---|
| 519 | |
---|
| 520 | * Robust text output, so that the columns are sized correctly given |
---|
| 521 | the data being written, and the relevant units (derived from the |
---|
| 522 | FITS header) are included in the output table. |
---|
| 523 | |
---|
| 524 | * Improved the way the reconstructed image is saved and read back in, |
---|
| 525 | with a better naming scheme and a better set of new FITS header |
---|
| 526 | keywords. The MW headers are now not written. |
---|
| 527 | |
---|
| 528 | Other, more minor changes include: |
---|
| 529 | |
---|
| 530 | * MW channels now not set to 0, but just ignored for searching |
---|
| 531 | purposes (and for the scaling of the spectral output -- they are |
---|
| 532 | plotted though and highlighted with a hashed box). |
---|
| 533 | |
---|
| 534 | * The scale bar in the moment map in the spectral output file has its |
---|
| 535 | length indicated. |
---|
| 536 | |
---|
| 537 | * Improved VOTable output, with more information about the way Duchamp |
---|
| 538 | was run. |
---|
| 539 | |
---|
| 540 | * Made sure all statistics calculations in the reconstruction are |
---|
| 541 | based on robust (ie. median) methods. |
---|
| 542 | |
---|
| 543 | Also moved to an autoconf based configure/make compilation, for ease of use. |
---|
| 544 | |
---|
| 545 | |
---|
| 546 | Duchamp version 0.9.2 (2006/06/27) |
---|
| 547 | -------------------------------- |
---|
| 548 | |
---|
| 549 | * Added the use of warning flags for detections: for either edge |
---|
| 550 | location or negative enclosed flux. |
---|
| 551 | |
---|
| 552 | * A new command line option added so that the user can specify a FITS |
---|
| 553 | file to be searched with the default parameters, rather than giving |
---|
| 554 | a full parameter file. |
---|
| 555 | |
---|
| 556 | * The scale bar on the moment cutout now works in general case, using |
---|
| 557 | an iterative process to get to the correct length. |
---|
| 558 | |
---|
| 559 | * RA axes are now done correctly on the full-scale maps. |
---|
| 560 | |
---|
| 561 | * Various coding fixes, improving the readability of the code, |
---|
| 562 | particularly regarding the declaration of temporary variables. |
---|
| 563 | |
---|
| 564 | * Changed the way the time of execution is called : now using time.h |
---|
| 565 | functions, rather than a system call. |
---|
| 566 | |
---|
| 567 | * Changed output in Detection/outputDetection.cc for the pixel |
---|
| 568 | information of detected objects (the info printed above the spectral |
---|
| 569 | plots) -- now print out number of voxels in object, and have |
---|
| 570 | improved the formatting a little. |
---|
| 571 | |
---|
| 572 | * Improved the functionality of saving the FITS file containing the |
---|
| 573 | reconstructed array. Added ability to save and read back in the MW |
---|
| 574 | parameters when saving a reconstructed cube (if a reconstructed cube |
---|
| 575 | has different MW range to that being considered, it would cause |
---|
| 576 | problems). ReadRecon now just returns a FAILURE and will reconstruct |
---|
| 577 | the cube anew. |
---|
| 578 | |
---|
| 579 | * Changed default value of flagGrowth to 0. |
---|
| 580 | |
---|
| 581 | |
---|
| 582 | |
---|
| 583 | Duchamp version 0.9 (2006/05/05) |
---|
| 584 | -------------------------------- |
---|
| 585 | |
---|
| 586 | First public release version. |
---|