GitLab

Move the SED creation modules to pcigale.creation_modules to be more
consistent with the analysis module location.

The quasar contributions must contain the name of the attenuation used
because using several attenuations will lead to a key error when adding
the second quasar contribution.

Class name should be CamelCased, arguments and variable inside functions
should be lower case.

There's no need to put my name in authors when I did not do anything.

Use the new post-fixed key names for contributions.

Manage the bugs / todo with bugs-everywhere [1]. It's less readable but
can export fancy HTML lists.

[1] http://www.bugseverywhere.org/

astropy v0.3 cosmology methods now returns quantities. We keep only the
value to avoid problems in numpy computations.

A table containing the parameters of the best SED for each observation,
as well as the values for the analysed variables for these best SEDs, is
saved.

In the sfhfromfile module, make the SFH normalisation to 1 solar mass
produced at the given age optional. When using pcigale to simulate SEDs,
one may not want this normalisation to happend.

Such SEDs should not be stored in the database (but SEDs made using
sfhfromfile should not anyway be stored in the database). We will have
to make the SED storing optional in the warehouse.

Add a method to generate SED corresponding to a list of modules and
parameter sets, one at a time to the warehouse.

Make the cosmology changeable by importing the desired cosmology in
pcigale.sed.cosmology. If one day the users need to change the cosmology
more easily, make it a configuration parameter of pcigale.

Also warn the user when an output was renamed.

For redshift and analysis module, we don't need to evaluate each
parameter as an array as we don't expect arrays here (and that force us
to use parameter[0] to get the value).

Configobj return strings, to evaluate the booleans on their "string"
content.

Instead of prefixing the key in the SED with the module name, we postfix
them with the same postfix as the module name if any. This makes easier
to inter-change modules adding the same information (for instance
attenuation modules adding the attenuation value).
That implies that when using several modules adding the same
information, one must postfix the name of each.

Instead of prefixing the key in the SED with the module name, we postfix
them with the same postfix as the module name if any. This makes easier
to inter-change modules adding the same information (for instance
attenuation modules adding the attenuation value).
That implies that when using several modules adding the same
information, one must postfix the name of each.

When one value for a parameter is a list (for instance the list of
attenuation keys for re-emission modules) we had to use the "eval [["a",
"b"]]" notation. Convert these module to use a single string with items
separated by a & ("a & b").

WARNING we must still change the way parameters are evaluated not to
return everytime a list.

So that the configuration files and the serialized data have a logical
order.

Use sphinx with astropy _templates (it would be great to make pcigale an
affilated package).
Make the skeleton of the documentation.
Start to write pcigale script usage.

We follow the astropy version number scheme VERSION-RELEASE.