MadGraph tarballs on cvmfs

[kpedro88]

Rather than downloading the MG5 source tarball from the web every time:

genproductions/bin/MadGraph5_aMCatNLO/gridpack_generation.sh

Line 183 in d0d03f8

wget --no-check-certificate ${MGSOURCE}

genproductions/bin/MadGraph5_aMCatNLO/gridpack_generation.sh

Line 141 in d0d03f8

MGSOURCE=https://cms-project-generators.web.cern.ch/cms-project-generators/$MGTAR

,
which leaves the possibility that the job will fail because of a transient connectivity issue,
why not host the tarballs for the MG versions that we use on cvmfs?

[agrohsje]

Hi Kevin, in central production we had the same issue with cvmfs. Jobs are failing because gridpacks are not accessible on cvmfs. Did you encounter problems with the web? Me neither, despite producing hundreds of gridpacks.

[kpedro88]

Did you encounter problems with the web?

Yes, I had gridpack creation jobs fail yesterday because the wget call (noted above) did not succeed.

[sihyunjeon]

@agrohsje i agree with this change though, since the web is at the stage where it is impossible to clean up at this point. why don't we clean things up by minimally changing the logics? + central production not finding gridpacks from cvmfs would likely be site issue, no? local running gridpacks seem safe from this matter

[agrohsje]

I think there is nothing wrong with moving. It is just a question of priorities and other requests. If someone has time to fix, no problem. It is also not a lot of work, but too often not a lot of work is a lot of work.