United States Nuclear Regulatory Commission - Protecting People and the Environment

ACCESSION #: 9902050085


BOEING

Shared Services Group
P.O. Box 3707
Seattle, WA 98124-2207

January 25, 1999

G-1151-SJA-98-033

Document Control Desk
United States Nuclear Regulatory Commission
Washington, D.C. 20555

Reference: a) Boeing Letter G-1151-RSO-92-365 dated August 31, 1992; R.S. Orr to the NRC Operations Center
b) NRC Letter Docket No. 99901227 dated August 12, 1992; L. J. Norrholm to R. S. Orr; Subject: Response to 10 CFR 21 Inquiry

Dear Sir or Madam:

In accordance with the reference correspondence and 10 CFR 21, Boeing is sending the NRC the attached error notice(s) received from our former software suppliers. Because of unknown current addresses, the following former customers were not notified:

Reactor Controls, Inc.
Echo Energy Consultants, Inc.
Nuclear Applications and Systems Analysis Company (Japan)
Nuclear Power Services

Error notices have been sent to our other former customers.

Very truly yours,

Sandra J. Andrews
Nuclear Administrator
Phone: (425) 865-6248
FAX: (425) 865-4851
Mail Stop: 7A-33, or
e-mall: Sandra.J.Andrews@Boeing.com

Enclosure(s): Error Reports 1998-33 through 1998-45, 1998-07 R1, QA1998-10, SCB1998-05 & SCB 1998-06


ANSYS "Register Trademark"

January 20, 1998

Dear Class3 Error Recipient

Enclosed you will find ANSYS Class3 Error Reports 1998-33 through 1998-45, Class3 Error Report 1998-07 R1, ANSYS QA Notice QA1998-10 and ANSYS Support Coordinator Bulletins SCB1998-05 and SC91998-06. These reports were issued in the birth quarter of 1998.

Revised Class3 Error Report

  • Class3 Error Report 1998.07 R.1 has been issued to correct the release in which the error first occured and the release that will be corrected.

QA Notice

  • QA Notice QA1998-10 was issued to alert users of a possible Class3 error in the modal cyclic symmetry solution when using the CYCGEN and CYCSOL commands if element numbering is not sequential.

Support Coordinator Bulletins

  • ANSYS Support Coordinator Bulletin SCB1998-05 was issued to warn of possible licensing errors occurring after changing of system clocks.
  • ANSYS Support Coordinator Bulletin SCB1098-06 was issued to warn of possible license server code changes on window system between ANS YS 5.4 and ANSYS 5.5

Beginning with 1999 reports, Class3 errors; will be delivered by mail to the ANSYS Support Coordinator listed on your ANSYS license agreement semi-annually. Please notify your ASD of any personnel or address changes that should be incorporated into our record for your ANSYS agreement in order to avoid any interruptions in receiving your Class3 Error Report mailings.

Class3 Errors and QA Notices are posted on ANSYS's Internet HomePage. The address is http://www.ansys.com. They am located in the ANSYS Zones sections of the HomePage under "Customer". The username to enter this area is "customer" and effective February 1, 1999 the password will be changed to "werfea1" (We are FEA 1). Users desiring access to Class3 errors on a more timely basis can be added to our email distribution list. To for email notification of reports, simply send an email request including your email address, company name/address and ANSYS agreement number to bonny.podolek@ansys.com If you are a current subscriber to email distribution, please keep us informed of any changes in your email address by emailing bonny.podolek@ansys.com. After two flailed transmissions, your name will be removed from the email distribution list. We are also adding Product Support News distribution to our Class3 error email subscribers. Product Support News provides helpful information and tips on running ANSYS products. Please refer to the subject line of the transmittal to determine what type of mailing you have received.

Included with this quarter's mailing is a customer survey that the ANSYS Inc. Documentation Group created to get your feedback about the ANSYS product documentation. Please take some time to complete the survey and return it to the Documentation Group using one of the methods described on the survey.

For your convenience, also enclosed you will find ANSYS Class3 Error Summary Reports sorted both by error number and keyword for Release 5.5 and Release 5.5.1 of ANSYS program.

I would like to take this opportunity to extend to you wishes for a prosperous new year.

Sincerely,

William J. Bryan
Quality Assurance Manager

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-33

KEYWORDS: EMAG CIRCUIT TRANSIENT

DESCRIPTION OF ERROR:

