Log a hash of every fktable upon vp-setupfit

[scarlehoff]

[felixhekhorn]

related to NNPDF/pineko#225

[jekoorn]

I am looking into this today and have a question
My assumption is that we want to save a key that looks something like <theoryid>_<fktable_name>_<hash> where the hash is constructed from the theory metadata used to generate the fk table, or the grid metadata as was done in NNPDF/pineko#247. But from just the FK table, this metadata key cannot be accessed unless you are loading every fk table, correct? So what do I make a hash of?

[scarlehoff]

During vp-setupfit you have access to the fktables that go into the fit. That means you can access its metadata of the FkTable (given NNPDF/pineko#247, we could simply propagate that information to vp-setupfit for instance).

[jekoorn]

perfect. then I will do that

[jekoorn]

just to clarify, do we mean here the metadata that is in the check_commondata.metadata? Or the actual metadata that is in the pineappl grid itself? pineappl read --show <fk>.pineappl.lz4 Because the latter would require one to have pineappl installed before doing vp-setupfit, which can induce other complications. But that is the only 'real' metadata. Or is the hash of this exact information going to be stored in the check_commondata.metadata? (this is not fully clear to me from https://github.com/NNPDF/pineko/pull/247/changes)

[scarlehoff]

The metadata inside the grid fktable.
pineappl needs to be installed for the fit to work because otherwise the fktables cannot be loaded (you can access the metadata also programatically).

[jekoorn]

ah lol of course, thanks!