Known issues and patches
Home Downloads Manual Issues/Patches Additional Models Xspec In Python
    (updated 10/23/18) (updated 03/28/19)    

New issues from Xspec 12.10.1

Frequently Asked Questions

List of currently outstanding issues.


Patches:

latest update 12.10.1e Mar 28, 2019

Requires patch installer v4.10

To apply patches, you'll need to have downloaded and already built the source code distribution of XSPEC. For details about the patch installer including options available with the latest v4.10, click here. Otherwise, just follow the instructions below.


(Note: This assumes you have already set your HEADAS environment variables with the headas-init script, as you would if you were running XSPEC.)

To make sure your XSPEC installation is up to date with ALL listed patches:

1.    If you don't already have the patch installer tcl script (v4.10), download and place it in the XSPEC src directory. This directory should be at heasoft-[ver]/Xspec/src from the source code distribution.

2.    Download the latest patchfile into the same directory. There is no need to unzip/untar the patchfile since the installer will do that.

3.    At the command line, launch the script by typing 'tclsh patch_install_[ver].tcl', and that's all.


The script should detect which patches you've installed previously, copy the new code files to the necessary directories, determine whether complete or only partial rebuilds are necessary, and finally perform the rebuilds. Numbers listed in red indicate that the patch modifies the interface to one or more of XSPEC's libraries. These patches will generally cause longer rebuilds. If you have a local model library, it is recommended (though not always necessary) that you rebuild it with initpackage after applying red patches.


12.10.1a For users attaching the models-only library to their own programs, a crash may occur when calling the FNINIT initialization function. FNINIT is also not properly reading the default settings from a user's Xspec.init file (when one exists). Our thanks to Doug Burke for pointing this out. Report added on Oct 25, 2018.

This patch modifies heasoft-6.25/Xspec/src/XSFunctions/Utilities/ xsFortran.cxx.

12.10.1b Changed the default lower limits on the cph, vcph redshift parameters for consistency with other cooling flow models. Also changed the name of the spin parameter in kyconv and kyrline from 'a/M' to 'a' to avoid problems in PyXspec. Our thanks to Doug Burke for pointing this out. Report added on Oct 25, 2018.

This patch modifies heasoft-6.25/Xspec/src/manager/ model.dat.

12.10.1c An enhancement needed for PyXspec to run the error command on response parameters. This adds a flag as an optional second argument to the Fit.error() function, which must be set to True when running error on reponse parameters. For example, to calculate the error on the 2nd response parameter:

Fit.error('2',True)

Our thanks to Phil Kaaret for bringing this to our attention. Report added on Feb 27, 2019.

This patch modifies heasoft-6.25/Xspec/src/XSUser/Handler/ XSinterface.cxx and XSUser/Python/xspec/ fit.py.

12.10.1d This fixes a bug the rdblur, kdblur, kdblur2, and kerrconv convolution models when the model was evaluated on a non-uniform energy grid. Report added on Mar 04, 2019.

This patch modifies heasoft-6.25/Xspec/src/XSFunctions/ blurring.cxx, kdblur.cxx, kdblur2.cxx, rdblur.cxx and spinconv.cxx.

12.10.1e Bug fixes for the mdefine command. This primarily applies to cases using built-in Xspec multiplicative and convolution components in the mdefine expression. Also fixes cases using component names with upper-case letters. Report added on Mar 28, 2019.

This patch modifies heasoft-6.25/Xspec/src/XSFunctions/Utilities/ MdefExpression.cxx and .h.


Older Versions:

     12.10.0
    12.9.1
    12.9.0
Links to v11 bugs pages:
       v11 Bugs       v11 Bug reporters

Xspec Xspec Home Page


HEASARC Home | Observatories | Archive | Calibration | Software | Tools | Students/Teachers/Public

Last modified: Thursday, 28-Mar-2019 18:27:11 EDT

HEASARC support for unencypted FTP access will be ending possibly as early as July 31, 2019. Please see this notice for details.