CPU-optimize the grid PDF interpolator code
Cache log(x), log(Q) between samplings -> log() still accounts for 15% of CPU. Caching grid index lookup, caching interpolation weights, encorage vectorization.
New Fortran API completeness
Extrapolation, interpolation, and alpha_s control, and metadata & uncertainty functions in Fortran.
Restructure for greater use of vectorisation, GPUs, MPI, etc.?
Requires very clear specification of use-cases from e.g. DISTRESS profiling, NLO Sherpa HPC experience, etc.
Add C++ SFINAE helpers for no-inheritance PDF interface definition
We don't want LHAPDF to become a code dependency just to define what a "PDF object" behaves like. Could using SFINAE template specialisation be a more hands-off route than inheritance? These would probably just be examples, so in doc rather than code?
Handle zipped data files (AB)
Prefer zipped single member data files rather than virtual filesystem access to the tarball? Can transparently read zipped files with LD_PRELOAD and zlibc: is that enough? Or embed a zip-stream and link against zlib?
Speed up interpolation with GPUs
Interpolation of PDFs seems like an potential use case for GPUs, since it's normal to query for all partons in the set at once: if we can load the relevant ipol anchors for all flavours onto the GPU then we can maybe get a substantial speedup. OpenMP did not particuarly help, from quick tests.
PDF flavor aliasing mechanism
e.g. allow anti-flavours to be identical without duplicating their grids in the data files or memory. How could we implement this?
Allow use of valence/sea etc. decompositions?
GridPDF may be inherited from to allow the returned values to be built from separate interpolations of component PDFs such as interpolated valence, sea, or difference PDFs that are combined to make the physical ones. The PDG ID code range for "generator specific" applications may be used, but we'll need to bear in mind that this will mean that the flavor ID list has different meanings and contents for internal and external purposes: maybe the "internal" PDG ID list needs to become part of the grid data header, or can the metadata be used?
Separate the x and Q2 inter/extrapolation?
Allow mix & match combinations. Would this simplify the code since the 1D interpolation methods are very simple and the 2D is built from them?
Make GridPDFs not read their info or data blocks until an xf value is requested?!
Super-laziness! But is there a real gain other than < 1 sec initialization speed?