Skip to main content

Call for Early Allocations to High Performance Computing Resources

Already have an allocation and need help? Submit a ticket.

Submit a ticket

National AI Research Resource (NAIRR) Pilot

Resource Requests to Advance AI Research and Education

In the NAIRR Pilot, the US National Science Foundation (NSF), the US Department of Energy (DOE), and numerous private and non-profit sector partners are providing an opportunity for the research community to request access to a set of computing, model, platform and educational resources for projects related to advancing AI research and education. This call for proposals will be open from May 6, 2024, until the end of the NAIRR Pilot program or until all resources have been committed to projects.

Proposals will be reviewed on an ongoing monthly cycle. Requests submitted by the 15th of the month will be reviewed and have their outcome decided by the end of the month. Projects will be awarded for twelve (12) months duration.

Eligibility

This call is open to meritorious proposals by US-based researchers and educators from US-based institutions including academic institutions, non-profits, federal agencies or federally funded R&D centers, state, local, or tribal agencies, startups and small businesses with federal grants. However, the individual resources available via this call may have differing eligibility rules. Assignment of supported proposals will be guided by these constraints.

Note that the email address you provide must be your institutional email. Requests providing personal email addresses such as “.gmail.com” addresses will not be considered.

Focus Areas

This call for allocation proposals encompasses projects covering any of the cross-cutting or domain focus areas for the NAIRR Pilot.

Cross-cutting focus areas:

  • Advancing AI methods that enable scientific discovery.
  • Creating open-source foundation models for specific applications.
  • Using large-scale models to explore complex datasets interactively.
  • Advancing approaches for integrating simulations and AI.
  • Using experimental data from sensors, detectors, or other edge instruments.
  • Empowering use of scientific data by other stakeholders and the public.
  • Training and educating a cohort of scholars in AI technologies and their responsible use.

Domain specific focus areas:

  • Accelerating societally-relevant research on AI safety, reliability, security, and privacy.
  • Empowering advances in cancer treatment and individual health outcomes.
  • Supporting resilience and optimization of agricultural, water, and grid infrastructure.
  • Improving design, control, and quality of advanced manufacturing systems.
  • Addressing earth, environmental, and climate challenges via integration of diverse data and models.

Other projects that align with the broader objectives of the NAIRR Pilot, as well as projects in other areas of AI research and applications, may secondarily be considered for allocation.

Available Resources

The set of resources available through the NAIRR Pilot has been expanded to include additional resources funded by federal agencies as well as resources contributed by private and non-profit sector partners. Over time, we expect new resources will be added to the NAIRR Pilot, and some resources may be removed from the pilot as their available contributions are committed to projects.

Researchers are strongly encouraged to review the most up-to-date list of resources, which will always be available via the NAIRR Pilot Resource Catalog.

Note that some resources contributed to the NAIRR Pilot, such as pre-trained models,datasets, and relevant platforms, may be accessible to researchers and educators without the need for a proposal. For details, see this full list of pilot resources.

Expectations of Projects

All persons submitting proposals should note the following parameters and expectations:

  • Because of the strong public component of the NAIRR, all project results must be open and publishable. Teams who receive NAIRR Pilot access are expected to publish their results in the open scientific literature or otherwise disseminate publically, and to make all project products publically available, to the extent possible. The NAIRR Pilot wishes to catalyze open, pre-competitive results that can impact the future of the NAIRR.
  • If a PI believes that a project will result in commercializable intellectual property (IP), the PI should discuss directly with the assigned resource provider to determine if commercialized IP requirements can be accommodated.
  • NAIRR Pilot projects are intended to be completed within twelve (12) months. Projects with longer-term timelines should contact help@allocations.nairrpilot.org to be referred to existing proposal and allocation opportunities.
  • All supported projects will have the name of the principal investigator (PI), their affiliation, the project title, and project abstract posted on the NAIRR Pilot website.
  • All project PIs will be added to a NAIRR Pilot mailing list to foster a community of NAIRR Pilot researchers.
  • Project PIs are expected to provide brief (2–3 paragraphs) project updates 1 month and 6 months into the project, and a final report (three pages) upon project completion.

Proposal Instructions

Proposals require completing a form and uploading a three-page PDF proposal. See proposal preparation instructions and expectations.

As part of the process of completing the form, researchers should include information about funding grants directly supporting,related, or adjacent to the proposed research. Proposals for research activities without merit-reviewed support will be accepted, but will be subject to additional review regarding the scientific merit of the work.

