Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
doku:win2vsc [2021/09/29 09:42] – [Terminal connection] goldenbergdoku:win2vsc [2021/09/29 13:05] (current) – [The job file: text editors on the Cluster] goldenberg
Line 46: Line 46:
  
 In this terminal, your application can be (re-)compiled. In this terminal, your application can be (re-)compiled.
-Please use the latest "Intel" MPI-Environment as described in [[doku:mpi|MPI Environment]] for VSC-2 (SGE). On VSC-3, batch jobs are submitted under [[doku:slurm|SLURM]] instead of [[doku:sge|SGE]].+Batch jobs are submitted under [[doku:slurm|SLURM]].
  
 {{ :doku:win2cluster:putty.png |}} {{ :doku:win2cluster:putty.png |}}
Line 56: Line 56:
 ==== The job file: text editors on the Cluster ==== ==== The job file: text editors on the Cluster ====
  
-Create a job file as described in the section [[doku:sge|Submitting batch jobs (SGE)]] for VSC-2 or in the section [[doku:slurm|Submitting batch jobs (SLURM)]] for VSC-3. +Create a job file as described in the section [[doku:slurm|Submitting batch jobs (SLURM)]]. 
 You have to submit a remote job, it is not allowed to run your application directly on the login nodes. You have to submit a remote job, it is not allowed to run your application directly on the login nodes.
  
-Editors in //Windows// may add additional invisible characters to the job file which render it unreadable and, thus, it is not executed. It can be quite cumbersome to find and remove these additional characters. Therefore, it is advisable to write the job file directly on the VSC linux cluster. Available editors on the VSC 2 include [[http://www.nedit.org|NEdit]], see Figure 3. //NEdit// opens if you enter  +Editors in //Windows// may add additional invisible characters to the job file which render it unreadable and, thus, it is not executed. It can be quite cumbersome to find and remove these additional characters. Therefore, it is advisable to write the job file directly on the VSC linux cluster. Available editors on the VSC include [[http://www.nedit.org|NEdit]], see Figure 3. //NEdit// opens if you enter  
 <code> <code>
-[<username>@l21 ~]$ nedit &        [+ return]+[<username>@l41 ~]$ nedit &        [+ return]
 </code> </code>
 on the command line. This editor works similar to //ms windows// applications. on the command line. This editor works similar to //ms windows// applications.
 +**Note:** You have to connect via X-forwarding to use it
 The **&** is used to open the application in the background and to be able to continue to work in the terminal. Alternatively to //NEdit// the [[http://www.vim.org/docs.php|vim]] editor may be used. The command The **&** is used to open the application in the background and to be able to continue to work in the terminal. Alternatively to //NEdit// the [[http://www.vim.org/docs.php|vim]] editor may be used. The command
 <code> <code>
-[<username>@l21 ~]$ vim <job_myjobname>        [+ return]+[<username>@l41 ~]$ vim <job_myjobname>        [+ return]
 </code> </code>
 calls the application //vim// and the file <job_myjobname> is opened if it exists already, otherwise it is created. //vim// in general has 2 different modi, one editing mode where you can write and a command mode.  calls the application //vim// and the file <job_myjobname> is opened if it exists already, otherwise it is created. //vim// in general has 2 different modi, one editing mode where you can write and a command mode. 
  • doku/win2vsc.1632908552.txt.gz
  • Last modified: 2021/09/29 09:42
  • by goldenberg