source: tags/release-1.0.6/CHANGES @ 813

Last change on this file since 813 was 195, checked in by Matthew Whiting, 18 years ago

Implemented a request (from ticket:1) for the ability to not display the pgplot
window showing the moment map. This is now switched on and off by the
flagXOutput parameter.
Updated code and documentation.

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