Skip to content

ARCC Installed Software

ARCC Icon

ARCC uses the Lmod module system on both MedicineBow and GannettPeak HPC systems to manage what software is loaded in researchers environment. This allows for the flexibility for many different use cases so that researchers who use different workflows can only load what software they need without all of the extra software that may conflict with others. Read more about Using the Module System on the next page of this documentation.

ARCC Software Installation Policy

ARCC's software policy is stated with the following goals:

  • Helping our users to become better HPC users,
  • by reflect systems and processes similar to other HPC centers,
  • by assisting via consultation and training to developing transferable skills and good practices
  • as well as allowing easier transition and move to other HPC centers.

What is Available?

On MedicineBow ARCC will be providing a small set of core compilers, languages, libraries and applications, which will be updated on a semi regular basis. Latest versions have been installed and we will not be supporting older versions of compilers.

The GNU family of compilers (i.e. gcc) will be our initial primary focus, but we do provide Intel’s oneAPI suite of compilers/libraries as well as NVidia’s hpc-sdk toolset.

Please refer to the MedicineBow Software List or GannettPeak Software List for what is available and/or use the module spider command to search.

ARCC will consider adding to this on a case-by-case basis.

The software you need is unavailable?

If you have a software package that is not installed as a module there are two options:

  • Install it yourself. You can install to your project (to share with your project members) or locally (just for you to use). Further documentation is available on Installing-Software
  • If you think it would be widely utilized on the cluster, You can make a request through our service portal for installation as a module.

Making Request

When you’re ready to submit a request, either: - Request a HPC Software Consultation via our portal. - Send an email to arcc-help@uwyo.edu with a subject of “Software Request" if you have questions that the form doesn't capture.

Request Details

When requesting software please consider the questions below and try to provide, where possible, as much related detail. We do appreciate that depending on your expertise with the software you might not be able to answer all of the following, but the more detail the better.

  • Name of the software:
  • Link to software resource (download, repository, documentation):
  • Purpose for software use/installation:
  • What research project is the software required for?
  • Is this a standalone piece of software?
  • Which version of the software do you need?
  • Is it a library/package to be used alongside a programming language such a C/C++, Python, R, Julia?
  • Which version of the programming language is required?
  • Are there any related dependencies you know about, require?
  • What Operating System is required?
  • Please note that Teton uses RedHat, not Windows/Mac.
  • We can run flavors of Linux via the Singularity container.
  • If this is an upgrade to existing software, what additional functionality does the new version provide (where possible please provide details):
  • Who is to use the software (individual, project, general):
  • Does the software require a license?
  • If yes, where will the funds to purchase the license come from?
  • Do you currently use the software?
  • If so, where and how?
  • Can you detail a typical workflow?
  • How do you intend to use the software on the cluster?
  • Is this different to previous use in another environment?
  • What is your level of experience of using the software?
  • Can and how do you test the software Installation?
  • Can you provide existing, working code and data, and expected results? Something we can use to replicate what you do to verify the installation.
  • If you're using examples, please point to where you got them from.
  • Timescales? Please indicate timescales for when required:
  • Is this required for an active/forthcoming class?

Depending on the extent of the request we may follow up with a consultation / discussion of some form to clarify the request, and to map out expectations and timelines.