Cache LAI Max Look Up Tables

[philippeverley]

To the question: do LUTs change often ? Isabelle answered:

the only exception is LookUpLAImax (initialise in InitialiseLookUpLAImax which is called at the end of the InitialiseLookUpTables), which depend on the number and idenitity of species provided in the input species file.
Apart for this one, the other should not change, unless we, at some point decide to try applying TROLL in other biomes... but not currently.

Originally posted by @IsabelleMarechaux in #19

The generate-lut-header should be able to read the input parameters before generating the lut.hpp header file if we also want to cache LAI max LUT.

[sylvainschmitt]

I do not get this suggestion. For me the compilation is only done once to get a generic TROLL model that can be used in multiple simulations with different input parameters, especially species here. Or did I miss something?

[philippeverley]

Indeed, the compile time approach is not going to work for the LUTs tables depending on user defined parameters. For such tables I should implement runtime caching approach.

And since we want to keep things simple, I may give up on the compile-time approach, especially since it would be practical that the size of the LUTs are set and check programmatically, depending on the input parameters.

I'll update the related issues 👍