Proposal Evaluation

Proposals will be accepted starting May 6, 2024, through the end of the NAIRR Pilot program or until all available resources have been committed to projects.

All proposals will be evaluated by independent peer reviewers for scientific and technical appropriateness and feasibility. Proposals will be evaluated on the following criteria:

  • Alignment with the NAIRR Pilot focus areas;
  • Project readiness and potential for near-term progress;
  • Feasibility of the technical approach;
  • Need for the computing, support, or other resources available in the NAIRR Pilot;
  • Knowledge and experience of the proposing team related to the proposed work; and
  • Estimated resource requirements and justification

After completion of the independent review process, proposals will be matched to the appropriate resource through matching committees for each resource category (such as agency supported advanced computing platforms, cloud computing resources and other private sector hosted platforms, API access to models, and software/platforms/collaborations). All partners, including non-governmental partners will have a representative on the corresponding matching committee to assure the proposal is a strong match for their contributed resource and will be able to see reviews of proposals in their resource category. All reviewers and members of matching committees will be subject to a confidentiality agreement that prohibits sharing review and/or proposal content. Note, if a researcher does not wish their proposal to be viewed by a non-governmental partner, they should choose only government agency resources.

Proposal Submission and Review

All proposals must be submitted electronically via the NAIRR Pilot submission site.

Proposals will be reviewed on an ongoing monthly cycle. Typically, requests submitted by the 15th of the month will be reviewed and have their outcome decided by the end of the following month. Projects will be awarded for twelve (12) months duration.

Start your Submission

Questions

Questions about this call and allocations can be directed to: help@allocations.nairrpilot.org.

Debug Console

