cc_staff
1,857
edits
Ansys: Difference between revisions
m
no edit summary
(Marked this version for translation) |
mNo edit summary |
||
| Line 108: | Line 108: | ||
<!--T:19--> | <!--T:19--> | ||
The Ansys [https://www.ansys.com/it-solutions/platform-support Platform Support] | The Ansys [https://www.ansys.com/it-solutions/platform-support Platform Support] page states "the current release has been tested to read and open databases from the five previous releases". The page also provides software and hardware version information defining optimal supported platform infrastructure to run Ansys on for both the current AND previous Ansys releases. | ||
== What's New == <!--T:6739--> | |||
Ansys posts [https://www.ansys.com/products/release-highlights Product Release and Updates] for the latest releases. Similar information for previous releases can generally be pulled up for various application topics by visiting the Ansys [https://www.ansys.com/blog blog] page and using the FILTERS search bar. For example searching on <code>What’s New Fluent 2024 gpu</code> pulls up a document with title <code>[https://www.ansys.com/blog/fluent-2024-r1 What’s New for Ansys Fluent in 2024 R1?]</code> containing a wealth of the latest gpu support information. Specifying a version number in the [https://www.ansys.com/news-center/press-releases Press Release] search bar is also a good way to find new release information. At the time of this writing Ansys 2024R2 is the current release and will be installed when interest is expressed or there is evident need to support newer hardware or solver capabilities. To request a new version be installed submit a problem ticket. | |||
== Service Packs == <!--T:6740--> | == Service Packs == <!--T:6740--> | ||
Ansys regularly releases service packs to fix various issues with its major releases. Therefore starting with Ansys 2024 a separate ansys module will appear on the clusters with a decimal and two digits appearing after the release number whenever a service pack is been installed over the initial release. For example, the initial 2024 release without any service pack applied maybe loaded by doing <code>module load ansys/2024R1</code> while a module with Service Pack 3 applied maybe loaded by doing <code>module load ansys/2024R1.03</code> instead. Most users will likely want to load the latest module version equipped with latest installed service pack which can be achieved by simply doing <code>module load ansys</code>. While its not expected | |||
Ansys regularly releases service packs to fix and enhance various issues with its major releases. Therefore starting with Ansys 2024 a separate ansys module will appear on the clusters with a decimal and two digits appearing after the release number whenever a service pack is been installed over the initial release. For example, the initial 2024 release without any service pack applied maybe loaded by doing <code>module load ansys/2024R1</code> while a module with Service Pack 3 applied maybe loaded by doing <code>module load ansys/2024R1.03</code> instead. If a service pack is already available by the time a new release is to be installed, then most likely only a module for that service pack number will be installed unless otherwise a requeste to install the initial release also is received. | |||
Most users will likely want to load the latest module version equipped with latest installed service pack which can be achieved by simply doing <code>module load ansys</code>. While its not expected service packs will impact numerical results, the changes they make are extensive and so if computations have already been done with the initial release or an earlier service pack than some groups may prefer to continue using it. Having separate modules for each service pack makes this possible. Starting with Ansys 2024R1 a detailed description of what each service pack does can be found by searching this [https://storage.ansys.com/staticfiles/cp/Readme/release2024R1/info_combined.pdf link] for <I>Service Pack Details</I>. Future versions will presumably be similarly searchable by manually modifying the version number contained in the link. | |||
= Cluster batch job submission = <!--T:20--> | = Cluster batch job submission = <!--T:20--> | ||