Introduction<\/h2><\/h2><\/span><\/div><\/div><\/div>Abaqus Unfied FEA can be run under both Windows and Linux. Linux offers some advantages in terms of maintenance and performance.<\/p>\n
The Program Directories, see image below, can be accessed online and provide much essential information on the installation and maintenance of Dassault Syst\u00e8mes software. If you select ‘SIMULIA Abaqus, Isight, fe-safe, Tosca’ under the Product Line, you will get information about the products of the Abaqus Unified FEA Line [1]. Here you can find the prerequisites for the different products under Deployment. For the time being, our focus is on Abaqus.<\/p>\n<\/div>
<\/div>![](\"https:\/\/plm.systemworkx.de\/wp-content\/uploads\/2023\/04\/linuxabaqus-Bild-1.png\")
<\/a><\/span><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/span>Which Linux?<\/h2><\/h2><\/span><\/div><\/div><\/div>Supported Platforms lists the two commercial Linux systems Red Hat Enterprise [2] and SUSE Linux Enterprise [3] and the versions tested for these systems. For these systems, the operation of Abaqus is confirmed and – officially – support is offered within the scope of the contracts.<\/p>\n
Now there are a variety of free Linux systems that may be suitable for running Abaqus as well. The colleagues from Dassault Syst\u00e8mes have been offering support for these Linux systems within clear limits for a long time. Here it must be emphasized that the operation on another Linux system is always the responsibility of the user and tmight be excluded from general support.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Info about the operating system<\/h2><\/h2><\/span><\/div><\/div><\/div><\/div><\/div>The best way to get information about the operating system is to use shell commands:<\/p>\n
\n- ‘uname’ usually returns Linux as result<\/li>\n
- ‘uname -rm’ the kernel version and the system architecture<\/li>\n
- ‘lsb_release -d’ the name of the Linux system<\/li>\n
- ‘lsb_release -a’ Information about the used Linux system<\/li>\n
- ‘lscpu’ information about the used hardware<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/span>
Installation<\/h2><\/h2><\/span><\/div><\/div><\/div>Under the prerequisites there are several required libraries, which should be available. In our experience, this changes depending on the Abaqus version and the Linux used. What is missing is named during the installation. Sometimes you may have to search for some libraries. Here, we are always happy to assist in solving any problems that may arise.<\/p>\n
In the example below, the installation of Isight already failed because of the missing Korn shell.<\/p>\n
In general, the installation is a bit easier than on Windows. It does not link against Microsoft libraries, which makes fewer demands on the operating system. Also, you cannot (should not) install as a user with admin rights, but as a “normal” user.<\/p>\n
If you use a Linux other than the one listed in the Supported Platforms, the definition of certain variables is required for the installation, QA000024409 in [4]. The installation under CentOS 7 [5] did not need these variables in the past because of the similarity to Red Hat 7 in our experience. However, CentOS 7 support will be discontinued in 2024.<\/p>\n
Using openSUSE Leap 15.4 [6] as an example, the installation is run through here.<\/p>\n
We install here under \/var\/software\/Simulia (installation directory), which is ultimately a personal decision. For example, Dassault Syst\u00e8mes installs the DSLS license server under \/var\/DassaultSystemes\/Licenses.
\nWe copy the downloaded software from [7] into a directory ‘DVD’ below it (naming convention for each version ‘extended-v2023-GA’ for the first release and ‘extended-v2023-fp2306’ for a service pack).<\/p>\n
We then proceed as follows:<\/p>\n<\/div>
\n- Unpack: with ‘tar -xovf 2023.AM_SIM_Abaqus_Extend.AllOS.1-5.tar’ etc.<\/li>\n
- The following directory is created: AM_SIM_Abaqus_Extend.ALLOS<\/li>\n
- Setting the variables\n
\n- export DSY_Force_OS=linux_a64<\/li>\n
- export DSYAuthOS_`lsb_release –short –id |sed ‘s\/ \/\/g’`=1<\/li>\n<\/ul>\n<\/li>\n
- in the directory AM_SIM_Abaqus_Extend.ALLOS\/1 we start the installation with ‘.\/StartGUI.sh’, see picture below,<\/li>\n<\/ul>\n<\/div><\/div>
![](\"https:\/\/plm.systemworkx.de\/wp-content\/uploads\/2023\/04\/linuxabaqus-Bild-2.png\")
<\/a><\/span><\/div><\/div><\/div>Usually we do not specify a license server and use the skip function (however, this did not work stably with earlier versions under certain Windows versions). Otherwise we follow the installation so far.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Calling\/starting Abaqus<\/h2><\/h2><\/span><\/div><\/div><\/div>The best way is to start Abaqus from the console. During the installation of Abaqus no PATH variables are set for calling Abaqus. But you can also quickly do it yourself.<\/p>\n<\/div>
<\/div><\/div><\/span>Variant 1 – alias<\/h3><\/h2><\/span><\/div><\/div><\/div>Under OpenSuSE the Bash Shell is used as standard. Therefore there should be a ‘.bashrc’ file in the home directory of every user. In our case ‘.bashrc’ contains the following line ‘test -s \uff5e\/.alias && . \uff5e\/.alias || true’. This will call a ‘.alias’ file. In this ‘.alias’ file you can define variables for the call of Abaqus:<\/p>\n
\n- alias abaqus=\/var\/software\/Simulia\/Commands\/abaqus (call the current Abaqus version)<\/li>\n
- alias abq2022hf5=\/var\/software\/Simulia\/Commands\/abq2022hf5 (call the last updated Abaqus version 2022)<\/li>\n
- etc.<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/span>
Variant 2 – PATH<\/h3><\/h2><\/span><\/div><\/div><\/div>Now edit the ‘.bashrc’ file in the home directory and add the following line to the path variable:<\/p>\n
export PATH=”$PATH:\/var\/software\/Simulia\/Commands”<\/p>\n
The second variant is recommended. One should note that only either a restart of the console or the command ‘source .bashrc’ or ‘source .alias’ will activate changes in these files.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Summary<\/h2><\/h2><\/span><\/div><\/div><\/div>Abaqus Unified FEA can also be operated under the Linux operating system, including the fe-safe, Isight and Tosca products. OpenSource variants can also be used here. During installation as well as operation, one encounters one or the other small obstacle. In this article we want to present obstacles and their solutions.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/span>Literature<\/h2><\/h2><\/span><\/div><\/div><\/div><\/div>\n\n\n\n\n\n\n\n\nIn part, this text and illustrations shown are based on research of evaluated literature. If this is the case, the sources are marked in the text by a number, e.g. [2], and the source is listed here.<\/p>\n
In part, however, the sources listed here should simply be understood as recommendations for further reading.<\/p>\n<\/div>\n
\n\n<\/div>\n<\/div>\n\n\n\n[1] Dassault Syst\u00e8mes, P. D., 2023, \u201cProgram Directories Library<\/a>\u201d [Online] [Accessed: 16-Mar-2023]<\/div>\n\n\n\n[2] Red Hat, 2023, \u201cRed Hat Enterprise<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[3] SUSE, L., 2023, \u201cSUSE \u2013 Open Source L\u00f6sungen f\u00fcr Enterprise Server und Cloud<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[4] Dassault Syst\u00e8mes, 2023, \u201cDS Support Knowledge Base<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n
Abaqus Unfied FEA can be run under both Windows and Linux. Linux offers some advantages in terms of maintenance and performance.<\/p>\n
The Program Directories, see image below, can be accessed online and provide much essential information on the installation and maintenance of Dassault Syst\u00e8mes software. If you select ‘SIMULIA Abaqus, Isight, fe-safe, Tosca’ under the Product Line, you will get information about the products of the Abaqus Unified FEA Line [1]. Here you can find the prerequisites for the different products under Deployment. For the time being, our focus is on Abaqus.<\/p>\n<\/div>
<\/a><\/span><\/div><\/div>Which Linux?<\/h2><\/h2><\/span><\/div><\/div><\/div>Supported Platforms lists the two commercial Linux systems Red Hat Enterprise [2] and SUSE Linux Enterprise [3] and the versions tested for these systems. For these systems, the operation of Abaqus is confirmed and – officially – support is offered within the scope of the contracts.<\/p>\n
Now there are a variety of free Linux systems that may be suitable for running Abaqus as well. The colleagues from Dassault Syst\u00e8mes have been offering support for these Linux systems within clear limits for a long time. Here it must be emphasized that the operation on another Linux system is always the responsibility of the user and tmight be excluded from general support.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Info about the operating system<\/h2><\/h2><\/span><\/div><\/div><\/div><\/div><\/div>The best way to get information about the operating system is to use shell commands:<\/p>\n
\n- ‘uname’ usually returns Linux as result<\/li>\n
- ‘uname -rm’ the kernel version and the system architecture<\/li>\n
- ‘lsb_release -d’ the name of the Linux system<\/li>\n
- ‘lsb_release -a’ Information about the used Linux system<\/li>\n
- ‘lscpu’ information about the used hardware<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/span>
Installation<\/h2><\/h2><\/span><\/div><\/div><\/div>Under the prerequisites there are several required libraries, which should be available. In our experience, this changes depending on the Abaqus version and the Linux used. What is missing is named during the installation. Sometimes you may have to search for some libraries. Here, we are always happy to assist in solving any problems that may arise.<\/p>\n
In the example below, the installation of Isight already failed because of the missing Korn shell.<\/p>\n
In general, the installation is a bit easier than on Windows. It does not link against Microsoft libraries, which makes fewer demands on the operating system. Also, you cannot (should not) install as a user with admin rights, but as a “normal” user.<\/p>\n
If you use a Linux other than the one listed in the Supported Platforms, the definition of certain variables is required for the installation, QA000024409 in [4]. The installation under CentOS 7 [5] did not need these variables in the past because of the similarity to Red Hat 7 in our experience. However, CentOS 7 support will be discontinued in 2024.<\/p>\n
Using openSUSE Leap 15.4 [6] as an example, the installation is run through here.<\/p>\n
We install here under \/var\/software\/Simulia (installation directory), which is ultimately a personal decision. For example, Dassault Syst\u00e8mes installs the DSLS license server under \/var\/DassaultSystemes\/Licenses.
\nWe copy the downloaded software from [7] into a directory ‘DVD’ below it (naming convention for each version ‘extended-v2023-GA’ for the first release and ‘extended-v2023-fp2306’ for a service pack).<\/p>\n
We then proceed as follows:<\/p>\n<\/div>
\n- Unpack: with ‘tar -xovf 2023.AM_SIM_Abaqus_Extend.AllOS.1-5.tar’ etc.<\/li>\n
- The following directory is created: AM_SIM_Abaqus_Extend.ALLOS<\/li>\n
- Setting the variables\n
\n- export DSY_Force_OS=linux_a64<\/li>\n
- export DSYAuthOS_`lsb_release –short –id |sed ‘s\/ \/\/g’`=1<\/li>\n<\/ul>\n<\/li>\n
- in the directory AM_SIM_Abaqus_Extend.ALLOS\/1 we start the installation with ‘.\/StartGUI.sh’, see picture below,<\/li>\n<\/ul>\n<\/div><\/div><\/a><\/span><\/div><\/div><\/div>
Usually we do not specify a license server and use the skip function (however, this did not work stably with earlier versions under certain Windows versions). Otherwise we follow the installation so far.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Calling\/starting Abaqus<\/h2><\/h2><\/span><\/div><\/div><\/div>The best way is to start Abaqus from the console. During the installation of Abaqus no PATH variables are set for calling Abaqus. But you can also quickly do it yourself.<\/p>\n<\/div>
<\/div><\/div><\/span>Variant 1 – alias<\/h3><\/h2><\/span><\/div><\/div><\/div>Under OpenSuSE the Bash Shell is used as standard. Therefore there should be a ‘.bashrc’ file in the home directory of every user. In our case ‘.bashrc’ contains the following line ‘test -s \uff5e\/.alias && . \uff5e\/.alias || true’. This will call a ‘.alias’ file. In this ‘.alias’ file you can define variables for the call of Abaqus:<\/p>\n
\n- alias abaqus=\/var\/software\/Simulia\/Commands\/abaqus (call the current Abaqus version)<\/li>\n
- alias abq2022hf5=\/var\/software\/Simulia\/Commands\/abq2022hf5 (call the last updated Abaqus version 2022)<\/li>\n
- etc.<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/span>
Variant 2 – PATH<\/h3><\/h2><\/span><\/div><\/div><\/div>Now edit the ‘.bashrc’ file in the home directory and add the following line to the path variable:<\/p>\n
export PATH=”$PATH:\/var\/software\/Simulia\/Commands”<\/p>\n
The second variant is recommended. One should note that only either a restart of the console or the command ‘source .bashrc’ or ‘source .alias’ will activate changes in these files.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Summary<\/h2><\/h2><\/span><\/div><\/div><\/div>Abaqus Unified FEA can also be operated under the Linux operating system, including the fe-safe, Isight and Tosca products. OpenSource variants can also be used here. During installation as well as operation, one encounters one or the other small obstacle. In this article we want to present obstacles and their solutions.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/span>Literature<\/h2><\/h2><\/span><\/div><\/div><\/div><\/div>\n\n\n\n\n\n\n\n\nIn part, this text and illustrations shown are based on research of evaluated literature. If this is the case, the sources are marked in the text by a number, e.g. [2], and the source is listed here.<\/p>\n
In part, however, the sources listed here should simply be understood as recommendations for further reading.<\/p>\n<\/div>\n
\n\n<\/div>\n<\/div>\n\n\n\n[1] Dassault Syst\u00e8mes, P. D., 2023, \u201cProgram Directories Library<\/a>\u201d [Online] [Accessed: 16-Mar-2023]<\/div>\n\n\n\n[2] Red Hat, 2023, \u201cRed Hat Enterprise<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[3] SUSE, L., 2023, \u201cSUSE \u2013 Open Source L\u00f6sungen f\u00fcr Enterprise Server und Cloud<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[4] Dassault Syst\u00e8mes, 2023, \u201cDS Support Knowledge Base<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n
Supported Platforms lists the two commercial Linux systems Red Hat Enterprise [2] and SUSE Linux Enterprise [3] and the versions tested for these systems. For these systems, the operation of Abaqus is confirmed and – officially – support is offered within the scope of the contracts.<\/p>\n
Now there are a variety of free Linux systems that may be suitable for running Abaqus as well. The colleagues from Dassault Syst\u00e8mes have been offering support for these Linux systems within clear limits for a long time. Here it must be emphasized that the operation on another Linux system is always the responsibility of the user and tmight be excluded from general support.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
Info about the operating system<\/h2><\/h2><\/span><\/div><\/div><\/div><\/div><\/div>The best way to get information about the operating system is to use shell commands:<\/p>\n
\n- ‘uname’ usually returns Linux as result<\/li>\n
- ‘uname -rm’ the kernel version and the system architecture<\/li>\n
- ‘lsb_release -d’ the name of the Linux system<\/li>\n
- ‘lsb_release -a’ Information about the used Linux system<\/li>\n
- ‘lscpu’ information about the used hardware<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/span>
Installation<\/h2><\/h2><\/span><\/div><\/div><\/div>Under the prerequisites there are several required libraries, which should be available. In our experience, this changes depending on the Abaqus version and the Linux used. What is missing is named during the installation. Sometimes you may have to search for some libraries. Here, we are always happy to assist in solving any problems that may arise.<\/p>\n
In the example below, the installation of Isight already failed because of the missing Korn shell.<\/p>\n
In general, the installation is a bit easier than on Windows. It does not link against Microsoft libraries, which makes fewer demands on the operating system. Also, you cannot (should not) install as a user with admin rights, but as a “normal” user.<\/p>\n
If you use a Linux other than the one listed in the Supported Platforms, the definition of certain variables is required for the installation, QA000024409 in [4]. The installation under CentOS 7 [5] did not need these variables in the past because of the similarity to Red Hat 7 in our experience. However, CentOS 7 support will be discontinued in 2024.<\/p>\n
Using openSUSE Leap 15.4 [6] as an example, the installation is run through here.<\/p>\n
We install here under \/var\/software\/Simulia (installation directory), which is ultimately a personal decision. For example, Dassault Syst\u00e8mes installs the DSLS license server under \/var\/DassaultSystemes\/Licenses.
\nWe copy the downloaded software from [7] into a directory ‘DVD’ below it (naming convention for each version ‘extended-v2023-GA’ for the first release and ‘extended-v2023-fp2306’ for a service pack).<\/p>\n
We then proceed as follows:<\/p>\n<\/div>
\n- Unpack: with ‘tar -xovf 2023.AM_SIM_Abaqus_Extend.AllOS.1-5.tar’ etc.<\/li>\n
- The following directory is created: AM_SIM_Abaqus_Extend.ALLOS<\/li>\n
- Setting the variables\n
\n- export DSY_Force_OS=linux_a64<\/li>\n
- export DSYAuthOS_`lsb_release –short –id |sed ‘s\/ \/\/g’`=1<\/li>\n<\/ul>\n<\/li>\n
- in the directory AM_SIM_Abaqus_Extend.ALLOS\/1 we start the installation with ‘.\/StartGUI.sh’, see picture below,<\/li>\n<\/ul>\n<\/div><\/div><\/a><\/span><\/div><\/div><\/div>
Usually we do not specify a license server and use the skip function (however, this did not work stably with earlier versions under certain Windows versions). Otherwise we follow the installation so far.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Calling\/starting Abaqus<\/h2><\/h2><\/span><\/div><\/div><\/div>The best way is to start Abaqus from the console. During the installation of Abaqus no PATH variables are set for calling Abaqus. But you can also quickly do it yourself.<\/p>\n<\/div>
<\/div><\/div><\/span>Variant 1 – alias<\/h3><\/h2><\/span><\/div><\/div><\/div>Under OpenSuSE the Bash Shell is used as standard. Therefore there should be a ‘.bashrc’ file in the home directory of every user. In our case ‘.bashrc’ contains the following line ‘test -s \uff5e\/.alias && . \uff5e\/.alias || true’. This will call a ‘.alias’ file. In this ‘.alias’ file you can define variables for the call of Abaqus:<\/p>\n
\n- alias abaqus=\/var\/software\/Simulia\/Commands\/abaqus (call the current Abaqus version)<\/li>\n
- alias abq2022hf5=\/var\/software\/Simulia\/Commands\/abq2022hf5 (call the last updated Abaqus version 2022)<\/li>\n
- etc.<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/span>
Variant 2 – PATH<\/h3><\/h2><\/span><\/div><\/div><\/div>Now edit the ‘.bashrc’ file in the home directory and add the following line to the path variable:<\/p>\n
export PATH=”$PATH:\/var\/software\/Simulia\/Commands”<\/p>\n
The second variant is recommended. One should note that only either a restart of the console or the command ‘source .bashrc’ or ‘source .alias’ will activate changes in these files.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Summary<\/h2><\/h2><\/span><\/div><\/div><\/div>Abaqus Unified FEA can also be operated under the Linux operating system, including the fe-safe, Isight and Tosca products. OpenSource variants can also be used here. During installation as well as operation, one encounters one or the other small obstacle. In this article we want to present obstacles and their solutions.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/span>Literature<\/h2><\/h2><\/span><\/div><\/div><\/div><\/div>\n\n\n\n\n\n\n\n\nIn part, this text and illustrations shown are based on research of evaluated literature. If this is the case, the sources are marked in the text by a number, e.g. [2], and the source is listed here.<\/p>\n
In part, however, the sources listed here should simply be understood as recommendations for further reading.<\/p>\n<\/div>\n
\n\n<\/div>\n<\/div>\n\n\n\n[1] Dassault Syst\u00e8mes, P. D., 2023, \u201cProgram Directories Library<\/a>\u201d [Online] [Accessed: 16-Mar-2023]<\/div>\n\n\n\n[2] Red Hat, 2023, \u201cRed Hat Enterprise<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[3] SUSE, L., 2023, \u201cSUSE \u2013 Open Source L\u00f6sungen f\u00fcr Enterprise Server und Cloud<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[4] Dassault Syst\u00e8mes, 2023, \u201cDS Support Knowledge Base<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n
The best way to get information about the operating system is to use shell commands:<\/p>\n
- \n
- ‘uname’ usually returns Linux as result<\/li>\n
- ‘uname -rm’ the kernel version and the system architecture<\/li>\n
- ‘lsb_release -d’ the name of the Linux system<\/li>\n
- ‘lsb_release -a’ Information about the used Linux system<\/li>\n
- ‘lscpu’ information about the used hardware<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/span>
Installation<\/h2><\/h2><\/span>
<\/div><\/div><\/div>Under the prerequisites there are several required libraries, which should be available. In our experience, this changes depending on the Abaqus version and the Linux used. What is missing is named during the installation. Sometimes you may have to search for some libraries. Here, we are always happy to assist in solving any problems that may arise.<\/p>\n
In the example below, the installation of Isight already failed because of the missing Korn shell.<\/p>\n
In general, the installation is a bit easier than on Windows. It does not link against Microsoft libraries, which makes fewer demands on the operating system. Also, you cannot (should not) install as a user with admin rights, but as a “normal” user.<\/p>\n
If you use a Linux other than the one listed in the Supported Platforms, the definition of certain variables is required for the installation, QA000024409 in [4]. The installation under CentOS 7 [5] did not need these variables in the past because of the similarity to Red Hat 7 in our experience. However, CentOS 7 support will be discontinued in 2024.<\/p>\n
Using openSUSE Leap 15.4 [6] as an example, the installation is run through here.<\/p>\n
We install here under \/var\/software\/Simulia (installation directory), which is ultimately a personal decision. For example, Dassault Syst\u00e8mes installs the DSLS license server under \/var\/DassaultSystemes\/Licenses.
\nWe copy the downloaded software from [7] into a directory ‘DVD’ below it (naming convention for each version ‘extended-v2023-GA’ for the first release and ‘extended-v2023-fp2306’ for a service pack).<\/p>\nWe then proceed as follows:<\/p>\n<\/div>
- \n
- Unpack: with ‘tar -xovf 2023.AM_SIM_Abaqus_Extend.AllOS.1-5.tar’ etc.<\/li>\n
- The following directory is created: AM_SIM_Abaqus_Extend.ALLOS<\/li>\n
- Setting the variables\n
- \n
- export DSY_Force_OS=linux_a64<\/li>\n
- export DSYAuthOS_`lsb_release –short –id |sed ‘s\/ \/\/g’`=1<\/li>\n<\/ul>\n<\/li>\n
- in the directory AM_SIM_Abaqus_Extend.ALLOS\/1 we start the installation with ‘.\/StartGUI.sh’, see picture below,<\/li>\n<\/ul>\n<\/div><\/div><\/a><\/span><\/div><\/div><\/div>
Usually we do not specify a license server and use the skip function (however, this did not work stably with earlier versions under certain Windows versions). Otherwise we follow the installation so far.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Calling\/starting Abaqus<\/h2><\/h2><\/span>
<\/div><\/div><\/div>The best way is to start Abaqus from the console. During the installation of Abaqus no PATH variables are set for calling Abaqus. But you can also quickly do it yourself.<\/p>\n<\/div>
<\/div><\/div><\/span>Variant 1 – alias<\/h3><\/h2><\/span>
<\/div><\/div><\/div>Under OpenSuSE the Bash Shell is used as standard. Therefore there should be a ‘.bashrc’ file in the home directory of every user. In our case ‘.bashrc’ contains the following line ‘test -s \uff5e\/.alias && . \uff5e\/.alias || true’. This will call a ‘.alias’ file. In this ‘.alias’ file you can define variables for the call of Abaqus:<\/p>\n
- \n
- alias abaqus=\/var\/software\/Simulia\/Commands\/abaqus (call the current Abaqus version)<\/li>\n
- alias abq2022hf5=\/var\/software\/Simulia\/Commands\/abq2022hf5 (call the last updated Abaqus version 2022)<\/li>\n
- etc.<\/li>\n<\/ul>\n<\/div><\/div><\/div><\/span>
Variant 2 – PATH<\/h3><\/h2><\/span>
<\/div><\/div><\/div>Now edit the ‘.bashrc’ file in the home directory and add the following line to the path variable:<\/p>\n
export PATH=”$PATH:\/var\/software\/Simulia\/Commands”<\/p>\n
The second variant is recommended. One should note that only either a restart of the console or the command ‘source .bashrc’ or ‘source .alias’ will activate changes in these files.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/span>Summary<\/h2><\/h2><\/span>
<\/div><\/div><\/div>Abaqus Unified FEA can also be operated under the Linux operating system, including the fe-safe, Isight and Tosca products. OpenSource variants can also be used here. During installation as well as operation, one encounters one or the other small obstacle. In this article we want to present obstacles and their solutions.<\/p>\n<\/div><\/div><\/div><\/div><\/div>
<\/div><\/div><\/div><\/div><\/span>Literature<\/h2><\/h2><\/span>
<\/div><\/div><\/div><\/div>\n\n\n\n\n\n\n\n\nIn part, this text and illustrations shown are based on research of evaluated literature. If this is the case, the sources are marked in the text by a number, e.g. [2], and the source is listed here.<\/p>\n
In part, however, the sources listed here should simply be understood as recommendations for further reading.<\/p>\n<\/div>\n
\n\n<\/div>\n<\/div>\n\n\n\n[1] Dassault Syst\u00e8mes, P. D., 2023, \u201cProgram Directories Library<\/a>\u201d [Online] [Accessed: 16-Mar-2023]<\/div>\n\n\n\n[2] Red Hat, 2023, \u201cRed Hat Enterprise<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[3] SUSE, L., 2023, \u201cSUSE \u2013 Open Source L\u00f6sungen f\u00fcr Enterprise Server und Cloud<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n[4] Dassault Syst\u00e8mes, 2023, \u201cDS Support Knowledge Base<\/a>\u201d [Online]. [Accessed: 17-Mar-2023]<\/div>\n