Getting Help


We have transitioned to another service and are no longer actively updating this site.

Refer to our new documentation at:

Consulting Services

To ensure efficient support, please submit a help ticket rather than reaching out to individual consulting staff members directly.

Consulting is available free of cost to everyone and we welcome you to reach out! Our services include, but are not limited to:

  • Help for new users getting started with our resources. We know using HPC systems for the first time can be intimidating so scheduling an in-person meeting where you can ask loads of questions can help a lot
  • General issues that may occur, e.g., why is my job spending so long in the queue, where can I find information on topic <A>, why is this strange and unexpected thing happening, etc.
  • Advice on debugging software, package installations, and job failures
  • Advice on code optimization and utilizing our resources more effectively/efficiently

How to Reach Us

We use ServiceNow and can be reached with a support ticket. Many in our research community are accustomed to using the list service for hpc-consult. That continues to work but is not as efficient. And we really want to discourage sending emails directly to your favorite consultant.  

When Can I Ask for Help?

Any time! But first, we encourage you to:

(lightbulb) Double-check our FAQs - We keep track of commonly asked questions and document their solutions. You might find what you're looking for there.

(lightbulb) Look through our online documentation - There's lots of information to help get you started that may answer your question or help give you a better idea of what to ask.

How Can I Effectively Write a Support Request?

Glad you asked, helping us help you goes a long way and can give you better answers faster. Some general rules of thumb:

(lightbulb) Detail detail detail - A full error log may seem like a lot to send, but the more information we have, the more likely we are to be able to diagnose and/or replicate your issue. Information that can help us includes:

  • The cluster you're using
  • The modules you have loaded
  • The exact commands you're running
  • Full error logs
  • How you're connecting to the system (is it through a terminal, Open OnDemand shell, or virtual desktop?)
  • Your batch submission script. This can be included either as a text file or by providing its full path and filename on the system.
  • Screenshots

(lightbulb) Use reply-all to email chains - We will cc hpc-consult in our responses so that our (small) consulting team is able to view the issue and contribute.

(lightbulb) Provide context - There's a common support issue called The XY Problem. Say you have a problem and try to solve it yourself but the attempted solution produces an additional problem. Submitting a ticket requesting help with the attempted solution without information about the original issue can lead to more confusion. Knowing the full context will help us be able to more effectively assist you.

(lightbulb) Submit a ticket for your questions - If you reply to general system announcements or send emails to an HPC staff member's private inbox without cc'ing hpc-consult, your ticket may get lost and go unanswered. Submitting a ticket will ensure we have a record of your question and will get to it as promptly as we are able.

What Are Our Support Policies

Mostly it is common sense rather than strict rules. The primary consideration is that our consultants work regular hours with some flexibility built-in. So don't expect detailed responses at night or on the weekends. You might get a quick response but don't count on it.

Our consultants typically don't know how to run your applications unless they have broad usage like Python or R. So once we determine it is likely an issue with the code we will refer you to the provider. We don't troubleshoot bugs or run profilers, but we support tools like Valgrind for you to use.

We don't mind you asking lots of questions. We encourage you to ask for a consulting session via zoom or Office Hours (see below). We are not in the office so you can't drop by (although we kind of miss that personal engagement).

The bottom line is that the supercomputers are only really productive tools when you have the support to gain the most out of them to improve both your results and the time to get results.

Office Hours

We host virtual, drop-in office hours every Wednesday from 2pm to 4pm. Drop by to visit with our consultants to ask any questions you have about using HPC resources. It might be a bunch of getting started questions, or you might want to share your screen to walk us through a particular problem you're hung up on. We have private spaces for one-on-one consults. You can join us in Gather Town at this link.

If you have never used Gather Town before and would like additional information, check out this page.


For help with local installations, contact the College of Engineering IT services:

Ansys-specific support (debugging, questions about usage, etc) is available through PADT:

To report license connection issues, contact:

Community Resources

Research Bazaar

Want to get involved with the Tucson coding community? ResBaz AZ offers weekly events that brings together scientists, software engineers, and enthusiasts of all skill levels. Additionally, an annual Research Bazaar is held each spring hosting research computing workshops and career panels:

UArizona Data Science

Have some code-specific, data science, or related questions? Consider joining the UArizona Data Science Slack channel:

Code Commons

Code Commons provides a physical space for community and collaboration. Join to share experience, learn, mentor, discover opportunities, and work on your programming projects in the presence of others doing the same. Held every Wednesday from 2:00-6:00pm at the UArizona Library in the CATalyst Data Studios. For more information, see: