How do I renew a TeraGrid allocation?

Renewing a Startup allocation

Note: Although renewals for Startup allocations are permitted with appropriate justification, a principal investigator (PI) should consider requesting a Research allocation to continue research on the TeraGrid. In most cases, Startup allocations will not be renewed.

To renew a Startup TeraGrid allocation (i.e., request to continue research activities after an allocation has ended), the principal investigator (PI) can use the Partnership Online Proposal System (POPS). On the Submission Home page, under "Request Action", click Renewal, and then fill out and submit the resulting form.

For the renewal form, you can use much of the information you provided for your original allocation request. Additionally, you should add a statement that summarizes what your project has accomplished so far, and another stating what you intend to accomplish with the renewal.

Note: Files stored in archival storage are kept for one year after the expiration of an allocation. You can access archived files as soon as your renewal application is approved.

Renewing a Research allocation

To renew a Research allocation, submit your renewal request to the Resource Allocations Committee for the same month you submitted your original request. For submission deadlines, see On the TeraGrid, what types of allocations are available?

Other options for continuing research

You can request more calendar time to complete your research (see How do I request additional calendar time for my TeraGrid allocation?), or you can request supplemental service units (SUs) for an allocation (see How do I request supplemental service units for a TeraGrid allocation?).

For multi-year allocations, the PI is required to submit a yearly progress report. For more, see the NSF Resource Allocations Policies in the TeraGrid User Support documentation.

This document was developed with support from the National Science Foundation (NSF) under Grant No. 0503697 to the University of Chicago and subcontracted to Indiana University. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF.

Comments/Questions/Corrections