The Crank-Nicholson integration scheme (THETA=0.5 on the TINTP command, which is the default) for a transient electromagnetic analysis (ANTYPE, TRANS) produces oscillating and therefore unreliable results when using the CIRCU124 massive conductor options:

1. CIRCU124 with Keyopt(1)=6 (2D Massive Conductor Voltage Source), along with PLANE53, Keyopt(1)=4 (2D Circuit Coupled Massive Conductor); or 2. CIRCU124 with Keyopt(1)=7 (3D Massive Conductor Voltage Source), along with SOLID97, Keyopt(1)=4 (3D) Circuit Coupled Massive Conductor).

TYPICAL GUI PATH(S):

Preprocessor>Element Type>Add/Edit/Delete/Solution>New Analysis (Transient)

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Rev. 5.2 Release 5.5.1*_

*_/At Release 5.5.1, the THETA parameter on the TINTP command will defaULt to 1.0 for a problem containing the element CIRCUI124 with the massive conductor options. Additionally, a warning message will be issued if THETA is set less than or equal to 0.5 when using CIRCUI124 or PLANE53 with the massive conductor options.

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

Set the Integration parameter THETA to 1.0:

TINTP,,,,1.0

This corresponds to the backward Euler integration scheme.

AUTHOR/CORRECTOR: DATE: November 5, 1998

Jian-She Wang

REVIEWED BY QA: DATE: November 5,1998

William J. Bryan

APPROVAL: DATE: November 5, 1998

David L. Conover

----------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases aft the first incorrect one and prior to the corrected release. All releases after "corrected in" we corrected. Manual corrections are included in on-line documentation as appropriate. Please see the reverse side of this shoe for additional Information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1---interim release identifier

Major release level -- -- minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-34

KEYWORDS: SHELL181 EDGE PRESSURE DOCUMENTATION

DESCRIPTION OF ERROR:

The documentation in the Elements Manual for SHELL181, the Finite Strain Shell Element, (Section 4.181.1) does not correctly describe how SHELL181 handles edge pressures. The documentation erroneously states:

"Edge pressures are input as force per unit area. The element accounts for change in thickness while calculating pressure load operators in a geometrically nonlinear analysis."

The correct documentation for SHELL181 edge pressures is:

"Edge pressures are Input as force per unit length."

TYPICAL GUI PATH(S):

Main Menu>Preprocessor>Element Type>Add/Edit/Delete>Shell>Hyper 4node181

Main Menu>Solution>Apply>Pressure>On Elements

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.3 User Manual Release 5.5 User Manual

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

Input pressure values in terms of force per unit length for SHELL181 edge pressures.

COMMENTS:

SHELL181 behavior is in conformity with other similar element types in ANSYS (eg. SHELL43, SHELL63).

AUTHOR/CORRECTOR: DATE: November 5, 1998

Grama Bhashyam

REVIEWED BY QA: DATE: November 5, 1998

William J. Bryan

APPROVAL: DATE: November 5, 1998

David L. Conover

---------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1--- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-35

KEYWORDS: CFD FLOTRAN COMPRESSIBLE ENERGY

DESCRIPTION OF ERROR:

When running a compressible flow problem with energy equation solution, the stress work terms are not computed correctly in both two and three dimensional problems. The stress work term appears as a source term In the compressible energy equation and is the product of fluid viscosity and velocity gradients.

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Rev. 5.1 Release 5.5.1

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

COMMENTS:

For most practical problems this error should not ovate a serious problem since the viscosities are generally small. A slight change in solution should be anticipated after this correction.

AUTHOR/CORRECTOR: DATE: November 5, 1998

Deepak Ganjoo

REVIEWED BY QA: DATE: November 5, 1998

William J. Bryan

APPROVAL DATE: November 5, 1998

David L. Conover

---------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed in shown below:

5.5.1--- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-36

KEYWORDS: SPECTRUM GROUPING METHOD VELOCITY ACCELERATION

DESCRIPTION OF ERROR:

If a velocity or acceleration solution is requested for the grouping mode combination method (GRP,,VELO or GRP,,ACEL), then results are incorrect if there were any closely spaced modes. Closely spaced modes are identified in the output by the message "FREQUENCY ... HERTZ PART OF CLOSELY SPACED MODE".

TYPICAL GUI PATH(S):

