Skip to content

Make EKO into a separate resource

Emanuele Roberto Nocera requested to merge eko_as_resource into master

Created by: scarlehoff

Closes #2081 (closed)

It can be tested with theory_40001002

From an user perspective there should be no differences. When you only need the fktables / theory (i.e., for reports or fits, when doing check_theoryID) only the fktables will be downloaded. If the eko needs to be downloaded as well (only for evolution), then it will be downloaded into the same folder as the theory (done in this way so that all the theories that have the eko inside work just the same).

There's a separate check_eko(thid) which is used by evolven3fit and returns the path to the eko.tar of the theory, checking first the theory.

At the moment the ekos range between the 1.5 and 3.5 GB while the whole set of fktables used for 4.0 is about 600 MB so this can have a huge impact e.g. when doing reports in your laptop when the PDF has been generated elsewhere.

Merge request reports