Monthly Archives: April 2020

Accessing CU network drives while working from home

Posted by on April 1, 2020 No comments

If you are outside CU campus network (I bet you are now) but want to access W-drive or H-drive or R-drive, you need to connect to CU VPN first. Then open “This PC” (a.k.a. My Computer or Windows Explorer) and enter in the address bar the following addresses:

 

  • W-drive:   \\coventry.ac.uk\csv\Students\Shared\EC\STUDENT\
  • H-Drive Students: \\coventry.ac.uk\csv\Students\Personal  (then check each folder inside to see in each of them your Documents folder is located, you won’t be able to see any others)
  • H-Drive Staff: \\coventry.ac.uk\csv\Staff\Personal  (then check each folder inside to see in each of them your Documents folder is located, you won’t be able to see any others)
  • R-Drive: \\coventry.ac.uk\csv\Research

You will need to authenticate with your CU username in this format:   COVENTRY\yourusername  and your CU password. If you want to make this “permanent” you can mount these folders on your Windows 10 PC by right-clicking on “This PC” –> More –> Map Network Drive –> enter one of these addresses -> check “Connect Using different credentials (if your PC is not CU computer)” –> enter username and password as described above.

Running Parallel Python3 Jupyter Notebook on zeus HPC

Posted by on April 1, 2020 No comments

This is an approach to launch Jupyter notebook on a compute node of EEC HPC. Normally you launch Jupyter locally and then open associated web interface on your local machine. This is also possible to do on the HPC, however because the compute nodes of the cluster are mostly accessible via CLI only and are not “exposed” to the external to HPC network, one need to tunnel through the headnodes in order to reach them. The provided set of 2 HTA scripts simplifies the procedure: first script submits the Jupyter job to the queuing system of HPC (slurm) using html forms and ssh command tool (plink.exe from PuTTY). The second script (again using plink) establishes the ssh-tunnel to the target node, where the Jupyter server is running and starts the default browser on the client machine, pointing to the local port brought by the tunnel to the client machine. Since the compute nodes of HPC have multiple CPUs (some up to 32 cores), it is also shown that Jupyter notebook can utilise IPython ipcluster for running notebook codes on parallel threads.

link to scripts on coventry github

 

Video:

https://web.microsoftstream.com/embed/video/cb944d42-8d10-4784-8407-6e53fbaf3cbe?autoplay=false&showinfo=true

 

css.php