[Hadstruct] Fwd: USQCD award notification

[David Richards]

Dear All,

Please see below our USQCD allocation.  Note we have Skylake time at FNAL as well, which might be useful for e.g. Tanjib.

Regards,
David

Begin forwarded message:

From: David Richards <dgr at jlab.org<mailto:dgr at jlab.org>>
Subject: USQCD award notification
Date: June 5, 2020 at 5:49:09 PM EDT
To: David Richards <dgr at jlab.org<mailto:dgr at jlab.org>>
Cc: Tanmoy Bhattacharya <tanmoy at lanl.gov<mailto:tanmoy at lanl.gov>>

Dear David,

The Scientific Program Committee (SPC) has finalized its recommendations for allocation awards on USQCD resources, and these recommendations have been accepted by the Executive Committee. We are pleased to inform you that your project entitled

“Parton Distribution Functions and Amplitudes of the Pseudoscalar Mesons and the Nucleon from Lattice QCD”

has been recommended for a USQCD computing award of 34M KNL-core hours and 500K RTX-GPU-hours at JLab, and 3M Skylake-core-hours at FNAL.

The SPC evaluated all of the proposals we received for scientific merit and relevance to the experimental programs funded by the DOE HEP and NP offices and to the scientific goals of the USQCD collaboration, and concluded that all proposals we received should be funded. Unfortunately, the total of the requested computing resources exceeds the available resources by factor of over 1.5.

As a result, allocation awards are generally smaller than what was requested in the proposals. The allocation award  listed above is the amount available for your project while balancing the needs of the entire collaboration. Please note that this allocation is subject to the continued availability of DOE funding for the LQCD hardware projects.

1) Run plan:
According to our records, your quarterly run plan foresees an approximate quarterly usage (as a percentage of your allocation) of:

Q1:  25%   Q2:  25%   Q3:  25%
Please specify any changes to your quarterly run plan, given that your allocation award differs from your request.

2) Storage:
The above compute allocation does not include your request for an allocation of storage resources. While the site managers will try to accommodate your disk storage request, please note that the requests for tape and disk storage at JLAB in particular exceed availability.

Please let us know if there are changes to your storage request given your allocation award.

3) Changes in usage or scope:
Please note that changes to the scope of your project or significant changes to your usage plans must be approved by the SPC. Please inform us by email of your plans for such changes at your earliest convenience, before you implement them.

4) Jeopardy policy:
Please note the USQCD jeopardy policy, which can be found in detail at https://www.usqcd.org/jeopardy.pdf. In brief, the jeopardy policy penalizes projects which are significantly behind on using their allocations on a monthly basis; no penalties are assessed in the first two months.  Conversely, allocation increases will be awarded after the end of the first four months to projects which are running at or above 110% of annual pace. The jeopardy policy (penalties and rewards) will not be applied to small projects (with allocations awards of less than 2.7 M Sky-core-hours).

5) Acknowledgements:
As stressed in the 2020 USQCD Call for Proposals, which can be found at https://www.dropbox.com/s/go62kpuijfcixub/USQCD_2020_CfP.pdf?dl=0, scientific publications describing calculations carried out with these awards should include the following sentence in the acknowledgments:

“Computations for this work were carried out in part on facilities of the USQCD Collaboration, which are funded by the Office of Science of the U.S. Department of Energy.”

Projects whose sole source of computing is USQCD should omit the phrase “in part’’.

Thank you again for your proposal to USQCD and please feel free to share this report with your coauthors.

Sincerely,

The USQCD Scientific Program Committee
Alexei Bazavov
Tanmoy Bhattacharya
Jack Laiho
Meifeng Lin
Keh-Fei Liu
Ethan Neil
David Richards


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/hadstruct/attachments/20200605/cf599685/attachment.html>