Skip to content

Separate `eko.tar` and fastkernel tables in the server

Created by: scarlehoff

Given that the tables for our current NNLO theory are about ~700 MB and the eko for the postfit evolution instead ~1 GB, I think it would be very convenient to separate both.

I think this would bring only advantages:

  1. ekos are not needed for validphys, so no need to have them in your computer to make plots
  2. If you need to copy stuff to your nodes when doing a fit, you halve the size of what you are copying for the fit itself.
  3. We have many theories without an eko, where the eko is actually shared (e.g. theory 200, 400, 700, 708, 600, 40000000). Making it a separate entity means you can have just one 1GB object in the server instead of many.

I would not change anything of the architecture once they are downloaded since they get used in the same manner. I would just create another resource which then gets downloaded to the right theory id and evolven3fit will depend on it.