Difference between revisions of "SciNet User Support"

From oldwiki.scinet.utoronto.ca
Jump to navigation Jump to search
m
Line 1: Line 1:
 +
=== Support team ===
 
SciNet's [http://www.scinet.utoronto.ca/about/Personnel.htm support team of system administrators and technical analysts] can help you with wide range problems such as
 
SciNet's [http://www.scinet.utoronto.ca/about/Personnel.htm support team of system administrators and technical analysts] can help you with wide range problems such as
 
* how to use SciNet's systems,
 
* how to use SciNet's systems,
Line 4: Line 5:
 
* how to parallize or optimize your code,
 
* how to parallize or optimize your code,
 
* using and installing libraries.
 
* using and installing libraries.
If you have problems, questions, or requests, and you couldn't find the answer in this wiki, e-mail to:
+
 
 +
=== How to request help ===
 +
If you have problems, questions, or requests, and you couldn't find the answer in this wiki, send an e-mail '''with all relevant information''' to:
  
 
:[mailto:support@scinet.utoronto.ca <support@scinet.utoronto.ca>]  
 
:[mailto:support@scinet.utoronto.ca <support@scinet.utoronto.ca>]  
  
You can you the same e-mail if you want to make an appointment with one of our analysts. There is no formal ticketing system. Avoid sending email only to specific individuals at SciNet. Your chances of a quick reply increase significantly if you email our team.
+
'''''For connection problems, include:'''''
 +
* Where you are connecting from,
 +
* Where you are trying to connect to
 +
* The type of computer you are connecting from
 +
 
 +
'''''For failed jobs, include:'''''
 +
* What cluster you were using
 +
* A description of what the run is supposed to do
 +
* Job ID
 +
* Error messages you got
 +
* Full path to the job script
 +
* Full path to your code
 +
* Location of input/error files (please do not delete these!)
 +
 
 +
'''''For failed compilations, include:'''''
 +
* What cluster you were using
 +
* Full path to the code and Makefiles
 +
* A description of what the code is supposed to do
 +
* Error messages you got
  
Note: If your problem is with a specific code or job, please include as much relevant information as possible in your email, such as
+
'''''To make an appointment with one of our analysts:'''''
* Username
+
* Use the same e-mail.
* Cluster (GPC or TCS)
+
* There is no formal ticketing system.
* Error messages
+
*Avoid sending email only to specific individuals at SciNet. Your chances of a quick reply increase significantly if you email our team.
* Commands given before the error(s)
 
* For connection problems, the type of computer you are connecting from.
 
Furthermore, if applicable, let us know about the following:
 
* Path to your code
 
* Location of the job script
 
* Directory from which it was submitted
 
* and a description of what it is supposed to do.
 
  
 
'''Note that your password should never, never, never be to sent to us, even if your question is about your account.'''
 
'''Note that your password should never, never, never be to sent to us, even if your question is about your account.'''

Revision as of 12:09, 31 August 2010

Support team

SciNet's support team of system administrators and technical analysts can help you with wide range problems such as

  • how to use SciNet's systems,
  • how to set up your runs most efficiently,
  • how to parallize or optimize your code,
  • using and installing libraries.

How to request help

If you have problems, questions, or requests, and you couldn't find the answer in this wiki, send an e-mail with all relevant information to:

<support@scinet.utoronto.ca>

For connection problems, include:

  • Where you are connecting from,
  • Where you are trying to connect to
  • The type of computer you are connecting from

For failed jobs, include:

  • What cluster you were using
  • A description of what the run is supposed to do
  • Job ID
  • Error messages you got
  • Full path to the job script
  • Full path to your code
  • Location of input/error files (please do not delete these!)

For failed compilations, include:

  • What cluster you were using
  • Full path to the code and Makefiles
  • A description of what the code is supposed to do
  • Error messages you got

To make an appointment with one of our analysts:

  • Use the same e-mail.
  • There is no formal ticketing system.
  • Avoid sending email only to specific individuals at SciNet. Your chances of a quick reply increase significantly if you email our team.

Note that your password should never, never, never be to sent to us, even if your question is about your account.