source: trunk/CHANGES @ 638

Last change on this file since 638 was 616, checked in by MatthewWhiting, 15 years ago

Making the trunk version of CHANGES consistent with 1.1.8, with the addition of the note about the API changes.

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