uabrc / uabrc/uabrc.github.io

National Cyberinfrastructure table

Open
#839 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

style: article/section 📝
Dominant language
Python
Stars
24
Forks
15
Avg merge
10d 3h
Merged PRs (30d)
1

Description

What would you like to see added?

Think like the storage table in our docs, let's create a table of pros/cons for national cyberinfrastructure.

To start us off:

  • OSG (https://osg-htc.org/) (Maybe called OSPool?)
    • HTC
    • Suitable for short runtimes, low resource, many replicates
    • Lead time?
    • Proposal required?
    • Caveats? Pre-emption...
    • Resource limits?
    • Documentation?
    • How to get to it?
  • ACCESS (https://access-ci.org/)
  • JetStream2 (https://jetstream-cloud.org/)
    • Special-case of an ACCESS resource for GPU-intense cloud options
  • NAIRR (National AI Research Resource: https://nairrpilot.org/)
    • Expressly for AI-related research, or research using AI
    • Broad suitability depending on resource needs
    • Lead time?
    • Proposal requirement?
    • Caveats?
    • Resource limits?
    • Documentation?
    • How to get to it?

In addition to the table:

Any others?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the storage table in the documentation and review the listed OSG, ACCESS, JetStream2, NAIRR, and community-resource links. Add a pros/cons table covering the requested suitability, lead time, proposal, caveats, limits, documentation, and access details, plus the related links; include the ACCESS on-ramp script if appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, markdown
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.