Rotate FK-tables instead of EKOs

Open
#183 15 comments 0 reactions 0 assignees View on GitHub

@Radonirinaunimi is already working on this.

Since Jun 22, 2025.

  • #227 by @Radonirinaunimi — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Read src/pineko/evolve.py around the linked lines 282–286 and 313–320, then inspect the PineAPPL grid rotation change linked in the issue. The issue proposes evolving unrotated EKOs and rotating the resulting FK-tables; check the existing evolution tests and add coverage for that flow. The linked pull request #227 is open, so review its status before starting.

Written by the indexing model from the issue text.

Description

good first issue refactor

There's another big optimization potential to speed up the generation of FK-tables. Currently, I believe, pineko works the following way (correct me if I'm wrong):

  1. we store flavour-basis to flavour-basis EKOs for all Q2 slices, but always for the standard 50 x-node points. The biggest EKO that we have, ATLAS_1JET_8TEV_R06, is 2.4 GB.
  2. Next, we reinterpolate the EKO to match the x-grid points actually used in the grid. For ATLAS_1JET_8TEV_R06 this blows up the size of the EKO to 22 GB.
  3. Finally, we rotate the EKO, such that the resulting FK-tables are in the evolution basis. This further increases the size, resulting in whopping 45 GB.

But thanks to some developments on PineAPPL's side, we can now perform a rotation at the level of grids (and therefore also FK-tables). So I suggest that

  • we perform the evolution using the unrotated EKOs, which has the advantage that the EKOs are much smaller, and finally
  • rotate the evolved FK-tables from the flavour-basis to the evolution basis.

The evolution in the flavour basis is much faster, it's roughly the quotient of the size of the EKOs. For ATLAS_1JET_8TEV_R06 it's roughly twice as fast (45 GB / 22 GB). With the added benefit that we need less disk space, of course.

Practically speaking, the changes on pineko's side should be minimal. We probably have to delete the following lines:
https://github.com/NNPDF/pineko/blob/9f8b03ce9132c91866a160e4396998abaca843c2/src/pineko/evolve.py#L282-L286
and instead add the rotation after the evolution:
https://github.com/NNPDF/pineko/blob/9f8b03ce9132c91866a160e4396998abaca843c2/src/pineko/evolve.py#L313-L320

Dominant language
Python
Stars
2
Forks
0
Avg merge
10d 34m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NNPDF/pineko

All issues in NNPDF/pineko

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.