Main Menu>Solution>Spectrum>Mode Combine

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.4 Release 5.5.1

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

Edit the file.mcom and multiply the factors on the closely spaced mocks (on the LCFACT commands) by (2*_/PI*_/freq)**_/N, where freq is the frequency of the mode (in Hertz) and N is 1 for velocity solutions and 2 for acceleration solutions.

COMMENTS:

AUTHOR/CORRECTOR: DATE: November 5, 1998

David L. Conover

REVIEWED BY QA: DATE: November 5, 1998

William J. Bryan

APPROVAL: DATE: November 5, 1998

Mark C. Imgrund

----------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-37

KEYWORDS: GRAPHICS POWERGRAPHICS AVPRIN

DESCRIPTION OF ERROR:

The von Mises equivalent strain (eg., EPEL,EQV) in PowerGraphics mode (/GRAPH,POWER) may not be correct when de effective Poisson's ratio is changed by the AVPRIN command.

TYPICAL GUI PATH (S):

Main Menu>General Postproc>Element Table>Define Table

Main Menu>General Postproc>List Results>List Nodal Solution Data

Main Menu>General Postproc>Options for Outp

Main Menu>General Postproc>Path Operations>Map onto Pat

Main Menu>General Postproc>Plot Results>Contour Nodal Solution Data

Main Menu>General Postproc>Plot Results>Contour Element Solution Data

Utility Menu>List>Results>Nodal Solution

Utility Menu>List>Results>Options

Utility Menu>Plot>Results>Contour Plot>Elem Solution

Utility Menu>Plot>Results>Contour Plot>Nodal Solution

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.4 Release 5.5.1

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

The user should issue an ALLSEL command after the AVPRIN command to force PowerGraphics to calculate the equivalent strain using the newly input effective Poisson's ratio.

AUTHOR/CORRECTOR: DATE: November 5, 1998

Paul Tallon

REVIEWED BY QA: DATE: November 5, 1998

William J. Bryan

APPROVAL: DATE: November 5, 1998

David L. Conover

---------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-38

KEYWORDS: MAGNETICS LMATRIX COILS INDUCTANCE

DESCRIPTION OF ERROR:

The LMATRIX command will produce incorrect inductance results for cases where there is an excited coil in the model that is not identified in the command arguments (Coilname and Curname).

TYPICAL GUI PATH(S):

Main Menu>Solution>Electromagnet>Mode Combine

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.5 Release 5.5.1

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

COMMENTS:

Ensure that all excited coils are included in the LMATRIX command arguments.

AUTHOR/CORRECTOR: DATE: December 10, 1998

Miklos Gyimesi

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

------------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-39

KEYWORDS: LSDYNA EDWELD NUMCMP

DESCRIPTION OF ERROR:

Node numbers in spot-weld definitions (EDWELD command) for ANSYS/LS-DYNA are not redefined when node number are compressed (NUMCMP command). Any spot weld definition on a node that was re-numbered due to a node number compress operation (NUMCMP) will be incorrect.

TYPICAL GUI PATH(S):

Isdyna options>Spotweld>define, list

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.4 Release 5.5.2

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

Define spotwelds only after using the NUMCMP command.

COMMENTS:

AUTHOR/CORRECTOR: DATE: December 10, 1998

Ahmed Salem

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-40

KEYWORDS: MODAL CYCLIC SYMMETRY EXPAND CWRITE LCDEF LCOPER

DESCRIPTION OF ERROR:

POST1 load case combinations (LCxx family of commands) produce incorrect results if they are used with a modal cyclic symmetry solution in which the results are expanded to the full model (EXPAND command).

TYPICAL GUI PATH(S):

Main Menu>General Postproc>Modal Cyclic Sym

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.4 Release 5.5

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

COMMENTS:

AUTHOR/CORRECTOR: DATE: December 10, 1998

John A. Swanson

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

--------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-41

KEYWORDS: EMAG HF120 ELEMENT VOLUME WEDGE SHAPE

DESCRIPTION OF ERROR:

The calculated element volume for the wedge option of element HF120 is incorrect. The element volume is accessed in POST1 using the ETABLE command with the Item VOLU option.

TYPICAL GUI PATH(S):

General Postproc>Element Table>Define Table>Add

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.4 Release 5.5

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

COMMENTS:

AUTHOR/CORRECTOR: DATE: December 10, 1998

Jian-She Wang

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

--------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-42

