== The different queues ==

The larger hpc clusters, most notably hpc03, hpc06, hpc11 and hpc12, are shared by two or more research groups. On those clusters every group has their own queue, sometimes even more than one. These queues give exclusive and full access to a specific set of nodes.

There is also a guest queue on every hpc cluster that gives access to all nodes, but with some restrictions, you will not be able to run non-rerunable and interactive jobs.

In most cases, access to one of the queues is based on group membership in the Active Directory. If your netid is not a member of the right group, you default to the guest queue if you submit a job. If you have access to the group and bulk network shares of your research group, you should also have access to the normal queue on the hpc cluster. If not, contact the secretary in your research group and let him/her arrange the group membership of your netid.

You can check your default queue by submitting a small test job and then have a look at the list with jobs with the qstat command.

[jsmith@hpc10 ~]$ echo "sleep 60" | qsub
[jsmith@hpc10 ~]$ qstat -u jsmith

If you see anything other than guest in the third column, then you are all set.

There are two ways to select the guest queue;

With the -q switch on the commandline:

qsub -q guest job1

Or with a directive at the start of your job script:

#PBS -q guest

It is important to know that a job in the guest queue can be interrupted and resumed at any time. You should make sure that the application in your job saves the intermediate results at regular intervals and that it knows how to continue when your job is resumed. If you neglect this, your job in the guest queue will start all over again every time it is interrupted and resumed.

== The different nodes ==

On most hpc clusters you'll find that worker nodes are not all identical, different series of nodes exist which were purchased at different times and with different specifications. To distinguish between the different series of nodes, they are labelled with properties like typea, typeb, typec, etc. On some hpc clusters, nodes have extra properties showing to which queue they belong or showing additional features, like an infiniband network or extra memory compared to similar nodes.

A useful command that shows all nodes and how they are utilized is <code>LOCALnodeload.pl</code>. A typical output looks like this:

<pre>
[jsmith@hpc10 ~]$ LOCALnodeload.pl
Node Np State/jobs Load Properties
---------- -- ---------- ----- ----------
n10-01 12 12 12.01 typea
n10-02 12 free 0.00 typea
n10-03 12 free 0.00 typea
n10-04 12 free 0.00 typea
n10-05 16 12 11.93 typeb
n10-06 16 free 0.00 typeb
n10-07 16 offline 0.00 typeb
n10-08 16 down 0.00 typeb
</pre>

The first column (Node) shows the names of the nodes. The second column (Np) shows the total number of processors. The third column (State/jobs) shows the number of processors currenly in use or the status of the node (free, offline or down). The forth colum (Load) shows the actual load on the nodes. In an ideal situation the load matches the number of processors in use. The last column (Properties) shows the properties as described above. As you can see in the example, typea nodes have 12 processors and typeb nodes have 16. Node n10-01 is fully occupied, node n10-05 is running one or more jobs but still has 4 processors free. Nodes n10-07 and n10-08 cannot be used.

== Selecting nodes ==

If you submit a job, the scheduler automatically selects a node to run it. By default a jobs gets one node and one processor. You can manually select the number of processors and nodes for your job by using the <code>-l</code> switch with the <code>qsub</code> command. You can also select nodes by property. the <code>-l</code> switch works like this:

qsub -l nodes=<x>:ppn=<c>:<property>:<property>...

* <x> is either an amount of nodes or the name(s) of the selected node(s)
* <c> is number of processors per node
* <property> is any of the properties you see in Properties column of the LOCALnodeload.pl command.

Examples:

{|
|-
| <code>qsub -l nodes=4</code> || Request 4 nodes of any type
|-
| <code>qsub -l nodes=n10-07+n10-08</code> || Request 2 specific nodes by hostname
|-
| <code>qsub -l nodes=4:ppn=2</code> || Request 2 processors on each of four nodes
|-
| <code>qsub -l nodes=1:ppn=4</code> || Request 4 processors on one node
|-
| <code>qsub -l nodes=2:typea</code> || Request 2 nodes with the <code>typea</code> property
|-
|}
Instead of using the -l or the -q switches on the commandline when you submit your job with qsub, you can also add them as a directive to your job script. For instance, if you add

#PBS -l nodes=1:ppn=4
#PBS -q guest

at the start of your script, you can just use

qsub job.sh

instead of

qsub -l nodes=1:ppn=4 -q guest job.sh

== Avoid over- and underutilization ==

