University Large Allocation Request Preparation Instructions

Note: Requests for more than 400,000 core-hours on Cheyenne are considered large requests. We also offer small allocations for NSF awardees or for graduate students and postdocs. See the CISL University Allocations page for eligibility requirements and other information.

The next deadline for Large Allocation Requests is March 26, 2018.

More than 160 million Cheyenne system core-hours are allocated during each allocation cycle. See this section below to compare Cheyenne and Yellowstone core-hours.

Submitting a Large Allocation Request

Requesters must prepare and submit a Request Summary document and attach it to the Large Allocation Request form as a PDF file that is no larger than 5 MB.

The instructions below explain how to prepare the document. When your document is ready, submit your request via the Large Allocation Request form.

Request Summary Document

The Request Summary document must provide a self-contained description of your project and allocation request. The Request Summary may be no more than five (5) pages for Sections A–D below; Sections E–G should be included in the same uploaded document and are permitted an additional five (5) pages. The five-page limit is mandatory for all requests, and it is strongly recommended that you follow the template below to help the panel locate required information within your request.

The CHAP Allocation Review Criteria provide further detail on considerations the review panel uses in identifying meritorious requests. Recent successful requests are available at: Proposal Sample 1 and Proposal Sample 2.

A. Project Information

  • Title of Project
  • Title of NSF award (if different from title of project) supporting the computational experiments. Important: The NSF award must explicitly support the computational experiments being proposed. 
  • NSF award number. Please note that, due to high demand for resources, the CHAP no longer reviews requests for pending awards. Only submit your request after the NSF has awarded a grant for the research.
  • Name of Project Lead and his or her institution
  • Submission Date

B. Overview of Project 
The overview of the project should typically be less than half a page and include:

  • A summary of the science question and computational plan.
  • The relationship of the proposed work to atmospheric, oceanic and closely related sciences.
  • The explicit linkage between the NSF award and the computational experiments being proposed. This is especially important if the published NSF award abstract does not clearly describe the computational component of the work funded.

C. Science Objectives
The science objectives should be briefly described. This section should give sufficient information for understanding the computational plan in section D; it is not necessary to justify the science objectives as they must have already passed NSF review. 

Advice for preparing your request. "Brief" is the operative word for your science description. The panel is not judging your science, only trying to understand how and if your computational experiments (described in Section D) will help you find answers to your science questions. This section should be between 1/2 and 1 page long.

D. Computational Experiments and Resource Requirements
The bulk of the Request Summary should focus on Section D. Discuss your planned computational experiments and the resources needed to conduct the work in this section. Please cover the following topics; advice for how to best address each topic is included.

Computational Experiments

  • Numerical Approach. The numerical approach(es) or model should be described briefly. If a standard community model is being used, simply explain why it is appropriate for the scientific objectives and include a reference to a published description of the model or method. If a community model is being modified, include a description of the modification sufficient to explain any changes in the computational cost of the model and explain why modifications are necessary for the scientific objectives. For a non-standard or non-community model, the numerical description should briefly describe the approximations and other methods proposed to obtain valid solutions to the problem.
  • Computational Experiments. Describe the computational experiments needed to address the scientific objectives. The description should clearly indicate the number and type of experiments and how they relate to the objectives. Be sure to justify the model configuration choices that are relevant to the experiment such as domain, grid size, time steps, simulated time span, ensemble size, and parameter choices. References on the selection of the ensemble size are strongly encouraged.  Without an adequate justification of the model configuration, the panel may reduce or deny your computing request.
  • Code Performance. Include documentation on program code performance (for example, timings, performance monitoring tools); you may refer to a web page detailing code performance. Describe how flexible your code is in the number of processors it can use and why you may choose a particular number. The CHAP will evaluate the likelihood that a request can scale up its production runs based on this information. Information on the portability of the code to other platforms may also be very useful to the CHAP; requesters are strongly encouraged to provide this information about the code and the team’s knowledge/use of HPC systems similar to Cheyenne or Yellowstone.

Resource Requirements

Provide a table summarizing the resources required for each experimental configuration and the complete set of computational experiments. This must include the number of core-hours needed and the terabytes of data destined for HPSS if such storage is required. The table should be accompanied by a narrative that elaborates on how you arrived at the numbers in the table and describes any needs for project disk space or data analysis and visualization resources as detailed below. 

With the petascale systems’ ability to generate vast amounts of data, CISL allocation requests require users to consider their data workflows and to justify their long-term storage resource use. Requesters should note that the CHAP Allocation Review Criteria also apply to requests for allocated storage resources—that is, HPSS archive use and GLADE project spaces. The CHAP reviewers do not expect lengthy justifications; in most cases, a paragraph that demonstrates forethought commensurate with the scale of anticipated need will suffice. As requests approach a petabyte (or more!), longer justifications become appropriate. In addressing the criteria with respect to storage resources, justify the project’s need to retain the data to be stored, the project’s rationale for which data will be stored, and the project’s work plan for minimizing temporary data migration from disk to tape. While some statement of storage resource needs is expected in Section D, you may choose to provide details in Section E (Data Management Plan) to keep sections A-D within the five-page limit. Please note that temporary data that never move beyond scratch disk space need not be justified in the project's allocation request.

