XSPEC v11.2 issues fixed in 11.3

11.2.0a

There are two bugs in fakeit. If there is no background file in use then the BACKFILE command in the faked file is set incorrectly. The value of the fit statistic written to the screen by the fakeit command is wrong.

11.2.0b

The normalization (Mdot) of the cooling flow models does not depend on the cosmology set by the cosmo command.

11.2.0c

The model is not recalculated when the abundance ratios are changed by the abund command.

11.2.0d

The error command can go into an infinite loop in (hopefully) unusual circumstances.

11.2.0e

The help on apec and vapec erroneously refers to the XSPEC_APEC environment variable instead of the new xset APECROOT method for changing the files used.

11.2.0f

The error option on flux and lumin does not work correctly under Solaris.

11.2.0g

The xspec library (libxspec.a) gives a link error when used with a program other than XSPEC.

11.2.0h

There is an error in the (v)npshock and (v)sedov models for neispec versions 1.0 and v1.1.

11.2.0i

The BACKFILE keyword is written incorrectly by fakeit when a background file is in use.

11.2.0j

The cooling flow models produce no flux. The reason is that the cosmological parameters are not initialized to non-zero values.

11.2.0k

The ignore command is really slow with grating data.

11.2.0l

The identify command (and seplot id option) miss off the final line in the list. Also, identify using the apec table does not change the file in use if xset apecroot is used.

11.2.0m

The (v)pshock models produce garbage if only the abundance is changed between successive model evaluations.

11.2.0n

The ? command fails to give a list of the available commands if local models are in use.

11.2.0o

Integral IBIS files do not work in XSPEC due to a certain laxity in applying the standard. This fix allows the nth spectrum in the file to be accessed by filename{n} as though the file was in the standard type II format. A similar fix for the ARF is included.

11.2.0p

XSPEC will not execute a script in the parent directory to the current one.

11.2.0q

Within a script, a blank line following the newpar command will cause the command to be ignored. Additionally, any newpar command in a script that attempts to modify multiple parameters will not change the first parameter requested.

11.2.0r

Under Linux or MacOS X garbage is written to the screen if the user gives the command cpd / or if the extend command is given when no datasets have been read.

11.2.0s

The newpar command sets the first parameter entered twice: this problem was introduced by patch 11.2.0q which is therefore superseded by this fix.

11.2.0t

The reflect model produces incorrect results if the response matrix does not have constant width energy bins.

11.2.0u

There are three minor problems with saved command files : if the model string is too long it will be split into separate lines which cannot then be reread by xspec; any string parameters specified by xset are not written out; cornorm commands are written out even if no correction file is in use.

11.2.0v

Under very unusual (and obscure) circumstances fakeit can overwrite the existing file instead of creating a new one with different name.

11.2.0w

Giving show an incorrect argument can crash xspec under Linux and MacOS X.

11.2.0x

The mdef command does not work if any bug patch has been applied.

11.2.0y

The plot sum command doesn't work with gcc/g77 compilers.

11.2.0z

The model is not completely reset if an error is made when using the model command. This can lead to problems if a fit command is given before redefining the model.

11.2.0aa

The help files for xspec and plt cannot both be accessed in the same xspec session. If the help command is invoked from the xspec prompt then subsequent invocations from the plt prompt (after iplot) will give help for xspec and not for plt. If the plt help is accessed first then that is what appears when the xspec help command is invoked.

11.2.0ab

Removing a dataset (through data none) can cause the final bin in a remaining dataset to have incorrect energy bounds. This can lead to all the channels being removed when ignoring on energy.

11.2.0ac

Local models cannot include C routines.

11.2.0ad

The name for a save file cannot contain upper case characters.

11.2.0ae

The tclout flux command actually writes out the luminosity (in 10⁴4 erg/s) if a lumin command has been given more recently than a flux command.

11.2.0af

The NEI models can sporadically die with seg fault, memory error, or floating exception (depending on the system).

11.2.0ag

plot icounts doesn't work if setplot add has been set. Also, 2-panel plots with the top being icounts don't work.

11.2.0ah

In an attempt to reduce compute time XSPEC doesn't recalculate models for any datasets with identical energy ranges to an earlier dataset. This is fine except for models that actually use the IFL argument and treat each dataset individually. There are no standard models which do this but users may run into this issue when writing local models.

11.2.0ai

The net errors can be (obviously) incorrect if changing to a non-standard weighting (eg gehrels) for a dataset without a background file.

11.2.0aj

In the data command attempting to skip over a non-existent dataset (eg data ,,file2 when only one file has been read in) causes a crash.

11.2.0ak

The lumin command writes q0 and lambda0 with only one decimal place of accuracy leading to confusion if lambda0 is set to eg 0.65.

11.2.0al

The tclout plot contour command doesn't write out all the values in the steppar run.

11.2.0am

The xion model can give zero flux after a parameter is changed (ie when the function is called for a second or subsequent time) for systems compiling using g77.

11.2.0an

The tclout flux and eqwidth commands take the dataset number as an argument not the datagroup number. There was also a bug that the valid argument range was based on datagroups not datasets.

11.2.0ao

