[com4FlowPy]: Selective calculation of Model Output Rasters

[ahuber-bfw]

We now have the outputFiles option in [PATHS] in the (local_)com4FlowPyCfg.ini, but up to now only use it in com4FlowPy.py -> mergeAndWriteResults() to select which result-Rasters are finally written to disk as .tif or .asc files.

However, regardless of the options provided in outputFiles we still do all the calculations for all possible result rasters (i.e. we calculate routFluxSum, depFluxSum and everything else, even if we don't write it to disk later).

• Potentially we can save some CPU-time/RAM/HD-Space by only initializing and calculating the result arrays, that are specified in [PATHS] 'outputFiles' option -- e.g. by passing the option to calculation() and return None for all the arrays, that are not specified in the .ini

This will be increasingly important (1) if we plan to introduce additional output rasters in the future and (2) for any regional scale application

[ahuber-bfw]

moved this point from issue #1062 to this separate issue

[PaulaSp3]

in flowCore.py in the function run() the part where the outputs are computed and saved does need much CPU-time (when the simulation needs 58 s, this part needs 0.2 s), so with a modification we can't save CPU-time significantly

[PaulaSp3]

we could think about selecting the methods of a cell that are executed depending on the output rasters (e.g. the execution of calc_fp_travelangle is only necessary for the raster fp_travelAngle)