... | ... |
@@ -19,12 +19,6 @@ If you have any questions or concerns, please contact us using the [Inquiry Form |
19 | 19 |
|
20 | 20 |
For information on system maintenance, failures, etc., please refer to [Information on IIMC](https://www.iimc.kyoto-u.ac.jp/en/whatsnew/). |
21 | 21 |
|
22 |
-### Notice(Apr. 04, 2023) |
|
23 |
-Changes due to maintenance work at the end of March 2023 |
|
24 |
-* Removed System D/E manuals |
|
25 |
-* Moved Cloud System manuals from "Other" to "Job Execution |
|
26 |
-* Expansion of English-enabled pages |
|
27 |
- |
|
28 | 22 |
### Table of Contents |
29 | 23 |
{% for p in page.collection %} |
30 | 24 |
* [{{ p.menu|e }}](https://web.kudpc.kyoto-u.ac.jp{{p.link}}) |
... | ... |
@@ -21,13 +21,6 @@ menu: システムの使い方 |
21 | 21 |
|
22 | 22 |
システムのメンテナンス情報、障害情報等は、[情報環境機構のお知らせ](https://www.iimc.kyoto-u.ac.jp/ja/whatsnew/)をご参照ください。 |
23 | 23 |
|
24 |
-### お知らせ(2023/04/04) |
|
25 |
- |
|
26 |
-2023年3月末の保守作業に伴う変更点 |
|
27 |
-- システムD/Eのマニュアルを削除 |
|
28 |
-- クラウドシステムのマニュアルを「その他」から「ジョブ実行」に移動 |
|
29 |
-- 英語化ページの拡大 |
|
30 |
- |
|
31 | 24 |
### 目次 |
32 | 25 |
{% for p in page.collection %} |
33 | 26 |
* [{{ p.menu|e }}](https://web.kudpc.kyoto-u.ac.jp{{p.link}}) |
34 | 27 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,210 @@ |
1 |
+--- |
|
2 |
+title: 'Modules - a tool for setting up' |
|
3 |
+taxonomy: |
|
4 |
+ category: |
|
5 |
+ - docs |
|
6 |
+--- |
|
7 |
+ |
|
8 |
+[toc] |
|
9 |
+ |
|
10 |
+ |
|
11 |
+## Modules Overview{#overview} |
|
12 |
+ |
|
13 |
+The Modules software package can dynamically switch and configure the environment settings required to use the compiler, library, and application by executing the module command. |
|
14 |
+The module command allows you to easily change environment settings for each different versions of compilers, libraries, and applications. |
|
15 |
+ |
|
16 |
+ |
|
17 |
+## How to Use{#usage} |
|
18 |
+ |
|
19 |
+ |
|
20 |
+### Basic Operation of the Module Command {#basic} |
|
21 |
+| Command | Purpose | |
|
22 |
+|--- |--- | |
|
23 |
+| module list | Display all loaded module files. | |
|
24 |
+| module avail | Display all available module files. | |
|
25 |
+| module show [module_file_name] | Display the module file settings. | |
|
26 |
+| module load [module_file_name] | Load the module files. | |
|
27 |
+| module unload [module_file_name] | Unload the module files. | |
|
28 |
+| module switch [module_file_name1] [module_file_name2] |Switch the module files. (module_file_name1→module_file_name2) | |
|
29 |
+ |
|
30 |
+### Forced switching that ignore module file dependencies |
|
31 |
+ |
|
32 |
+Module load / unload / switch errors may occur due to dependencies between module files. |
|
33 |
+If you are aware of the possibility of errors in dependencies, you can force module files to load or switch by using -f option. |
|
34 |
+ |
|
35 |
+```bash |
|
36 |
+## Status immediately after login |
|
37 |
+$ module list |
|
38 |
+Currently Loaded Modulefiles: |
|
39 |
+ 1) slurm/2022 2) SysB/2022 3) intel/2022.3(default) 4) intelmpi/2022.3(default) 5) PrgEnvIntel/2022(default) |
|
40 |
+ |
|
41 |
+## When trying to switch intel compiler to 2018.4, error occurs. |
|
42 |
+$ module switch intel/2018.4 |
|
43 |
+Unloading intel/2022.3 |
|
44 |
+ ERROR: intel/2022.3 cannot be unloaded due to a prereq. |
|
45 |
+ HINT: Might try "module unload PrgEnvIntel/2022" first. |
|
46 |
+ |
|
47 |
+Switching from intel/2022.3 to intel/2018.4 |
|
48 |
+ ERROR: Unload of switched-off intel/2022.3 failed |
|
49 |
+ |
|
50 |
+ using |
|
51 |
+## Forced switching using -f option |
|
52 |
+$ module switch intel/2018.4 -f |
|
53 |
+Unloading intel/2022.3 |
|
54 |
+ WARNING: Dependent 'PrgEnvIntel/2022' is loaded |
|
55 |
+ |
|
56 |
+## Status after change |
|
57 |
+$ module list |
|
58 |
+Currently Loaded Modulefiles: |
|
59 |
+ 1) slurm/2022 2) SysB/2022 3) intelmpi/2022.3(default) 4) PrgEnvIntel/2022(default) 5) intel/2018.4 |
|
60 |
+ |
|
61 |
+``` |
|
62 |
+ |
|
63 |
+ |
|
64 |
+### How to Use Compiler and Library{#compiler} |
|
65 |
+ |
|
66 |
+#### Checking the loaded module files |
|
67 |
+ |
|
68 |
+We provide following three types of comprehensive modules file sets for each programming environment. |
|
69 |
+These module files provide initial settings for the compiler environment and the MPI environment. |
|
70 |
+ |
|
71 |
+- Intel programming environment (standard environment for system A/B/C/D/E) : PrgEnvIntel |
|
72 |
+- NVIDIA HPC SDK programming environment (standard environment for system G) : PrgEnvNvidia |
|
73 |
+- GNU programming environment : PrgEnvGCC |
|
74 |
+ |
|
75 |
+Please use `module list` command to check the current module environment. |
|
76 |
+ |
|
77 |
+```bash |
|
78 |
+$ module list |
|
79 |
+Currently Loaded Modulefiles: |
|
80 |
+ 1) XXX |
|
81 |
+``` |
|
82 |
+ |
|
83 |
+#### Switching a programming environment |
|
84 |
+ |
|
85 |
+The system is the main compiler environment when logging in. |
|
86 |
+An example of switching programming environments is provided below. |
|
87 |
+ |
|
88 |
+**Example: Switching from an Intel environment to an NVIDIA environment** |
|
89 |
+ |
|
90 |
+```nohighlight |
|
91 |
+$ module switch PrgEnvIntel PrgEnvNvidia |
|
92 |
+``` |
|
93 |
+ |
|
94 |
+#### How to switch compiler versions |
|
95 |
+ |
|
96 |
+If multiple versions are available, you can switch the compiler version to be used. |
|
97 |
+The following is an example of how to operate for the intel compiler. |
|
98 |
+ |
|
99 |
+**Example: Switching between prepared programming environments** |
|
100 |
+ |
|
101 |
+```nohighlight |
|
102 |
+$ module switch PrgEnvIntel/2022 PrgEnvIntel/2018 |
|
103 |
+``` |
|
104 |
+ |
|
105 |
+**Example: When you load another version of the Intel compiler additionally (the later loaded version takes priority)** |
|
106 |
+```nohighlight |
|
107 |
+$ module load intel/Y.Y |
|
108 |
+``` |
|
109 |
+ |
|
110 |
+**Example: When you switch Intel compiler versions individually (-f is required)** |
|
111 |
+```nohighlight |
|
112 |
+$ module switch intel/X.X intel/Y.Y -f |
|
113 |
+``` |
|
114 |
+ |
|
115 |
+The description of the currently loaded version (intel/X.X in the above example) can be omitted. |
|
116 |
+ |
|
117 |
+```nohighlight |
|
118 |
+$ module switch intel/Y.Y -f |
|
119 |
+``` |
|
120 |
+ |
|
121 |
+### How to Use Application With Modules{#application} |
|
122 |
+ |
|
123 |
+**Example of using MATLAB** |
|
124 |
+ |
|
125 |
+Execute the module command to make a environment settings. (Load the module files of any version you want.) |
|
126 |
+ |
|
127 |
+ |
|
128 |
+```nohighlight |
|
129 |
+$ module load matlab/R2020b |
|
130 |
+``` |
|
131 |
+ |
|
132 |
+It will be able to execute MATLAB startup commands. |
|
133 |
+ |
|
134 |
+```nohighlight |
|
135 |
+$ matlab |
|
136 |
+``` |
|
137 |
+ |
|
138 |
+**Switching the version of MATLAB(R2020b→R2021a)** |
|
139 |
+ |
|
140 |
+Execute the module command to change a environment settings. |
|
141 |
+ |
|
142 |
+ |
|
143 |
+```nohighlight |
|
144 |
+$ module unload matlab/R2020b |
|
145 |
+$ module load matlab/R2021a |
|
146 |
+または |
|
147 |
+$ module switch matlab/R2021a |
|
148 |
+``` |
|
149 |
+For how to use the modules with other applications, please refer to [Available Software](/software). |
|
150 |
+ |
|
151 |
+ |
|
152 |
+## Creating/Adding a Module file{#add_module} |
|
153 |
+ |
|
154 |
+You can create and use your own module files for your convenience. |
|
155 |
+For details on how to create a module file, please refer to [man page](http://modules.sourceforge.net/man/modulefile.html). To use your customized module file, specify the directory where your module file is stored to the module use command and add the path. To delete the previously-added path, execute the module unuse command. You can check the path of module files using the environment variable MODULEPATH. |
|
156 |
+ |
|
157 |
+**Example: Checking the path of module files** |
|
158 |
+ |
|
159 |
+```nohighlight |
|
160 |
+## Make the created module file available (for user of x12345) |
|
161 |
+$ module use /home/x/x12345/mymodule |
|
162 |
+ |
|
163 |
+## Check the path of the module file |
|
164 |
+$ echo $MODULEPATH |
|
165 |
+/home/x/x12345/mymodule:/opt/app/modulefiles/common: |
|
166 |
+/opt/system/app/env/intel/isv: |
|
167 |
+/opt/system/app/env/intel/oss: |
|
168 |
+ |
|
169 |
+## Delete the path you added |
|
170 |
+$ module unuse /home/x/x12345/mymodule |
|
171 |
+ |
|
172 |
+## Make the created module file available with a lower priority than the original path |
|
173 |
+$ module use -a /home/x/x12345/mymodule |
|
174 |
+ |
|
175 |
+## Check the path of the module file |
|
176 |
+$ echo $MODULEPATH |
|
177 |
+/opt/app/modulefiles/common:/opt/system/app/env/intel/isv: |
|
178 |
+/opt/system/app/env/intel/oss: |
|
179 |
+/home/x/x12345/mymodule: |
|
180 |
+``` |
|
181 |
+ |
|
182 |
+**Example: Adding and using a module file** |
|
183 |
+ |
|
184 |
+```nohighlight |
|
185 |
+## Check the created module file |
|
186 |
+$ ls -F /home/x/x12345/mymodule |
|
187 |
+ruby/ |
|
188 |
+$ ls -F /home/x/x12345/mymodule/ruby |
|
189 |
+1.8.7 1.9.3 2.1.2 |
|
190 |
+ |
|
191 |
+## Make the created module file available |
|
192 |
+$ module use /home/x/x12345/mymodule |
|
193 |
+ |
|
194 |
+## Check that the created module file is displayed |
|
195 |
+$ module avail |
|
196 |
+--------------------------- /home/x/x12345/mymodule/ --------------------------- |
|
197 |
+ruby/1.8.7 ruby/1.9.3 ruby/2.1.2 |
|
198 |
+------------------------- /opt/system/app/intel/ -------------------------- |
|
199 |
+PrgEnvIntel/2022 intel/2022.3 |
|
200 |
+(Omitted) |
|
201 |
+ |
|
202 |
+## Load the created module file |
|
203 |
+$ module load ruby/2.1.2e |
|
204 |
+``` |
|
205 |
+ |
|
206 |
+## Links{#link} |
|
207 |
+ |
|
208 |
+[Welcome to the Environment Modules Project](http://modules.sourceforge.net/) |
|
209 |
+[Man page of Modulefile](http://modules.sourceforge.net/man/modulefile.html) |
|
210 |
+ |
... | ... |
@@ -159,15 +159,15 @@ The following options can be set in the [option] field. |
159 | 159 |
|Description in [option] |Execution details| |
160 | 160 |
|--- | --- | |
161 | 161 |
|:[0-9] | Execute every specified number. For example, if you specify "1-5:2", 1,3,5 will be executed.| |
162 |
-|%[0-9] | The specified number is set as the maximum number of the concurrent executions.For example, if you specify "%2", the maximum number of concurrent executions will be "2". | |
|
162 |
+|%[0-9] | The specified number is set as the maximum number of the simultaneous executions.For example, if you specify "%2", the maximum number of simultaneous executions will be "2". | |
|
163 | 163 |
|
164 |
-## How to execute multiple programs concurrently on a single computing node{#multirun} |
|
164 |
+## How to execute multiple programs simultaneously on a single computing node{#multirun} |
|
165 | 165 |
|
166 |
-You can use computing resources effectively by executing multiple programs concurrently as a single job. |
|
167 |
-You can execute multiple programs concurrently as a single job by describing multiple execution commands in a shell script and executing the shell script. |
|
166 |
+You can use computing resources effectively by executing multiple programs simultaneously as a single job. |
|
167 |
+You can execute multiple programs simultaneously as a single job by describing multiple execution commands in a shell script and executing the shell script. |
|
168 | 168 |
|
169 | 169 |
※This method is for a sequential program or a program that is thread-parallelized by OpenMP or automatic parallelization functions. |
170 |
-※It is not possible to execute multiple MPI programs concurrently as a single job. |
|
170 |
+※It is not possible to execute multiple MPI programs simultaneously as a single job. |
|
171 | 171 |
|
172 | 172 |
An example of each script is shown below. |
173 | 173 |
|
... | ... |
@@ -175,7 +175,7 @@ An example of each script is shown below. |
175 | 175 |
|
176 | 176 |
** Job scripts to be executed by sbatch command (sequential) ** |
177 | 177 |
|
178 |
-※The following script is a sample of executing four programs concurrently. |
|
178 |
+※The following script is a sample of executing four programs simultaneously. |
|
179 | 179 |
|
180 | 180 |
```nohighlight |
181 | 181 |
#!/bin/bash |
... | ... |
@@ -190,7 +190,7 @@ srun ./multiprocess.sh |
190 | 190 |
* Specify the queue with the -p option. |
191 | 191 |
* Specify the resource to be used with the --rsc option as follows. |
192 | 192 |
* The argument p is the number of processes to be used. |
193 |
- * Specify the number of programs you wish to execute concurrently. In this case, the number is 4. |
|
193 |
+ * Specify the number of programs you wish to execute simultaneously. In this case, the number is 4. |
|
194 | 194 |
* The argument c is the number of cores to be used per process (program). |
195 | 195 |
* Since the program is a single-threaded execution, specify 1. |
196 | 196 |
* The argument t is the number of threads to be used per process (program). |
... | ... |
@@ -214,13 +214,13 @@ esac |
214 | 214 |
* When resources are allocated, a rank number is assigned to each process. |
215 | 215 |
* When the process is executed, it is possible to read the assigned rank number from the environment variable SLURM_PROCID. |
216 | 216 |
* By creating shell scripts that use rank numbers to branch processing, it is possible to separate the programs to be executed by process. |
217 |
-This allows multiple programs to be executed concurrently as a single job. |
|
217 |
+This allows multiple programs to be executed simultaneously as a single job. |
|
218 | 218 |
|
219 | 219 |
#### OpenMP Execution |
220 | 220 |
|
221 | 221 |
** Job script to be executed by sbatch command (OpenMP) ** |
222 | 222 |
|
223 |
-※The following script is a sample to execute 8 programs with 4 threads execution concurrently. |
|
223 |
+※The following script is a sample to execute 8 programs with 4 threads execution simultaneously. |
|
224 | 224 |
|
225 | 225 |
```nohighlight |
226 | 226 |
#!/bin/bash |
... | ... |
@@ -236,7 +236,7 @@ srun ./multiprocess.sh |
236 | 236 |
* Specify the queue with the -p option. |
237 | 237 |
* Specify the resource to be used with the --rsc option as follows. |
238 | 238 |
* The argument p is the number of processes to be used. |
239 |
- * Specify the number of programs you wish to execute concurrently. In this case, the number is 8. |
|
239 |
+ * Specify the number of programs you wish to execute simultaneously. In this case, the number is 8. |
|
240 | 240 |
* The argument c is the number of cores to be used per process (program) . |
241 | 241 |
* The program is a 4-thread execution, so 4 is specified. |
242 | 242 |
* The argument t is the number of threads to be used per process (program) used. |
... | ... |
@@ -264,7 +264,7 @@ esac |
264 | 264 |
|
265 | 265 |
* When resources are allocated, a rank number is assigned to each process. |
266 | 266 |
* When the process is executed, it is possible to read the assigned rank number from the environment variable SLURM_PROCID. |
267 |
-* By creating shell scripts that use rank numbers to branch processing, it is possible to separate the programs to be executed by process. This allows multiple programs to be executed concurrently as a single job. |
|
267 |
+* By creating shell scripts that use rank numbers to branch processing, it is possible to separate the programs to be executed by process. This allows multiple programs to be executed simultaneously as a single job. |
|
268 | 268 |
|
269 | 269 |
By specifying "\#SBATCH --rsc t=4" in the job script, the job scheduler is automatically configured to use 4 threads per process. Therefore, in the above shell script, each program is executed with 4 threads. |
270 | 270 |
|
271 | 271 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,83 @@ |
1 |
+--- |
|
2 |
+title: 'Compilers and MPI Libraries' |
|
3 |
+taxonomy: |
|
4 |
+ category: |
|
5 |
+ - docs |
|
6 |
+external_links: |
|
7 |
+ process: true |
|
8 |
+ title: false |
|
9 |
+ no_follow: true |
|
10 |
+ target: _blank |
|
11 |
+ mode: active |
|
12 |
+--- |
|
13 |
+ |
|
14 |
+[toc] |
|
15 |
+ |
|
16 |
+ |
|
17 |
+## Compiler{#compiler} |
|
18 |
+ |
|
19 |
+\+ : Available for all users |
|
20 |
+\- : Not available |
|
21 |
+ |
|
22 |
+Compiler | System B/C | System G | Cloud System |
|
23 |
+- | - | - | - |
|
24 |
+[Intel](/compilers/intel_classic) | + | - | + |
|
25 |
+[NVIDIA HPC SDK](/compilers/nvidia) | - | + | - |
|
26 |
+ |
|
27 |
+## Libraries{#library} |
|
28 |
+ |
|
29 |
+\+ : Available for all users |
|
30 |
+AU : Available for academic users only |
|
31 |
+\- : Not available |
|
32 |
+ |
|
33 |
+### Libraries for the Message Passing Interface(MPI){#mpi} |
|
34 |
+ |
|
35 |
+Compiler | System B/C | System G | Cloud System |
|
36 |
+- | - | - | - | - | - |
|
37 |
+[Intel MPI](/compilers/intelmpi) | + | - | + |
|
38 |
+[OpenMPI](/compilers/openmpi) | - | + | - |
|
39 |
+ |
|
40 |
+### Numerical Libraries{#sci} |
|
41 |
+ |
|
42 |
+Compiler | System B/C | System G | Cloud System |
|
43 |
+- | - | - | - | - | - |
|
44 |
+[Intel oneMKL](/software/mkl) | + | - | + |
|
45 |
+[NAG](/software/nag) | AU | - | - |
|
46 |
+[IMSL](/software/imsl) | AU | - | - |
|
47 |
+ |
|
48 |
+<!-- |
|
49 |
+### データ解析ライブラリ |
|
50 |
+### マルチスレッドライブラリ |
|
51 |
+### ビデオ処理ライブラリ |
|
52 |
+### コレクティブコミュニケーションライブラリ |
|
53 |
+### ディープニューラルネットワークライブラリ |
|
54 |
+--> |
|
55 |
+<!-- |
|
56 |
+## プログラミング支援ツール{#tool} |
|
57 |
+ |
|
58 |
+\+ : すべてのユーザが利用可能 |
|
59 |
+AU : 学術研究機関限定で利用可能 |
|
60 |
+\- : 利用不可 |
|
61 |
+ |
|
62 |
+### プロファイラ{#profiler} |
|
63 |
+ |
|
64 |
+プロファイラ | システムA | システムB | システムC |
|
65 |
+- | - | - | - |
|
66 |
+[Intel VTune Amplifier](/compilers/intel_vtune) | - | + | + |
|
67 |
+[Intel Trace Analyzer/ Collector](/compilers/intel_traceanalyzer) | ― | + | + |
|
68 |
+[Intel Advisor](/compilers/intel_advisor) | - | + | + |
|
69 |
+ |
|
70 |
+### デバッグ支援ツール{#debugger} |
|
71 |
+ |
|
72 |
+ツール | システムA | システムB | システムC |
|
73 |
+- | - | - | - |
|
74 |
+[TotalView](/compilers/totalview) | AU | AU | AU |
|
75 |
+[Intel Inspector](/compilers/intel_inspector) | - | + | + |
|
76 |
+[Allinea MAP/DDT](/compilers/allinea-map-ddt) | + | + | + |
|
77 |
+--> |
|
78 |
+ |
|
79 |
+<!-- |
|
80 |
+## オープンソースライブラリ{#oss} |
|
81 |
+ |
|
82 |
+[オープンソースソフトウェア・ライブラリ](/oss)を参照してください。 |
|
83 |
+--> |
... | ... |
@@ -68,7 +68,7 @@ Please refer to [Interactive Processing](/run/interactive) for details on the t |
68 | 68 |
|
69 | 69 |
|
70 | 70 |
```nohighlight |
71 |
-$ tssrun --x11 lsprepost |
|
71 |
+$ tssrun --x11 lspp49 |
|
72 | 72 |
``` |
73 | 73 |
|
74 | 74 |
We provide paper-based materials for the programming seminar on how to use LS-DYNA and LS-PREPOST for your reference at the counter of the Media Center North Building on a first-come, first-served basis. (Please note that the number of materials are limited.) |
... | ... |
@@ -174,17 +174,7 @@ ls971_d i=sample.dyn ncpu=$SLURM_CPUS_PER_TASK |
174 | 174 |
``` |
175 | 175 |
|
176 | 176 |
## Reference{#references} |
177 |
- |
|
178 |
- |
|
179 |
- |
|
180 |
-### Reference in Japanese{#ref_ja} |
|
181 |
- |
|
182 |
-* [LS-DYNA ver971 R5 テクニカルノート](https://web.kudpc.kyoto-u.ac.jp/App_Manual/LS-DYNA/LS-DYNA_ver971r5_TechnicalNote_201008.pdf) |
|
183 |
- |
|
184 |
- |
|
185 |
-### Reference in English{#ref_en} |
|
186 |
- |
|
187 |
-* [LS-DYNA KEYWORD USER’S MANUAL VOLUME I/II](https://web.kudpc.kyoto-u.ac.jp/App_Manual/LS-DYNA/ls-dyna_971_manual_k.pdf) |
|
177 |
+* [LSDYNA Manuals(Ansys)](https://lsdyna.ansys.com/manuals/) |
|
188 | 178 |
|
189 | 179 |
|
190 | 180 |
## Links{#link} |
... | ... |
@@ -193,10 +183,5 @@ ls971_d i=sample.dyn ncpu=$SLURM_CPUS_PER_TASK |
193 | 183 |
|
194 | 184 |
### External Links{#ex_link} |
195 | 185 |
|
196 |
-* [LS-DYNA "JSOL Corporation"](http://ls-dyna.jsol.co.jp/) |
|
197 |
- |
|
198 |
- |
|
199 |
-## Programming Seminars{#seminar} |
|
200 |
- |
|
186 |
+* [LS-DYNA "JSOL Corporation"](https://www.jsol-cae.com/product/struct/lsdyna/) |
|
201 | 187 |
|
202 |
-We periodically held [programming seminars](http://www.iimc.kyoto-u.ac.jp/en/services/comp/support/course/), and distribute the seminar materials. |
... | ... |
@@ -70,7 +70,7 @@ $ module load ls-prepost |
70 | 70 |
[FastX](/login/fastx)、[NiceDCV](/login/nice-dcv) など、X Window Systemが利用可能な環境でログインした後に、次のコマンドを実行すると起動します。 **tssrun** コマンドの詳細は [会話型処理](/run/interactive) をご覧ください。 |
71 | 71 |
|
72 | 72 |
```nohighlight |
73 |
-$ tssrun --x11 lsprepost |
|
73 |
+$ tssrun --x11 lspp49 |
|
74 | 74 |
``` |
75 | 75 |
|
76 | 76 |
なおLS-DYNA、LS-PREPOSTの使用方法の参考資料として、メディアセンター北館窓口で紙媒体の講習会資料を先着順で配布しています。(部数に限りがありますので、ご了承ください。) |
... | ... |
@@ -177,29 +177,12 @@ ls971_d i=sample.dyn ncpu=$SLURM_CPUS_PER_TASK |
177 | 177 |
``` |
178 | 178 |
|
179 | 179 |
## 参考資料{#references} |
180 |
- |
|
181 |
- |
|
182 |
- |
|
183 |
-### 日本語{#ref_ja} |
|
184 |
- |
|
185 |
-* [LS-DYNA ver971 R5 テクニカルノート](https://web.kudpc.kyoto-u.ac.jp/App_Manual/LS-DYNA/LS-DYNA_ver971r5_TechnicalNote_201008.pdf) |
|
186 |
- |
|
187 |
- |
|
188 |
-### 英語{#ref_en} |
|
189 |
- |
|
190 |
-* [LS-DYNA KEYWORD USER’S MANUAL VOLUME I/II](https://web.kudpc.kyoto-u.ac.jp/App_Manual/LS-DYNA/ls-dyna_971_manual_k.pdf) |
|
191 |
- |
|
180 |
+* [LSDYNA Manuals(Ansys)](https://lsdyna.ansys.com/manuals/) |
|
192 | 181 |
|
193 | 182 |
## リンク{#link} |
194 | 183 |
|
195 | 184 |
|
196 |
- |
|
197 | 185 |
### 外部リンク{#ex_link} |
198 | 186 |
|
199 |
-* [LS-DYNA (株式会社JSOL)](http://ls-dyna.jsol.co.jp/) |
|
200 |
- |
|
201 |
- |
|
202 |
-## 講習会{#seminar} |
|
203 |
- |
|
187 |
+* [Ansys LS-DYNA (株式会社JSOL)](https://www.jsol-cae.com/product/struct/lsdyna/) |
|
204 | 188 |
|
205 |
-[プログラム講習会](http://www.iimc.kyoto-u.ac.jp/ja/services/comp/support/course/) を定期的に開催しています。講習会資料を配布していますので、ご利用ください。 |
206 | 189 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,13 @@ |
1 |
+--- |
|
2 |
+title: 'Installation of MobaXterm' |
|
3 |
+--- |
|
4 |
+ |
|
5 |
+[toc] |
|
6 |
+ |
|
7 |
+## What is MobaXterm? |
|
8 |
+MobaXterm is an extended terminal for Windows with SSH client, X11 server, network tools and more. |
|
9 |
+ |
|
10 |
+## Installation |
|
11 |
+Download the Installer edition from "Download" on the [MobaXterm homepage](https://mobaxterm.mobatek.net/). |
|
12 |
+Extract the downloaded zip file and execute the installer (MobaXterm_installer_xx.msi). |
|
13 |
+※xx is the version number. |
|
0 | 14 |
\ No newline at end of file |
1 | 15 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,62 @@ |
1 |
+--- |
|
2 |
+title: 'Installation of Archaea (Former HCP Tools)' |
|
3 |
+--- |
|
4 |
+ |
|
5 |
+[toc] |
|
6 |
+## What is Archaea (former HCP Tools)?{#hcp_tools} |
|
7 |
+We provide Archaea (former HCP Tools) as a high-speed file transfer tool. |
|
8 |
+ |
|
9 |
+Archaea (former HCP Tools) uses HpFP protocol and available for fast file transfer. |
|
10 |
+You can use it by installing dedicated package. |
|
11 |
+ |
|
12 |
+※"HCP Tools" has been renamed "Bytrix Archaea tools". |
|
13 |
+ |
|
14 |
+## Client Software{#client} |
|
15 |
+### Version{#current_version} |
|
16 |
+Archea tools ver.1.4 is installed on the server. When installing the client software, please install **Archaea tools ver.1.4** or **Archaea dialog ver.1.0**. |
|
17 |
+ |
|
18 |
+### Supported OS{#os} |
|
19 |
+* Windows:10 |
|
20 |
+* RHEL:7 / 8 / 9 |
|
21 |
+* Ubuntu:1804 / 2004 / 2204 |
|
22 |
+* Raspberry Pi OS:9 / 11 |
|
23 |
+* openSUSE Leap:15.2 / 15.3 / 15.4 |
|
24 |
+* macOS:12 / 13 |
|
25 |
+ |
|
26 |
+### How to Obtain Client Software{#download} |
|
27 |
+[Download【Latest Version】(CLEALINK TECHNOLOGY)](https://support.bytix.tech/latest/) |
|
28 |
+ |
|
29 |
+### How to Install{#install} |
|
30 |
+For how to install, please refer to [Download【Latest Version】(CLEALINK TECHNOLOGY)](https://support.bytix.tech/latest/). |
|
31 |
+ |
|
32 |
+## How to Use{#how_to_usage} |
|
33 |
+For how to use Archaea (former HCP Tools), please refer to [File Transfer with Archaea (former HCP Tools)](/login/hcp_tools). |
|
34 |
+ |
|
35 |
+<!-- |
|
36 |
+### Archea tools{#tools} |
|
37 |
+ |
|
38 |
+#### インストール(Windows){#install_windows} |
|
39 |
+1. ダウンロードした BytixArchaeaToolsInstaller.msi を実行します. |
|
40 |
+2. セットアップ画面が開きますので、使用許諾契約書の内容を確認し、"使用許諾契約書に同意します"にチェックを入れ、インストール をクリックします。![](hcp_client_install_1.png?resize=500) |
|
41 |
+4. インストールするが終了すると完了画面が出ますので、完了 を押してください。インストールはこれで完了です。![](hcp_client_install_2.png?resize=500) |
|
42 |
+ |
|
43 |
+#### インストール(RHEL,SLE){#install_rhel} |
|
44 |
+1. 必要なrpmパッケージをダウンロードします。 |
|
45 |
+2. 以下のようなコマンドでインストールしてください。 |
|
46 |
+```nohighlight |
|
47 |
+# rpm -ivh bytix-archaea-tools-1.4.2-13.el9.x86_64.rpm |
|
48 |
+``` |
|
49 |
+ |
|
50 |
+#### インストール(Ubuntu,Debian){#install_ubuntu} |
|
51 |
+1. 必要なrpmパッケージをダウンロードします。 |
|
52 |
+2. 以下のようなコマンドでインストールしてください。 |
|
53 |
+```nohighlight |
|
54 |
+# sudo dpkg -i bytix-archaea-tools_1.4.2-13_armhf.deb |
|
55 |
+``` |
|
56 |
+ |
|
57 |
+### Archea dialog{#dialog} |
|
58 |
+#### インストール(Windows){#dialog_windows} |
|
59 |
+1. ダウンロードした BytixArchaeaDialogInstaller.msi を実行します。 |
|
60 |
+2. セットアップ画面が開きますので、使用許諾契約書の内容を確認し、"使用許諾契約書に同意します"にチェックを入れ、インストール をクリックします。![](dialog_install_1.png?resize=500) |
|
61 |
+3. インストールするが終了すると完了画面が出ますので、完了 を押してください。インストールはこれで完了です。![](dialog_install_2.png?resize=500) |
|
62 |
+--> |
|
0 | 63 |
\ No newline at end of file |
1 | 64 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,18 @@ |
1 |
+--- |
|
2 |
+title: 'Installation of Various Tools' |
|
3 |
+taxonomy: |
|
4 |
+ category: |
|
5 |
+ - docs |
|
6 |
+--- |
|
7 |
+ |
|
8 |
+[toc] |
|
9 |
+ |
|
10 |
+## MobaXterm{#mobaxterm} |
|
11 |
+MobaXterm is an extended terminal for Windows with SSH client, X11 server, network tools and more. |
|
12 |
+You can download it from [MobaXterm's website](https://mobaxterm.mobatek.net/). <br> |
|
13 |
+For how to install, please refer to [Installation of MobaXterm](/install/mobaxterm). |
|
14 |
+ |
|
15 |
+## HCP Tools{#hcptools} |
|
16 |
+HCP Tools is a file transfer tool using HpFP protocol. |
|
17 |
+You can use it by installing a dedicated package. <br> |
|
18 |
+For how to install, please refer to [Installation of HCP Tools](/install/hcp_tools). |
... | ... |
@@ -1,5 +1,5 @@ |
1 | 1 |
--- |
2 |
-title: 'How to Use Network Storage Services' |
|
2 |
+title: 'Network Storage Services' |
|
3 | 3 |
taxonomy: |
4 | 4 |
category: |
5 | 5 |
- docs |
... | ... |
@@ -13,15 +13,15 @@ media_order: 'Cyberduck_S3Connect.png,portal_afterlogin.png,WinSCP_FTPinit.png,r |
13 | 13 |
|
14 | 14 |
[toc] |
15 | 15 |
|
16 |
-## Overview |
|
17 |
-We have started offering a network storage service on a trial basis to expand our research data storage environment and data collection infrastructure from May 2022. |
|
16 |
+## 概要 |
|
17 |
+We have started offering a network storage service to expand our research data storage environment and data collection infrastructure from May 2022. |
|
18 | 18 |
You can start using the service by following the procedure from [User Portal](https://web.kudpc.kyoto-u.ac.jp/portal). |
19 |
-Please note that the maintenance may be performed and service content may be revised without prior notice during the trial period. |
|
19 |
+Please note that the maintenance may be performed and service content may be revised without prior notice. |
|
20 | 20 |
|
21 | 21 |
### Examples |
22 |
-* Research data sharing by storage linkage with [GakuNin RDM](https://rdm.nii.ac.jp/) |
|
23 |
-* Data collection for IoT devices, etc. |
|
24 |
-* Back up of the storage of the supercomputer |
|
22 |
+* Research data sharing by storage linkage with [GakuNin RDM](https://rdm.nii.ac.jp/) |
|
23 |
+* Data collection for IoT devices, etc. |
|
24 |
+* Back up of the storage of the supercomputer |
|
25 | 25 |
|
26 | 26 |
## System Configuration |
27 | 27 |
Small network storage cluster connected to a network independent from the supercomputer system. |
... | ... |
@@ -32,16 +32,16 @@ Device | DELL EMC isilon A200 x 4<br>DELL EMC PowerScale F200 x 4 |
32 | 32 |
Storage capacity | 260TB |
33 | 33 |
Front-end network | 5Gbps |
34 | 34 |
|
35 |
-## Services Provided |
|
36 |
-If you have a user number/account of Large-scale computer system, you can use the following services free of charge. |
|
37 |
-**<span style="color:red">This service does not back up the user's data by the system administrator.</span>Please take measures such as backups as necessary to prepare for the loss of the registered data when using this service. |
|
38 |
-** |
|
35 |
+## Services Provided |
|
36 |
+If you have a user ID of Large-scale computer system, you can use the following services free of charge. |
|
37 |
+**<span style="color:red">This service does not back up the user's data by the system administrator.</span>Please make backups as necessary to prepare for the loss of the registered data when using this service.** |
|
39 | 38 |
|
40 | 39 |
Item | Content |
41 | 40 |
-----| ------- |
42 | 41 |
Supported protocols | FTPS and S3 (Amazon S3 compatible, path format) |
43 | 42 |
Storage capacity | 100GB |
44 | 43 |
Transfer capacity | Unlimited |
44 |
+Backup | None |
|
45 | 45 |
FTP account | 1 |
46 | 46 |
S3 account | 1 |
47 | 47 |
Number of S3 Buckets | 1 |
... | ... |
@@ -50,7 +50,7 @@ Number of S3 objects | Unlimited |
50 | 50 |
Tine zone of Device | UTC |
51 | 51 |
|
52 | 52 |
## How to Start |
53 |
-1. Access the [User Portal](https://web.kudpc.kyoto-u.ac.jp/portal)and log in with your user number of Large-scale computer system. |
|
53 |
+1. Access the [User Portal](https://web.kudpc.kyoto-u.ac.jp/portal)and log in with your user ID of Large-scale computer system. |
|
54 | 54 |
2. Click "Network Storage Service" in the left column. |
55 | 55 |
![portal_afterlogin](portal_afterlogin.png) |
56 | 56 |
3. Select "Generate (Regenerate)" from the drop-down list surrounded by red when issuing a password used for FTP or blue when issuing a secret key for S3, and agree to the precautions. Then click the "Submit" button. |
... | ... |
@@ -59,7 +59,7 @@ Tine zone of Device | UTC |
59 | 59 |
![generate_passwd](generate_passwd.png) |
60 | 60 |
|
61 | 61 |
|
62 |
-## How to Connect (S3) |
|
62 |
+## How to Connect(S3) |
|
63 | 63 |
#### Connection Information |
64 | 64 |
|
65 | 65 |
Item|Content |
... | ... |
@@ -74,7 +74,7 @@ Bucket name | Please check the user portal. |
74 | 74 |
#### How to Install |
75 | 75 |
Please refer to the [Official Manual](https://docs.aws.amazon.com/ja_jp/cli/latest/userguide/getting-started-install.html). |
76 | 76 |
The supercomputer system provides module files. Please see [here](../oss#awscli) for details. |
77 |
-#### Initial Setting |
|
77 |
+#### Initial Setting |
|
78 | 78 |
```nohighlight |
79 | 79 |
$ aws configure --profile kudpc |
80 | 80 |
AWS Access Key ID [None]: ## Enter the access key issued by the User Portal |
... | ... |
@@ -94,7 +94,7 @@ $ aws --profile kudpc --endpoint-url=https://s3.kudpc.kyoto-u.ac.jp s3 ls s3://b |
94 | 94 |
## Upload Files |
95 | 95 |
$ aws --profile kudpc --endpoint-url=https://s3.kudpc.kyoto-u.ac.jp s3 cp sample.sh s3://b59999 |
96 | 96 |
|
97 |
-##Download Files |
|
97 |
+## Download Files |
|
98 | 98 |
$ aws --profile kudpc --endpoint-url=https://s3.kudpc.kyoto-u.ac.jp s3 cp s3://b59999/sample.sh ./ |
99 | 99 |
|
100 | 100 |
## Delete files from network storage |
... | ... |
@@ -115,7 +115,7 @@ The supercomputer system can be used without loading the module. |
115 | 115 |
$ mkdir ./kudpc-s3 |
116 | 116 |
|
117 | 117 |
## Create S3 authentication information |
118 |
-$ echo "{accesss key}:{secret key}" > ${HOME}/.passwd-s3fs |
|
118 |
+$ echo "{accesss key}:secret key}" > ${HOME}/.passwd-s3fs |
|
119 | 119 |
$ chmod 600 ${HOME}/.passwd-s3fs |
120 | 120 |
``` |
121 | 121 |
|
... | ... |
@@ -144,7 +144,7 @@ Access key ID | S3 access key |
144 | 144 |
Secret access key | S3 secret key |
145 | 145 |
![Cyberduck_S3Connect](Cyberduck_S3Connect.png) |
146 | 146 |
|
147 |
-## How to Connect (FTP) |
|
147 |
+## How to Connect(FTP) |
|
148 | 148 |
#### Connection Information |
149 | 149 |
Item|Content |
150 | 150 |
-------| ----------------------------------- |
... | ... |
@@ -160,7 +160,8 @@ Please refer to [Installing WinSCP](../install/winscp). |
160 | 160 |
1. Start WinSCP. |
161 | 161 |
2. Please enter your session information as shown in the table below and click the "Login" button. |
162 | 162 |
|
163 |
- Item | Content |
|
163 |
+ |
|
164 |
+Item | Content |
|
164 | 165 |
-----| ---------- |
165 | 166 |
Transfer protocol|FTP |
166 | 167 |
Encryption|Explicit TLS/SSL encryption |
... | ... |
@@ -169,7 +170,7 @@ Port number|21 |
169 | 170 |
User name| FTP account name |
170 | 171 |
Password| FTP Password |
171 | 172 |
![WinSCP_FTPinit](WinSCP_FTPinit.png "WinSCP_FTPinit") |
172 |
-1. If successful, the WinSCP screen will be displayed and file transfer will be possible. |
|
173 |
+3. If successful, the WinSCP screen will be displayed and file transfer will be possible. |
|
173 | 174 |
|
174 | 175 |
### When using Cyberduck |
175 | 176 |
#### How to Install |
... | ... |
@@ -188,30 +189,30 @@ User name| FTP account name |
188 | 189 |
Password|FTP Password |
189 | 190 |
![Cyberduck_FTPinit](Cyberduck_FTPinit.png "Cyberduck_FTPinit") |
190 | 191 |
<!-- |
191 |
-### When using FTP commands |
|
192 |
-#### How to Connect |
|
192 |
+### FTPコマンドを使用する場合 |
|
193 |
+#### 接続方法 |
|
193 | 194 |
```nohighlight |
194 |
-## Connection |
|
195 |
+## 接続 |
|
195 | 196 |
$ ftp s3.kudpc.kyoto-u.ac.jp |
196 |
-Name (s3.kudpc.kyoto-u.ac.jp:b59999): #Enter FTP account name |
|
197 |
-Password: #Enter FTP password |
|
197 |
+Name (s3.kudpc.kyoto-u.ac.jp:b59999): #FTPのアカウント名を入力 |
|
198 |
+Password: #FTPのパスワードを入力 |
|
198 | 199 |
``` |
199 | 200 |
|
200 |
-#### How to operate the file |
|
201 |
+#### ファイルの操作方法 |
|
201 | 202 |
```nohighlight |
202 |
-## Obtain a list of files |
|
203 |
-> ls |
|
203 |
+## ファイルの一覧を取得 |
|
204 |
+#> ls |
|
204 | 205 |
|
205 |
-## Displays the current directory of the connecting terminal |
|
206 |
-> lcd |
|
206 |
+## 接続元端末のカレントディレクトリを表示 |
|
207 |
+#> lcd |
|
207 | 208 |
|
208 |
-## Upload Files |
|
209 |
-> put sample.sh ./ |
|
209 |
+## ファイルをアップロード |
|
210 |
+#> put sample.sh ./ |
|
210 | 211 |
|
211 |
-## Download Files |
|
212 |
-> get sample.sh ./ |
|
212 |
+## ファイルをダウンロード |
|
213 |
+#> get sample.sh ./ |
|
213 | 214 |
|
214 |
-## Delete files from network storage |
|
215 |
-> delete sample.sh |
|
215 |
+## ファイルをネットワークストレージから削除 |
|
216 |
+#> delete sample.sh |
|
216 | 217 |
``` |
217 | 218 |
--> |
... | ... |
@@ -19,7 +19,8 @@ Once you receive the Registration Completion Notice, please follow the Procedure |
19 | 19 |
|
20 | 20 |
If you have been using our service since the previous year, you are not required to follow these steps. |
21 | 21 |
|
22 |
-## Flow of Procedure |
|
22 |
+ |
|
23 |
+## Flow of the Procedure |
|
23 | 24 |
|
24 | 25 |
When you start the service for the first time, please follow the steps below. |
25 | 26 |
On this page, we will describe the following 1 to 4 steps with specific images. |
... | ... |
@@ -33,15 +34,17 @@ and the "Approval Notice" with the "Registration Confirmation Notice". |
33 | 34 |
3. Open the one-time URL which is sent to your registered email address and download the Approval Notice and set the password. |
34 | 35 |
4. After that, you can log in to the user portal by the password authentication (Continuously, please set the public key authentication, etc.) |
35 | 36 |
|
37 |
+ |
|
36 | 38 |
## 1. Receiving the Registration Completion Notice |
37 | 39 |
|
40 |
+ |
|
38 | 41 |
We are sending the following email to notify you of the completion of your registration. |
39 | 42 |
Although some expressions are omitted, we will send you an email with both English and Japanese text. |
40 | 43 |
The user number described in this email will be used to login to the user portal and the supercomputer. |
41 | 44 |
Make sure not to forget the password. |
42 | 45 |
|
43 | 46 |
```nohighlight |
44 |
-Subject: [Supercomputer System of Kyoto University] Registration Completion Notice(FY20xx) |
|
47 |
+Subject: [Supercomputer System of Kyoto University] Registration Completion Notice (FY20xx) |
|
45 | 48 |
From: User Portal of Supercomputer System of Kyoto University |
46 | 49 |
-------------------------------------------------------------------------------------------- |
47 | 50 |
The registration of your supercomputer account has been completed. |
... | ... |
@@ -50,11 +53,11 @@ You can start the service by downloading the Approval Notice and setting the pas |
50 | 53 |
User number: b59999 |
51 | 54 |
|
52 | 55 |
URL of the Procedure to Start the Service: |
53 |
-https://web.kudpc.kyoto-u.ac.jp/portal/..."omitted" |
|
56 |
+https://web.kudpc.kyoto-u.ac.jp/portal/...omitted |
|
54 | 57 |
|
55 | 58 |
If you publish a paper or other publication of the research results which you have obtained using our supercomputer, |
56 | 59 |
please report it in the manner described at the following URL. |
57 |
-http://www.iimc.kyoto-u.ac.jp/ja/services/comp/apply/report.html |
|
60 |
+http://www.iimc.kyoto-u.ac.jp/en/services/comp/apply/report.html |
|
58 | 61 |
|
59 | 62 |
Supercomputer System User's Guide |
60 | 63 |
https://web.kudpc.kyoto-u.ac.jp/manual/en |
... | ... |
@@ -64,15 +67,16 @@ Academic Center for Computing and Media Studies, Kyoto University |
64 | 67 |
Supercomputer Systems |
65 | 68 |
``` |
66 | 69 |
|
70 |
+ |
|
67 | 71 |
## 2. Request for the Procedure to Start the Service |
68 | 72 |
|
69 | 73 |
### Access to the User Portal |
70 | 74 |
|
71 |
-Start up your web browser and access the URL described in the email of the registration confirmation notice. |
|
75 |
+Start up your web browser and access the URL described in the email of the Registration Completion Notice. |
|
72 | 76 |
Or, from the top page of the User Portal ([https://web.kudpc.kyoto-u.ac.jp/portal/](https://web.kudpc.kyoto-u.ac.jp/portal/)), |
73 | 77 |
click on the "Procedure to Start the Service" button circled by the red square in the following image. |
74 | 78 |
|
75 |
-! [](portal-init-01.png?lightbox=100%&resize=400) |
|
79 |
+![](portal-init-01.png?lightbox=100%&resize=400) |
|
76 | 80 |
|
77 | 81 |
### Request for the Procedure to Start the Service |
78 | 82 |
|
... | ... |
@@ -92,6 +96,7 @@ If you have a problem with your registered email address, please contact our off |
92 | 96 |
We will notify you of the URL containing a unique long string of characters as follows. |
93 | 97 |
The URL is valid for one hour, so if it expires, please repeat the above procedure. |
94 | 98 |
|
99 |
+ |
|
95 | 100 |
```nohighlight |
96 | 101 |
Subject: [Supercomputer System of Kyoto University] Procedure to Start the Service |
97 | 102 |
From: User Portal of Supercomputer System of Kyoto University |
... | ... |
@@ -105,15 +110,15 @@ Necessary procedure |
105 | 110 |
・ Password setting |
106 | 111 |
|
107 | 112 |
[URL] |
108 |
-https: //web.kudpc.kyoto-u.ac.jp/portal / ... "omitted" ... / c2cxwupu6jobyn ... "omitted" |
|
113 |
+https://web.kudpc.kyoto-u.ac.jp/portal/...omitted.../c2cxwupu6jobyn...omitted |
|
109 | 114 |
* The URL is valid for 1 hour. |
110 |
-* If you get an error when connecting, please apply again. |
|
115 |
+* If you get an error when connecting, please apply for again. |
|
111 | 116 |
|
112 |
-- |
|
117 |
+-- |
|
113 | 118 |
Academic Center for Computing and Media Studies, Kyoto University. |
114 | 119 |
Supercomputer system |
115 | 120 |
User portal |
116 |
-````` |
|
121 |
+``` |
|
117 | 122 |
|
118 | 123 |
## 3. Procedure to Start the Service |
119 | 124 |
|
... | ... |
@@ -145,12 +150,11 @@ Once the password setting is completed, the following screen will be displayed. |
145 | 150 |
After that, you can log in to the user portal using your user number and the registered password. |
146 | 151 |
In the User Portal, you can register your public key which is used in the supercomputer. |
147 | 152 |
|
153 |
+ |
|
148 | 154 |
![](portal-init-05.png?lightbox=100%&resize=400) |
149 | 155 |
|
150 |
-## 4. Access to the supercomputer |
|
156 |
+## 4.Access to the supercomputer |
|
151 | 157 |
|
152 | 158 |
Please refer to the following pages to access to your supercomputer. |
153 | 159 |
|
154 | 160 |
[Access](../../login) |
155 |
- |
|
156 |
- |
20 | 18 |
new file mode 100644 |
... | ... |
@@ -0,0 +1,15 @@ |
1 |
+--- |
|
2 |
+title: 'Activation of the seminar ID' |
|
3 |
+published: true |
|
4 |
+login: |
|
5 |
+ visibility_requires_access: false |
|
6 |
+media_order: short_course_login.mov |
|
7 |
+--- |
|
8 |
+ |
|
9 |
+### Activation of the seminar ID |
|
10 |
+You must activate your seminar ID at [https://web.kudpc.kyoto-u.ac.jp/portal/guest/short_course_activation](https://web.kudpc.kyoto-u.ac.jp/portal/guest/short_course_activation) <br> |
|
11 |
+To issue and activate your seminar ID, you will need the **"verification code "** that you will receive in the chat when you attend a seminar (Zoom Webiner). <br> |
|
12 |
+※ We recommend **Google Chrome** for your web browser. |
|
13 |
+ |
|
14 |
+### How to activate the seminar ID and log in to the system (video manual) |
|
15 |
+![short_course_login](short_course_login.mov?resize=960) |
|
0 | 16 |
\ No newline at end of file |