E Verification procedure

Appendix E: Verification procedure

The verification procedure checks the installation of all licensed Abaqus products and reports on the success or failure of verification for each product. The verification procedure runs automatically during the Abaqus installation procedure, but only a subset of the products are verified (see the install option below for details). The verification procedure can be run also as an Abaqus command option and from the Start menu on Windows platforms at any time following the installation.

The procedure runs verification problems for each licensed product and compares the results to reference values. The command line options are not affected by license type; that is, the verification procedure attempts to verify all products named in the command. Before the verification procedure is run, licensing and system requirements are checked for the selected product(s). If a teaching academic license is detected, the verification procedure that is run during installation checks only Abaqus/Standard, Abaqus/Explicit, and Abaqus/CAE.

Product verification is skipped if the product is not licensed or if it fails to meet system requirements. The command line options -NoLicenseCheck and -NoSystemCheck bypass these checks.

The verification problems for all Abaqus products are extracted automatically from the disk during the installation. When it runs, the verification procedure attempts to create a new directory called verify in the current working directory. During the Abaqus installation procedure, the verify directory is created in the release installation_info directory.

To run the verification procedure from the command line:

Run the procedure by typing the following command:

abaqus verify [-adams -all -ams -atom -cae -catiav4 -catiav5
-cfd -contextHelp -cPerf -dcatiav5 -design -docUrl -exp -foundation -help
-ideas -install -ioPerf -log -make -moldflow -noGui -NoLicenseCheck
-NoSystemCheck -parallel -param -parasolid -proe -retainFiles
-scripting -std -swi -user_exp -user_std -verbose -viewer]

Common options

`all`	Verify all licensed products. All other verification options except `log`, `NoLicenseCheck`, and `NoSystemCheck` are ignored.
`help`	Print summary of `verify` usage.
`install`	Verify the subset of products that are verified during installation. They include `user_std` (or `std`), `user_exp` (or `exp`), `param` (`std` or `exp`), and `cae` (or `viewer`). All other verification options except `log`, `NoLicenseCheck`, and `NoSystemCheck` are ignored.
`log`	Direct all output to a file named `verify.log` in the current working directory.

Product options

`ams`	Verify Abaqus/AMS.
`atom`	Verify Abaqus/CAE Topology Optimization Module.
`cae`	Verify Abaqus/CAE.
`cfd`	Verify Abaqus/CFD.
`design`	Verify Abaqus/Design.
`exp`	Verify Abaqus/Explicit.
`foundation`	Verify Abaqus/Foundation.
`param`	Verify parametric studies in Abaqus.
`std`	Verify Abaqus/Standard.
`user_exp`	Verify Abaqus/Explicit with user subroutines. Required FORTRAN compiler and libraries must be installed.
`user_std`	Verify Abaqus/Standard with user subroutines. Required FORTRAN compiler and libraries must be installed.
`viewer`	Verify Abaqus/Viewer.

Translator options

`adams`	Verify Abaqus Interface for MSC.ADAMS.
`catiav4`	Verify Geometry Translator for CATIA V4.
`catiav5`	Verify Geometry Translator for CATIA V5.
`dcatiav5`	Verify Direct Geometry Import for CATIA V5 (Direct Geometry Import is a component of the CATIA V5 Associative Interface). Verifies geometry import capability in Abaqus/CAE; does not verify installation or functionality of the CATIA V5 Associative Interface plug-in.
`ideas`	Verify Geometry Translator for I-DEAS.
`moldflow`	Verify Abaqus Interface for Moldflow.
`parasolid`	Verify Geometry Translator for Parasolid.
`proe`	Verify Geometry Translator for Pro/ENGINEER (the Geometry Translator is a component of the Pro/ENGINEER Associative Interface). Verifies geometry import capability in Abaqus/CAE; does not verify installation or functionality of the Pro/ENGINEER Associative Interface plug-in.
`swi`	Verify Geometry Translator for SolidWorks (the Geometry Translator is a component of the SolidWorks Associative Interface). Verifies geometry import capability in Abaqus/CAE; does not verify installation or functionality of the SolidWorks Associative Interface plug-in.

Additional options

`contextHelp`	Verify Abaqus/CAE context-sensitive help functions.
`cPerf`	Verify Abaqus/CAE performance.
`docUrl`	Verify Abaqus HTML documentation URL.
`ioPerf`	Verify I/O performance.
`make`	Verify the abaqus make utility.
`noGui`	Verify the `-noGUI` option for Abaqus/CAE and Abaqus/Viewer.
`NoLicenseCheck`	Requires `all`, `install`, or a list of product options. Run the verification procedure for the specified products but bypass all licensing checks. The procedure attempts to verify all selected products regardless of licensing.
`NoSystemCheck`	Requires `all`, `install`, or a list of product options. Run the verification procedure for the specified products but bypass all system requirement checks. The procedure attempts to verify all selected products regardless of system requirements.
`parallel`	Verify Abaqus analysis jobs using parallelization.
`scripting`	Verify the Abaqus scripting interface.
`retainFiles`	Retain all verification files in the `verify` directory (by default, the files are deleted after a successful verification).
`verbose`	Include additional details for debugging purposes.

If a product selected for verification is not licensed, an Abaqus warning is displayed for the selected product and the verification of other selected products continues.

To run the verification procedure on Windows platforms:

From the taskbar, click Start.
From the menu, select ProgramsAbaqus releaseVerification, where release corresponds to the release you wish to verify.
This procedure attempts to verify all licensed products. Use the command line option to verify individual products.

Reviewing and resolving verification procedure failures

If the verification procedure finishes successfully, all files and the verify directory are removed (unless you use the retainFiles option). Error diagnostics for all products that fail verification remain in the verify directory. It is very important that you review these error messages.

The following suggestions may help you to correct common installation errors that cause the verification procedure to fail:

Make sure that the license file was installed properly. If there are problems with the license file, error messages will be written to standard output.
Make sure that you have not tried to execute Abaqus products for which you are not licensed.
Make sure that the operating system and compiler level are consistent with those specified for this release under System Information on the Support page at www.simulia.com.

If the error messages and these suggestions are insufficient to verify the installation, check for information about installation problems, resolutions, and verification in the Dassault Systèmes DSX.ECO Knowledge Base at www.3ds.com/support/knowledge-base or the SIMULIA Online Support System, which is accessible through the My Support page at www.simulia.com.

If you are still unable to resolve the problem, contact your local office or representative for help. An overview of support options is available in the Dassault Systèmes DSX.ECO Knowledge Base at www.3ds.com/support/knowledge-base or the SIMULIA Online Support System, which is accessible through the My Support page at www.simulia.com.