Today, we have made several major changes to the Abaqus configuration on the RWTH-HPC systems. These changes include an automatic configuration of many batch job parameters which previously have been generated on-the-fly as part of the example batch script we described in our Abaqus documentation .
With this new setup, users should experience less problems when starting Abaqus batch jobs and receive descriptive error messages including suggested solutions when something goes wrong during configuration. These changes only affect Abaqus 2020 and newer.
Do I need to change my batch scripts?
No. The previous example batch scripts still work. However, you may omit the part that generates a local abaqus_v6.env file. If such a file exists in the job’s working directory, its settings will override the system settings but in most cases these are identical as of now.
What to do if I experience problems?
If you have trouble running the Abaqus GUI on a frontend node, please make sure to delete the abaqus_v6.env file from the working directory. Alternatively, you can try starting the GUI from another directory. If you still experience problems or if your batch jobs behave in an unexpected fashion, please report the issue to servicedesk@itc.rwth-aachen.de
