Description

In Sherpa parlance, a ``dataspace'' is an N-dimensional grid defined by the independent variables of the dataset (i.e., x_i in the expression y = f(x_0, x_1,...,x_(N-1))). Simple examples include the CHANNELS array in PHA datasets and the pixel numbers along each axis of FITS images.

The get_photon_wave_axes() function retrieves the dataspace, or filtered data set axes of the appropriate data set (if no argument is given, the axes for data set 1 are retrieved). Regardless of the current Sherpa ANALYSIS setting, this function returns the dataspace in units of wavelength (A). However, the dataspace is also translated into ``photon space''. The get_wave_axes() function returns the dataspace in ``wavelength space''. In essence, ``photon space'' is what one would see if one could undo the redistribution of energies by the detector. (One can't really ``deconvolve'' the data in this manner with any confidence, but for the purposes of visualization only, the data from the appropriate RMF and ARF files are used to estimate what the data would look like after a ``deconvolution''.)

Thus, for example, if one is working with filtered PHA data in energy-space, what is returned are the low and high bin boundaries in A (quantities assigned, e.g., by the ENERG_LO and ENERG_HI columns of the ARF). But if one is working in energy-space or channel-space, the bin boundaries returned are still in A. These boundaries generally do not match the boundaries that would be returned by get_wave_[b]axes().

(The function get_photon_wave_baxes() acts as get_photon_wave_axes(), save that it retrieves the dataspace for the background associated with the appropriate data set.)

One may display photon-space model amplitudes et al. on the same grid output by get_photon_axes using the Sherpa plotting commands LPLOT SOURCE et al.