Using the CSF from MS Windows

Introduction

The CSF can easily be accessed from your Windows desktop. Here we provide some useful information for Windows users who may be less familiar with Linux.

Logging in from Windows

Please following the logging in from windows instructions.

Important information about batch submission scripts

If you use an editor on Windows (e.g., Notepad) to create a batch job submission script and transfer it to the CSF, your batch job will fail to run.

This is because Windows and Linux have different ways of indicating end-of-lines in text files (using hidden characters) and the batch system cannot understand the Windows line-end convention. We have three recommended ways of dealing with this:

1. Use gedit on the CSF login node to write your jobscript – although this is a Linux editor it is GUI based and can be run directly on the CSF which means you do not need to transfer files back and forth to your desktop. If you’ve logged in with MobaXterm then this will work straight away.
2. If you do create your jobscript text file in Windows and upload it to the CSF, run the following command on the login node before you submit it to batch:

   dos2unix filename

   where filename is the name of your jobscript file.

   Please note: you should never run dos2unix on other files you may have uploaded to the CSF from Windows. It should only be used to convert text-file jobscripts. If you run dos2unix on other files, such as data files, you will corrupt them – even if you used a Windows application to create the data files. dos2unix is for converting jobscripts only.

3. On Windows install and use Notepad++. Within Notepad++ select Edit menu -> EOL Conversion -> UNIX/OSX Format when creating/editing a new text file. When you then upload that file the CSF will understand it.
4. In the mobaxterm text editor it may be changed through the menu:
   Encoding ⇒ Unix.

Our recommendation is to use gedit (or any other Linux editor) directly on the CSF. Further information about gedit.

File and directory/folder names

DO NOT use spaces, and other non-alpha-numeric characters, in filenames and directories on Linux. Doing so can cause problems. In particular, the batch system may not be able to fully resolve the names of directories and cause jobs to error. Command line listing of files will be less clear, and without the use of escape characters, navigation of the filesystem, manipulation and deletion of files can be difficult. Acceptable non-alpha-numeric characters are underscore and dash. For example instead of:

Chemistry Simulation 1              # Bad folder name - it contains spaces

use:

Chemistry_Simulation_1              # A better choice - it contains _ instead of space

or

Chemistry-Simulation-1              # An equally good choice - it contains - instead of space

You may need to ensure that the folder structure and filenames on your windows PC/laptop follows these conventions to avoid problems when you upload then to the CSF. On Windows you should not encounter any problems using these conventions, provided you name only your files and folders in that way, i.e. do not change any of the system files or directories on your windows PC/laptop.

Basic Linux Commands and Compute Cluster Usage

If you are unfamiliar with Linux/Unix it is recommended that you work through one of the following:

• IT Services online Intro to Unix/Linux course
• Beginners guide to UNIX/Linux (University of Surrey)

We have also provided a list of basic linux commands for your reference.

Approximately three times a year an Intro to CSF course is run which provides an excellent starting point for users new to compute clusters and parallel computing concepts.