Check available ekos

[alecandido]

At this point we start having a few ekos computed, and as we found out with @felixhekhorn computing one of them is quite an expensive task (at least for development, since it's blocking us).

Moreover, I believe that a few eko can really be recycled, e.g. I think that most of LHC pineapplgrids will have the same x_grid and Q2_grid.

However it is a bit annoying to check which one of the available ekos is the correct one, but we have all the tools required to automatize the process.

Proposal

Let's make a trivial function (and maybe provide a subcommand) that given a folder explore the files inside (or even all the files in the tree) for ekos, and output all the compatible ones that has been found.

Note

This is a step forward towards the toolchain automation and assets management. I'm considering that maybe we'll simply need to progressively improve tasks that we're doing manually at the moment, instead of projecting an actual automation pipeline all-together.

[felixhekhorn]

Should be doable ...

• split the check function maybe into a new module
• improve https://github.com/N3PDF/pineko/blob/6fe8bb31a7d5e513c2725f5009b76734dfcfd17e/src/pineko/__init__.py#L26
• this is slightly related to the idea of generating a single EKO

[alecandido]

• this is slightly related to the idea of generating a single EKO

Indeed, that is still possible, but I considered that we'll always have multiple ekos, because we generate a given one at fixed time, than we say "but we would like to have one with these other specs", and then you start getting the second and so on...

Looking for a single one it's not that bad, it will reduce the number of operators in any case, but still they will sum up at some point.

[alecandido]

I guess this outdated enough, and superseded by #12 in any case. Is it correct @felixhekhorn?

[felixhekhorn]

• actually this functionality was implemented in fkutils: https://github.com/NNPDF/fktables/blob/8ce3969fe05316c33780d5227981c712982bb36c/fkutils/builder.py#L191
• however, I did not port it here - again relying on Memory saving output eko#96