Abaqus licensing is built on a token system with many factors that contribute to token utilization.
Abaqus CAE (the Graphical User Interface) always checks out exactly one CAE token (or Interactive Seat) for each active user – these are tracked and purchased separate of tokens.
Each time you execute Abaqus, one or more tokens are “checked-out” from the license server. Once your execution has finished, the tokens are “checked back in” to the pool and made available again. The number of tokens used depends on how you use Abaqus. Examples include, if you are running the interactive CAE mode or if you are taking advantage of its parallel processing capabilities.
The number of tokens is determined by how many CPU cores you wish to utilize. A single CPU core requires 5 tokens and additional token requirements can be calculated by using: 5 x N0.422 , with N being the number of CPU cores.
The tables below illustrate these licensing requirements:
Abaqus Tokens per Core | ||||||||||
CPU Cores | 1 | 2 | 4 | 8 | 12 | 16 | 24 | 32 | 64 | 128 |
Abaqus Tokens | 5 | 6 | 8 | 12 | 14 | 16 | 19 | 21 | 28 | 38 |
Abaqus CAE Tokens per Simultaneous User (across Missouri S&T) | |||||
Users | 1 | 2 | 3 | 4 | 5 |
CAE Tokens | 1 | 2 | 3 | 4 | 5 |