Up: XSPEC Manual Previous: Matching keyword arguments

XSPEC v9 bugs fixed in v10

9.00a Plots of multiple datasets with an energy x-axis and use of setp rebin to bin up to a certain number of sigma produce some garbage points.

9.00b The ascac model requires the XFLT0001 keyword to be an integer followed by two reals. The documentation only mentions the integer. The function actually does nothing with the two reals but will register an error if they are not there.

9.00c The pexrav and pexriv models go haywire if the response matrix is changed in the course of an XSPEC session.

9.00d Equated parameters are not propagated. eg if par1 = par2 and a command is given to set par2 = par3 then par1 ends up not equated to anything while it should be set to par3.

9.00e The plot summ command does not work correctly.

9.00f When multiple datagroups are in use, the gain fitting is enabled, and the model contains a null component then the addcomp command causes total confusion.

9.00h The untie command leaves the parameter value correct but not the step size, lower limits, or upper limits.

9.00k The Chebyshev polynomials used in the models cp6mkl and cp6vmkl are incorrectly defined. The result is that only positively rising polynomials are allowed, a subset of the available phase space.

9.00l There is a minor error in the plotting of spectra against wavelength. The wavelength scale is in error by a factor of 0.99982.

9.00m An ignore or notice command whose first channel is 0 causes XSPEC to get confused. If you do this you need to exit from the program and restart. Note that XSPEC always uses 1 for the first channel of a spectrum.

9.00n The message written by abun ? is misleading. The default for relative abundances is angr.

9.00o After a large number of calls to the model command when using table models bizarre things start happening due to the available number of i/o channels being exceeded.

9.00p The weight gehrels command with more than one dataset causes xspec to prompt for the first dataset name. The workaround is to enter the name here and xspec will work correctly.

9.00r There is an error in the comptt model.

9.00s The script command does not work as advertised. Just giving the command script generates a file called xspec.log not xspec.xcm. Also the scripting cannot be turned off using the command script none.

9.00t The second parameter of the zvfeabs model is not the metal abundance but the metal abundance abundance times the value of the first parameter.

9.00v The save command loses any additive constant in a parameter link e.g. parameter 1 = parameter 2 + 0.5 is saved as parameter 1 = parameter 2.

9.00w If the flux command resets the energy limits for a dataset then the new energy limits are used for all subsequent datasets.

9.00x If multiple datasets are in use and one is replaced from a new file with more channels than the original then all subsequent datasets are trashed.

Up: XSPEC Manual Previous: Matching keyword arguments

Keith Arnaud (kaa@genji.gsfc.nasa.gov)
Wed May 28 10:59:33 EDT 1997

9.00a	Plots of multiple datasets with an energy x-axis and use of setp rebin to bin up to a certain number of sigma produce some garbage points.
9.00b	The ascac model requires the XFLT0001 keyword to be an integer followed by two reals. The documentation only mentions the integer. The function actually does nothing with the two reals but will register an error if they are not there.
9.00c	The pexrav and pexriv models go haywire if the response matrix is changed in the course of an XSPEC session.
9.00d	Equated parameters are not propagated. eg if par1 = par2 and a command is given to set par2 = par3 then par1 ends up not equated to anything while it should be set to par3.
9.00e	The plot summ command does not work correctly.
9.00f	When multiple datagroups are in use, the gain fitting is enabled, and the model contains a null component then the addcomp command causes total confusion.
9.00h	The untie command leaves the parameter value correct but not the step size, lower limits, or upper limits.
9.00k	The Chebyshev polynomials used in the models cp6mkl and cp6vmkl are incorrectly defined. The result is that only positively rising polynomials are allowed, a subset of the available phase space.
9.00l	There is a minor error in the plotting of spectra against wavelength. The wavelength scale is in error by a factor of 0.99982.
9.00m	An ignore or notice command whose first channel is 0 causes XSPEC to get confused. If you do this you need to exit from the program and restart. Note that XSPEC always uses 1 for the first channel of a spectrum.
9.00n	The message written by abun ? is misleading. The default for relative abundances is angr.
9.00o	After a large number of calls to the model command when using table models bizarre things start happening due to the available number of i/o channels being exceeded.
9.00p	The weight gehrels command with more than one dataset causes xspec to prompt for the first dataset name. The workaround is to enter the name here and xspec will work correctly.
9.00r	There is an error in the comptt model.
9.00s	The script command does not work as advertised. Just giving the command script generates a file called xspec.log not xspec.xcm. Also the scripting cannot be turned off using the command script none.
9.00t	The second parameter of the zvfeabs model is not the metal abundance but the metal abundance abundance times the value of the first parameter.
9.00v	The save command loses any additive constant in a parameter link e.g. parameter 1 = parameter 2 + 0.5 is saved as parameter 1 = parameter 2.
9.00w	If the flux command resets the energy limits for a dataset then the new energy limits are used for all subsequent datasets.
9.00x	If multiple datasets are in use and one is replaced from a new file with more channels than the original then all subsequent datasets are trashed.