Close6 MBRequestSessionTimelineDatabase22Events25
$_GET
Array( ) Array(

)
$_POST
Array( ) Array(

)
$_COOKIE
Array( ) Array(

)
$_SERVER
Array( TEMP => /var/www/tmp, TMPDIR => /var/www/tmp, TMP => /var/www/tmp, PATH => /usr/lo... Array(
TEMP => /var/www/tmp,
TMPDIR => /var/www/tmp,
TMP => /var/www/tmp,
PATH => /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin,
USER => apache,
HOME => /var/www,
FCGI_ROLE => RESPONDER,
REDIRECT_HTTP_AUTHORIZATION => ,
REDIRECT_UNIQUE_ID => ZoRMx60BAnBvjO1IJXLGlwAAAAo,
REDIRECT_SCRIPT_URL => /opportunities/allocations,
REDIRECT_SCRIPT_URI => https://shunko.aws.hubzero.org/opportunities/allocations,
REDIRECT_HTTPS => on,
REDIRECT_SSL_TLS_SNI => shunko.aws.hubzero.org,
REDIRECT_STATUS => 200,
HTTP_AUTHORIZATION => ,
UNIQUE_ID => ZoRMx60BAnBvjO1IJXLGlwAAAAo,
SCRIPT_URL => /opportunities/allocations,
SCRIPT_URI => https://shunko.aws.hubzero.org/opportunities/allocations,
HTTPS => on,
SSL_TLS_SNI => shunko.aws.hubzero.org,
HTTP_ACCEPT => */*,
HTTP_USER_AGENT => Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com),
HTTP_ACCEPT_ENCODING => gzip, br, zstd, deflate,
HTTP_HOST => shunko.aws.hubzero.org,
SERVER_SIGNATURE => ,
SERVER_SOFTWARE => Apache,
SERVER_NAME => shunko.aws.hubzero.org,
SERVER_ADDR => 10.68.128.8,
SERVER_PORT => 443,
REMOTE_ADDR => 3.23.103.140,
DOCUMENT_ROOT => /var/www/shunko,
REQUEST_SCHEME => https,
CONTEXT_PREFIX => ,
CONTEXT_DOCUMENT_ROOT => /var/www/shunko,
SERVER_ADMIN => root@localhost,
SCRIPT_FILENAME => /var/www/shunko/index.php,
REMOTE_PORT => 23650,
REDIRECT_URL => /opportunities/allocations,
GATEWAY_INTERFACE => CGI/1.1,
SERVER_PROTOCOL => HTTP/1.1,
REQUEST_METHOD => GET,
QUERY_STRING => ,
REQUEST_URI => /opportunities/allocations,
SCRIPT_NAME => /index.php,
PHP_SELF => /index.php,
REQUEST_TIME_FLOAT => 1719946439.106,
REQUEST_TIME => 1719946439
)
separator ⇒ .
orderBy ⇒ id
orderDir ⇒ asc
1 ⇒ registerIP
2 ⇒ access
always ⇒
renew ⇒
tracker.sid ⇒ 3a6b685acaa85cd4edd95c887dfc7ac0
tracker.ssid ⇒ 3a6b685acaa85cd4edd95c887dfc7ac0
tracker.rsid ⇒ 3a6b685acaa85cd4edd95c887dfc7ac0
  • site 0.037 seconds (+0.037); 3.50 MB (+3.500) - afterInitialise
  • site 0.062 seconds (+0.025); 4.25 MB (+0.750) - afterRoute
  • site 0.099 seconds (+0.037); 5.50 MB (+1.250) - afterDispatch
  • site 0.111 seconds (+0.012); 5.50 MB (0.000) - beforeRenderModule mod_search (Search)
  • site 0.115 seconds (+0.004); 5.75 MB (+0.250) - afterRenderModule mod_search (Search)
  • site 0.115 seconds (+0.001); 5.75 MB (0.000) - beforeRenderModule mod_menu (Main Menu)
  • site 0.120 seconds (+0.005); 5.75 MB (0.000) - afterRenderModule mod_menu (Main Menu)
  • site 0.124 seconds (+0.004); 5.75 MB (0.000) - onAfterRender
  • site 0.128 seconds (+0.004); 5.75 MB (0.000) - sessionStore
6 MB

22 Queries Logged: 0.014984369277954 seconds

  1. SELECT data
      FROM `jos_session`
      WHERE `session_id` = '3feba14f223598b5dbcfa056951a167a'
  2. DELETE
      FROM `jos_session`
      WHERE `session_id` = '3feba14f223598b5dbcfa056951a167a'
  3. SELECT data
      FROM `jos_session`
      WHERE `session_id` = '3a6b685acaa85cd4edd95c887dfc7ac0'
  4. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_languages'
  5. SELECT session_id
      FROM `jos_session`
      WHERE `session_id` = '3a6b685acaa85cd4edd95c887dfc7ac0'
      LIMIT 1
  6. INSERT INTO `jos_session` (`session_id`,`client_id`,`time`,`ip`)
      VALUES ('3a6b685acaa85cd4edd95c887dfc7ac0','0','1719946439','3.23.103.140')
  7. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_members'
  8. SELECT b.id, b.title
      FROM `jos_usergroups` AS `a`
      LEFT JOIN jos_usergroups AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`id` = '1'
  9. SELECT *
      FROM `jos_viewlevels`
  10. SELECT folder AS type,element AS name,protected,params
      FROM `jos_extensions`
      WHERE `enabled` >= '1'
      AND `type` = 'plugin'
      AND `state` >= '0'
      AND `access` IN ('1','1','4')
      ORDER BY `ordering` ASC
  11. SELECT m.id,m.menutype,m.title,m.alias,m.note,m.path AS route,m.link,m.type,m.level,m.language,m.browserNav,m.access,m.params,m.home,m.img,m.template_style_id,m.component_id,m.parent_id,e.element AS component
      FROM `jos_menu` AS `m`
      LEFT JOIN jos_extensions AS e
      ON e.extension_id = m.component_id
      WHERE `m`.`published` = '1'
      AND `m`.`parent_id` > '0'
      AND `m`.`client_id` = '0'
      ORDER BY `m`.`lft` ASC
  12. SELECT jos_template_styles.id,jos_template_styles.home,jos_template_styles.template,jos_template_styles.params,jos_extensions.protected
      FROM `jos_template_styles`
      INNER JOIN jos_extensions
      ON jos_extensions.element = jos_template_styles.template
      WHERE `jos_template_styles`.`client_id` = '0'
      AND `jos_extensions`.`enabled` = '1'
      AND `jos_extensions`.`type` = 'template'
      AND jos_extensions.`client_id` = `jos_template_styles`.`client_id`
      ORDER BY `home` DESC
  13. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_content'
  14. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_categories'
  15. SELECT a.rules
      FROM `jos_assets` AS `a`
      WHERE `a`.`id` = '1'
      GROUP BY a.id, a.rules, a.lft
  16. SELECT b.rules
      FROM `jos_assets` AS `a`
      LEFT JOIN jos_assets AS b
      ON b.lft <= a.lft
      AND b.rgt >= a.rgt
      WHERE `a`.`name` = 'com_content'
      GROUP BY b.id, b.rules, b.lft
      ORDER BY `b`.`lft` ASC
  17. SELECT a.*,a.id,a.asset_id,a.title,a.alias,a.title_alias,a.introtext,a.fulltext,
      CASE WHEN badcats.id IS NULL THEN a.state ELSE 0 END AS state,a.mask,a.catid,a.created,a.created_by,a.created_by_alias,
      CASE WHEN a.modified IS NULL THEN a.created ELSE a.modified END AS modified,a.modified_by,a.checked_out,a.checked_out_time,a.publish_up,a.publish_down,a.images,a.urls,a.attribs,a.version,a.parentid,a.ordering,a.metakey,a.metadesc,a.access,a.hits,a.metadata,a.featured,a.language,a.xreference,c.title AS category_title,c.alias AS category_alias,c.access AS category_access,u.name AS author,parent.title AS parent_title,parent.id AS parent_id,parent.path AS parent_route,parent.alias AS parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating,v.rating_count AS rating_count
      FROM `jos_content` AS `a`
      LEFT JOIN jos_categories AS c
      ON c.id = a.catid
      LEFT JOIN jos_users AS u
      ON u.id = a.created_by
      LEFT JOIN jos_categories as parent
      ON parent.id = c.parent_id
      LEFT JOIN jos_content_rating AS v
      ON a.id = v.content_id
      LEFT
      OUTER JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published <= 0
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      WHERE `a`.`id` = '39'
      AND (`a`.`publish_up` IS NULL OR `a`.`publish_up` <= '2024-07-02 18:53:59' )
      AND (`a`.`publish_down` IS NULL OR `a`.`publish_down` >= '2024-07-02 18:53:59' )
      AND `a`.`state` IN ('1','2')
  18. SELECT c.*,
      CASE WHEN CHAR_LENGTH(c.alias) THEN CONCAT_WS(':', c.id, c.alias) ELSE c.id END as slug
      FROM `jos_categories` AS `c`
      LEFT JOIN jos_categories AS s
      ON (s.lft <= c.lft
      AND s.rgt >= c.rgt) OR (s.lft > c.lft
      AND s.rgt < c.rgt)
      LEFT JOIN (SELECT cat.id as id
      FROM jos_categories AS cat JOIN jos_categories AS parent
      ON cat.lft BETWEEN parent.lft
      AND parent.rgt
      WHERE parent.extension = 'com_content'
      AND parent.published != 1
      GROUP BY cat.id) AS badcats
      ON badcats.id = c.id
      WHERE (`c`.`extension` = 'com_content' OR `c`.`extension` = 'system' )
      AND `c`.`access` IN ('1','1','4')
      AND `c`.`published` = '1'
      AND `s`.`id` = '2'
      AND badcats.id is null
      GROUP BY c.id,c.asset_id,c.access,c.alias,c.checked_out,c.checked_out_time,c.created_time,c.created_user_id,c.description,c.extension,c.hits,c.language,c.level,c.lft,c.metadata,c.metadesc,c.metakey,c.modified_time,c.note,c.params,c.parent_id,c.path,c.published,c.rgt,c.title,c.modified_user_id
      ORDER BY `c`.`lft` ASC
  19. SELECT m.id,m.title,m.module,m.position,m.content,m.showtitle,m.params,mm.menuid,e.protected
      FROM `jos_modules` AS `m`
      LEFT JOIN jos_modules_menu AS mm
      ON mm.moduleid = m.id
      LEFT JOIN jos_extensions AS e
      ON e.element = m.module
      AND e.client_id = m.client_id
      WHERE `m`.`published` = '1'
      AND `e`.`enabled` = '1'
      AND (`m`.`publish_up` IS NULL OR `m`.`publish_up` <= '2024-07-02 18:53:59' )
      AND (`m`.`publish_down` IS NULL OR `m`.`publish_down` >= '2024-07-02 18:53:59' )
      AND `m`.`access` IN ('1','1','4')
      AND `m`.`client_id` = '0'
      AND (`mm`.`menuid` = '293' OR `mm`.`menuid` <= '0' )
      ORDER BY `m`.`position` ASC,`m`.`ordering` ASC
  20. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_users'
  21. SELECT extension_id AS id,element AS "option",params,enabled
      FROM `jos_extensions`
      WHERE `type` = 'component'
      AND `element` = 'com_search'
  22. UPDATE `jos_session`
      SET `data` = '__default|a:9:{s:15:\"session.counter\";i:1;s:19:\"session.timer.start\";i:1719946439;s:18:\"session.timer.last\";i:1719946439;s:17:\"session.timer.now\";i:1719946439;s:8:\"registry\";O:23:\"Hubzero\\Config\\Registry\":2:{s:7:\"\0*\0data\";O:8:\"stdClass\":1:{s:1:\"0\";s:7:\"session\";}s:9:\"separator\";s:1:\".\";}s:4:\"user\";C:17:\"Hubzero\\User\\User\":22:{a:1:{s:5:\"guest\";b:1;}}s:11:\"tracker.sid\";s:32:\"3a6b685acaa85cd4edd95c887dfc7ac0\";s:12:\"tracker.ssid\";s:32:\"3a6b685acaa85cd4edd95c887dfc7ac0\";s:12:\"tracker.rsid\";s:32:\"3a6b685acaa85cd4edd95c887dfc7ac0\";}',`time` = '1719946439',`ip` = '3.23.103.140'
      WHERE `session_id` = '3a6b685acaa85cd4edd95c887dfc7ac0'
  • onAfterInitialise — Method — plgSystemP3p::onAfterInitialise → /core/plugins/system/p3p/p3p.php:21
  • onAfterInitialise — Method — plgSystemRemember::onAfterInitialise → /core/plugins/system/remember/remember.php:20
  • onAfterInitialise — Method — plgSystemHubzero::onAfterInitialise → /core/plugins/system/hubzero/hubzero.php:21
  • onAfterInitialise — Method — plgSystemXFeed::onAfterInitialise → /core/plugins/system/xfeed/xfeed.php:21
  • onAfterInitialise — Method — plgSystemSupergroup::onAfterInitialise → /core/plugins/system/supergroup/supergroup.php:113
  • onAfterInitialise — Method — plgSystemReferrerpolicy::onAfterInitialise → /core/plugins/system/referrerpolicy/referrerpolicy.php:21
  • onAfterRoute — Method — plgSystemJquery::onAfterRoute → /core/plugins/system/jquery/jquery.php:21
  • onAfterRoute — Method — plgSystemSpamjail::onAfterRoute → /core/plugins/system/spamjail/spamjail.php:21
  • onAfterRoute — Method — plgSystemIncomplete::onAfterRoute → /core/plugins/system/incomplete/incomplete.php:21
  • onAfterRoute — Method — plgSystemUnconfirmed::onAfterRoute → /core/plugins/system/unconfirmed/unconfirmed.php:21
  • onAfterRoute — Method — plgSystemUnapproved::onAfterRoute → /core/plugins/system/unapproved/unapproved.php:21
  • onAfterRoute — Method — plgSystemPassword::onAfterRoute → /core/plugins/system/password/password.php:21
  • onContentPrepare — Method — plgContentLoadmodule::onContentPrepare → /core/plugins/content/loadmodule/loadmodule.php:35
  • onContentPrepare — Method — plgContentEmailcloak::onContentPrepare → /core/plugins/content/emailcloak/emailcloak.php:25
  • onContentPrepare — Method — plgContentPagebreak::onContentPrepare → /core/plugins/content/pagebreak/pagebreak.php:35
  • onContentPrepare — Method — plgContentXhubtags::onContentPrepare → /core/plugins/content/xhubtags/xhubtags.php:25
  • onContentPrepare — Method — plgContentFormatwiki::onContentPrepare → /core/plugins/content/formatwiki/formatwiki.php:63
  • onContentPrepare — Method — plgContentFormathtml::onContentPrepare → /core/plugins/content/formathtml/formathtml.php:105
  • onContentPrepare — Method — plgContentExternalhref::onContentPrepare → /core/plugins/content/externalhref/externalhref.php:41
  • onContentBeforeDisplay — Method — plgContentPagenavigation::onContentBeforeDisplay → /core/plugins/content/pagenavigation/pagenavigation.php:25
  • onContentBeforeDisplay — Method — plgContentVote::onContentBeforeDisplay → /core/plugins/content/vote/vote.php:32
  • onAfterDispatch — Method — plgSystemMobile::onAfterDispatch → /core/plugins/system/mobile/mobile.php:22
  • onAfterDispatch — Method — plgSystemDebug::onAfterDispatch → /core/plugins/system/debug/debug.php:60
  • onAfterDispatch — Method — PlgSystemHighlight::onAfterDispatch → /core/plugins/system/highlight/highlight.php:25
  • onAfterRender — Method — plgSystemSef::onAfterRender → /core/plugins/system/sef/sef.php:21