KEYWORDS: SOLID45 SOLID92 EXPAND CYCSOL MODAL CYCLIC SYM

DESCRIPTION OF ERROR:

Stresses, strains, and strain energies obtained after using the command EXPAND in POST1 are incorrect for models consisting of any of the element types SOLID45, SOLID92, and SOLID95 for modal cyclic symmetry analysis performed by the CYCSOL command.

TYPICAL GUI PATH(S):

Main Menu>General Postproc>Modal Cyclic Sym

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Release 5.5 Release 5.5.2

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

COMMENTS:

AUTHOR/CORRECTOR: DATE: December 10, 1998

Pakal Rahulkumar

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

----------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1 --- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-43

KEYWORDS: GRAPHICS POWERGRAPHICS RESULTS LISTING

DESCRIPTION OF ERROR:

PowerGraphics nodal results listings (i.e. PRNSOL) for all shell elements may not have the TOP/BOTTOM results listed in the correct order.

TYPICAL GUI PATH(S):

Utility Menu>List>Results>Nodal Solution...

Main Menu>General PostProc>List Results>Nodal Solution

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Rev. 5.1 Rev. 5.5.2

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

Use Full Graphics (i.e./GRAPH,FULL) to verify TOP/BOTTOM results for shell elements or look at the plots.

COMMENTS:

AUTHOR/CORRECTOR: DATE: December 10, 1998

Paul Tallon

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

----------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1--- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released.

All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-44

KEYWORDS: FMAGSUM FMAGBC EMAG FORCES 2D

DESCRIPTION OF ERROR:

The FMAGSUM command macro will report incorrect virtual work forces for two-dimensional planar and axisymmetric problem for cases where the printout summary header includes the term "Force-Z". This may occur when element types other than magnetic elements are present in the model.

TYPICAL GUI PATH(S):

Main Menu>General Postproc>Elec&Mag Calc>Comp. Force

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Rev. 5.2 Release 5.5.2

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

The virtual work forces may be obtained correctly by using the ETABLE command to extract the data from the element NMISC record, and then summing the data (SSUM) to obtain the total force. The data is stored in the "air" elements attached to the element component prescribed in FMAGSUM. See the Elements Manual for the location in the NMISC record containing the virtual work forces.

COMMENTS:

AUTHOR/CORRECTOR: DATE: December 10, 1998

Vladimir Zhulin

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

--------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1--- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-45

KEYWORDS: MAGNETICS PLANE53 SOLID97 COILS INDUCTANCE

DESCRIPTION OF ERROR:

Inductance values (NMISC item 9 for PLANE53 and NMISC item 17 for SOLID97) are incorrect for voltage-fed stranded coils (PLANE53 or SOLID97 with Keyopt(1)=2) or circuit-coupled stranded coils (PLANE53 or SOLID97 with Keyopt(1)=3 or 4) except under the following conditions:

The problem is linear (constant permeability); and only a single coil exists in the model; and there are no permanent magnets in the model.

TYPICAL GUI PATH(S):

Preprocessor>Element Type>Add>Magnetic Vector>Vect Quad 8nod53

Preprocessor>Element Type>Add>Magnetic Vector>Vector Brick 97

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

Rev. 5.2 Release 5.6 Elements Manual

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

In Release 5.5 or later, use the LMATRIX command to compute inductance for single or multiple coil systems.

COMMENTS:

Computed field solutions using the voltage-fed or circuit-coupled options in PLANE53 or SOLID97 are correct and not limited to the above noted restrictions. Only computed inductance values are limited to be valid under the noted restricted conditions.

AUTHOR/CORRECTOR: DATE: December 10, 1998

Miklos Gyimesi

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

-------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1

--- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS CLASS3 ERROR REPORT

ERROR NO: 1998-07 R1

KEYWORDS: SPECTRUM PSD PSDFRQ PSDVAL

DESCRIPTION OF ERROR:

If PSD solutions erroneously produce negative numbers for the diagonal terms of modal covariance matrix (i.e., where mode i=mode j), the input PSD curve is improperly represented. Consequently, the 1 sigma results mar be incorrect.

TYPICAL GUI PATH(S):

Solution>Spectrum>PSD vs Freq

FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/

[Red line: Release 5.3 Release 5.5.2]

SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:

Verify that there are no negative diagonal terms in the modal covariance matrix, and if not, the calculation was performed as documented.