An important thing to consider when you create your own job script is matching the number of processors that you request with the number of processors that the software in your script will actually use. It is possible that you request only one processor and that your program will use all processors available on the nodes. This is called overutilization and is not very efficient when other jobs are already running on the same node and using the same processors.

It is also possible that you request several (or all) processors and that your program will only use one. This will leave the other processors you claimed unused (underutilization), which is also not very efficient because the unused processors you requested will not be used for other jobs.

How to avoid over- and underutilization? Many programs have options that will let them use only one thread (utilization of only one processor) or a specific number of threads.

For example, Ansys has the <code>-np</code> switch:

ansys -np N

and Fluent has the <code>-t</code> switch

fluent -tN

where N matches the number of processors that you request in your job.

If your program does not have an option to limit the number of processor, you can try to add this line in your job script, just before the line where your progam starts:

export OMP_NUM_THREADS=N

Of course, N must match the number of processors that you request in your job. Alternatively, you could also request an entire node (all processors) in your job and let your program use all available resources of that node.

== Avoid excessive reads and writes on your homedir ==

Some programs read and write a lot of data to and from your home directory. This is not very efficient, on the nodes your home directory is a network share, so access is relatively slow and it keeps the master node unnecessarily busy. If you expect that your job will do a lot of reading and writing to disk, you can use the local disk on the node instead, which is mounted on /var/tmp on all nodes. You can do this by adding a few extra lines to your job script, right before the line that starts the program in your job, for example:

<pre>
TMP=/var/tmp/${PBS_JOBID}
mkdir -p ${TMP}
/usr/bin/rsync -vax "${PBS_O_WORKDIR}/" ${TMP}/
cd ${TMP}
</pre>

Once your program is done you can copy the results back to your home directory and clean up by adding these two lines at the end of your job script:

<pre>
/usr/bin/rsync -vax ${TMP}/ "${PBS_O_WORKDIR}/"
[ $? -eq 0 ] && /bin/rm -rf ${TMP}
</pre>

This usually works best if you create a seperate directory in your homedir, move the necessary files and the job script to it and run your job from there. Otherwise you would end up copying your entire home directory to the node for no good reason.

== Access to nodes ==

All nodes are independant Linux machines and you could be tempted to log in to one of the nodes and work from there. This is however forbidden, any attempt to log in to a node will fail. There is one exception, you can log in to a node if you have a job running on it, this way you can check on the progress of your job and see if things are still working as intended. To check which node runs your job, type:

qstat -u $USER -n1

This will get you a list of all your jobs, in the last column you'll see the nodes in use. If you log in to a node, please do not run any additional CPU intensive programs to avoid overutilization.

If you must log in to a node in order to run software that can not be run from a script, you can start an interactive job. This is done using the <code>-I</code> switch with qsub, like this:

qsub -I

As soon as a node is assigned to you (this may take a while), you'll get a new command line prompt, as if you just logged in with ssh. This will reserve only one processor, you should take care that if you start a CPU intensive program, it does not use more than one processor. If you need more processors or if you want to use a specific node, you can request this for your interactive job with the <code>-l</code> switch, for example, if you want to request 8 processors on node n10-08:

qsub -I -l nodes=n10-08:ppn=8

If you want to run a progam with a graphical interface on a node, you'll need to make sure that X forwarding works when logged in to the master node. Then you can use the <code>-X</code> switch start your interactive job with X forwarding enabled:

qsub -I -X

It is important to know that an interactive can only be run in the normal queues, '''you can not run an interactive job in the guest queue!'''

== A generic example of a job script ==

The script below can be used as a starting point to create your own jobs. Feel free to copy, paste and modify it to your needs. Lines starting with # will not be executed and contain useful information.

<pre>
#!/bin/bash
#
# Torque directives (#PBS) must always be at the start of a job script!
#
# Request nodes and processors per node
#
#PBS -l nodes=1:ppn=1
#
#
# Set the name of the job
#
#PBS -N name_of_job
#
#
# Set the mail options (type 'man qsub' for more information)
#
#PBS -m bea
#
#
# Set the email address where you want notifications sent to
# By default mail will be sent to your TU Delft mailbox
#
#PBS -M $USER@mailboxcluster.tudelft.net
#
#
# Set the rerunable flag, 'n' is not rerunable, default is 'y'
#
#PBS -r y

# Make sure I'm the only one that can read my output
umask 0077

