The CIP pool consists of workstations in the pool rooms CIP1 and CIP2, in the CIP rooms in the container building, in the mini pool room next to the main entrance and in the foyer. All workstations run Ubuntu 20.04 LTS.

All hosts are in the domain. I.e. the fully qualified domain name for cip1sandy1 is Since the hosts use the TUM ADS system for authentication, their "official" names are prepended by "tuphcom-".

Only is accessible from outside the MWN via SSH on port 222.

The workstation configuration is listed below.

Host            CPU                                 Memory 
cip1sandy1-6    Intel i7-2600K 3.40GHz (SandyBridge) 16 GB
cip1coffee1-2 Intel i5-8/9500 3.00GHz (CoffeeLake) 16 GB
cip1ivy Intel i5-3570 3.40GHz (IvyBridge) 8 GB cip1pavilion1-6 Intel i3-3220 3.30GHz (IvyBridge) 4 GB

cip2ryzen1-3 AMD Ryzen 7 2700 3.20GHz (Zen+) 32 GB
cip2ryzen4 AMD Ryzen 7 7700 3.8-5.3GHz 64 GB
cip2skylake1-4 Intel i5-6600 3.30GHz (SkyLake)    16 GB
cip2smart Intel i3-2120 3.30GHz (SandyBridge) 8 GB

cont1sandy1-6 Intel i7-2600K 3.40GHz (SandyBridge) 16 GB
cont1think1-2 Intel Core2 Duo 2.93GHz 2 GB

cont2sandy1-2 Intel i7-2600K 3.40GHz (SandyBridge) 16 GB
cont2smart Intel i7-2600K 3.40GHz (SandyBridge) 16 GB
cont2think Intel Core2 Duo 2.93GHz 2 GB

mini1-6 Intel i3-3220 3.30GHz (IvyBridge) 4 GB
foyer1-3 Intel Core2 Duo 2.93GHz 4 GB
cipgate Redundantly hosted virtual machine 2 GB

Most computers in CIP2 have CUDA-enabled GPU cards and the corresponding SDKs.

User profiles are shared between all hosts. Every host has the same set of applications.


The amount of space you can use in your home directory is limited to 3 GB per user (although this can be increased if you can convince us that you do not want to use the space to backup your mp3 collection). If you need more space for temporary storage (e.g. simulation data) please use the local /scratch directory. You may use as much space as you like. However please keep in mind that files in /scratch are stored on the local workstation, are never backuped and can be lost at any time.

If you want to access another host's scratch, sshfs is very useful:

user@host:/scratch$ mkdir cip1sandy1
user@host:/scratch$ sshfs cip1sandy1:/scratch cip1sandy1
user@cip1sandy1's password:
user@host:/scratch$ ls cip1sandy1/
ga25sux lost+found

you can mount any ssh/scp-accessible directory this way. Please note that the mount point should be on a local drive (i.e. scratch), mounting stuff into an NFS-directory (e.g. your home directory) means asking for trouble.

  • No labels