Part 21 Report - 1995-145
ACCESSION #: 9506130013
The Boeing Company
P.O. Box 3707
Seattle, WA 98124-2207
BOEING
June 1, 1995
G-1151 -RSO-95-224
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,
R. S. Orr
Nuclear Administrator
G-1151 M/S 7A-33
(206) 865-6248
Attachment(s): GTICES Program Report Form No. 95.12
ANSYS Class3 Error Reports 95-30, 95-31, 95-32, 95-33,
95-34, 95-35, and 95-36; 95-07 R1; ANSYS QA Notices
QA95-05 and QA95-06
Georgia Tech Computer Aided Structural Engineering Center
Georgia Institute of Technology
School of Civil & Environmental Engineering
Atlanta, Georgia 30332-0355
USA
404 o 894 o 2260
404 o 894 o 8014 FAX
May 25, 1995
JUN 01 1995
CONTRACTS
Attention: Nuclear Administrator
Boeing Computer Services
P.O.Box 24346, M/S 7A-33
Seattle, Washington 98124-0346
RE: GT STRUDL
Dear Sir or Madam:
Enclosed please find a copy of GTICES PROGRAM REPORT FORM No. 95.12 and a
VENDOR ACKNOWLEDGEMENT FORM. Please sign and return the VENDOR
ACKNOWLEDGEMENT FORM to acknowledge receipt of the GTICES Program Report.
Thank you for reviewing the Program Report and for returning the
Acknowledgement Form.
Best regards,
CASE Center
Catherine Lee
Configuration Control Manager
CL/jhb
Enclosures
GTSTRUDL Program Report Form
GPRF No.: 95.12
DATE: May 25, 1995
FROM: Computer-Aided Structural Engineering Center
Georgia Institute of Technology
Atlanta, Georgia 30332-0355
SEVERITY LEVEL:
x URGENT Problem results in incorrect answers which may not be
apparent or job aborts and cannot be recovered within the
session or job.
_ SERIOUS Problem results in incorrect answers which are obvious or
problem prevents completion of a particular user's task.
_ MINOR Problem can be worked around or problem poses high
frustration factor.
- INFORMATIVE Documentation error, program usage tip, user
inconveniences.
Date Problem Confirmed May 24, 1995
Date Notification Sent May 26, 1995
Computers All
Operating System All
Version All version prior to and including 94.01
Target Release for Correction 95.01
Software Developer
Signature Title
R & D Division
Rami A. Nagib May 25, 1995
Typed or Printed Name Date of Signature
Signature Title
Professional Services Division
Typed or Printed Name Date of Signature
Rev. 2.2
GTSTRUDL Program Report Form
(Continued)
GPRF No.: 95.12
DATE: May 25, 1995
DESCRIPTION:
Generate N point in GTMODELER,
Problem may result in wrong answer or job aborts when more than 20
points are generated along a line using the GEN PT, NPTL menu in
GTModeler. The model will be distorted if one tries to redraw the
screen.
Workaround:
There is no workaround for this problem. The problem will not occur
if less than 20 points are generated.
Applicable Documents:
GTSTRUDL User Manual - Section 7.1.8, (NPTL) GENERATE N POINTS
ALONG A STRAIGHT LINE, Volume 8.
Rev. 2.2
ANSYS (Registered Trademark)
ANSYS, Inc.
201 Johnson Road Telephone 412.746.3304
Houston, PA 15342-1300 Facsimile 412.746.9494
JUN 01 1995
CONTRACTS
May 24, 1995
Dear Class3 Error Recipient:
Enclosed you will find ANSYS Class3 Error Reports 95-30, 95-31, 95-
32, 95-33, 95-34, 95-35, and 95-36 as well as 95-07 R1.
Class3 Error Report 95-07 R1 has been re-issued to include a
workaround.
Also included in this mailing are two ANSYS QA Notices, QA95-05 and
QA95-06. QA95-05 discusses implications of an ANSYS-imposed binary file
size limit. QA95-06 provides clarification on display of large
deflection analysis results in POST1.
Sincerely,
ANSYS, Inc.
Prashant Ambe
Quality Assurance Manager
ANSYS Revision Identifier Description
ANSYS revision identifiers consist of a major revision level, a
minor revision level, a correction level, and occasionally a special
version level. An example of how this is constructed is shown below:
5.0A-10
major revision level special version identifier
minor revision level correction level
Major revision level changes indicate that new features have been added
to the program and that some level of program architecture change and/or
file structure has occurred. Minor revision level changes also indicate
that new features have been added to the program, but files are upwardly
compatible. All known error fixes are included in both minor and major
revisions. Changes to the correction level indicate that it is primarily
an error correction release. Special version identifiers indicate that
one or more additional minor changes have been made to the program,
normally to circumvent an error. Special versions are not general
releases to all ANSYS licensees, since they typically represent errors
occurring only on one system, a subset of our customers who have specific
graphics devices, etc.
The ANSYS revision identifier(s) shown under "corrected in" on the
front side of this Class3 Error Report indicates the first possible
revision that could contain the correction. A major program change
needed to fix an error can dictate that the next minor or major revision
will contain the fix rather than the next correction level. For example,
when errors were being reported while Rev. 4.3A was the latest production
version, most Class3 error reports indicated that 4.3B was the "corrected
in" revision. Others requiring significant code restructuring were
reported as fixed in 4.4. Rev. 4.3B was never released, but Rev. 4.4
contained all error corrections noted as fixed in 4.3B.
An identifier indicated under "corrected in" does not guarantee that
a general release of that revision of ANSYS will occur. It does indicate
that the correction is known and implemented in the coding that would be
part of that general release.
Equivalent Product Identifiers
The ANSYS family of products occasionally undergoes name changes
between revisions and/or changes in the functionality of derived products
(such as ANSYS-PC/LINEAR). To minimize the potential for confusion in
these areas, the important product name equivalences (similar program
functionality and error content) are listed below.
ANSYS/ED contains all errors shown for the full ANSYS product,
starting at Rev. 5.0,
and beyond, unless
otherwise noted.
PC/LINEAR is equivalent to WS/LINEAR at Rev. 4.4A
and ANSYS/LINEAR starting
at Rev. 5.0.
PCTHERMAL is equivalent to WS/THERMAL at Rev.
4.4A,
and ANSYS/THERMAL starting
at Rev. 5.0.
PREPPOST contains relevant the full ANSYS
errors shown for product, for included
pre- and postprocessing
functionality
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-30
KEYWORDS: GUI MAGNETICS POST1 MECHANICAL TORQUE
DESCRIPTION OF ERROR:
The LCSYS and RADTOL fields of the TORQC2D command macro are
reversed when using the TORQC2D dialog box in the Graphical User
Interface (GUI). This could cause incorrect calculation of the torque.
The dialog box for the TORQC2D command macro is found in the following
menu path: Main Menu - General Postproc - Magnetic Calcs - Circular
Torque.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.1 Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Type the TORQC2D command directly in the input window.
COMMENTS:
AUTHOR/CORRECTOR: DATE: May 23, 1995
Eric Clevenger
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. ALL
revisions after "corrected in" are corrected. Manual corrections are
included in on-tine documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-31
KEYWORDS: ENTITY RANGE NEGATIVE INCREMENT BOUNDARY
CONDITIONS
DESCRIPTION OF ERROR:
For commands that permit specifying an entity number range with an
increment (e.g. NODE, NEND, NINC), if a negative value is used for the
increment then the command will not operate on the correct entity
numbers. This can result in various items being incorrect (see comment).
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.1 Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Use positive increments when specifying entity number range.
COMMENTS:
This error has potentially non-obvious results when it is
encountered during application/deletion of items such as loads, boundary
conditions, master DOFs, coupled sets, gaps etc.
AUTHOR/CORRECTOR: DATE: May 23, 1995
Anthon V. Mobley
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. ALL
revisions after "corrected in" are corrected. Manual corrections are
included in on-tine documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-32
KEYWORDS: POST1 RSYS LOCAL CS
DESCRIPTION OF ERROR:
In POST1, the coordinate system for printout or display of results
(RSYS) will not be correctly used if:
1. The RSYS command specifies a user-defined coordinate system
(reference number greater than 10):
and 2. The user-defined system is subsequently re-defined (LOCAL, CS,
CLOCAL, CSKP, etc.);
and 3. The RSYS command is reissued to specify the re-defined system.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.0 Rev. 5.2
Component Products Rev. 5.0 Component Products Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Use a different coordinate system reference number redefining the
system and then use RSYS to activate the new coordinate system, or
specify a different coordinate system (e.g. RSYS.0) before reissuing the
RSYS command to specify the redefined system.
COMMENTS:
In the corrected version, the RSYS command must be reissued after
the user-defined coordinate system is changed
AUTHOR/CORRECTOR: DATE: May 23, 1995
Herb Mroz
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. All
revisions after "corrected in" are corrected. Manual corrections are
included in on-line documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-33
KEYWORDS: PRO/ENGINEER THERMAL STRESS MULTI CONSTRAINT CASES
DESCRIPTION OF ERROR:
Results from any thermal/stress solution run from within the ANSYS-
Pro/ENGINEER environment will be incorrect if more than one constraint
case was defined and active.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
ANSYS-Pro/Engineer Interface 9345 ANSYS-Pro/Engineer Interface 9526
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Select the proper constraint case via the "Sel Cons Case" item under
the "Run Study" menu.
COMMENTS:
The ANSYS/ProFEA User's Guide states that a thermal/stress analysis
will solve only the first constraint case and ignore the remaining cases.
However, if more than one constraint case was defined and active
(default), the ANSYS solver will use a combination of all thermal
constraint cases and the last structural case.
AUTHOR/CORRECTOR: DATE: May 23, 1995
Robert W. Gorman
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. ALL
revisions after "corrected in" are corrected. Manual corrections are
included in on-line documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-34
KEYWORDS: SHELL63 ELEM63 MEMBRANE APPLICATION REACTION FORCES
DESCRIPTION OF ERROR:
The reaction forces produced by SHELL63 using the membrane-only
option (KEYOPT(1)=1) are incorrect when transverse pressures are applied.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.0 Rev. 5.2
ANSYS/LinearPlus Rev. 5.0A ANSYS/LinearPlus Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Use SHELL41 (membrane shell) element.
COMMENTS:
Reaction forces are correct when other types of loads (edge
pressures/point loads) are applied with KEYOPT(1)=1.
AUTHOR/CORRECTOR: DATE: May 23, 1995
Yong-Cheng Liu
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. All
revisions after "corrected in" are corrected. Manual corrections are
included in on-line documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-35
KEYWORDS: PCG SOLVER LARGE STRAIN CONSTRAINT EQUATIONS
DESCRIPTION OF ERROR:
If the PCG solver (EQSLV,PCG) is used with constraint equations in a
nonlinear analysis (Newton-Raphson or modified Newton Raphson), the
constant term of the constraint equation (CE command) changes with the
load step numbers, giving incorrect results.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.1 Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
COMMENTS:
The results are correct if the constant term of each constraint
equation is equal to zero.
AUTHOR/CORRECTOR: DATE: May 23, 1995
Yong-Cheng Liu
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. All
revisions after "corrected in" are corrected. Manual corrections are
included in on-line documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-36
KEYWORDS: COUPLED NODES PICKING INTERACTIVE
DESCRIPTION OF ERROR:
When more than 10 nodes are coupled using interactive picking, nodes
not in the picked set may be included.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.1 Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
1. Limit number of picks to 10 nodes when applying coupling.
or 2. Use select picking to activate the desired nodes then type in
the CP command with ALL for the NODE1 field.
COMMENTS:
This error is the result of an array overwrite. This error may
manifest itself differently on different machines.
AUTHOR/CORRECTOR: DATE: May 23, 1995
Anton V. Mobley
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. All
revisions after "corrected in" are corrected. Manual corrections are
included in on-line documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS (Registered Trademark) CLASS3 ERROR REPORT
ERROR NO: 95-07 R1
KEYWORDS: PRO/ENGINEER THERMAL STRESS REFERENCE TEMPERATURE
DESCRIPTION OF ERROR:
Results from any thermal-stress solution run from within the ANSYS-
Pro/ENGINEER environment will be incorrect unless the intended thermal
expansion reference temperature for the thermal strain calculation is 0
degrees.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
ANSYS-Pro/ENGINEER Interface 9345 ANSYS-Pro/ENGINEER Interface 9526
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
The following two steps should be done:
1. Select the proper constraint case via the "Sel Cons Case" item
under the "Run Study" menu (required only if more than 1
constraint case was defined).
and 2. Include the proper Reference Temperature via the "Use .inp
File" item under the "Run Study" menu using the following
sequence of commands (temp should be the numerical value of the
required Reference Temperature):
/SOLU
TREF, temp
SOLVE
FINISH
COMMENTS:
The thermal expansion reference temperature may be specified in the
Pro/ENGINEER material file. However, this value is not included in the
list of material properties given to the ANSYS program unless a
structural temperature is defined in Pro/MESH.
AUTHOR/CORRECTOR: DATE: May 23, 1995
Bob Gorman
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
*_/ If a product name is not included in the "first incorrect version",
the full ANSYS program is implied. For products not listed, this error
does not apply, but see the reverse side for equivalent product
designations.
Unless noted otherwise, this error report also applies to all revisions
after the first incorrect one and prior to the corrected revision. All
revisions after "corrected in" are corrected. Manual corrections are
included in on-line documentation as appropriate. Please see the reverse
side of this sheet for additional information on ANSYS revision
identifiers.
FORM SASI-QA25
DEC 19, 1988
ANSYS QA NOTICE
NOTICE NO: QA95-05
SUBJECT: POST1 RSYS LARGE DEFLECTION PRNSOL PRESOL
DESCRIPTION:
In POST1, for a large deflection analysis (NLGEOM,ON) the element
stress and strain results displayed by the PRNSOL and PRESOL commands
should state that rigid body rotations are included when rotation of the
data is requested (RSYS). Instead the output header implies that the
stress-strain results are in the requested coordinate system.
Note that this is documented correctly in the Procedures Manual
(section 11.2.3); only the output header is incorrect when these
quantities are listed.
AFFECTED VERSIONS: Rev. 5.0, Rev. 5.0A, Rev. 5.1, and
ANSYS LinearPlus Rev. 5.0A
AUTHOR: DATE: May 23, 1995
Herb Mroz
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
SASI-QA3
AUG. 29, 1993
ANSYS QA NOTICE
NOTICE NO: QA95-06
SUBJECT: SYSTEM FILES SIZE LIMIT
DESCRIPTION:
There is an ANSYS-imposed 8 gigabyte limit for the total size of an
ANSYS binary file. The limit is applicable to all files, but most likely
will be encountered on the .tri files. This affects:
A. all computers which use 32 bit integers (this includes all
computers which run ANSYS except those from Cray Computers)
or B. all computers when the files are specified as type external
(default).
WORKAROUND:
Use the PCG or JCG solver if possible (which do not use a .tri
file), or run on the Cray with the binary files specified as type
internal (/FTYPE,,INT).
COMMENTS:
Because most computers have a file size limit of 2 gigabytes, the 8
gigabyte ANSYS-imposed limit can usually be achieved only by using file
splitting on a .tri file (beta feature at Revisions 5.0A and 5.1). In
this case, the 8 gigabyte limit applies to the total size of the
individual .tri file pieces.
AFFECTED VERSIONS: Rev. 5.0 and beyond
Component Products Rev 5.0A and beyond
AUTHOR: DATE: May 23, 1995
Jim Pasquerell
REVIEWED BY QA: DATE: May 23, 1995
Prashant Ambe
APPROVAL: DATE: May 23, 1995
John A. Swanson
SASI-QA3
AUG, 29, 1993
*** END OF DOCUMENT ***
Page Last Reviewed/Updated Wednesday, March 24, 2021