During a given run the set of wavelengths will always be the same. Then it means we do not have to recompute the shape of the attenuation curve each time. So we compute it only the first time reuse it later.

We use only a memory-based cache, so we get rid of the option. For the time being we keep the architecture in place.

Cleaned up version of the upper limit handling code written by Denis. Some further optimisations should be easy.

Add back the possibility to read the redshifts from the input file. To do so, do not give any redshift to the redshifting module. To avoid having too many redshifts, it is rounded to 2 decimals. This number can be changed in the analysis modules.

Rewrite the savefluxes module to make use of the new infrastructure. Though this implementation is not terribly scalable in case of some really large arrays. It should be enough for now anyway. Famous last words.

Centralise OUT_DIR in one location. One day we will have to have a second look at all these files and maybe rearrange them a little.

Move the backup dir function to the utils file common to all analysis modules so it can easily be used by all anlysis modules.

Optimise the computation of the fluxes. 1) consider only the SED section corresponding to the filter when computing the best grid. 2) As filters are already normalised, there is no need to divide my its integral to get the flux.

Get rid of the parameters array. Rather we generate parameters on-on-fly. This is done using a new class ParameterHandlers, which handles the generation of parameters from a given 1D index. While at it, also do away with global variables. This allows to spawn processes rather than fork them. Even if it takes a little time to do the spawn, this allows to solves some deadlocks with libraries which do not support being used on both sides of a forked process. Overall these modifications makes startup faster (no need to compute the cache cleaning parameters beforehand) and the generation speed is also a few percent faster when the number of models is large enough to compensate for the relatively slow spaning time.

Remove the SED parts dedicated to the lines as lines are perfectly generic now. No need to have this still hanging around.

If the code is to be run only on 1 core, then there is no need to fork a new process for that. As a side effect, it should at least allow people who have a multiprocessing code to run the code, even if only on one core.