RESCOMP Archives

February 2006

RESCOMP@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stephen E. Wright" <[log in to unmask]>
Reply To:
Research Computing Support <[log in to unmask]>, Stephen E. Wright
Date:
Mon, 13 Feb 2006 08:53:37 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
I agree with Dave that we shouldn't cancel, if at all possible.

In addition to the topics Dave's indicated, I suggest spending a few 
minutes demonstrating how "easy" it is for someone to transfer a data file 
to the system, request an interactive session on a compute node, and to run 
Matlab and/or SAS with an X-window display.  The handouts should include 
info (Knowledge Base case numbers would suffice) on getting the necessary 
desktop software like openssh, cygwin, and so on.

Also, for the purpose of classroom demonstrations, faculty will want to 
know that it's possible to schedule an interactive session in advance for a 
specific date and time.

Steve

At 07:58 AM 2/13/2006, you wrote:
>I think that cancelling the training sessions should only be done if
>absolutely necessary.  There are several people who have registered for
>these sessions, and cancelling them might send a bad message.  If needed, we
>can limit the exercises that are done in the session.  Right now, I had
>planned on the following:
>- login
>- load and unload modules
>- run a batch job that uses shell commands like sleep and date
>- compile a simple hello world C or FORTRAN program
>- compile a hello world MPI program and run it as a batch job
>
>
>Dave

ATOM RSS1 RSS2