Mega-patch of bugs and some small new features that have been requested. Includes: a) fixed setplot dev none; b) fixed projct model so it works correctly for multiple observations ie more than one dataset per datagroup; c) added fstat and query options to tclout to return information on results of last ftest command and current setting of the query; d) if steppar has been performed on only one parameter then plot contour produces a 1-D plot; e) the model description written out can now be cut and paste to use in the model or editmod commands.

11.2.0ap

The command fakeit filename does not work correctly. If no previous dataset has been read it creates fake source and background files with zero counts and if a previous dataset has been read then it uses the backscal and areascal from this dataset instead of from the filename specified in the fakeit command.

11.2.0aq

There is a subtle bug in the code that interpolates mtables. This can cause incorrect models where an input table energy range is split across response energy ranges.

11.2.0ar

Parameters are written with an insufficient number of significant figures for some analysis of grating data.

11.2.0as

Long model string parameters can be truncated when using the xset command with no arguments to get a list of parameters.

11.2.0at

The mdef command doesn't work correctly for convolution models.

11.2.0au

The bug fix to reflct in 11.2.0t introduced a new bug that causes the calculated amount of reflection above 10 keV to be smaller than it ought to be. The effect of this can be seen by comparing reflct(cutoffpl) with pexrav.

11.2.0av

XSPEC under Linux can die due to undefined symbols when running local models which are included at run-time. This has been extensively reported for the acisabs and compps models.

11.2.0aw

There are several points to watch out for when using the error option on the flux or lumin commands. The model cannot be changed (using model, editmod, addc, or delc) between doing a fit and flux/lumin with errors. If a parameter is changed, eg the absorption column set to zero, the realizations used to estimate the error will vary the parameter around its new value but with a variance from the last fit.

11.2.0ax

There is an error in the cooling flow models (cflow, mkcfl, vmkcf) causing incorrect weightings to the emission measure at the extremes of the temperature range. The main effect seems to be an approximately 10 normalization. The old model is available using the XSPEC command xset cflow_version 1. The new version is the default and can be set by xset cflow_version 2. The new version also allows the number of temperature steps in the integration to be varied. The default is 10 and can be changed by eg xset cflow_ntemps 20. Note that changing the number of integration steps will have little practical effect unless switch=0 in the mkcfl or vmkcf models.

11.2.0ay

The compbb model crashes under Linux if the electron temperature is a frozen parameter.

11.2.0az

If MAXVPR in xspec.inc is set to more than 100 then XSPEC core dumps.

11.2.0ba

Fakeit produces an incorrect background file if the input source and background files have different values of BACKSCAL.

11.2.0bb

Gain fitting parameters that are saved to a script are not read back correctly.

11.2.0bc

There is an error in the XSPEC implementation of the APEC model which causes the continuum to be calculated a factor of (1+z)² too low. Note that this will change fitted abundance values for high redshift clusters.

11.2.0bd

The diskbb model crashes under some (apparently rare) circumstances.

11.2.0be

The documentation for the srcut model contains an error.

11.2.0bf

The save command (and autosave) do not save the abundance table or cross-section option.

11.2.0bg

The NEI models v1.x do not work correctly with response matrices with varying energy binning - spurious line features can arise at energies where the binning changes.

11.2.0bh

The projct model produces spurious warning messages if all the channels are ignored for one or more datasets.

11.2.0bi

Models with gain fit, linked parameters, and multiple datagroups are not saved correctly. The linked parameters end up linked to the wrong parameters.

11.2.0bj

Command files created by the save command cannot contain upper case letters.

11.2.0bk

Multiplicative models set up using mdefine are (incorrectly) multiplied by the response bin width.

11.2.0bl

The model command can seg fault if the model erroneously contains delimiters (eg (,),*,+) that are not part of a valid component. An example is ending the model string with (.

11.2.0bm

Reading the xautosav.xcm file back into XSPEC does not work correctly under some circumstances involving complicated models and many datasets.

11.2.0bn

Giving the error or uncertainty command between doing a fit and a flux err causes the latter to give an incorrect result.

11.2.0bo

The etable model does not work correctly for response energies which lie outside those tabulated in the table model file. The model is set to exp(-1.0) and not the correct value of 1.0.

11.2.0bp

The eqwidth command does not reset the internal total model array correctly. The result is that following an eqwidth command with a flux or lumin command will give the flux or luminosity of the model without the line component.

11.2.0bq

When using parameters whose maximum is not equal to their top or minimum is not equal to their bottom it is possible for apparent parameter values to swing between maximum and minimum but for the model itself not to change. One diagnostic of this can be that saving a model then later reading it back in will give very different values of the fit statistic and a clearly incorrect fit.

11.2.0br

The cutoffpl model can generate floating exceptions or NaNs when using with responses that run up to high energies (>100 keV). It also becomes less accurate at these energies especially if the individual energy bins are wide.

11.2.0bs

Fitting with C-stat and a background file does not work correctly if the background file has lots of channels with zero counts.

11.2.0bt

There is a bug in the projct model when analyzing multiple observations. The calculated models are applied to the wrong observations.

11.2.0bu

The thleqw command doesn't work.

11.2.0bv

The component plots produced after ``setplot add'' are slightly wrong for models of the form A1 + M1(....). The plot of the A1 component is actually of M1*A1. This does not effect the fit or plot of total model.