Changes between Version 27 and Version 28 of NewC17


Ignore:
Timestamp:
2018-01-31T17:19:06Z (4 months ago)
Author:
peter
Comment:

Describe bug in TABLE STAR rebinning code.

Legend:

Unmodified
Added
Removed
Modified
  • NewC17

    v27 v28  
    1111A bug causing '''''the SAVE XSPEC command to produce faulty FITS files''''' has been fixed. Several other bugs in this command were also fixed, such as the covering factor being omitted in each of the reflected components of the spectrum.
    1212
    13 The SED produced by the '''''table SED NGC5548''''' command has been extrapolated into the radio and gamma-ray using asymptotic slopes.  This is the make the SED more physical and similar to those used in AGN STORM models.
    14 
    1513A new option to normalize the spectra in the SAVE XSPEC FITS files has been added. See Hazy 1 for details.
    1614
    1715A bug causing '''''the reflected components of the SAVE CONTINUUM output to have the wrong normalization''''' has been fixed. This would affect spherical models with an open geometry in the luminosity case. See [wiki:HotFixes_17] for details.
     16
     17The SED produced by the '''''table SED NGC5548''''' command has been extrapolated into the radio and gamma-ray using asymptotic slopes.  This is to make the SED more physical and similar to those used in AGN STORM models.
     18
     19A bug potentially causing '''''part of the SED from a stellar atmosphere grid to be omitted''''' has been fixed. Investigation of the standard grids supported by Cloudy (i.e. those covered by the '''''compile stars''''' command) shows the effect of this bug is benign. The situation for other grids is not clear and could potentially be more serious (e.g. SEDs taken from the PoWR grids). It is recommended to recompile the binary stellar atmosphere files, otherwise the fix will not have any effect (unless you work directly on the ascii files of course).
    1820
    1921A bug has been fixed that could cause line labels to be parsed incorrectly under certain circumstances (see [wiki:KnownProblems_17]). The solution is to make the parser stricter, resulting in the following user-visible changes: