Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove HepData raw tables from the repository #2228

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

Radonirinaunimi
Copy link
Member

@Radonirinaunimi Radonirinaunimi commented Nov 27, 2024

Addresses #2199 by removing the HepData raw tables from the repository. This adds a module that downloads the raw tables from the server and from the HepData when the commondata need to be regenerated.

TO DO:

  • download the raw tables from the NNPDF server
  • propagate across all the datasets
    • fixed-target DIS
    • collider DIS
    • fixed-target inclusive DY
    • Tevatron inclusive DY
    • ATLAS inclusive DY
    • ATLAS DY+jet
    • ATLAS single-inclusive jet and dijet production
    • ATLAS top pair production
    • ATLAS single top production
    • ATLAS pormpt photon production
    • CMS inclusive DY
    • CMS DY+jet
    • CMS single-inclusive jet and dijet production
    • CMS top pair production
    • CMS single top production
    • LHCb inclusive DY
  • fail commondata tests only when kinematics.yaml, data.yaml, and uncertainties*.yaml are modified

@RoyStegeman
Copy link
Member

RoyStegeman commented Nov 27, 2024

I understood @scarlehoff was going to purge the rawdata (that already got merged, which shouldn't be much) from the history entirely, not just remove it from the repo but keep it in the history?

@scarlehoff
Copy link
Member

the raw tables from the server and from the HepData when the commondata need to be regenerated.

And, after regeneration, the blob of data in the server gets updated.

I understood @scarlehoff was going to purge the rawdata (that already got merged, which shouldn't be much) from the history entirely, not just remove it from the repo but keep it in the history?

First we need the infrastructure so that it is truly not needed, then we change the history of the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants