12.5.0i The energies extend option does not work properly for the case of a data group containing multiple responses whose energy bins differ. Our thanks to Joel Frioriksson for pointing this out. Report added on Dec 15, 2008.

Monday, December 15, 2008

At the request of Andrea Prestwich at the CUC I've added the pile-up model to WebSpec. In the simple interface there is a check box to added it while in the advanced interface the user is expected to select pileup as the option for the first model component.

One tweak could be to set the default pile-up parameters appropriately for each instrument.

Friday, December 12, 2008

The recent cfitsio version region filtering fails when the first region is an exclude. This was an error I introduced when extending to multiple components as allowed in the FITS REGION extension. The fix should be available next week. Meanwhile a work-around is to include an initial region covering the entire field.

Update 12/15/08: There is also a memory-handling error in the code which reads a FITS REGION. This bug is only triggered if the extension contains a large number (>100) of exclude regions.

Dave Henley reported problems with the new extractor when using detector coordinates for the region. This is because I wasn't correctly handling the case when the WCS type is blank. This is corrected in v5.09 which should be released as part of HEAsoft patch update next week.

Tuesday, December 09, 2008

Another set of recent xspec patches. Two of these are minor mistakes in the 12.5 release, the others cover relatively obscure problems.

12.5.0e

In the FNINIT function (for users linking the XSPEC models library into their own programs), the default model data directory name needs to be updated from "modelIonData" to "modelData" to coincide with v12.5.0 restructuring. Our thanks to John Houck for pointing this out. Report added on Dec 05, 2008.

12.5.0f

Patch to improve the behavior of an exceptional case of Levenberg-Marquardt fitting, where a parameter becomes pegged due to a zero second-derivative matrix diagonal element AND the user chooses to exit before convergence. This prevents an attempt at a covariance calculation on the parameter, which otherwise might lead to a segmentation fault. Our thanks to Stefano Bianchi and Jeremy Sanders for pointing this out. Report added on Dec 05, 2008.

12.5.0g

Fix to the swind1 model function. Now that it is included as part of XSPEC's built-in models library, it should no longer look to the $LMODDIR symbol for finding the model data directory. Our thanks to Delphine Porquet for pointing this out. Report added on Dec 09, 2008.

12.5.0h

When doing a 2-panel plot of plot counts/lcounts chisq and the current fit statistic is cstat, the Y-axis scaling of the chisq panel is wrong. Our thanks to Fill Humphrey for pointing this out. Report added on Dec 09, 2008.

