Page Comparison

This page details the list of questions that you need to consider and provide details on when requesting new or an update to software. This will assist us in understanding your needs and assessing and prioritizing the installation.

Contents

Glossary

...

Making Request

When you’re ready to submit a request, either:

• Request a HPC Software Consultation via our portal.

• Questions? Send an email to arcc-help@uwyo.edu with a subject of “Software Request.

Request Details

When requesting software please con he consider the questions below and try and to provide, where possible, as much related detail. We do appreciate that depending on you 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

  using

  • 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, do you have where will the funds to purchase itthe license come from?

• Do you currently use the software?

  • If so, where and how?

  • Can you detail a typical workflow?

• How do you indent intend to use the software on the cluster?

  • Is this different to previous use on 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?

...