new file mode 100644

@@ -0,0 +1,169 @@

+---

+title: 'Logging In with FastX'

+media_order: 'fastx_login_200.png,fastx_login_1022.png,fastx_login_101.png,fastx_login_102.png,fastx_login_103.png,fastx_login_104.png,fastx_login_105.png,fastx_login_106.png,fastx_login_107.png,fastx_login_108.png,fastx_login_109.png,fastx_login_110.png,fastx_login_201.png,fastx_login_202.png,fastx_login_203.png,fastx_login_204.png,fastx_login_205.png,fastx_login_301.png'

+taxonomy:

+    category:

+        - docs

+visible: true

+published: true

+---

+

+[toc]

+

+## What is FastX?{#fastx}

+

+FastX is a X Window System that can connect to supercomputer systems using HTTPS (443/TCP).

+Communication traffic is suppressed by data compression technology and you can  use the system comfortably such as GUI-based application operations even in remote areas. 

+

+A web browser such as Google Chrome or Firefox is required to use remote access service of FastX.

+It is not necessary to install dedicated client software or plug-in for the web browser.

+

+<!--

+専用のクライアントソフト（Windows版）からの利用のほか、ブラウザから利用することも可能です。この場合はクライアントソフトのインストール不要でご利用できます。

+-->

+

+## Prerequisites{#before}

+