1. HPC. The table should give the core-hours per simulated year or appropriate time period and the total core-hours needed for each experimental configuration as well as the total core-hours for the request. Describe how you arrived at the number of core-hours for each proposed computational experiment.  If not provided elsewhere, details on how HPC resource requirements are estimated MUST be included to help reviewers evaluate whether the resources sought are justified and will be used efficiently.

For the early rounds of Cheyenne allocation requests, submitters can assume that one Yellowstone core-hour is equivalent to 0.82 Cheyenne core-hours. That is, estimate your computational need based on Yellowstone costs and multiply the total by 0.82 to arrive at your Cheyenne estimate.

2. HPSS archive. If your data storage in CISL’s HPSS archive during the life of this project will be less than 20 TB, stating “<20 TB” is sufficient and no detailed justification is required.  Otherwise, in the table showing core-hours include a column for the terabytes of HPSS space required for each experimental configuration and include the total terabytes stored. Projects with larger anticipated archival storage needs must include a description of how the estimate was calculated. If this request is a continuation of a previous request on the same project, please include a separate entry in the table for current data stored in HPSS.

Justifying HPSS requests. A successful justification for HPSS archive space would describe, for example, that the data have a meaningful purpose beyond initial post-processing steps; that variables or time steps not needed for planned analyses will be filtered out; and that HPC and analysis stages are interleaved where practical to minimize the need for temporary data to occupy tape. From the review criteria, it should be clear that a simple summation of all bytes generated by all proposed HPC runs may set an upper limit on HPSS needs but will not automatically constitute a sufficient justification in and of itself. Where appropriate, the justification should also describe how the project will reduce HPSS holdings in subsequent years (for example, a project may have a larger need during peak activity that will be reduced in out-years). As with computational justifications, the detail for storage justifications should grow commensurately with the project’s anticipated need.

3. Project file space. Large University projects can request dedicated long-term, large-scale disk space on the GLADE resource. The justification for GLADE project space should describe how the requested size was determined, how other available resources (such as /glade/scratch, /glade/p/work, and HPSS) will be used to minimize the size of the project space needed, why other storage options are not well suited for all of the project's needs, and how the requested project space will benefit or accelerate the project. Project spaces on GLADE must typically be for more than 50 TB. Smaller needs should be managed via scratch disk. Contact if you need help with increasing your team's scratch quotas. Again, projects do not need to request or justify access to scratch or work file spaces, which are available to all users.

Justifying project space requests. A successful justification for GLADE project space must demonstrate your understanding of the unique capability offered by project spaces and show that the project will also make efficient use of scratch space and work spaces when possible. As with HPSS requests, a simple summation of all bytes generated by all proposed HPC runs may set an upper limit on overall disk use but almost certainly will not constitute a sufficient justification for dedicated project space. A description of how a project will adapt its workflow to leverage project space (along with scratch and work space) and improve its overall efficiency will strengthen the justification. Where applicable, the justification may also describe how a project space allocation will permit a project to substantially reduce its use of HPSS. As with computational justifications, the detail for storage justifications should grow commensurately with the project’s anticipated need.

4. Data analysis and visualization. Describe any planned need for CISL’s Geyser and Caldera clusters to analyze or visualize your results. For standard interactive access to these clusters, the number of users expected to use the DAV clusters will serve as sufficient justification for up to 5,000 core-hours per user. Projects with more extensive plans for use of the clusters (for example, long-duration, multi-node batch runs) must justify their needs in a manner similar to their HPC requests.

Multi-Year Plan. While the CHAP makes an effort to award each project its full resource need, very large requests should consider providing a breakdown showing the projected use of core-hours and, if applicable, terabytes to be stored in HPSS during each year of the allocation. Tie this to the planned computational experiments completed or partially completed each year.

Special Requirements. Please specify any resource requirements that fall outside of the default environment limits, such as the need for longer job runtime limits, that may affect your ability to complete the proposed computational experiments.

Additional Supporting Information

Sections E through G together must be no more than an additional five pages.

E. Data Management Plan. Consistent with NSF’s new requirement that all proposals include a Data Management Plan, summarize your plan for managing the data resulting from this computational work. This section can be used to provide additional details or justification for the storage resource needs, to describe plans for sharing the project’s data, and to summarize any anticipated long-term storage needs beyond the lifetime of the supporting NSF award. A well-justified data management plan is critical because of the potential for large-scale projects to produce extensive data output.

F. Accomplishment Report. The Accomplishment Report should encompass computations performed using CISL resources by the PI or Project Lead. Clearly distinguish accomplishments on this CISL project (i.e., for prior CISL use associated with the same NSF award) and accomplishments from all past use of CISL resources. Related work performed on CISL resources by other members of a larger research group may be described, if relevant to this request. Briefly describe the calculations and scientific accomplishments that were completed. Include publications submitted or published that resulted from use of CISL resources. List graduate students who used these computational resources and indicate if these resources supported their thesis or dissertation research. If so, please include the thesis or dissertation title(s). 

G. References.  Please limit to those directly related to the proposed project and referenced in your Request Summary document.

H. Figures and captions. Optional. Figures may be embedded within the main body of the Request Summary; embedded figures count against the five-page limit. Figures and charts at the end of the Request Summary will not count against the five-page limit.