Part 21 Report - 1996-203
ACCESSION #: 9512290071
Information & Support Services
P. O. Box 3707
Seattle, WA 98124-2207
December 19,1995
G-1151-SJA-95-548
Document Control Desk
United States Nuclear Regulatory Commission
Washington, D. C. 20555
BOEING
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
Tenera Engineering Services
Error notices have been sent to our other former customers.
Very truly yours,
Sandra J. Andrews
Nuclear Administrator
G-1151 M/S 7A-33
(206) 865-6248
Attachment(s): ANSYS Class3 Error Reports 95-60, 95-61, 95-62 and
95-13R1. Also, ANSYS QA Notices QA95-09 and QA95-10
ANSYS [Registered Trademark]
ANSYS, Inc.
201 Johnson Road Telephone 412.746.3304
Houston, PA 15342-1300 Facsimile 412.746.9494
December 7, 1995
Dear ANSYS Class3 Error Recipient:
Attached you will find ANSYS Class3 Error Reports 95-60, 95-61 and
95-62. Also enclosed are ANSYS QA Notices QA95-09 and QA95-10.
QA Notice QA95-09 has been issued to clarify the use of element
CIRCU124.
QA Notice QA95-10 contains an errata sheet that lists the features
in the ANSYS Program that were known to be incorrect at the time Rev.
5.2 was released.
Also included is ANSYS Class3 Error Report 95-13 R1. This report
has been revised to clarify the original Class3 Error Report 95-13 and
update the suggested user actions for running on uncorrected versions.
Sincerely,
ANSYS Inc.
William J. Bryan
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:
Figure omitted
Major revision level changes indicate that new features have been
added to the program and that some level of program architecture change
an/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 the full ANSYS product, starting
shown for 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.
PC/THERMAL is equivalent to WS/THERMAL at Rev. 4.4A,
and ANSYS/THERMAL starting at Rev.
5.0.
PREPPOST contains relevant the full ANSYS product, for
errors shown for included pre- and postprocessing
functionality
ANSYS [Registered Trademark] CLASS3 ERROR REPORT
ERROR NO: 95-60
KEYWORDS: GRAPHICS POST1 SET POWERGRAPHICS SYSTEM
DESCRIPTION OF ERROR:
With powergraphics turned on (i.e./GRAPH,POWER or by pressing the
POWRGRPH button in the toolbar), displacements used for graphical
processing are cumulatively added together when multiple SET commands are
issued in POST1. This affects only the display and query picking.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.2 SUN, SGI, IBM, HP, and Rev. 5.3
DEC Alpha/OFS versions only
Component Products Rev. 5.2 Component Products Rev. 5.3
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
For a single load set, do not issue the SET command more than once.
For multiple load sets, turn powergraphics off (i.e. /GRAPH, FULL or by
using the POWRGRPH button in the toolbar) or, after issuing the SET
command, change the number of element facets (/EFACET command) and replot
the deformed shape.
COMMENTS:
Printed displacements (i.e., displacements from PRDISP in the output
or in list windows) are unaffected by this error. Other results are also
unaffected by this error.
AUTHOR/CORRECTOR: DATE: December 4, 1995
Paul Tallon
REVIEWED BY QA: DATE: December 4, 1995
William J. Bryan
APPROVAL: DATE: December 4, 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-61
KEYWORDS: POST1 LCASE LCFACT
DESCRIPTION OF ERROR:
In POST1, when reading in a load case (LCASE command) with active
scale factors (LCFACT command), the non-summable data are not set to zero
possibly leading to mis-interpretation of data by user.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.0 Rev. 5.3
Component Products Rev. 5.0A Components Products Rev. 5.3
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Ignore the non-summable data.
COMMENTS:
AUTHOR/CORRECTOR: DATE: December 4, 1995
Herb Mroz
REVIEWED BY QA: DATE: December 4, 1995
William J. Bryan
APPROVAL: DATE: December 4, 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-62
KEYWORDS: SPECTRUM SPRS DSUM
DESCRIPTION OF ERROR:
The DSUM Method of Mode Combination (MCOMB,DSUM) does not use the
absolute value of the modal responses during summation.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.0 Rev. 5.3
ANSYS/LinearPlus Rev. 5.0A ANSYS/LinearPlus Rev. 5.3
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Edit the file.mcom and change all negative values on the LCFACT
commands to positive values. In addition, the command LCABS,ALL,1 should
be added after each LCDEF command in the file.
COMMENTS:
AUTHOR/CORRECTOR: DATE: November 30, 1995
Ashraf Ali
REVIEWED BY QA: DATE: November,30, 1995
William J. Bryan
APPROVAL: DATE: November 30, 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-13 R1
KEYWORDS: MODAL PRESTRESS LARGE DEFLECTION STRESS STIFFENING
DESCRIPTION OF ERROR:
A pre-stressed modal analysis performed based upon a successful
large deflection (NLGEOM, ON) analysis will give incorrect frequencies
for BEAM3 and BEAM54.
FIRST INCORRECT VERSION(S):*_/ CORRECTED IN:*_/
Rev. 5.0 Rev. 5.1 (BEAM4)
Rev. 5.2 (BEAM3, BEAM54)
ANSYS/LinearPlus Rev. 5.0A ANSYS/LinearPlus Rev. 5.2
SUGGESTED USER ACTION FOR RUNNING ON UNCORRECTED VERSION:
Use BEAM23, BEAM24 or BEAM44 if using Revision 5.0 or 5.0A. Also,
you may use BEAM4 at Revision 5.1.
COMMENTS:
AUTHOR/CORRECTOR: DATE: December 4, 1995
Yong-Cheng Liu
REVIEWED BY QA: DATE: December 4, 1995
William J. Bryan
APPROVAL: DATE: December 4, 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-09
SUBJECT: EMAG CIRCU124 CIRCUIT SIMULATION
DESCRIPTION:
Changing real constants between load steps for electric circuit
transient simulation involving inductor, capacitor or mutual inductor
options in CIRCU124 may result in loss of solution accuracy across
different platforms. Up to 3% error in solutions has been observed.
AFFECTED VERSIONS: Rev. 5.2 with Emag 2D, Emag 3D
COMMENTS:
CIRCU124 as implemented in Rev. 5.2 has only linear circuit element
options, while changing real constants is a nonlinear switching
operation. During such an operation, the inductor voltage and capacitor
current may become discontinuous.
If real constants have to be changed, provide the correct initial
inductor current and capacitor voltage.
AUTHOR: DATE: November 30, 1995
Jian-She Wang
REVIEWED BY QA: DATE: November 30, 1995
William J. Bryan
APPROVAL: DATE: November 30, 1995
John A. Swanson
ANSYS QA Notice
NOTICE NO. QA95-10
SUBJECT:. 5.2 FEATURES LIMITATIONS ERRORS
DESCRIPTION:
The attached errata sheets indicate the list of those features in
the program that were known to be incorrect at the time Rev. 5.2 was
released. Some of these limitations could cause Class3-type errors if
their presence is not known to the user. Even though this information is
part of each ANSYS Rev. 5.2 shipment, the information is supplied here to
ensure that all users are aware of these known Rev.
5.2 limitations.
AFFECTED VERSIONS: Rev. 5.2
AUTHOR: DATE: December 4,1995
William J. Bryan
REVIEWED BY QA: DATE: December 4, 1995
Mark C. Imgrund
APPROVAL: DATE: December 4, 1995
John A. Swanson
Page 1 of 4
- NOTICE -
Program Errata Items
1. The calculated current in the 3-D Massive source option for
CIRCU124 is incorrect if a current load is applied and a 3-D
model simulating an infinitely long straight massive conductor
that is circuit-fed is being modeled. However, the calculated
voltages and resulting finite element domain solution is
correct. Applying a volt loading gives correct results.
2. Overconstraining the VOLT degree of freedom could lead to
incorrect results in the massive circuit element (CIRCU124,
KEYOPT(1)=7). Care must be used in assigning boundary
conditions to a circuit-coupled 3-D massive conductor. Results
for the plane and solid elements are correct.
The massive conductor should not have VOLT constraints placed
directly on a conductor face that connects to the massive
circuit element. If a constraint is warranted, it should be
placed on the node of the massive circuit element instead, in
which case the face nodes of the finite element conductor
should be coupled. See Figure 8.1-11 in the Procedures manual
for clarification of boundary conditions for circuit-fed
massive conductors.
3. When coupling ANSYS electromagnetic elements with FLOTRAN fluid
elements through Lorentz forces, the units used are
inconsistent. The electromagnetic element produces Lorentz
forces with units of force, while the FLOTRAN element accepts
nodal body forces (via the BF command) with units of
force/volume. Instead of directly loading the forces onto the
FLOTRAN element using the LDREAD command, a macro should be
used. This macro may be retrieved by contacting ANSYS
Technical Support for the FLOTRAN or electromagnetic products.
A macro is also required to load Lorentz forces from a harmonic
electromagnetic analysis. Both macros are currently restricted
to quad elements. Transfer of element heat generation (Joule
heating) is not affected by this and may be done directly with
the LDREAD command.
4. A dialog box is missing from the GUI that allows selecting p-
elements based upon their exclusion or inclusion from
convergence checking. The user must issue the command
ESEL,,PEXC or ESEL,,PINC directly.
Page 2 of 4
5. The fatigue menu of POST 1 is incorrectly filtered in the GUI.
If the fatigue menus are needed, then issue the following
command to be able to get into the menus (after setting GUI
preferences):
KEYW,PR_SET,0
After leaving the fatigue menus, issue the following command so
that filtering is correct for the rest of the GUI:
KEYW,PR_SET,1
6. Parallel Processing is not available on SUN multiprocessor
machines at initial release. A parallel processing version for
SUN will be released at a later date.
7. When using the CDWRITE command in any of the component products
(Emag-2D, Emag-3D, LinearPlus, LinearPlusThermal, Thermal), the
file written by CDWRITE (Jobname.cdb) must be edited to remove
commands which are not available in the respective component
product before reading the file (CDREAD).
8. For problems with large numbers of constraint equations, the
PowerSolver (EQSLV,PCG) may converge slowly, resulting in
little or no performance gain relative to the frontal solver.
This will also result in poor performance when PCG is used with
p-element shells (SHELL150) because SHELL150 automatically
generates large numbers of constraint equations. In some
instances, an abort may occur. For large numbers of constraint
equations or models dominated by SHELL150 elements, use the
frontal solver.
9. When using PowerGraphics in POST1 for derived quantities on
solid elements, the maximum value on the plot and the maximum
value in the printout may not agree. Averaging does not occur
for plotting across any geometric discontinuities (e.g., 90
degree angle faces), but does occur for the printout.
10. When using 20-noded elements (VISCO89, SOLID90, SOLID95, and
SOLID 122) as tetrahedra, incorrect nodal output and graphics
information are reported when the PowerGraphics capability is
being used.
11. On systems running SunOS 4.1.3 and SunOS 4.1.4, IXI Motif
libraries are used. Dialog windows that must dynamically
resize themselves may not always attain the correct size.
Under such circumstances the user may need to manually resize
the dialog window to view all of its contents.
Page 3 of 4
12. Models with more than 5 internal cavities may fail to mesh when
using the tetrahedron mesher. If the tetrahedron mesher fails
while meshing a volume with internal cavities, the model should
be divided so as to 'remove' the internal voids.
13. When meshing VISCO89, SOLID90, SOLID95, or SOLID122 elements
using the mapped meshing capability, and dropping mid-side
nodes (ESHAPE,,2), only the mid-side nodes along the area
boundary lines are drooped. The interior mid-side nodes in
that area are not dropped. The workaround is to mesh using a
lower order element such as SOLID45, then change to the desired
element type.
14. An ADRAG operation may attempt to create an area by dragging an
entity in a direction opposite to what is expected depending
upon the length and orientation of the drag line. For a single
line defining the drag path, the selected entities are dragged
in a direction starting from the keypoint closest to the first
keypoint of the entity being dragged, instead of from the first
drag line keypoint to the second keypoint of the entity being
dragged. Extending the drag path or modifying the path
orientation will result in expected behavior.
Page 4 of 4
*** END OF DOCUMENT ***
Page Last Reviewed/Updated Wednesday, March 24, 2021