COMMENTS:

[Red line: The diagonal terms of modal covariance matrix must be positive numbers. The error can be seen directly from the output. It is difficult to predict the error from the input because the input PSD curve is transformed into polynomials by internal implementation. The chance of incorrect 1 sigma results due to negative diagonal terms is rare and the incorrect results are usually unreasonably huge].

AUTHOR/CORRECTOR: DATE: December 10, 1998

Mu-Tsang Chen

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

----------

*_/Unless noted otherwise, this report applies to all ANSYS family products which contain the described feature in the indicated Release(s). See the reverse side for details regarding product applicability.

Unless noted otherwise, this report also applies to all releases after the first incorrect one and prior to the corrected release. All releases after "corrected in" are corrected. Manual corrections are included inn on-line documentation as appropriate. Please see the reverse side of this sheet for additional information on ANSYS release identifiers.

ANSYS Release Identifier Description

ANSYS release identifiers consist of a major release level, a minor release level, and an interim release identifier (in some cases). An example of how this is constructed is shown below:

5.5.1

--- interim release identifier

major release level -- --minor release level

Major release level changes indicate that new features have been added to the program and that some level of program architecture change and/or file structure may have occurred. Minor release level changes also indicate that new features have been added to the program, but files are upwardly compatible. Interim releases are primarily for changes that are needed to support the functionality of other products being released. All known error fixes are included in minor, major and interim releases.

For example, a Class3 Error Report with "5.4 for FIRST INCORRECT VERSION and "5.5.2" for "CORRECTED IN" would apply to all 5.4 releases, the 5.5 release and the 5.5.1 release.

An identifier that is indicated under "corrected in" does not guarantee that a general distribution of that release of ANSYS will occur. It does indicate that the correction is known and implemented in that or any subsequent release.

Equivalent Product identifiers

The ANSYS family of component products occasionally undergoes name changes between releases and/or changes in the functionality of derived products (such as ANSYS-PC/LINEAR). To minimize the potential for confusion in these areas, unless otherwise noted on the front side of the Class3 Error Report, the error report applies to all ANSYS family products (including standalone component products) that contain the described feature(s) in the designated release(s).

ANSYS QA NOTICE

NOTICE NO. QA1998-10

SUBJECT: CYCGEN CYCSOL

DESCRIPTION:

This QA Notice describes a potential Class3 error for which the full scope has not yet been determined. When the full scope of this error is determined, this QA Notice will be updated and re-issued along with a Class3 Error Report, if required.

A modal cyclic symmetry solution using the CYCGEN and CYCSOL commands may not produce correct results if there is any break in the element numbering sequence in the mode. Currently, this error has only been seen to cause termination of the run with an error message but the possibility of a successfully completed solution with incorrect solution results has not been ruled out.

AFFECTED VERSIONS: Not yet determined

Note that CYCGEN and CYCSOL were first introduced in Release 5.4.

SUGGESTED USER ACTION:

Compress all element numbers (NUMCMP, ELEM) before performing CYCGEN.

AUTHOR/CORRECTOR: DATE: December 10, 1998

Kenneth G. Podlaszewski

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

ANSYS SUPPORT COORDINATOR BULLETIN

SCB 1998-05

KEYWORDS: YEAR 2000 TESTING

Moving the system clock forward to do year 2000 testing and then back can result in the ANSYS program (all releases) not starting due to licensing errors. To prevent this from happening, year 2000 testing should be done on a computer system that:

Is not being used for ANSYS production work

Is not the ANSYS license server

Is not part of the corporate network

Will be completely restored after all year 2000 testing has been completed

For information on how to obtain ANSYS year 2000 test license keys, visit http://www.ansys.com/Products/year 2000/y2ktest.html or contact your ASD.

AUTHOR/CORRECTOR: DATE: December 10, 1998

Sam Murgie

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL DATE: December 10, 1998

David L. Conover

ANSYS SUPPORT COORDINATOR BULLETIN

SCB 1998-06

KEYWORDS: LICENSING WINDOWS SYSTEM SERVERCODE

Enhancements to the Elan License Manager software supplied with ANSYS 5.5 may cause the server code on your ANSYS license server machine to be different at ANSYS 5.5 than It was at ANSYS 5-4. This is true only on some, but not all Windows systems. Unix license severs are unaffected. Those Windows systems affected will be unable to instal license keys either during the ANSYS 5.5 Installation process or by using the ANS-ADMIN utility once ANSYS 5.5 is installed.

