Motivation: As soon as you install eko, you'll need to wait a while on first import. This is needed for the eko application, but unnecessary and completely counter-intuitive for the eko library.
At the moment importing eko means importing eko.runner, and also eko.output.
Then, as it makes sense, importing runner means importing everything (see dependency graph).
How to improve
From my point of view:
- there is no way to improve on
eko.runner: it's quite intuitive that uses all (or almost all) of the library
- but I'd say that we should not wait on the compilation of all the anomalous dimensions and so on, if you only need interpolation or strong coupling (or even masses, basis rotation, ...)
In particular, having to wait every time you install anew it's already a bit unpleasant in yadism, but much more in banana or runcards.
In practice
I'd say we just need to:
Motivation: As soon as you install
eko, you'll need to wait a while on first import. This is needed for theekoapplication, but unnecessary and completely counter-intuitive for theekolibrary.At the moment importing
ekomeans importingeko.runner, and alsoeko.output.Then, as it makes sense, importing runner means importing everything (see dependency graph).
How to improve
From my point of view:
eko.runner: it's quite intuitive that uses all (or almost all) of the libraryIn particular, having to wait every time you install anew it's already a bit unpleasant in
yadism, but much more inbananaorruncards.In practice
I'd say we just need to:
run_dglapinsideeko.runner__init__.pyjust for the version (no need for a separate module)