dopmap revision history Update 2.3.1 dd 22 January 2001 Fixed a bug in syncdop.pro and added a parameter `mem' to dopmap.pro: Contrary to what the documentation said, the parameter /size in syncdop did not give the correct estimate for the expected memory usage. Such a parameter is important if you reach the limits of your available memory (as can happen with high-resolution spectra). A new parameter has been added in dopmap.pro, which has the same function. To find out the expected memory usage, say IDL> dopmap,/mem All dopmap does then is print the expected memory needed in MB. If this is more than your system can handle, try reducing the resolution of the output map: IDL> dopmap,over=0.5,/mem for example, and adjust over until the memory requirements fit your system, and then run dopmap with this reduction: IDL> dopmap,over=xxx See also the added discussion in `memory requirements' in the new version of the documentation. Version 2.3 dd 29 September 2000 ----------- - Fixed a significant bug in lobe.f. The stream as plotted by stream.pro was incorrectly calculated. - Improvements in the documentation. - Bug in the overview postscript plotfile dopmap.ps corrected. With thanks to Guillaume Dubus for correcting the error in the stream paths. Thanks also to Ronald Mennickent for feedback. Update 2.2.1 dd 14 Jan 2000 Fixed bug in dop.f (input parameters pb0 and pb1 did not work as advertized). Version 2.2 dd 14 Dec 1999 ----------- - added parameters xra, yra to stream.pro. These allow modifying the velocity ranges to be plotted (useful if several plots have to be on the exact same scale) - added parameter ctab in stream.pro to specify a different color table Update 2.1.1 dd 3 Nov 1999 increased memory allocation a bit (was a bit too tight for some cases) Version 2.1, dd 4 May 1999 ----------- Changes w/r 2.0: Bug fixes, with thanks to Paul Groot and Gavin Ramsay. Version 2.0 dd 3 March 1999 ----------- Changes with respect to version 1: - The IDL routine dopmap.pro now adds a plot on screen showing the phase-averaged line profiles of input and reconstructed spectra. This is meant to help in adjusting the gamma-velocity and the absorption-fudge parameters `wid' and `af' in the parameter file dop.in. (see documentation) - The ps output of dopmap.pro now includes additional files with the input and reconstructed spectra separately (for more flexible importing into texts) The main change is that the program now allows for input data at an {\it arbitrary set of phase values}. In version 1, the Fortran program only worked with uniformly spaced phases between 0 and 1. The IDL routines (foldspec and dopin) provided this from unevenly spaced phases by a rebinning process. This rebinning is an appropriate procedure if the number of phase points is large (for example if several orbits are combined) but this does not seem to be the usual situation. Since the method used has no intrinsic requirements on the sampling in orbital phse, it is more logical to allow for arbitrarily sampled phases. The main consequence of this change is that the format of data-input and output files to the Fortran program have changed, since the new information about the sampling in phase has to be transferred. This has the following consequences. A. For those who only use the Fortran program: 1 THE FORTRAN PROGRAM IN THE NEW VERSION IS INCOMPATIBLE with the old data input ({\tt dopin}) files. The change to be made in {\tt dopin} is small, however. After the phase points a line has to be added with a single integer 1 or 0. If a 1 is given, the next lines must contain the width (in units of the orbital period) of each of the phase bins. If a 0 is given, a plausible guess is made for the width of the bins. The data are read as follows: open(4, file='dopin') read(4,*) (pha(i),i=1,nph) c next lines are new: read(4,*) iph if (iph.eq.1) then read(4,*) (dpha(i),i=1,nph) else do i=1,nph dpha(i)=1./nph enddo endif 2. THE DEFINITION OF THE PHASE BINS HAS BEEN CHANGED. Previously, the value of the phase pha(i) was the lower edge of the bin, now it is the MIDDLE. Thus, both the radial velocity and phase bins are now consistently CENTERED. 3. THE OUTPUT FILE dop.out HAS CHANGED. It now contains also the information on the widths of the phase bins; this is written as follows: open(3, file='dop.out') write(3,'(1p8e12.4)')(pha(i),i=1,nph) c next lines are new: write(3,*)iph if (iph.eq.1) write(3,'(1p8e12.4)')(dpha(i),i=1,nph) B Using the IDL routines. The routines foldspec, plfold, dopin, dopmap and reamap have changed. The consequence is that if you want to use the new version on old data, you have to repeat the whole sequence of calls to foldspec, dopin and dopmap. Since the format of {\tt dop.out} has also changed, old {\tt dop.out} files cannot be read by {\tt dopmap}. The new version now takes the phase values of the spectra and their widths (both in units of the orbital period) literally. The phases can be arbitrarily spaced, don't have to lie between 0 and 1, and the spectra can be in arbitrary order. However, it is probably a good idea to have phases not larger than 100 or so in absolute value, since cos and sines are taken of them and the machine accuracy is finite (i.e. don't use the absolute orbit counts from the ephemeris). Rebinning to an equidistant grid of phase points is now an OPTION in {\tt foldspec}. To get rebinned data as in the previous version, say foldspec,dir='your_spectra_directory',/rebin Note that the phases given in your input data are assumed to be CENTERED. Due to these changes, the IDL routines behave slightly differently. foldspec and dopin: if data are not rebinned, the plots produced by foldspec and plfold generally have a distorted phase axis: the spectra are just stacked above each other in order of their (reduced) phase (between 0 and 1). This is OK since the plots produced by these routines are mainly meant for visual inspection and check on the input data. The final output produced by dopmap has a clean phase axis. dopmap: The format of the doppler maps has not changed, but the representation of the input spectra and reconstructed spectra now reflects the nonuniform phases. By default, the input spectrum and reconstructed spectrum only shows information where input data exists. That means there will typically be many stripes due to data gaps. This is appropriate if the data are quite nonuniformly spaced, but a bit pedantic if the spacing is good. A new option `fill' in dopmap will produce smooth looking spectra by filling the gaps with the average of the two neighboring non-empty bins. This affects only the representation of these spectra on screen and ps-file, and has no effect on the doppler maps: dopmap,/fill (default is: fill=0).