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 [2016/06/21 11:19] – [The job file: text editors on the Cluster] irdoku:win2vsc [2021/09/29 13:05] (current) – [The job file: text editors on the Cluster] goldenberg
Line 7: Line 7:
 ==== File transfer ==== ==== File transfer ====
  
-Files can be transferred to your home directory on the cluster using the tool [[https://filezilla-project.org|FileZilla]] which requires the following input (compare Figure 1.a): +Files can be transferred to your home directory on the cluster using the tool [[https://filezilla-project.org|FileZilla]]. Due to the two-factor identification, "quick connect" does not work and the connection has to be established by means of the site manager, the icon of which is located at the top left side of FileZilla (compare Figure 1.a). In the first window  
-  * server name (VSC 2: vsc2.vsc.ac.at, VSC 3: vsc3.vsc.ac.at), +  * server name (VSC 3: vsc3.vsc.ac.at, VSC4: vsc4.vsc.ac.at) 
-  * user name: which you have created on VSC,+  * port: 22 
 +  * user name: which you have created on VSC, and 
 +  * Logon Type needs to be set to: interactive 
 +have to be specified. After clicking the button "connect", you will be asked for the
   * password: which you have created on VSC,   * password: which you have created on VSC,
-  * port: 22.+  * and the OTP.
  
 Alternatively, you may use [[http://winscp.net/|winscp]], see also Figure 1.b: Alternatively, you may use [[http://winscp.net/|winscp]], see also Figure 1.b:
-  * host name (VSC 2: vsc2.vsc.ac.at, VSC 3: vsc3.vsc.ac.at),+  * host name (VSC 3: vsc3.vsc.ac.at, VSC4: vsc4.vsc.ac.at),
   * port: 22,   * port: 22,
-  * user name and password: can be skipped here and provided later.+  * user name and password can be skipped here and provided later together with the OTP. 
 +{{ :doku:win2cluster:filezilla_10.png |}} 
 + 
 +**Figure 1.a:** [[https://filezilla-project.org|FileZilla]]. VSC-3: vsc3.vsc.ac.at | VSC-4: vsc4.vsc.ac.at. 
 + 
 +{{ :doku:win2cluster:winscp.png |}} 
 + 
 +**Figure 1.b:** [[http://winscp.net/|winscp]]. 
 ==== Terminal connection ==== ==== Terminal connection ====
  
 A terminal connection to the cluster opens on your windows machine by taking advantage of the tool [[http://www.putty.org|PuTTY]]. PuTTY, compare Figure 2, requires  A terminal connection to the cluster opens on your windows machine by taking advantage of the tool [[http://www.putty.org|PuTTY]]. PuTTY, compare Figure 2, requires 
-  * host name (VSC 2: vsc2.vsc.ac.at, VSC 3: vsc3.vsc.ac.at),+  * host name (VSC 3: vsc3.vsc.ac.at, VSC 4: vsc4.vsc.ac.at),
   * port: 22,   * port: 22,
   * connection type: SSH,   * connection type: SSH,
-  * after clicking //open// you will be asked for your user name and password.+after clicking //open// you will be asked for your user name, password, and OTP.
  
 Here, the usual linux commands apply, e.g., Here, the usual linux commands apply, e.g.,
Line 35: 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:filezilla_5_text.png |}} +
- +
-**Figure 1.a:** [[https://filezilla-project.org|FileZilla]]. VSC-1: vsc1.vsc.ac.at | VSC-2: vsc2.vsc.ac.at | VSC-3: vsc3.vsc.ac.at. +
- +
-{{ :doku:win2cluster:winscp.png |}} +
- +
-**Figure 1.b:** [[http://winscp.net/|winscp]].+
  
 {{ :doku:win2cluster:putty.png |}} {{ :doku:win2cluster:putty.png |}}
  
 **Figure 2:** [[http://www.putty.org|PuTTY]]. **Figure 2:** [[http://www.putty.org|PuTTY]].
 +
  
  
 ==== 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.1466507962.txt.gz
  • Last modified: 2016/06/21 11:19
  • by ir