Support chain
Where to send what
Staff phone numbers, office locations, and helpdesk appointment hours change over time. Confirm current specifics on the CUNY HPCC page before distributing them; don’t copy numbers from secondary sources.
How to write a useful support request
Tickets that include the right information are resolved faster. Include:- Your username and the system you’re on (
arrow,penzias, etc.). - The job ID if the issue is job-related (
squeue -u $USERorsacctto find it). - Exactly what you ran: the
sbatchcommand or SLURM script, not a summary. - Exactly what happened: error output, screenshots, or the content of
slurm-<jobid>.out/.err. - When it happened: timestamp or “submitted ~14:30 today”.
- What you’ve already tried.
When to escalate
If your ticket or email has gone ~2 business days without a response or resolution:- Reply to your existing thread and note that you’d like to escalate. Don’t open a new ticket; it splits the history.
- If the issue is urgent (e.g., a cluster is down and your research deadline is blocked), say so explicitly in the reply.
- Only after that, if still no movement, contact the Director.
Support hours
The HPC Helpline monitors email during normal business hours. After-hours email is still answered but response is slower. For urgent issues (outage, security incident) mark your subject line withURGENT or SECURITY.
Confirm current support hours and any drop-in helpdesk appointments on the HPCC Wiki’s training page before publishing specific times.

