cc_staff
1,894
edits
mNo edit summary |
(Marked this version for translation) |
||
Line 536: | Line 536: | ||
For abaqus to start in gui mode must be at least <b>one</b> free cae license (not in use). The SHARCNET license has 2 free and 2 reserved licenses. If all 4 are in use according to: | For abaqus to start in gui mode must be at least <b>one</b> free cae license (not in use). The SHARCNET license has 2 free and 2 reserved licenses. If all 4 are in use according to: | ||
[gra-vdi3:~] abaqus licensing lmstat -c $ABAQUSLM_LICENSE_FILE -a | grep "Users of cae" | <!--T:20918--> | ||
[gra-vdi3:~] abaqus licensing lmstat -c $ABAQUSLM_LICENSE_FILE -a | grep "Users of cae" | |||
Users of cae: (Total of 4 licenses issued; Total of 4 licenses in use) | Users of cae: (Total of 4 licenses issued; Total of 4 licenses in use) | ||
<!--T:20919--> | |||
Then the following error messages will occur when you attempt to start abaqus cae: | Then the following error messages will occur when you attempt to start abaqus cae: | ||
[gra-vdi3:~] abaqus cae | <!--T:20920--> | ||
[gra-vdi3:~] abaqus cae | |||
ABAQUSLM_LICENSE_FILE=27050@license3.sharcnet.ca | ABAQUSLM_LICENSE_FILE=27050@license3.sharcnet.ca | ||
/opt/sharcnet/abaqus/2020/Commands/abaqus cae | /opt/sharcnet/abaqus/2020/Commands/abaqus cae | ||
Line 560: | Line 563: | ||
SHARCNET provides a small but free license consisting of 2 cae and 35 execute tokens where usage limits are imposed 10 tokens/user and 15 tokens/group. For groups that have purchased dedicated tokens, the free token usage limits are added to their reservation. The free tokens are available on a first come first serve basis and mainly intended for testing and light usage before deciding whether or not to purchase dedicated tokens. Costs for dedicated tokens (in 2021) were approximately CAD$110 per compute token and CAD$400 per GUI token: submit a ticket to request an official quote. The license can be used by any Alliance researcher, but only on SHARCNET hardware. Groups that purchase dedicated tokens to run on the SHARCNET license server may likewise only use them on SHARCNET hardware including gra-vdi (for running Abaqus in full graphical mode) and Graham or Dusky clusters (for submitting compute batch jobs to the queue). Before you can use the license you must contact [[Technical support]] and request access. In your email 1) mention that it is for use on SHARCNET systems and 2) include a copy/paste of the following <code>License Agreement</code> statement with your full name and username entered in the indicated locations. Please note that every user must do this it cannot be done one time only for a group; this includes PIs who have purchased their own dedicated tokens. | SHARCNET provides a small but free license consisting of 2 cae and 35 execute tokens where usage limits are imposed 10 tokens/user and 15 tokens/group. For groups that have purchased dedicated tokens, the free token usage limits are added to their reservation. The free tokens are available on a first come first serve basis and mainly intended for testing and light usage before deciding whether or not to purchase dedicated tokens. Costs for dedicated tokens (in 2021) were approximately CAD$110 per compute token and CAD$400 per GUI token: submit a ticket to request an official quote. The license can be used by any Alliance researcher, but only on SHARCNET hardware. Groups that purchase dedicated tokens to run on the SHARCNET license server may likewise only use them on SHARCNET hardware including gra-vdi (for running Abaqus in full graphical mode) and Graham or Dusky clusters (for submitting compute batch jobs to the queue). Before you can use the license you must contact [[Technical support]] and request access. In your email 1) mention that it is for use on SHARCNET systems and 2) include a copy/paste of the following <code>License Agreement</code> statement with your full name and username entered in the indicated locations. Please note that every user must do this it cannot be done one time only for a group; this includes PIs who have purchased their own dedicated tokens. | ||
<!--T:20851--> | === License agreement === <!--T:20851--> | ||
<pre>---------------------------------------------------------------------------------- | <pre>---------------------------------------------------------------------------------- | ||
Subject: Abaqus SHARCNET Academic License User Agreement | Subject: Abaqus SHARCNET Academic License User Agreement | ||
Line 580: | Line 582: | ||
-----------------------------------------------------------------------------------</pre> | -----------------------------------------------------------------------------------</pre> | ||
<!--T:20854--> | === Configure license file === <!--T:20854--> | ||
Configure your license file as follows, noting that it is only usable on SHARCNET systems: Graham, gra-vdi and Dusky. | Configure your license file as follows, noting that it is only usable on SHARCNET systems: Graham, gra-vdi and Dusky. | ||
</translate> | </translate> | ||
Line 594: | Line 595: | ||
If your Abaqus jobs fail with the error message [*** ABAQUS/eliT_CheckLicense rank 0 terminated by signal 11 (Segmentation fault)] in the slurm output file, verify if your <code>abaqus.lic</code> file contains ABAQUSLM_LICENSE_FILE to use abaqus/2020. If your Abaqus jobs fail with an error message starting [License server machine is down or not responding, etc.] in the output file verify your <code>abaqus.lic</code> file contains LM_LICENSE_FILE to use abaqus/6.14.1 as shown. The <code>abaqus.lic</code> file shown contains both so you should not see this problem. | If your Abaqus jobs fail with the error message [*** ABAQUS/eliT_CheckLicense rank 0 terminated by signal 11 (Segmentation fault)] in the slurm output file, verify if your <code>abaqus.lic</code> file contains ABAQUSLM_LICENSE_FILE to use abaqus/2020. If your Abaqus jobs fail with an error message starting [License server machine is down or not responding, etc.] in the output file verify your <code>abaqus.lic</code> file contains LM_LICENSE_FILE to use abaqus/6.14.1 as shown. The <code>abaqus.lic</code> file shown contains both so you should not see this problem. | ||
<!--T:20661--> | === Query license server === <!--T:20661--> | ||
Log into graham, load abaqus and then run one of the following: | Log into graham, load abaqus and then run one of the following: | ||
<source lang="bash"> | <source lang="bash"> | ||
Line 603: | Line 603: | ||
</source> | </source> | ||
<!--T:20921--> | |||
I) Check the SHARCNET license server for started and queued jobs: | I) Check the SHARCNET license server for started and queued jobs: | ||
</translate> | </translate> | ||
Line 638: | Line 639: | ||
<translate> | <translate> | ||
<!--T:20859--> | === Specify job resources === <!--T:20859--> | ||
To ensure optimal usage of both your Abaqus tokens and our resources, it's important to carefully specify the required memory and ncpus in your Slurm script. The values can be determined by submitting a few short test jobs to the queue then checking their utilization. For <b>completed</b> jobs use <code>seff JobNumber</code> to show the total <i>Memory Utilized</i> and <i>Memory Efficiency</i>. If the <i>Memory Efficiency</i> is less than ~90%, decrease the value of the <code>#SBATCH --mem=</code> setting in your Slurm script accordingly. Notice that the <code>seff JobNumber</code> command also shows the total <i>CPU (time) Utilized</i> and <i>CPU Efficiency</i>. If the <i>CPU Efficiency</i> is less than ~90%, perform scaling tests to determine the optimal number of CPUs for optimal performance and then update the value of <code>#SBATCH --cpus-per-task=</code> in your Slurm script. For <b>running</b> jobs, use the <code>srun --jobid=29821580 --pty top -d 5 -u $USER</code> command to watch the %CPU, %MEM and RES for each Abaqus parent process on the compute node. The %CPU and %MEM columns display the percent usage relative to the total available on the node while the RES column shows the per process resident memory size (in human readable format for values over 1GB). Further information regarding how to [[Running jobs#Monitoring_jobs|monitor jobs]] is available on our documentation wiki | To ensure optimal usage of both your Abaqus tokens and our resources, it's important to carefully specify the required memory and ncpus in your Slurm script. The values can be determined by submitting a few short test jobs to the queue then checking their utilization. For <b>completed</b> jobs use <code>seff JobNumber</code> to show the total <i>Memory Utilized</i> and <i>Memory Efficiency</i>. If the <i>Memory Efficiency</i> is less than ~90%, decrease the value of the <code>#SBATCH --mem=</code> setting in your Slurm script accordingly. Notice that the <code>seff JobNumber</code> command also shows the total <i>CPU (time) Utilized</i> and <i>CPU Efficiency</i>. If the <i>CPU Efficiency</i> is less than ~90%, perform scaling tests to determine the optimal number of CPUs for optimal performance and then update the value of <code>#SBATCH --cpus-per-task=</code> in your Slurm script. For <b>running</b> jobs, use the <code>srun --jobid=29821580 --pty top -d 5 -u $USER</code> command to watch the %CPU, %MEM and RES for each Abaqus parent process on the compute node. The %CPU and %MEM columns display the percent usage relative to the total available on the node while the RES column shows the per process resident memory size (in human readable format for values over 1GB). Further information regarding how to [[Running jobs#Monitoring_jobs|monitor jobs]] is available on our documentation wiki | ||
<!--T:20860--> | === Core token mapping === <!--T:20860--> | ||
</translate> | </translate> | ||
<pre> | <pre> | ||
Line 656: | Line 655: | ||
The Western site license may only be used by Western researchers on hardware located at Western's campus. Currently, the Dusky cluster is the only system that satisfies these conditions. Graham and gra-vdi are excluded since they are located on Waterloo's campus. Contact the Western Abaqus license server administrator <jmilner@robarts.ca> to inquire about using the Western Abaqus license. You will need to provide your username and possibly make arrangements to purchase tokens. If you are granted access then you may proceed to configure your <code>abaqus.lic</code> file to point to the Western license server as follows: | The Western site license may only be used by Western researchers on hardware located at Western's campus. Currently, the Dusky cluster is the only system that satisfies these conditions. Graham and gra-vdi are excluded since they are located on Waterloo's campus. Contact the Western Abaqus license server administrator <jmilner@robarts.ca> to inquire about using the Western Abaqus license. You will need to provide your username and possibly make arrangements to purchase tokens. If you are granted access then you may proceed to configure your <code>abaqus.lic</code> file to point to the Western license server as follows: | ||
<!--T:20863--> | === Configure license file === <!--T:20863--> | ||
Configure your license file as follows, noting that it is only usable on Dusky. | Configure your license file as follows, noting that it is only usable on Dusky. | ||