Save the hash and theory directory of the grid

[scarlehoff]

One common problem that we have is that from one grid folder we can generate many different theories depending on the evolution.
Was it theory 4001? 4100000? 4005? Was it the current version of the grids or three bugs ago?

I think we should save a key when creating the fktable which saves 1) the hash of the grid 2) the theory number, something along the lines of grid_files: 4001-<name>-<hash> (plural grid files for DIS fktables). This key is not supposed to be used by anyone ever, hopefully with the information in the theory card we should be able to reproduce the grid (where it was coming from, which settings, etc) but if everything fails then with this information one can go to the server and browse the long list of hashes until the right grid is found.

[felixhekhorn]

• not sure about the theory id, because that is straight duplication with the theory card
• removing the theory id I would then suggest: grid_files -> name1: hash1\nname2: hash2

[felixhekhorn]

what does the "theory directory" in the title refer to? hash is good on it's own, no?

[scarlehoff]

Theory directory in order to know which folder was used for the grids.
For instance, for theory 700/708/40_000_000 and many of the variants the grids of theory 4001 are used.

Hopefully this distinction will happen less in the future but given that is just a few characters (and we have already seen the problem) I think it is worth it to include it.

[felixhekhorn]

I see - you mean the true underlying grid? i.e. in practice something like Path.resolve?

[scarlehoff]

Yes! As I said, it is meant as a last resort, so we want to have as much raw information as possible.