IDC User Guide
  • Welcome!
  • 🚀Getting started
  • Core functions
  • Frequently asked questions
  • Support
  • Key pointers
  • Publications
  • IDC team
  • Acknowledgments
  • Jobs
  • Data
    • Introduction
    • Data model
    • Data versioning
    • Organization of data
      • Files and metadata
      • Resolving CRDC Globally Unique Identifiers (GUIDs)
      • Clinical data
      • Organization of data, v2 through V13 (deprecated)
        • Files and metadata
        • Resolving CRDC Globally Unique Identifiers (GUIDs)
        • Clinical data
      • Organization of data in v1 (deprecated)
    • Downloading data
      • Downloading data with s5cmd
      • Directly loading DICOM objects from Google Cloud or AWS in Python
    • Data release notes
    • Data known issues
  • Tutorials
    • Portal tutorial
    • Python notebook tutorials
    • Slide microscopy
      • Using QuPath for visualization
  • DICOM
    • Introduction to DICOM
    • DICOM data model
    • Original objects
    • Derived objects
      • DICOM Segmentations
      • DICOM Radiotherapy Structure Sets
      • DICOM Structured Reports
    • Coding schemes
    • DICOM-TIFF dual personality files
    • IDC DICOM white papers
  • Portal
    • Getting started
    • Exploring and subsetting data
      • Configuring your search
      • Exploring search results
      • Data selection and download
    • Visualizing images
    • Proxy policy
    • Viewer release notes
    • Portal release notes
  • API
    • Getting Started
    • IDC API Concepts
    • Manifests
    • Accessing the API
    • Endpoint Details
    • V1 API
      • Getting Started
      • IDC Data Model Concepts
      • Accessing the API
      • Endpoint Details
      • Release Notes
  • Cookbook
    • Colab notebooks
    • BigQuery
    • Looker dashboards
      • Dashboard for your cohort
      • More dashboard examples
    • ACCESS allocations
    • Compute engine
      • 3D Slicer desktop VM
      • Using a BQ Manifest to Load DICOM Files onto a VM
      • Using VS Code with GCP VMs
      • Security considerations
    • NCI Cloud Resources
Powered by GitBook
On this page
  • How to get started
  • Why we recommend ACCESS allocations
  • Acknowledging ACCESS and JetStream2

Was this helpful?

Edit on GitHub
Export as PDF
  1. Cookbook

ACCESS allocations

PreviousMore dashboard examplesNextCompute engine

Last updated 1 year ago

Was this helpful?

is a program supported by the US National Science Foundation (NSF) to provide educators with free and convenient access to advanced computational resources.

If you have a university email account, you can complete a relatively easy application process to receive an allocation of free credits that you can then use to create pre-configured GPU-enabled cloud-based linux virtual machines with desktop interface available via browser. You can use those machines, for example, to have a convenient access to an instance of for experimenting with AI models, or for training DL networks.

How to get started

Follow these steps:

  1. Once you created a VM and your setup is complete, it’s very easy to connect to your VMs through ssh or Web desktop interface.

Why we recommend ACCESS allocations

  • It is free for academics!

  • You can do a lot with the basic credit allocation! Entry-level allocations can be on the order of 100,000s, while the burn rate is, for example, 8 SUs/hour for a medium size VM (8 CPUs/30 GB RAM). As a reference:

    • it takes about 1 hour to build Slicer application from scratch on a medium-sized VM using 7 threads

  • Geared to help you save! Unlike the VMs you get from the commercial providers, JetStream VMs can be shelved. Once a VM is shelved, you spend zero SUs for keeping it around (in comparison, you will keep paying for the disk storage of your GCP VMs even when they are turned off).

  • Customer support is excellent! We received responses within 1-2 days. On some occasions, we observed glitches with Web Desktop, but those could often be resolved by restarting the VM.

Acknowledging ACCESS and JetStream2

Create an account and request an ACCESS allocation at this page: . There are 4 different levels, with each giving you a different number of “credits” that you use to create your VM instances. Each of these levels requires you to submit a different application. For the Explore ACCESS allocation (lowest tier), you need to write a simple abstract to justify why you needed these resources. Other tiers require more lengthy descriptions of what you’ll do with the ACCESS resources. In our experience, applications can be approved in as soon as a few days after submitting the application. You can be a PI and have multiple Co-PIs with you on the project, so you can all access the Jetstream2 resources.

Once you get approved, your allocation is valid for a 12 month period, and you get half of the credits to start. To start using these credits you exchange them for Service Units (SUs) on different platforms. We experimented with the one called , which provides easy interface to cloud-based computing resources. If you want to use JetStream2, you will need to exchange your ACCESS credit allocation for JetStream2 SUs here: . Usually this exchange is approved within a few days if not less.

Once you get the SU’s you can access JetStream interface to configure and create VMs here: (you can lean more about available configurations from this documentation page: ).

Very easy to set up. As of writing, there is no similar product available from Google Cloud, which would provide desktop access to a VM with a comparable ease of access. AWS provides , but we have yet to experiment to evaluate it.

it took ~7 days and ~5000 SUs to train the model in (see summary in the slides ) using g3.large VM configuration

JetStream2:

ACCESS:

https://docs.jetstream-cloud.org/alloc/overview/
JetStream2
https://docs.jetstream-cloud.org/general/access/
https://jetstream2.exosphere.app/
https://docs.jetstream-cloud.org/general/vmsizes/
AppStream2
this repository
here
https://jetstream-cloud.org/research/index.html#cite-jetstream
https://access-ci.org/about/acknowledging-access/
Advanced Cyberinfrastructure Coordination Ecosystem (ACCESS)
3D Slicer
Example of the configurations available for the Ubuntu 22.04 base image
GPU configurations available, from
https://docs.jetstream-cloud.org/general/vmsizes/#jetstream2-gpu