# create a temporary directory in /var/tmp
TMP=/var/tmp/${PBS_JOBID}
mkdir -p ${TMP}
echo "Temporary work dir: ${TMP}"
if [ ! -d "${TMP}" ]; then
echo "Cannot create temporary directory. Disk probably full."
exit 1
fi

# copy the input files to ${TMP}
echo "Copying from ${PBS_O_WORKDIR}/ to ${TMP}/"
/usr/bin/rsync -vax "${PBS_O_WORKDIR}/" ${TMP}/

cd ${TMP}

#

module load application1
module load application2

export OMP_NUM_THREADS=1

# Here is where the application is started on the node

# job done, copy everything back
echo "Copying from ${TMP}/ to ${PBS_O_WORKDIR}/"
/usr/bin/rsync -vax ${TMP}/ "${PBS_O_WORKDIR}/"

# delete my temporary files
[ $? -eq 0 ] && /bin/rm -rf ${TMP}
</pre>

How to log in

2019-01-16T16:07:01Z

Paul Keekstra: /* Basics */

== Basics ==

In order to log in you need a valid [https://www.tudelft.nl/en/student/ict/ict-facilities/netid-account/ NetID] that is enabled for access to one of the clusters. To have your NetID enabled, ask the contact person for the cluster you want access to (See the [[Introduction]] page) or ask the secretary of the department or research group where you work, he or she can tell you who the contact person is for an hpc cluster.

If you want to collaborate with someone from outside the TU Delft and you want that person to access the same cluster as you, then you can request a guest account at the servicedesk. Once the guest account is created, it can be enabled for access to one of the clusters. '''Do not share your own NetID with others! Your NetID is for personal use only, sharing it with other people is forbidden!'''

The hpc clusters are only accessible via ssh (secure shell). To log in you need an ssh client. If you use Windows, you can download and use [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], Macintosh and Linux computers already have an ssh client built in. There is no need to log in to a bastion host first, you can log in from anywhere in the world.

Every time you log in you'll see an motd (message of the day). Please pay attention to this, it may contain information about current events on the cluster. It also shows you an email address that you can use if there are problems or if you have questions. You can mail at any time you like, but you'll usually only get a reply during office hours, there is no 24/7 support on the hpc clusters.

'''Please note:''' You have a local home directory on the cluster. No backups will be made of the home directories, if you make a mistake and loose a file, it is gone forever. '''Making backups of your important files on the hpc clusters is your own responsibility!'''

== How to log in from Windows ==

An often used ssh client for Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. If you use a Windows PC or a laptop that is provided and maintained by the TU Delft, it is already there, if you use your own Windows computer, you'll have to download and install it first from [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html www.chiark.greenend.org.uk].

Once you have started PuTTY you'll get a configuration window als shown.

[[File:PuTTY_01.png|center]]

You can type the name of the cluster, for example 'hpc10.tudelft.net', in the field 'Host Name'. You can save the settings for a cluster by choosing a name for the session, enter it in the 'Saved Sessions' box and click 'Save'. The next time you open PuTTY the settings can be restored by clicking on the name and a click on 'Load'.

By clicking 'Open' a connection is made to hpc10.tudelft.net. If this is the first time you are connecting to the cluster, PuTTY will warn you that you are connecting to a previously unknown host.

[[File:PuTTY_02.png|center]]

You can confirm this connection by clicking 'yes' so PuTTY will store the host key in its database. You'll have to do this only once for every new server that you connect to.

After you have accepted the connection, PuTTY opens a console and asks for your loginname. Once you have entered your NetID and your password, you are logged in to the cluster.

[[File:PuTTY_03.png|center]]

== How to transfer files to and from Windows ==

WinSCP is a freeware ftp client with support for secure file protocols sftp and scp. The login screen depicted below shows the settings for access within the University.

[[File:WinSCP_01.png|center]]

After clicking on 'Login' a warning about host keys will appear, similar to PuTTY. If it is the first time, you can safely click on 'yes' to accept.

Press 'Login'. If everything is setup correctly you are using the ssh tunnel the PuTTY bastion session has built and you are logged in on the cluster.

When logged in, you will see the commander-like interface below.

[[File:WinSCP_02.png|center|530px]]

The left side displays the files in your home directory on the windows system. The right side displays the files on the cluster. You can drag and drop files between the two windows or select files with the mouse and press 'F5' for transfer to the other window.

== How to log in from OS X or Linux ==

Mac OS X is in fact a full blown UNIX system under the hood. A terminal program comes standard with OS X, navigate with the finder to Applications -> Utilities to find it, the program is called 'Terminal'. There are many different flavours of Linux, each with their own desktop environments and customizations. Nearly every Linux system comes with a terminal program of some sort. Find the terminal program on your system and run it, once you get a command prompt type:

ssh <netid>@hpc10.tudelft.net

Where <netid> is of course your own netid.

Upon first access, ssh requires you to check if the host key is correct. Since this is the first time you connect to the system, it's fine to accept the host key by pressing 'y'.

== How to transfer files to and from OS X or Linux ==

To transfer files you can use scp, which is very similar to ssh:

scp <netid>@hpc10.tudelft.net:~/projects.txt ~

This will copy the file 'projects.txt' from your remote home directory (folder) to the local home directory on your workstation or laptop.

If you want to copy an entire directory with all its content, use the '-r' option, like this:

scp -r <netid>@hpc10.tudelft.net:~/projects/ ~

This will copy the directory 'projects' from your remote home directory to the local home directory on your workstation or laptop.

Of course, it is also possible to copy files and directories from your workstation or laptop to the remote machine:

scp -r projects.txt <netid>@hpc10:~/

This will copy the file 'projects.txt' from your current working directory to the home directory on the remote machine.

scp -r projects/ <netid>@hpc10:~/

And this will copy the directory 'projects' and all its content from your current working directory to the home directory on the remote machine.

== How to display graphical applications ==

=== Windows ===

There are several options for displaying graphical applications on a Windows system. A basic option is [http://www.straightrunning.com/XmingNotes/ Xming]. You can download it from: http://www.straightrunning.com/XmingNotes/ The site asks for a donation to use the latest version, but there is also a public domain version which can be used for free. Once you have installed it, you can find it in the usual place in the start menu. Before you log in to an hpc cluster and run graphical applications, you need to start Xming first. It will not show much, only a small X in the system tray once it's running. You also need to enable X forwarding in PuTTY. For that you need to click on the + next to SSH in the session panel (left part of the window), then click on X11. You'll see a line on the right side that says "Enable X11 forwarding", click once on the white square next to that line and it will show a check mark.

[[File:PuTTY_04.png|center]]

Now you can continue logging in to the hpc cluster. To check if X forwarding works, type <code>xeyes</code> on the command line, this will show a small window on your screen with two eyes that will follow the mouse pointer.

[[File:Xeyes.png|center]]

An alternative option for displaying graphical applications is Exceed, this is a commercial package for which the TU Delft has a license. It is not available by default on the standard Windows systems, but it can be installed upon request if you contact the servicedesk.

A second alternative is [https://mobaxterm.mobatek.net/ MobaXterm], this is an all-in-one solution containing an ssh client, X server and more. You can download a free version from: https://mobaxterm.mobatek.net/download.html The free version has some limitations, but it's still perfectly usable in our environment.

=== Mac OS X ===

For displaying graphical applications on a Mac OS X system you need a software package called [https://www.xquartz.org/ XQuartz] which can be downloaded from: [https://www.xquartz.org/ https://www.xquartz.org/] This will run on Mac OS X v10.6 and higher. Once it's installed, you end up with an application called XQuartz located in /Applications/Utilties. There is no need to start it first before you log in to an hpc cluster, it will start automatically as soon as it is needed. The only thing you need to do is add the option <code>-X</code> to the <code>ssh</code> command that you use to log in:

ssh -X <netid>@hpc10.tudelft.net

You can test if this works by typing <code>xeyes</code> on the command line, this will show a small window on your screen with two eyes that follow the mouse pointer. If it doesn't work, try the <code>-Y</code> option:

ssh -Y <netid>@hpc10.tudelft.net

=== Linux ===

Most Linux workstations come with a graphical environment. This works transparantly with the graphical applications on the hpc clusters. The only thing you need to do is add the option <code>-X</code> to the <code>ssh</code> command that you use to log in:

ssh -X <netid>@hpc10.tudelft.net

You can test if this works by typing <code>xeyes</code> on the command line, this will show a small window on your screen with two eyes that follow the mouse pointer. If it doesn't work, try the <code>-Y</code> option:

ssh -Y <netid>@hpc10.tudelft.net

== How to access your Windows network shares ==

It is possible to access the group and bulk shares of your research group, just type:

cd /tudelft/$USER/staff-group/

or

cd /tudelft/$USER/staff-bulk/

and navigate from there to the directories that you need.

You can access your Windows home directory as well, the path is:

/tudelft/$USER/staff-homes/

followed by the first letter of your surname and then your netid. For example, if your name would be John Smith and your netid jsmith;

cd /tudelft/$USER/staff-homes/s/jsmith

If you are a student, replace 'staff' with 'student' to access your files.

cd /tudelft/$USER/student-homes/s/jsmith

How to log in

2019-01-16T16:02:29Z

Paul Keekstra: /* Basics */

== Basics ==

In order to log in you need a valid [https://www.tudelft.nl/en/student/ict/ict-facilities/netid-account/ NetID] that is enabled for access to one of the clusters. To have your NetID enabled, ask the contact person for the cluster you want access to (See the [[Introduction]] page) or contact the secretary of the department or research group where you work, he or she can tell you who the contact person is for an hpc cluster.

If you want to collaborate with someone from outside the TU Delft and you want that person to access the same cluster as you, then you can request a guest account at the servicedesk. Once the guest account is created, it can be enabled for access to one of the clusters. '''Do not share your own NetID with others! Your NetID is for personal use only, sharing it with other people is forbidden!'''

The hpc clusters are only accessible via ssh (secure shell). To log in you need an ssh client. If you use Windows, you can download and use [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY], Macintosh and Linux computers already have an ssh client built in. There is no need to log in to a bastion host first, you can log in from anywhere in the world.

Every time you log in you'll see an motd (message of the day). Please pay attention to this, it may contain information about current events on the cluster. It also shows you an email address that you can use if there are problems or if you have questions. You can mail at any time you like, but you'll usually only get a reply during office hours, there is no 24/7 support on the hpc clusters.

'''Please note:''' You have a local home directory on the cluster. No backups will be made of the home directories, if you make a mistake and loose a file, it is gone forever. '''Making backups of your important files on the hpc clusters is your own responsibility!'''

== How to log in from Windows ==

An often used ssh client for Windows is [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY]. If you use a Windows PC or a laptop that is provided and maintained by the TU Delft, it is already there, if you use your own Windows computer, you'll have to download and install it first from [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html www.chiark.greenend.org.uk].

Once you have started PuTTY you'll get a configuration window als shown.

[[File:PuTTY_01.png|center]]

You can type the name of the cluster, for example 'hpc10.tudelft.net', in the field 'Host Name'. You can save the settings for a cluster by choosing a name for the session, enter it in the 'Saved Sessions' box and click 'Save'. The next time you open PuTTY the settings can be restored by clicking on the name and a click on 'Load'.

By clicking 'Open' a connection is made to hpc10.tudelft.net. If this is the first time you are connecting to the cluster, PuTTY will warn you that you are connecting to a previously unknown host.

[[File:PuTTY_02.png|center]]

You can confirm this connection by clicking 'yes' so PuTTY will store the host key in its database. You'll have to do this only once for every new server that you connect to.

After you have accepted the connection, PuTTY opens a console and asks for your loginname. Once you have entered your NetID and your password, you are logged in to the cluster.

[[File:PuTTY_03.png|center]]

== How to transfer files to and from Windows ==

WinSCP is a freeware ftp client with support for secure file protocols sftp and scp. The login screen depicted below shows the settings for access within the University.

[[File:WinSCP_01.png|center]]

After clicking on 'Login' a warning about host keys will appear, similar to PuTTY. If it is the first time, you can safely click on 'yes' to accept.

Press 'Login'. If everything is setup correctly you are using the ssh tunnel the PuTTY bastion session has built and you are logged in on the cluster.

When logged in, you will see the commander-like interface below.

[[File:WinSCP_02.png|center|530px]]

The left side displays the files in your home directory on the windows system. The right side displays the files on the cluster. You can drag and drop files between the two windows or select files with the mouse and press 'F5' for transfer to the other window.

== How to log in from OS X or Linux ==

Mac OS X is in fact a full blown UNIX system under the hood. A terminal program comes standard with OS X, navigate with the finder to Applications -> Utilities to find it, the program is called 'Terminal'. There are many different flavours of Linux, each with their own desktop environments and customizations. Nearly every Linux system comes with a terminal program of some sort. Find the terminal program on your system and run it, once you get a command prompt type:

ssh <netid>@hpc10.tudelft.net

Where <netid> is of course your own netid.

Upon first access, ssh requires you to check if the host key is correct. Since this is the first time you connect to the system, it's fine to accept the host key by pressing 'y'.

== How to transfer files to and from OS X or Linux ==

To transfer files you can use scp, which is very similar to ssh:

scp <netid>@hpc10.tudelft.net:~/projects.txt ~

This will copy the file 'projects.txt' from your remote home directory (folder) to the local home directory on your workstation or laptop.

If you want to copy an entire directory with all its content, use the '-r' option, like this:

scp -r <netid>@hpc10.tudelft.net:~/projects/ ~

This will copy the directory 'projects' from your remote home directory to the local home directory on your workstation or laptop.

Of course, it is also possible to copy files and directories from your workstation or laptop to the remote machine:

scp -r projects.txt <netid>@hpc10:~/

This will copy the file 'projects.txt' from your current working directory to the home directory on the remote machine.

scp -r projects/ <netid>@hpc10:~/

And this will copy the directory 'projects' and all its content from your current working directory to the home directory on the remote machine.

== How to display graphical applications ==

=== Windows ===

There are several options for displaying graphical applications on a Windows system. A basic option is [http://www.straightrunning.com/XmingNotes/ Xming]. You can download it from: http://www.straightrunning.com/XmingNotes/ The site asks for a donation to use the latest version, but there is also a public domain version which can be used for free. Once you have installed it, you can find it in the usual place in the start menu. Before you log in to an hpc cluster and run graphical applications, you need to start Xming first. It will not show much, only a small X in the system tray once it's running. You also need to enable X forwarding in PuTTY. For that you need to click on the + next to SSH in the session panel (left part of the window), then click on X11. You'll see a line on the right side that says "Enable X11 forwarding", click once on the white square next to that line and it will show a check mark.

[[File:PuTTY_04.png|center]]

Now you can continue logging in to the hpc cluster. To check if X forwarding works, type <code>xeyes</code> on the command line, this will show a small window on your screen with two eyes that will follow the mouse pointer.

[[File:Xeyes.png|center]]

An alternative option for displaying graphical applications is Exceed, this is a commercial package for which the TU Delft has a license. It is not available by default on the standard Windows systems, but it can be installed upon request if you contact the servicedesk.

A second alternative is [https://mobaxterm.mobatek.net/ MobaXterm], this is an all-in-one solution containing an ssh client, X server and more. You can download a free version from: https://mobaxterm.mobatek.net/download.html The free version has some limitations, but it's still perfectly usable in our environment.

=== Mac OS X ===

For displaying graphical applications on a Mac OS X system you need a software package called [https://www.xquartz.org/ XQuartz] which can be downloaded from: [https://www.xquartz.org/ https://www.xquartz.org/] This will run on Mac OS X v10.6 and higher. Once it's installed, you end up with an application called XQuartz located in /Applications/Utilties. There is no need to start it first before you log in to an hpc cluster, it will start automatically as soon as it is needed. The only thing you need to do is add the option <code>-X</code> to the <code>ssh</code> command that you use to log in:

ssh -X <netid>@hpc10.tudelft.net

You can test if this works by typing <code>xeyes</code> on the command line, this will show a small window on your screen with two eyes that follow the mouse pointer. If it doesn't work, try the <code>-Y</code> option:

ssh -Y <netid>@hpc10.tudelft.net

=== Linux ===

Most Linux workstations come with a graphical environment. This works transparantly with the graphical applications on the hpc clusters. The only thing you need to do is add the option <code>-X</code> to the <code>ssh</code> command that you use to log in:

ssh -X <netid>@hpc10.tudelft.net

You can test if this works by typing <code>xeyes</code> on the command line, this will show a small window on your screen with two eyes that follow the mouse pointer. If it doesn't work, try the <code>-Y</code> option:

ssh -Y <netid>@hpc10.tudelft.net

== How to access your Windows network shares ==

It is possible to access the group and bulk shares of your research group, just type:

cd /tudelft/$USER/staff-group/

or

cd /tudelft/$USER/staff-bulk/

and navigate from there to the directories that you need.

You can access your Windows home directory as well, the path is:

/tudelft/$USER/staff-homes/

followed by the first letter of your surname and then your netid. For example, if your name would be John Smith and your netid jsmith;

cd /tudelft/$USER/staff-homes/s/jsmith

If you are a student, replace 'staff' with 'student' to access your files.

cd /tudelft/$USER/student-homes/s/jsmith