+* Generate a key pair by the procedure of  [Generating Key Pair and Registering Public Key](/login/pubkey), and then register a public key from [User Portal](https://web.kudpc.kyoto-u.ac.jp/portal/). Also, **the private key must be saved in OpenSSH format (PEM format prior to 7.7).** 

+* Compatible browsers：Edge, Firefox, Chrome

+        * Bidirectional copy-pasting is only supported by Chrome. With other browsers, you can only copy and paste from the server side to the client side.

+

+

+### Format of the Private Key{#format}

+

+FastX is not available in ECDSA and ED25519 format keys, so please use RSA format keys.

+The private key in OpenSSH 7.8 or later formats cannot be loaded.

+In OpenSSH 7.8 or later formats, the private key has the following contents.

+

+```nohighlight

+-----BEGIN OPENSSH PRIVATE KEY-----

+*************************************

+*************************************

+*************************************

+-----END OPENSSH PRIVATE KEY-----

+```

+

+To create a private key in OpenSSH 7.8 or earlier format with the ssh-keygen command, use the `-m pem` option as follows.

+

+```nohighlight

+$ ssh-keygen -t rsa -b 3072 -m pem

+```

+

+The private key in OpenSSH 7.8 or earlier format (PEM format) has the following contents.

+

+```nohighlight

+-----BEGIN RSA PRIVATE KEY-----

+Proc-Type: 4,ENCRYPTED

+DEK-Info: AES-128-CBC,7A30F993641D4093A373703A3F644D2D

+

+*************************************

+*************************************

+*************************************

+-----END RSA PRIVATE KEY-----

+```

+

+## How to Log in{#procedure}

+<!--

+### ブラウザの場合{#procedure_browser}

+-->

+1. Start your browser and go to one of the following addresses.

+

+    Destination | Address

+    ---------- | ------------

+    System B/C  | [https://laurel31.kudpc.kyoto-u.ac.jp/](https://laurel31.kudpc.kyoto-u.ac.jp/)

+    System G  | [https://gardenia11.kudpc.kyoto-u.ac.jp/](https://gardenia11.kudpc.kyoto-u.ac.jp/)

+    Application Server  | [https://app.kudpc.kyoto-u.ac.jp/](https://app.kudpc.kyoto-u.ac.jp/)

+<!--

+    camphor31  | [https://camphor31.kudpc.kyoto-u.ac.jp/](https://camphor31.kudpc.kyoto-u.ac.jp/)

+    camphor32  | [https://camphor32.kudpc.kyoto-u.ac.jp/](https://camphor32.kudpc.kyoto-u.ac.jp/)

+    lauerl31  | [https://laurel31.kudpc.kyoto-u.ac.jp/](https://laurel31.kudpc.kyoto-u.ac.jp/)

+    lauerl32  | [https://laurel32.kudpc.kyoto-u.ac.jp/](https://laurel32.kudpc.kyoto-u.ac.jp/)

+    lauerl33  | [https://laurel33.kudpc.kyoto-u.ac.jp/](https://laurel33.kudpc.kyoto-u.ac.jp/)

+    gardenia11 | [https://gardenia11.kudpc.kyoto-u.ac.jp/](https://gardenia11.kudpc.kyoto-u.ac.jp/)

+    gardenia12 | [https://gardenia12.kudpc.kyoto-u.ac.jp/](https://gardenia12.kudpc.kyoto-u.ac.jp/)

+    gardenia13 | [https://gardenia13.kudpc.kyoto-u.ac.jp/](https://gardenia13.kudpc.kyoto-u.ac.jp/)

+    gardenia14 | [https://gardenia14.kudpc.kyoto-u.ac.jp/](https://gardenia14.kudpc.kyoto-u.ac.jp/)

+

+    なお、https://laurel.kudpc.kyoto-u.ac.jp/ や https://camphor.kudpc.kyoto-u.ac.jp/ 、https://gardenia.kudpc.kyoto-u.ac.jp/ （DNSラウンドロビンアドレス）にアクセスしても接続できますが、ブラウザのDNSキャッシュの更新タイミングで接続が切れる可能性があります。

+-->

+    

+2.  **（First time only）** Click "Manage Private Keys". A small window prompting you to upload the private key opens. Click "+" and select the private key of the **OpenSSH format**.

+    ![](01_pubkey_management.png?lightbox=100%&resize=600)

+    ![](02_add_pubkey.png?lightbox=100%&resize=600)

+

+3.  **（First time only）** Check that the name of the uploaded private key is displayed in the blue frame and click 'Done'. 

+    ![](03_select_pubkey.png?lightbox=100%&resize=600)

+

+4. Enter the user ID in the blue frame and click 'SSH Login'. 

+    ![](04_login.png?lightbox=100%&resize=600)

+

+5. Enter the passphrase in the blue frame and click 'Submit'.

+    ![](05_login_input_password.png?lightbox=100%&resize=600)

+

+6. To launch a new desktop screen or terminal, click on '+'.

+    ![](06_new_session.png?lightbox=100%&resize=600)

+

+7. To use the desktop screen, double-click 'GNOME' in the blue frame; to use the terminal, double-click 'GNOME terminal' in the green frame. 

+    ![](07_choose_app.png?lightbox=100%&resize=600)

+

+8. If a new tab opens and the desktop screen or terminal is displayed, the login will be successful.

+Please note that the password used to lock the GNOME Desktop screen is the password of the user portal (not the passphrase for the private key).

+    ![](08_gnome_desktop.png?lightbox=100%&resize=600)

+    ![](09_gnome_terminal.png?lightbox=100%&resize=600)

+

+9. By default, the keyboard layout is set to 'Japanese'. To set it to another language, pull down the tabs on the screen and click on the keyboard symbol.

+    ![](10_select_keyboard.png?lightbox=100%&resize=600)

+

+10. Change Layout to the desired language.

+    ![](11_change_keyboard.png?lightbox=100%&resize=600)

+

+<!--

+### クライアントソフトの場合(Windows){#procedure_clientsoft}

+

+1. Windowsの場合は[Pageant](/install/pageant)を起動し、秘密鍵を登録しておきます。

+2. FastX アイコンをクリックして、FastX を起動します。

+3. FastX の起動ウィンドウが開いたら、左上の「＋」アイコンをクリックします。

+    ![](fastx_login_206.png)

+4. Edit Connection ウインドウで、`ssh`を選択し、「Host」に `laurel.kudpc.kyoto-u.ac.jp` , 「User」に利用者番号、「Name」に`laurel` を入力し、「OK」をクリックします。

+    ![](fastx_login_207.png)

+5. 登録された`laurel`をダブルクリックします。

+    ![](fastx_login_208.png)

+6. laurelに接続成功すると、以下の画面が現れますので、左上の「＋」アイコンをクリックします。

+    ![](fastx_login_209.png)

+7. デスクトップを使う場合は「GNOME Desktop」をダブルクリック、ターミナルを使う場合は「GNOME terminal」をダブルクリックします。

+    ![](fastx_login_210.png)

+8. desktopまたはターミナルが表示されればログイン成功です。

+

+### クライアントソフトの場合(Mac){#procedure_clientsoft_mac}

+

+ログインの操作はWindows版と同様です。

+なお、起動時に下記の表示が出た場合は、FastXアイコンをFinderで表示し、Controlキーを押しながらアイコンをクリックして、ショートカットメニューから「開く」を選択してください。

+![](fastx_login_200.png?lightbox=100%&resize=600)

+参考情報：[https://support.apple.com/ja-jp/guide/mac-help/mh40616/mac](https://support.apple.com/ja-jp/guide/mac-help/mh40616/mac)

+-->

+

+## Notes{#notice}

+

+### The number of Simultaneous Sessions{#max_num_session}

+

+When one user uses multiple sessions at the same time (opens desktop or terminal), only one license is consumed on the same login node, but when sessions are opened from different login nodes, the corresponding licenses are consumed. The number of licenses that can be used by one user is set to 3. If you try to open more sessions, a notice indicating lack of license is displayed.

+

+### Session Timeout{#timeout}

+

+With FastX, the session is maintained even after disconnecting, and the user can reconnect. However, please note that the session will be automatically deleted after 2 days without reconnecting after disconnecting.

+

+<!--

+### GNOME Desktopからのログアウトについて{#desktop}

+

+GNOME Desktopからのログアウトは、画面右上の電源マークを押し、出てきたメニューの中からユーザ名を押して、「Log Out」からログアウトしてください。セッションが不要になった場合は、なるべくログアウトをお願いします。なお、電源オプションからのログアウトはできません。

+

+![](fastx_login_301.png?lightbox=100%&resize=600)

+-->

+

+## References{#fyi}

+### Client Software{#client}

+Client software is distributed on [the developer's official website](https://www.starnet.com/download/fastx-client).

+Please use it if necessary.

+

+The communication protocol used by the user should be **SSH**.

+Also, password authentication is not available, so an SSH agent (such as  [Pageant](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) that is included in Putty for Windows or ssh-agent for macOS and Linux) is required.

@@ -74,6 +74,7 @@ DEK-Info: AES-128-CBC,7A30F993641D4093A373703A3F644D2D

     ---------- | ------------

     システムB/C  | [https://laurel31.kudpc.kyoto-u.ac.jp/](https://laurel31.kudpc.kyoto-u.ac.jp/)

     システムG  | [https://gardenia11.kudpc.kyoto-u.ac.jp/](https://gardenia11.kudpc.kyoto-u.ac.jp/)

+    アプリケーションサーバ | [https://app.kudpc.kyoto-u.ac.jp/](https://app.kudpc.kyoto-u.ac.jp/)

 <!--

     camphor31  | [https://camphor31.kudpc.kyoto-u.ac.jp/](https://camphor31.kudpc.kyoto-u.ac.jp/)

     camphor32  | [https://camphor32.kudpc.kyoto-u.ac.jp/](https://camphor32.kudpc.kyoto-u.ac.jp/)

@@ -1,21 +1,21 @@

 ---

-title: 'For Users of the Previous System'

+title: 'For Users of the Previous Systems'

 taxonomy:

     category:

         - docs

 ---

-This information is for users to migrate the previous system to the new system replaced in fiscal 2016.

- 

 [toc]

+This information is for users to migrate the previous system to the new system replaced in fiscal 2022.

+

 ## Host Name and How to Log In{#login}

-There are no changes from the previous system in the host name (round robin) and how to log in. If you want to log in to the login node directly without going through the round robin, please refer to [how to connect to the system](/login#fqdn-1)  because the specific host name has been changed ( IP address is not changed).

+There are no changes from the previous system in the host name (round robin) and how to log in. 

+If you want to log in to the login node directly without going through the round robin, please refer to [Access](/login)  because the specific host name has been changed.

 ### If you encountered an error when login{#login_error}

-

-If you use the Portforwarder or PuTTY terminal and cannot connect to the supercomputer with the following message, you must delete the known_hosts information.

+If the following message appears and you cannot log in, you need to delete the known_hosts information.

 ```nohighlight

 @@@  WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!   @@@

@@ -33,178 +33,204 @@ requested strict checking.

 Host key verification failed.

 ```

-Please delete the known_host information with the following instruction.

-

-

-#### Windows

-

-** if you use Portforwarder **

-

-The known_hosts file exists in the directory the Portforwarder has been installed.

-All you have to do is to delete the known_hosts file.

-

-** if you use PuTTY **

-

-The known_hosts information is in the registry.

-You can delete the  known_hosts information by the accessory tool of PuTTY.

-

-* Open a command prompt window, then use cd command to move to the directory PuTTY has been installed.

-* Type "putty -cleanup", then the known_hosts is deleted.

-

-

-

-#### Mac

-

-You can delete the known_hosts information with one of the following methods.

-

- * ssh-keygen command: type the following commands on the terminal

-

-    ````nohighlight

-        ssh-keygen -R camphor.kudpc.kyoto-u.ac.jp

-        ssh-keygen -R laurel.kudpc.kyoto-u.ac.jp

-    ````

-

-* edit known_hosts file

-

-    Open /Users/(user name)/.ssh/known_hosts by an editor app,  then delete the content.

-

-#### Linux

-

-You can delete the known_hosts information with one of the following methods.

-

-* ssh-keygen command: type the following commands one the terminal

-

-    ````nohighlight

-        ssh-keygen -R camphor.kudpc.kyoto-u.ac.jp

-        ssh-keygen -R laurel.kudpc.kyoto-u.ac.jp

-    ````

-    

-* edit known_hosts file

-

-    Open the known_hosts file by an editor app.  Usually the file exists on /home/(user name)/.ssh directory.  Then, delete the content.

-

-## Logging In With Exceed onDemand{#eod}

-

-When logging in to the system with Exceed onDemand, port number of port forwarding has been changed.

-

-For how to log in with Exceed onDemand, see [Logging In With Exceed onDemand](/login/eod)

-

-System|Previous port number|New port number

--|-|-

-A|5500|5501

-B,C|5500|5500 (Not changed)

-Private Cluster|5500|5509

-

-

-

-## Data migration {#mv_data}

+You can delete the known_host information with the following instruction.

+#### Terminal{#terminal}

+* Use the ssh-keygen command<br>

+* (Example) Delete known_hosts in laurel

+```nohighlight

+$ ssh-keygen -R laurel.kudpc.kyoto-u.ac.jp

+```

+*  Edit the known_host file directly. 

+1. Open the file `%homepath%\.ssh\known_hosts` (Windows), `/Users/(username)/.ssh/known_hosts` (Mac, Linux) using an editor.

+3. Delete and save the contents.

+

+#### MobaXterm{#mobaxterm}

+1. Exit MobaXterm.

+2. Open `%appdata%\MobaXterm\MobaXterm.ini` in an editor.

+3.  Delete the information for the relevant host in [SSH_Hostkeys]. 

+```nohighlight

+ssh-ed25519@22:laurel.kudpc.kyoto-u.ac.jp=0xd152edcd(omitting the following)

+```

+4. Start MobaXterm.

+

+## How to initialize $HOME/.bashrc{#bashrc}

+The configuration of modules, location of applications and environment variables have changed since the previous system.

+If you used a customized .bashrc in the previous system, please modify the .bashrc as necessary.<br>

+You can also initialize the .bashrc by copying /etc/skel/.bashrc to your home directory as follows.<br>

+If you cannot log in, please let us know using the [Inquiries Form](https://www.iimc.kyoto-u.ac.jp/en/inquiry/?q=consult), and we will initialize the shell configuration file with administrator privileges.

+* When you copy /etc/skel/.bashrc to your home directory.

+```nohighlight

+$ cp /etc/skel/.bashrc $HOME

+```

-User data that had been saved in the previous system was migrated automatically and the absolute path was not changed. 

+## $HOME/.ssh directory{#ssh}

+From the new system, we have changed the operation to manage SSH public keys all together in the user portal. Accordingly, the .ssh directory in the home directory ($HOME) has been moved under $HOME/DOTFILES_20221108/. If you do not need it, please delete it.

+## Data migration{#mv_data}

-In accordance with the system replacement, the capacity of the home directory and the large volume disk (LARGE) of the system E is increased.

+User data that had been saved in the previous system was migrated automatically.

+<!--

+ホームディレクトリの容量は100GBです。パーソナル/グループ/専用クラスタの容量は、2022年度は前システムの容量を継承します。2023年度以降は大型計算機システム利用負担金規程の通りです。

-Directory|Capacity of the previous system|Capacity of new system

+ディレクトリ|前システムの容量|新システムの容量

 ---------|----------------|---------------

-Home directory    |30GB            |100GB

-Large volume disk(Personal Course)   |1TB|2TB

+ホームディレクトリ    |100GB            |100GB

+大容量ストレージ(パーソナルコース)   |3TB|8TB

-The capacity of the large volume disk follows the following formula.

+グループコースの大容量ストレージの容量は、以下の計算式に従います。

-**System A,B**

+**システムA,B**

-Type      |Capacity of the previous system|Capacity of new system

+タイプ     |前システムの容量   |新システムの容量

 ----------|------------------|----------------

-Third priority|1.2TB x  contract number of nodes|3.6TB x  contract number of nodes

-Second priority  |2.0TB x  contract number of nodes|6.0TB x  contract number of nodes

-Top priority  |2.0TB x  contract number of nodes|6.0TB x  contract number of nodes

+準々優先 | - | 6.4TB x 契約ノード数

+準優先  　|3.6TB x 契約ノード数|9.6TB x 契約ノード数

+優先　    |6.0TB x 契約ノード数|16.0TB x 契約ノード数

+占有　    |6.0TB x 契約ノード数|16.0TB x 契約ノード数

-**System C**

+**システムC**

-Type      |Capacity of the previous system|Capacity of new system

+タイプ     |前システムの容量   |新システムの容量

 ----------|------------------|----------------

-Third priority|1.2TB x  contract number of nodes|14.4TB x  contract number of nodes

-Second priority  |2.0TB x  contract number of nodes|24TB x  contract number of nodes

+準々優先 | - | 6.4 x 契約ノード数

+優先　    |24TB x 契約ノード数|16TB x 契約ノード数

-For the configuration of the file system of the new system, see [Using File System](/filesystem).

-

-

-## Process Limit of Login Nodes{#process_limit}

-

-The limit of CPU time and memory amount in the login nodes are extended to reduce a possibility of unintentional abortion of file transaction, etc.

+**システムG**

+タイプ     |前システムの容量   |新システムの容量

+----------|------------------|----------------

+準々優先 | - | 6.4 x 契約ノード数

+優先　    | - |16TB x 契約ノード数

+-->

+### Large Volume Storage (LARGE){#large}

+/LARGE2 has been consolidated into /LARGE0 and /LARGE3 into /LARGE1. We configure that you can link to /LARGE0 from /LARGE2 and link to /LARGE1 from /LARGE3 with the existing path, however the configuration will be removed in the future, so please update your path.

-System  | CPU Time(normal) | CPU Time(maximum) | Memory(normal)

-Previous system | 1 hour        | 20 hours       | 2GB          

-New system | 4 hour        | 24 hours        | 4GB          

+In addition, quota management for large volume  storage has been changed from Group Quota to Project Quota.

+As a result, capacity is managed in the unit of paths of the large volume storage group, not the group to which the file belongs.

-## System Compatibility{#compatibility_incompatibility}

+For details on the file system configuration of the new system, please refer to  [Use of Storage](/filesystem).

-<!-- in preparation

-### Application Software{#application}

-The new system has made the following changes to the application software.

+## Process limit of login node{#process_limit}

+CPU time and the amount of memory for each system's login node is extended in order to avoid interruptions during file transfers to PCs.

-#### **Newly provided application software**

+System  | CPU time (standard)| CPU time (maximum) |  Amount of memory (standard)

+-------- | ------------- | ------------- | -------------

+Previous system | 4 hours      | 24 hours   | 8GB          

+New system |4 hours | 24 hours | 16GB

+## Changes{#compatibility_incompatibility}

-* [Allinea MAP/DDT](/compilers/allinea-map-ddt)

+### OS

+The OS will be changed from CLE/RHEL 7 to RHEL 8.

 ### Compilers and Libraries{#compiler}

-* The compiler continue to provide Cray, Intel, PGI and GNU.

-

-* In the new system, ACML library is not available.

-

-* Since the new system does not support GPU, GPU-related CUDA C, CUDA Fortran and OpenACC are not available.

-

+Compilers will be provided for Intel, NVIDIA HPC SDK, and GNU. The Cray compiler will no longer be provided.

 ### Batch Job Scheduler{#lsf}

+The job scheduler will be changed from PBS to Slurm.

+

 #### Comparisons of Job Script Options

-Purpose| LSF | PBS 

+Purpose| PBS | Slurm 

 :--------------:|:-------------:|:-------------:

-Specify the queue for submitting a job.|-q _QUEUENAME_ |Not changed　

-Specify the execution group. | -ug _GROUPNAME_ | Not changed

-Specify running elapse time for batch-requests | -W _HOUR_ : _MIN_ | Not changed

-\* Establish per-request Vnodes limits <br>\* Establish per-vnode thread limit <br>\* Establish per-vnode CPUS limit  <br>\* Establish per-vnode/per-cpu normal_page memory limits |-A p=_X_:t=_X_:c=_X_:m=_X_ | Not changed 

- Direct stdout output to the stated destination  | -o _FILENAME_ | Not changed

- Direct stderr output to the stdout destination| -e _FILENAME_| Not changed

-Merge stderr output and stdout output |-o | **-j oe(output to STDOUT) / eo(output to STDERR)**

-Send mail |-B/-N| **-m a(in job abortion) / b(in beginning job) / e(in ending job)**

-Send mail for the batch request to the stated user |-u _MAILADDR_|**-M** _MAILADDR_ 

- Declare that batch request is not re-runnable |-rn | **-r n (A space character is needed between r and n.)**

+ Specify the queue to submit jobs|-q _QUEUENAME_ | -p _QUEUENAME_

+ Specify the execution group | -ug _GROUPNAME_ | Not required

+ Specify the elapsed time limit | -W _HOUR_ : _MIN_ | -t _HOUR_:_MIN_

+・ Specify the number of processes <br>・ Specify the number of threads per process<br>・ Specify the number of CPU cores per process<br>・ Specify the memory size per process |-A p=_X_:t=_X_:c=_X_:m=_X_ | --rsc p=_X_:t=_X_:c=_X_:m=_X_ 

+ Specify the standard output file name | -o _FILENAME_ | Not changed

+ Specify standard error output file name| -e _FILENAME_| Not changed 

+Summarize standard error output | -j oe(Output to standard output) / eo(Output to standard error) | Not changed

+Send Email|-m a(when a job interrupted) / b(When started) / e(When ended) | --mail-type=BEGIN(When started)/END(when ended)/FAIL(When a job interrupted)/REQUEUE(when re-executed)/ALL(All)

+Specify email address|-M _MAILADDR_ | --mail-user=_MAILADDR_

+Specify prohibition of job re-execution when failure occurs | -r n | --no-requeue

-#### Comparisons of Job Commands

+#### Comparison of job-related commands

-Purpose| LSF | PBS

+Purpose| PBS | Slurm

 :-----------------------:|:-----------------------------:|:-----------------------------:

-Check available queues  | qstat|**qstat -q**

-Submit a job | qsub |Not changed

-Check job status  |qjobs | **qstat**

-Cancel a submitted job  | qkill| **qdel**

-View a user’s own Job |qs | Not changed

+Check the queue where jobs can be submitted | qstat -q | spartition

+Submit a job to the queue| qsub | sbatch

+Check job status |qstat | squeue

+Cancel a submitted job. | qdel | scancel

+Check job details|qs | sacct -l

+

+

 #### Comparisons of Environment Variables 

-Purpose | LSF| PBS

+Purpose | PBS | Slurm

 :--------------------------:|:------------------------------------------:|:--------------------------------------:

-Job request identifier  | LSB_JOBID |**QSUB_JOBID**

-Batch queue name | LSB_QUEUE | **QSUB_QUEUE**

-Current directory of job submission | LSB_SUBCWD |**QSUB_WORKDIR**

-Number of assigned processes when submitting a job|LSB_PROCS| **QSUB_PROCS**

-Number of threads per assigned process when submitting a job | LSB_THREADS| **QSUB_THREADS**

-Number of CPUs per assigned process when submitting a job | LSB_CPUS | **QSUB_CPUS**

-Memory limit per assigned process  |LSB_MEMORY | **QSUB_MEMORY**

-Number of processes per node when executing jobs | LSB_PPN | **QSUB_PPN**

- 

+ Job ID | QSUB_JOBID | SLURM_JOBID

+ Name of the queue where the job was submitted| QSUB_QUEUE | SLURM_JOB_PARTITION

+ Current directory where the job was submitted| QSUB_WORKDIR | SLURM_SUBMIT_DIR

+ Number of processes allocated when executing a job|QSUB_PROCS | SLURM_DPC_NPROCS

+ Number of threads allocated per process when executing a job| QSUB_THREADS | SLURM_DPC_THREADS

+ Number of CPU cores allocated per process when executing a job| QSUB_CPUS | SLURM_DPC_CPUS

+ Upper limit for the amount of memory allocated per process when executing a job |QSUB_MEMORY|ー

+ Number of processes placed per node when executing a job | QSUB_PPN | ー

+

+## Job Script Conversion{#pbs2slurm}

+You can convert job script commands and options used in the PBS environment for Slurm with the **pbs2slurm** command.

+

+#### Format

+```nohighlight

+pbs2slurm input_script [output_script]

+```

+

+#### Examples

+```nohighlight

+[b59999@camphor1 script]$ cat pbs.sh

+#!/bin/bash

+#======Option========

+#QSUB -q gr19999b

+#QSUB -A p=1:t=1:c=1:m=1G

+#QSUB -W 12:00

+#QSUB -r n

+#QSUB -M kyodai.taro.1a@kyoto-u.ac.jp

+#QSUB -m be

+#====Shell Script====

+mpiexec.hydra ./a.out

+

+[b59999@camphor1 script]$ pbs2slurm pbs.sh slurm.sh

+

+[b59999@camphor1 script]$ cat slurm.sh

+#!/bin/bash

+#======Option========

+#SBATCH -p gr19999b

+#SBATCH --rsc p=1:t=1:c=1:m=1G

+#SBATCH -t 12:00

+#SBATCH --no-requeue

+#SBATCH --mail-user=kyodai.taro.1a@kyoto-u.ac.jp

+#SBATCH --mail-type=BEGIN,END

+#====Shell Script====

+srun ./a.out

+```

+

+#### Options for conversion

+The pbs2slurm command supports conversion of the following options.

+Options not included below should be modified individually.

+

+| Before conversion | After conversion | Purpose |

+|------- | ------ | -------|

+|#QSUB -q | #SBATCH -p | Specify queues |

+|#QSUB -A | #SBATCH --rsc | Specify resources|

+|#QSUB -W | #SBATCH -t | Specify elapsed time|

+|#QSUB -N | #SBATCH -J | Specify job name|

+|#QSUB -o | #SBATCH -o | Specify the destination for standard output|

+|#QSUB -e | #SBATCH -e | Specify the destination for standard error output|

+|#QSUB -m | #SBATCH --mail-type | Specify the timing of email sending|

+|#QSUB -M | #SBATCH --mail-user | Specify the recipient of the email|

+|#QSUB -r n | #SBATCH --no-requeue | prohibition of job re-execution |

+|#QSUB -J | #SBATCH -a | Specify array job|

+|mpiexec | srun | MPI Execution(If there is a option, it must be removed manually.)|

+|mpiexec.hydra | srun | MPI Execution(If there is a option, it must be removed manually.)|

@@ -21,6 +21,7 @@ Option                     |           Description

 --rsc p=_PROCS_:t=_THREADS_:c=_CORES_:m=_MEMORY_ <br> or <br> --rsc g=_GPU_ | Specify the amount of job-allocated resources. For more details, [click here](/run/resource#resouce) | tssrun -p gr19999b --rsc p=4:t=8:c=8:m=2G ./a.out <br> or <br> tssrun -p gr19999b --rsc g=1 ./a.out

 --x11                          | Execute GUI program on computing nodes        | tssrun -p gr19999b --x11 xeyes

+* The part *gr19999b* in the example must be changed to your own queue name.

 * Wen you enter the command, several messages are displayed, then the program begins execution and the results are displayed.

 * If the computing nodes for interactive execution are congested, execution may not start immediately after the message is displayed.

 * Interactive execution with queue for personal and group courses is also available. 

@@ -153,8 +153,7 @@ Available /tmp capacity in the cloud system is obtained by `Number of processes

 For example, if you submit a job with 4 processes (8 cores per process), you will be allocated **3,008GB** from `4 x 8 x 94`.

-## Supplemental information on storage access for cloud system

-{#supplemental}

+## Supplemental information on storage access for cloud system{#supplemental}

 ### Access to home directories and large volume storage{#storage}

 In the cloud system, the files can be accessed with the same PATH since the home directory ($HOME) and large volume storage (/LARGE) are mounted in the same way as on-premise systems such as system B.