GitLab

When giving the list of parameters through a file, cigale did not compute properly what parameter changed between to successive models.

With the new sanity check of the input parameters, cigale did not handle the fact that the redshift could be given in the parameters file. Now this is handled properly.

A significant fraction of the total run time is spent computing integrals (e.g. fluxes in passbands). We can make the integration faster by rewriting the trapezoidal rule in terms of np.dot(). This allows to offload the computation to optimised libraries. The end result is that the integration is twice as fast, with a gain of ~10-15% on the total run time.

0.9.0 release

Samuel Boissier gave us extended values down to a velocity of 40 km/s as well as
intermediate values for the SFH module sfh_buat08.

Convert individually each item of the input list as doing so on an the entire array generates an error if the expected type is int and the provided values are in floats.

Computers are much better at multiplying than at dividing. Therefore to correct the emission for redshifting we multiply by 1/(1+z) rather than dividing by 1+z.

The absorption of the Lyman continuum from old stars tended to be overestimated leading to some “negative fluxes” for the Lyman continuum.

In rare circumstances requiring a specific distribution of redshifts the integration of the spectrum in some filters was not done correctly, inducing relative errors of ~10¯⁵-10¯⁶.

To compute the stellar spectrum of the young component, do not pass the full SFH with the old part set to 0. Rather, only pass the corresponding part of the SFH. This nearly doubles the computing speed of the stellar spectrum.

We do not store the time grid in the SED anymore given that we assume it starts at 0 Myr with steps of 1 Myr, we can easily reconstruct to save it if needed. It should save a little bit of memory and it should go a little bit faster.

In the output the sfh.age parameter would correspond to the input value minus 1. Now both values are consistent with one another.

For convenience the time grids start at 0. Howver the SSP grids start at 1. This  offset means that the oldest bin in an SFH is set to 0, for both the young and old components. Now rather than trying to interpolate the SFH time grid on the SSP time grid, we rely on the fact that the SFH time grid starts from 0, so it is easy to know which SSP to select (as many as the number of steps). Also adapt the sfh_buat08 module.

Make sure all the variables are saved in the FITS and not just the ones with are in mass_proportional_info. Bug seen by Yannick 2Eagle Eye' Roehlly.

The optionally saved spectra in the pdf_analysis and savefluxes modules were saved in the VO-table format. The most important downside is that it is very slow to write to, which proves to be a major bottleneck in the computing speed. To overcome this issue, we rather save the spectra using the FITS formation. Instead of having one file containing the spectra (including the various components) and the SFH in a single file, now we have one file for the spectra and one file for the SFH.

When reading a table from a file, convert all the integer columns to float
(except the 'id' column).  These columns are fluxes or error on fluxes and thus
should be treated as float even when they contain only integer.  This solves the
problem of trying to affect NaN value to an integer column.

Fixes #6

When reading a table from a file, convert all the integer columns to float
(except the 'id' column).  These columns are fluxes or error on fluxes and thus
should be treated as float even when they contain only integer.  This solves the
problem of trying to affect NaN value to an integer column.

Fixes #6

The name creation_modules is a bit vague. For more clarity and consistency we rather use sed_modules now