Phil Evans spotted a problem in the new release when using an annulus region type. The region filtering is performed correctly however the WMAP created is too small in the case when the WMAP and image coordinates are the same. This is actually an error I introduced in the cfitsio code (which is however not used internally in cfitsio so doesn't change its standard use). A work-around is to use the elliptannulus region type instead of annulus. I also have a fix within the extractor code to get around this.

Monday, December 08, 2008

The switch to wild cards in xselect.mdb was a little too enthusiastic in the case of the ASCA SIS - the catcol list still needs to be specified for individual detectors. The current version causes an error when running make obscat for ASCA SIS. I have checked in a fixed version.

Thursday, December 04, 2008

I've written a little perl script split_rsp_to_rmf_arf which takes an input response matrix file and splits it into a response matrix file with unit total response at each energy and an arf which gives the total response at each energy. This can be used to mock up in v12 xspec the behaviour of v11 xspec with /b models. An example is given on the wiki section on backgrounds.

Three minor patches to the new release are available on the bugs page.

12.5.0b

When the editing commands addcomp, delcomp, or editmod have been used on a model that already contains linked parameters, the link expressions are not properly updated in the output to a save model file. Our thanks to Laura Brenneman for pointing this out. Report added on Dec 03, 2008.

12.5.0c

This removes the warnings issued if datasets contain CHANTYPE strings other than PI or PHA. It will still issue warnings if the CHANTYPE differs between the spectral data and RMF files. Report added on Dec 03, 2008.

12.5.0d

Additional C/Fortran function wrappers provided for the following recently added C++ models: cflux, partcov, simpl, and spexpcut. These are required for users who link the XSPEC models library into an external Fortran or C program. Our thanks to John Houck for pointing this out. Report added on Dec 03, 2008.

Tuesday, December 02, 2008

Li Xin-Li noted that his kerrbb model has an error in turning on/off self-irradiation and limb darkening. The model is fine if either both are on or both are off but if one is on and the other off then the wrong combination was calculated. Fixed as 12.5.0.

A couple of bug fixes that were too late to get into the recent release.

1. When using a GTI file for time filtering the fall-back position of looking in the first table extension for the table data was not working. This should not be a problem if the gtinam parameter was set correctly.

2. The fixwmp routine was unnecessarily slow with the new method of region filtering. It is still slow but not as slow as it was.

Monday, November 17, 2008

The xselect script xsl_chandra_acis_makeresp made some unwarranted assumptions about DSVAL1 holding the list of selected chips. Generalized this and fixed bug in one of the calls to mkacisrsp where I'd left off an wmap parameter specification. This change will make it into the release coming up this week.

Friday, November 07, 2008

Jörn Wilms pointed out it would be really useful in xspec to be able to write a bunch of information including best-fit parameters and errors to a single row in a FITS file. I've added a script writeFITS.tcl to do this. It either creates a new file or appends to an existing one. Obviously, this is not a general solution for all the information a user might want to save however it can easily be modified to save additional information.

Tuesday, November 04, 2008

Dick Willingale pointed out that the grbm model has a hard-coded, artificial lower limit of 1 keV on the third (tem) parameter. There is no good reason for this so I have removed it for the upcoming release.

Friday, October 31, 2008

I've updated WebSpec with Suzaku AO4 files. The HXD background files supplied had a total exposure of 3e6 seconds. The recommended procedure is to have a background file with the same exposure as the source file. This assumes that statistical errors on the background are Poisson and the systematic error can be represented by changing the total normalization (using corfile). I modified the standard background files to change them from COUNTS to RATE so an input background file could be created for a given exposure time just by changing the EXPOSURE keyword.

Note that fakeit with a background file creates a simulated source spectrum with the exposure requested and a simulated background spectrum with the same exposure as that of the input background file. A useful enhancement for fakeit would be to control the exposure of the simulated background file - one possibility would be to allow commands such asXSPEC12> fakeit inbackground.pha 50000

UPDATE 11/04/08: Fixed an error on the energy ranges for the PIN. The input background spectrum is only valid up to 75 keV. Also, use an background exposure time of 10 x that of the source for the PIN as recommended by the HXD team.

Thursday, October 30, 2008

Three patches have been put out in the last couple of weeks. Two of these deal with the case when parameters differ by very large amounts. This is not recommended - xspec will work best if all the parameters are scaled to O(1).

12.4.0ap

In a Levenberg-Marquardt fit, the zero threshold for the diagonals of the second-derivatives matrix needs to be reduced. This is relevant for cases where fit parameters may differ by enormously large (~10^20) magnitudes. Our thanks to Roderick Johnstone for pointing this out. Report added on Oct 21, 2008.

12.4.0aq

The tclout model command no longer appends a newline character to the model name. This allows its output value to be used more easily as an argument to another XSPEC command. Our thanks to Jeremy Sanders for pointing this out. Report added on Oct 23, 2008.

12.4.0ar

This adds automatic normalization to the covariance calculation performed at the end of a Levenberg-Marquardt fit, which makes it more robust when dealing with large differences in magnitude among the fit parameters. Report added on Oct 29, 2008.

Here is a possible generic way to handle redshifts in model components. Allow any component to have a "z" prepended to its name eg pow-> zpow. The model parser strips off the z while setting a has-redshift flag. Any model component with the has-redshift flag set gets a redshift parameter added (after all the other parameters and before any normalization). When evaluating the model the function is passed a redshifted energy array if has-redshift is set. The output flux array could also be corrected for the (1+z) normalization factors although we would have to be careful to make this consistent with the flux and luminosity commands.

The only type of model where this would not work is one which uses the redshift for something in addition to the energy shift - I think the only such case is the cooling flow which needs the luminosity distance to convert the Mdot parameter to an amount of flux to add.

Wednesday, October 29, 2008

The new release will include a partial covering convolution model (partcov) which can be used to turn any absorption model into a partially covered version. This depends on the new model parsing that takes into account the non-associative nature of convolution models. So, if P is the partial covering model, M the multiplicative absorption model and A the additive model then (PM)A turns M into a partial covering absorption. However PMA or P(MA) applies the partial covering the product of M and A which does not give the desired result.

Monday, October 27, 2008

The Suzaku HXD PIN files use a CHANTYPE of PI_PIN. Strictly speaking this is a violation of the standard however it seems too limiting to just allow CHANTYPE the values of PHA or PI. xspec currently generates a spurious error message about mismatched CHANTYPE when reading the HXD spectrum and response. I've put a temporary workaround in RealResponse.cxx which suppresses the spurious warning however we need a more general solution.

Friday, October 24, 2008

Jeremy Sanders pointed out that files created by his python script using SPEX have no pseudo-continuum causing a seg fault in sumape.f. I've checked in a fix to sumape and Jeremy has also supplied an updated version of the script which avoids the problem (by creating a zero pseudo-continuum).

Tuesday, October 21, 2008

I've worked out how to implement the v11 recornrm model in v12 and allow the correction file norm to be a free parameter. This is done through a new model recorn which has parameters the spectrum number and the correction norm. It is implemented as a mixing model though it doesn't actually do anything to the model spectrum - just changes the correction norm stored in the dataset object. It has to be done as a mixing model to ensure that the XSFunctions library stays free of symbol references to xspec internals - mixing models are not included in XSFunctions but have their own library. This model will be included in the release planned for early November.

Saturday, October 18, 2008

Pre-release testing on the Swift pipeline showed up an embarrassing bug in extractor v5 - the BACKSCAL keyword was not written correctly. This is now fixed in v5.02.

There was also a problem writing out the ROTBOX shape in the REGION extension. Further, Swift software does not recognize ROTBOX at present so I changed this to BOX even when there is a rotation angle. This may produce problems with other missions. These changes are v5.03.

And another bug this time when writing the REGION extension in the case when the input event file already has one and further region filtering is performed by extractor. v5.04.

More minor fixes. Removed the reference to number of events rejected because they fall outside the region (which extractor can no longer no). Eliminated duplication of identical regions in the same component being written to the REGION extension. v5.05.

Monday, October 06, 2008

Roderick Johnstone reported that the command "save time cursor" ignores the final argument and always then prompts for it. Triggering this bug depended on which commands had been used earlier. Fixed xsel_save.f.

Thursday, October 02, 2008

I've been working on building heasoft distributions using both gfortran and g95. This under Tiger with Xcode 2.4.1 (which is gcc 4.0.1).

g95 is the current snapshot binary from www.g95.org which is v0.92. It is installed under /usr/local. To build I had to edit the hmakerc files after configure to remove -fno-f2c from the FFLAGS macro.

gfortran is from "fink install gcc42" and is v4.2.2. To build requires editing hmakerc to change -O2 to -O in the FOPT macro and to add at the beginning of the F77LIBS4C the directories -L/usr/lib -L/usr/lib/i686-apple-darwin8/4.0.1 and -L/sw/lib/gcc4.2/lib/gcc/i686-apple-darwin8/4.2.2. Note that it is vital they be in this order and at the beginning of the macro or else the loader will link in gcc v4.2.2 libraries instead of gcc v4.0.1.

Saturday, September 27, 2008

Wednesday, September 24, 2008

Jeremy Sanders points out that the label for delchi plots is wrong or at least misleading. Fixed this by changing the entry in plotLabels.dat. Note that the label is now hardwired for the chi-squared statistic however the delchi plot doesn't make any sense for other statistics.

Jeremy also noted that the y-axis label is a long way to the left and this looks strange. The reason for the position is that with LAB ROT we need to leave space to write numbers of the formA x 10^(-B). Curiously, we are defaulting to rotated labels for 2-panel plots but unrotated labels for 1-panel plots. I've no idea why. Note that the easy way to move around the position of the y-axis label isPLT> lab pos y 3.0

Monday, September 22, 2008

Fixed bug that was adding a "#" to the next line instead of the current line of log file output. This is a partial fix to issue 1024. Input when setting parameter values (in model or newpar) is still not echoed to the log file - problem is in ModelContainer::setParameterFromPrompt.

Update: had to back this change out because it doesn't work with tcerr, which is not buffered and hence passes one character at a time to TclIO::write. Craig worked out how to fix xsLog.cxx to fix the problem.

Wednesday, September 17, 2008

I've created a Wiki page with a list of xspec priority enhancements. These are divided into large and small projects. At the moment they are not priority-ordered but I will add that along with additional information on the large projects.

Updated documentation to match recent enhancements and additional models. Note that the description of the bvapec model is now included along with the bapec model, not in a separate file.

Fixed a plotting bug. The green line marking 0 or 1 in the res, ratio, chi etc. plots did not go all the way across the plot if a rescale was done so that only part of the x-range of the data was included. Note that a rescale to start at an x-value below the initial data will not draw the green line for the x values below the start of the data.

Thursday, August 28, 2008

The cutoffpl model can show a distortion for very low energies (E/B approx. less than 10^-3). The incomplete gamma function calculation which this is based on needs to be improved in this region. Our thanks to Joern Wilms, Moritz Boeck, and Manfred Hanke for pointing this out. Report added on Aug 28, 2008.

12.4.0al

This adds the Fortran wrapper function xgtcht(console,log) for those wishing to retrieve XSPEC's console and log chatter level settings from inside their own Fortran local models. The function is equivalent to the xgtcht contained in the xanlib library used by XSPEC11. Report added on Aug 28, 2008.

12.4.0am

Enhancement patch required for reading data sets and responses in the new format used by GLAST GBM files. The modifications include the removal of the SPEC_NUM column for type-II data files, and the storing of multiple response matrix extensions into one response file. XSPEC will now distinguish among multiple response extensions by appending a curly-bracket specifier to the response file name: myResponse.rsp{n} where n is the EXTVER keyword value of the extension. Report added on Aug 28, 2008.

Friday, August 22, 2008

Craig has been experimenting with openMP which is included in gcc v4.2 and above. Since openMP uses a shared memory model the trick is to find places where multiple threads can be used which do not trash each others' memory. A valid case is the loop over responses in Model::fold. This speeds up the code if there are multiple datasets in the same datagroup. It involves changes to Model.cxx as well as MultiResponse.cxx and RealResponse.cxx.

Test was with a dual-processor machine running Solaris. Note that the -xopenmp compiler flag required either no optimization or -O3.

Thursday, August 21, 2008

Prompted by a question from Jeremy Sanders I have developed a new way of calculating fluxes and errors for models and parts of models. The trick is to provide a new convolution model called cflux whose first two parameters are the minimum and maximum energy over which the flux is calculated. The final parameter is the flux. The component is placed in front of the model component(s) whose flux is being calculated and one of the additive components has its normalization frozen. The standard fit and error command on the flux parameter will then provide the best fit flux and confidence region. This model is available through the extra models web page.

Thursday, August 07, 2008

The current version of xselect/extractor writes spectra with region extensions having the EXTNAME keyword set to REGION. This is required by CIAO. However, SAS requires EXTNAME to be REG00101 so added a command to xsl_xmm_epic_makeresp to change EXTNAME before calling the response and arf generation tools.

Tuesday, August 05, 2008

Allyn Tennant pointed out that genrsp writes a keyword LO_THRESH which should actually be LO_THRES. I fixed this as v2.04 by adding the new keyword while leaving the old just in case there is other s/w that expects it.

Friday, July 18, 2008

strain2xspectime.pl creates input file correctly for time series data and this is fit using the mbht model. However, residuals show high frequency correlations presumably because noise is beingapplied in frequency space in synthlisa. The strain2xspec.pl and mbh model which work in frequency space are not working correctly - the model doesn't match the data when it should. All current changes are checked into the repository.

I'm not clear how and why the postBuffer is used - need to check this with Sean or Ira.

Larger question is how should the noise be generated ? Is it correct to do this in the frequency domain ? A better detector model may be required.

Monday, July 14, 2008

When using the gsmooth or swind1 models, certain combinations of parameters can cause an invalid array access. On 64-bit Linux systems this will cause a crash. Our thanks to Curtis McCully for pointing this out. Report added on Jul 08, 2008.

12.4.0af

When settings have changed through either the xsect or cosmo commands, the model calculations should be immediately updated. (This patch also improves the cosmo command-line parser.) Our thanks to Stefano Bianchi for pointing this out. Report added on Jul 08, 2008.

12.4.0ag

The kerrd and nsa additive models will cause XSPEC to crash in certain cases, the latter primarily on Intel/Mac platforms. Report added on Jul 14, 2008.

Wednesday, July 09, 2008

Allyn Tennant spotted a bug in genrsp when making a response for a grating. I'd missed a case when the channel boundaries are in decreasing energy order and the result was the center bin of the gaussian response was chopped out. This is fixed in v2.03.

Friday, July 04, 2008

Kim Page at Leicester reported that the HEAsoft 6.5 version of extractor dies when using a time filter if the filename contains a "+". It was interpreting this as an HDU number. Fixed this and checked in a change which will be included in extractor v5.0.

Wednesday, July 02, 2008

At the request mainly of the ISIS folks I've managed to make a stripped-down HEAsoft 6.5 distribution which only includes the Xspec model library files to build only libXSFunctions, libXSUtil and libXS. I assume that the user has a cfitsio library already. Some minor hacks of the top level and Xspec configure files were necessary to make sure that hmake didn't try to build any heacore libraries. Also, moved some include files into Xspec/src/include from directories that otherwise aren't needed.

Monday, June 23, 2008

Mike Corcoran spotted a couple of minor problems. The ogip_92_009 memo refers to the incorrect location for the wftbmd.f and .c files. It should be $HEADAS/../ftools/spectral/tables/. Also the onepar and twopar Makefile don't work because they need to refer to the correct version numbers of xanlib and cfitsio - I fixed this by switching to standard HEADAS Makefiles so running hmake will automatically pick up current versions of libraries. These changes are checked in but won't make the imminent HEAsoft 6.5 release.

Thursday, June 05, 2008

When I added the support for 5x5 to 3x3 conversion I missed the case of the user already having done an extract events. If this has happened then the event file to be used has a different name. Checked in a fix to this and was a bit cleverer about jumping out of the 5x5to3x3 routine if we don't need to run it.

Friday, May 09, 2008

The likelihood-ratio test script doesn't work when there are multiple datagroups. The reason is that switching between models by making them active/inactive loses information on the parameters for groups > 1 when the model becomes inactive. We perhaps should modify the model inactive command to track multiple datagroups however as a workaround I modified lrt.tcl to use command files to store the model definitions. Each time the model is switched the appropriate command file is read.

Monday, May 05, 2008

Started work on the new version of extractor which will use cfitsio internal filtering as much as possible.

In the course of switching the region filtering to cfitsio I found an obscure bug. If the image and wmap coordinates are the same but have different binning and wtmapfix is set then the WMAP bins with -1 are not quite correct. Several bins at the edge of the selected region can have counts in them when the value should be -1.

Saturday, May 03, 2008

Dave Pooley reports that xselect has problems under Mac OS 10.4 but not 10.3 when using ROSAT data. I confirmed the error under 10.4. The error message is something like Could not find keyword for Instrument for ROSAT NONE Got new mission: ?4????AF?'?AF?AF?AF?? '7????P???? R??????D???51

I don't know why this occurs but the fix is to edit xselect.mdb to use the new wildcard facility to deal with the PSPCB and PSPCC instrument variant names instead of using the instkey specification to only read the first four characters of the INSTRUME keyword.

Wednesday, April 30, 2008

A few new patches have been added recently. 12.4.0x fixes a number of problems that showed up when using the new g++-4.3.0 compiler and when using gcc on Solaris platforms. This patch level is released as part of HEAsoft 6.4.1. 12.4.0y improves the handling of cases when the L-M algorithm pegs a parameter due to a zero or negative pivot value in the Hessian. 12.4.0z keeps the fit valid when the fit method is changed. This allows the improve command to be run after an L-M fit. 12.4.0aa is a fix to allow filenames prompted for by the fakeit command to being with a / ie to be absolute paths. Patches available from the usual place.

Thursday, April 24, 2008

Overhauled the response generation option on "save spec" for Chandra ACIS data. I added an extended? parameter to specify whether the source is a point source or not. For a point source the arf is created using mkarf, and for an extended source mkwarf is used. The rmf is generated using mkrmf or mkacisrmf depending on whether CTI correction has been performed. The script checks keywords in the spectrum to determine which is appropriate. Note that to find some of the auxiliary files required xselect should be being run in either main directory for the dataset or in a directory one level down (eg secondary).

Note that I also modified the FITS region extension written by extractor so that the EXTNAME is REGION and EXTVER is used to track multiple extensions. This is a change from an EXTNAME of REG001## and is made to conform with the CXC standard defined by McDowell & Rots. There may be an issue here is XMM-Newton SAS routines are expecting the REG001## names.

Monday, April 14, 2008

Tahir points out that the BeppoSAX RMFs don't work in rbnrmf. The problem is that these files have only RMFVERSN='1992a' and do not have the HDUVERS keyword that the software now requires. The workaround is to add HDUVERS='1.0.0' to the MATRIX extension. I've updated the relevant subroutines to check for RMFVERSN if HDUVERS is not found.

Tuesday, April 08, 2008

Changed the plotting units for the setplot wave option. Now showing f_nu and variants instead of f_lambda. The model and ufspec y-axis is photons/cm^2/s/Hz; emodel and eufspec are in Jansky (1e-23 erg/cm^2/s/Hz); eemodel and eeufspec in keV Jy. The latter is a bizarre mixed unit but it isn't clear to me what to use here. It might be an idea to have an option for the user to switch between f_lambda and f_nu.

Updated: decided that for the eemodel/eeufspec plots the units should be erg/cm^2/s corresponding to standard nu F_nu plots.

Independently, I fixed an error in setting the y-axis range for eufspec and eeufspec under setplot wave.

Monday, March 24, 2008

Added a new Tcl script, lrt.tcl, to calibrate the likelihood ratio test. Currently only works with one data set. The user defines two models (by default model0 and model1) then the script generates a user-specified number of simulated data sets based on model0 and for each one evaluates the log(likelihood ratio) between model1 and model0. The script returns the fraction of simulations with a smaller log(LR) than the data.

I will then use lrt.tcl as the basis for a script to calculate F-test probabilities foradding an additional model component.

Thursday, March 13, 2008

Enabled the automated response generation in xselect for Suzaku XIS spectra. I'm still waiting for a decision from the XIS team on what default energy and channel binning to use in the response matrix. Ishisaki-san has suggested that the correct estepfile option for xissimarfgen is "medium" so the response generation uses this.

Currently using a "medium" binning scheme which produces 2048 channels. Spectra extracted from xselect are binned using this scheme whether or not the automated response generation is used.

Note that I also modified the MDB code to allow trailing wild cards eg XIS* will match to any of XIS0, XIS1, XIS2, or XIS3.

Also, updated addascaspec so it runs correctly if there is no ARF used.

Checked in a change to xselect so that when there is a mix of 5x5 and 3x3 suzaku xis files read in then, when doing an extract, xis5x5to3x3 is used to create a temporary 3x3 file. This was requested by the xis team and ensures that doing an extract event creates a correct output 3x3 file. At the moment we aren't doing anything with the extra information in the 5x5 file.

Tuesday, March 11, 2008

Bryan points out that the documentation for local models in v11 doesn't include the special instructions required for the Mac OS X ie because we can't make a shared library the xspec11 executable must be rebuilt with the new local model library. I've added this to the relevant manual page although hopefully most people are using v12 now anyway.

Friday, March 07, 2008

The specifications rules for grade strings in the xselect "filter grade" command do seem lead to a little confusion so made them a but more lenient. Now allow spaces in between individual elements. eg "0:0 2:4 6:6" is now allowed as well as "0:0,2:4,6:6". This change is in extractor v4.83.

As noted yesterday the current version of suzpsf assumes the WMAP is in sky coordinates, which is no longer true. I've now fixed this. There are two changes required. Firstly, extractor has been modified (v4.83) to write the REF* keywords which XMM files use to record the original sky WCS keywords. Secondly, the suzpsf model has been modified to use these keywords (as the xmmpsf model already did).

To fix spectra that were created using older versions of extractor add the following keywords to the primary header with the values of the corresponding keywords from the EVENTS extension of the input event file. REFXCRVL REFXCRPX REFXCDLT REFYCRVL REFYCRPX REFYCDLT

12.4.0n If the precise best-fit values are input as starting parameter values to a Levenberg-Marquardt fit, for certain data sets and models the fit may run through a large number of redundant loop iterations and produce "SVDCMP" warning messages. Our thanks to Jeremy Sanders for pointing this out. Report added on Mar 06, 2008.

12.4.0o For xmmpsf and suzpsf mixing components, Xspec is unable to parse RA and DEC strings with colon delimiters (entered with the xset command). Report added on Mar 06, 2008.

Note also the there is a problem with suzpsf for all options except that of assuming the surface brightness distribution is centered on the middle of the WMAP. This issue arises because the model was written when the Suzaku XIS spectra used sky coordinates in their WMAP. Since late 2006 we have used detector coordinates but due to an oversight the suzpsf model was not updated.

Tuesday, March 04, 2008

Once the error command is run for a parameter belonging to a named model, it does not allow the user to specify unnamed-model parameters during future error runs. Our thanks to Kip Kuntz for pointing this out. Bug fix 12.4.0l.

Kip has pointed out that fakeit doesn't handle multiple sources correctly. If you set up with two sources with their own responses modelling a dataset then do a fakeit only the first source and response contribute to the simulated spectrum. This will take a bit of work to fix.

Jennifer Donley at Arizona e-mailed to worry about the warning message about incompatible CHANTYPE after simulating Chandra ACIS spectra for CY10. This is a minor bug in xspec which fails to pick up the CHANTYPE value from the response matrix when doing a "fakeit none".

Fabio Pizzolato reported a seg fault using rgsrmfsmooth in the case when the spectrum had been binned up by a factor of 4. The fix was to increase the space allocated for response groups in the output response.

In the course of diagnosing this I realized that rbnrmf was not setting the NUMGRP keyword in output response matrices correctly - it was the number of response groups from the input file that was being written. This shouldn't have made any practical difference but was confusing.

Monday, February 18, 2008

Alex Padgett points out that extractor doesn't handle filenames containing a '+' because it assumes that everything following the '+' is an extension number. Fixed this by checking whether the '+' comes before a '.' (v4.82).

Monday, January 14, 2008

xselect gives a really misleading message when the event file cannot be found : The input file is neither a FITS file nor an ASCII file containing a list of FITS filesI've improved this to make it clear that the file is not being found.

Thursday, January 03, 2008

12.4.0cDOS-mode scripts (with their extra carriage-return characters) are not properly handled for multi-line commands. Our thanks to Laura Brenneman for pointing this out. This also fixes another scripting bug in which a line with 'n' followed by blank spaces is wrongly interpreted as 'newpar' rather than 'no'. Report added on Dec 27, 2007.