If you encounter problems installing a license key on a Windows license server machines You can determine if this machine's server code changed by running both the 5.4 and 5.5 ANS_ADMIN option Generate a license server code. If the values returned are different, then the machine's code has changed, and the patch described below is required to instal the license key. Additional, the GETSERV/GETNET utility supplied with ANSYS 5.5 and 5.5.1 does not indicate whether or not your server code changed, since it always returns the same server code as ANSYS 5.4.

ANSYS has developed a correction which is available from ANSYS named ANSYS Service Pack #3 for Release 5.5 (http://www.ansys.com/Enhancements/spindex.html [EXIT]). Note that a username and Password are required to obtain this correction. This correction is included on ANSYS 5.5.1 media labeled as including ANSYS Service Pack #3 and will subsequently be included in ANSYS Release 5.5.2. Customers who have already received ANSYS 5.5.1 will automatically be sent 5.5.1 Windows platform installation media containing ANSYS Service Pack #3. The correction includes a fix so that the GETSERV/GETNET utility returns the correct server code, and a fix for the Installation program and ANS_ADMIN utility to allow your license keys to be installed.

AUTHOR/CORRECTOR: DATE: December 10, 1998

Julie Lesko

REVIEWED BY QA: DATE: December 10, 1998

William J. Bryan

APPROVAL: DATE: December 10, 1998

David L. Conover

ANSYS 5.5 Documentation Survey

Please help us to evaluate the ANSYS 5.5 documentation by answering the following questions. Questions are divided into two sections: one section for questions about the overall documentations, and another for questions about the installation process and documentation. (The overall documentation includes Analysis Guide; Commands, Elements, and Theory References; Operations Guide; and Installation Guides.) If you are not personally Involved with the Installation process, please feel free to forward the second part of the survey to someone at your company who would be better suited to answer questions about installing ANSYS.

When you have completed the survey, you can return it to the ANSYS, Inc.

Documentation Group in either of these ways:

  • Fax it to us at: (724) 514-1991
  • Send it via U.S. mail to: ANSYS Documentation Group

    ANSYS, Inc.
    Southpointe
    275 Technology Drive
    Canonsburg, PA 15317

We would appreciate receiving your completed surveys by March 15, 1999; however, we will continue to accept them throughout the year.

Section 1. "Overall Documentation" omitted.

ANSYS 5.5 Documentation Survey

Section 1. "Overall Documentation continued" omitted.

Which do you use most often to find information about new or changed features in ANSYS?

[ ] ANSYS Home Page
[ ] Release Notes
[ ] Quick Reference Guide
[ ] Other

Table "Which help system do you prefer when you are:" omitted.

Thank you for your participation!

ANSYS 5.5 Documentation Survey

Section 2. Installation Process and Documentation

If you are involved with the installation of ANSYS at your site, please answer the following questions regarding the installation Process and documentation. ff you are not personally involved with the installation process, please feel free to forward this part of the survey to someone at your company who would be better suited to answer these questions.

When you have completed the survey, you can return it to the ANSYS, Inc.

Documentation Group in either of these ways:

  • Fax it to us at: (724) 514-1991

  • Send it via U.S. mail to: ANSYS Documentation Group

    ANSYS, Inc.
    Southpointe
    275 Technology Drive
    Canonsburg, PA 15317

We would appreciate receiving your completed surveys by March 15, 1999; however, we will continue to accept them throughout the year.

Is this a row installation? [ ] Yes [ ] No

Table "Installation: Only one reply per question please" omitted.

If you answered anything other than (4) or (5), please indicate below how you think we can improve the installation process and/or documentation:

Where else would you like to find information about new or changed installation procedures in ANSYS?

[ ] ANSYS Home Page
[ ] Release Notes
[ ] Quick Reference Guide
[ ] Other

Thank you for your participation!


Figure 1. ANSYS 5.5 Class 3 Error Summary By Keyword


Figure 2. ANSYS 5.5 Class 3 Error Summary By Report Number


Figure 3. ANSYS 5.5.1 Class 3 Error Summary By Keyword


Figure 4. ANSYS 5.5.1 Class 3 Error Summary By Report Number


*** END OF DOCUMENT ***
Page Last Reviewed/Updated Thursday, March 29, 2012