| Both sides previous revision Previous revision Next revision | Previous revision |
| software:abaqus:caviness [2018-10-09 19:35] – anita | software:abaqus:caviness [2023-11-21 16:27] (current) – anita |
|---|
| ====== Abaqus on Caviness ====== | ====== Abaqus on Caviness ====== |
| |
| <note important>Abaqus version 6.14-1 will not work on Lustre. Please use [[:abstract:farber:filesystems:filesystems#workgroup-storage|workgroup storage]] ($WORKDIR) on Caviness.</note> | <note important> |
| | For best results, please copy the UD IT provided job script template for Abaqus which can be found at ''/opt/templates/slurm/applications/abaqus.qs'' and make changes for your job. It is **very important to read the comments** in the job script template and make the modifications according to your job requirements. if you want to be able to use ''/lustre/scratch'' versus workgroup storage ($WORKDIR) on Caviness for Abaqus, then make sure you update your job script for Abaqus with the most recent version of ''/opt/templates/slurm/applications/abaqus.qs''. |
| | </note> |
| |
| Abaqus requires user(s) to use purchase a license in order to gain access to the license server to actually use the software. This requires some amount of setup for each workgroup to do in order to use Abaqus on Caviness. One can define an environment variable that can be set to the license server "path" (''<port>@<hostname>''). However, there's a shortcut discussed at the top of Abaqus's VALET package definition on Caviness as shown below: | Abaqus requires user(s) to purchase a license in order to gain access to the license server to actually use the software. This requires some amount of setup for each workgroup to do in order to use Abaqus on Caviness. One can define an environment variable that can be set to the license server "path" (''<port>@<hostname>''). However, there's a shortcut discussed at the top of Abaqus's VALET package definition on Caviness as shown below: |
| |
| <code bash> | <code bash> |
| </code> | </code> |
| |
| Abaqus VALET package have a scripted component to their VALET actions. It checks for the file mentioned above and sets the appropriate license environment variable to that file's content. By putting the above file in the directory specified above, it is locked-down to the workgroup only and all members in the workgroup have access to Abaqus, and it doesn't require any modification to login files or job scripts. | Abaqus VALET package has a scripted component to their VALET actions. It checks for the file mentioned above and sets the appropriate license environment variable to that file's content. By putting the above file in the directory specified above, it is locked-down to the workgroup only and all members in the workgroup have access to Abaqus, and it doesn't require any modification to the workgroup members login files or job scripts. See [[abstract:caviness:install_software:workgroup-sw|Workgroup Software Installs on Caviness]] for help in understanding how to create the necessary workgroup directories referred to above. |
| | |
| | Another alternative is to set the environment variable LM_LICENSE_FILE before running the Abaqus program. This is done as follows. |
| | |
| | <code bash> |
| | export LM_LICENSE_FILE=port@hostname |
| | </code> |
| |
| <code bash> | <code bash> |
| </code> | </code> |
| |
| The VALET package for Abaqus is available to everyone on Caviness, and will load as expected. However, in order to use Abaqus, it will only work if the above file exists in the proper directory location with the appropriate license server ''<port>@<hostname>'' information which is only provided upon purchasing a license. | The VALET package for Abaqus is available to everyone on Caviness and will load as expected. Another important instruction specific to Caviness is, to avoid unexpected error messages while running the Abaqus programs, reset the SLURM_GTIDS variable just before running the Abaqus program in the job script. This is done as follows. |
| | |
| | <code bash> |
| | unset SLURM_GTIDS |
| | </code> |
| |
| | Include this command in the job script before the launch of Abaqus program. However, this has been already incorporated into our Abaqus job template that can be found at ''/opt/templates/slurm/applications/abaqus.qs''. |