13
SOFTWARE VALIDATION PLAN AND REPORT FOR HYPERMESH VERSION 7.0 Prepared by Troy Maxwell Center for Nuclear Waste Regulatory Analyses Southwest Research Institute San Antonio, Texas Approved by: Asadul Chowdhury, Element Manager Date Mining, Geotechnical, and Facility Engineering

HyperMesh Version 7.0 (Software Validation Plan and Report.)

  • Upload
    others

  • View
    5

  • Download
    0

Embed Size (px)

Citation preview

Page 1: HyperMesh Version 7.0 (Software Validation Plan and Report.)

SOFTWARE VALIDATION PLAN AND REPORT FOR HYPERMESH VERSION 7.0

Prepared by

Troy Maxwell

Center for Nuclear Waste Regulatory Analyses Southwest Research Institute San Antonio, Texas

Approved by:

Asadul Chowdhury, Element Manager Date Mining, Geotechnical, and Facility Engineering

Page 2: HyperMesh Version 7.0 (Software Validation Plan and Report.)

1

Global Y

SCOPE OF THE VALIDATION

Hypermesh is used in regulatory review to generate input files for the ABAQUS finite element analysis program. These input files define the finite element discretization and corresponding material properties and boundary conditions. Hypermesh is also used to view the results of finite element analysis graphically. Therefore, Hypermesh was validated by inputting node locations, material properties, and element types into the Hypermesh Graphic User Interface (GUI) and verifying the inputs do not change when converted to the required format for ABAQUS. The results from the ABAQUS analyses are then transferred back into Hypermesh and viewed graphically. The validation results were considered acceptable if the data input into Hypermesh did not change when converted to ABAQUS ‘ h p ’ file, and the ABAQUS results do not change when viewed graphically in Hypermesh. The graphical results viewed in hypermesh were compared to the numerical results produced in the ABAQUS ‘.dat’ file. The input comparison will be identified as Case 1 and the graphical comparison will be identified as Case 2.

The Finite Element Model (FEM) used to conduct this validation exercise is a cross-section of a waste package taken from Software Validation Plan and Report for DTHERM Version 1.2 (Maxwell, 2005). The FEM cross-section was constructed with two-dimensional, four node continuum, axisymmetric, temperature dependant elements for the inner and outer barrier walls. The model was constrained axially at the waste package midpoint. The outer barrier lid was modeled as a two node rigid body element which employs the top center node of the outer barrier as a reference node. The model is shown in the Figure 1-1.

L Figure 1-1. The FEM is Used to Conduct This Validation Exercise

2 REFERENCES

Maxwell, T. “Software Validation Plan and Report For DHTERM Version 1.2.” San Antonio, Texas: CNWRA. 2005.

1

Page 3: HyperMesh Version 7.0 (Software Validation Plan and Report.)

3

3.1 e

e

3.2

ENVIRONMENT

Software

Hypermesh, Version 7.0 ABAQUS/Standard, Version 6.3, SunOS Version 5.9

Hardware

HyperMesh is not limited to a specific computer hardware or operating system and presents the same appearance on all platforms. Most of the HyperMesh source code is independent and can be compiled on various systems. This validation exercise was performed on a Windows 2000 PC. The following hardware platforms are currently supported:

e Pentium-based PC or compatible running Windows WIN NT 4.0, WIN ZOOO/XP. IBM running AIX 4.3.3, 5.1, or 5.2. HP-PARISC (HPUX) running 11 .O or 11.11. HP-ITANIUM (HPUX-IA32) running 11.23. Silicon Graphics family of workstations running IRlX 6.5.1 1 m and IRlX 6.5.13 m. SUN workstations running Solaris 2.8. LINUX running RH 7.3 or RH 8.0.

e

e . 4 PREREQUISITES

No prerequisites are required to perform testing activities.

5 ASSUMPTIONS AND CONSTRAINTS

No assumptions or constraints are required to implement this software validation test plan.

6 TEST CASES

6.1 Test Case 1

6.1.1 Test Case 1 Input

The objective of Test Case 1 is to verify that the data input into Hypermesh does not change when converted to ABAQUS. Tables 6-1 through 6-3 are the nodal input coordinates, FEM card data, and material properties respectively. The coordinates in Table 6-1 are the bounding nodes of the Waste Package Inner and Outer Barrier.

2

Page 4: HyperMesh Version 7.0 (Software Validation Plan and Report.)

w V

Node Number X Coordinate Y Coordinate

I 1,000 I 0.764

1,004

2,000

2,010

0.00

0.784 0.00

0.712 0.00

0.762 0.00

1,044

2,050

2,040

I Corner Nodes of Outer Barrier I ~ ~ ~ ~ ~ ~

0.784 2.453

0.712 2.438

0.762 2.438

I 1,048

Collector Name

0.764

Card Image

2.453 I

INNER-BARRIER

OUTER-BARRIER

SOLIDSECTION

SOLIDSECTION

Alloy22 ABAQUS-MATERIAL

31 6SS 1 ABAQUS-MATERIAL

3

Page 5: HyperMesh Version 7.0 (Software Validation Plan and Report.)

L

Model Parameter Parameter Value

TY Pe Inner Barrier Thermal Conductivity (W/ m-K)

I Inner Barrier Thermal Expansion Coefficient (I/K)

Isotropic

25.44

17.5 x

Type Outer Barrier Thermal Conductivity (W/ m-K)

Outer Barrier Thermal Expansion Coefficient (IIK)

I Inner Barrier Modulus of Elasticity (Pa)

Isotropic

21.63

13.7 x

124.8 x I O 9

I Inner Barrier Poisson’s Ratio 0.27

I Element Type CAX4T

Outer Barrier Modulus of Elasticity (Pa) 155.8 x l o9 I Outer Barrier Poisson’s Ratio I 0.30 I

I CAX4T I Element Type I

6.1.2 Test Case 1 Procedure

Test Case 1 used the following procedure:

Input nodal coordinates from Table 6-1 into Hypermesh and generate a finite element mesh.

Input card image data from Table 6-2 into Hypermesh.

Input material properties from Table 6-3 into Hypermesh.

0 Transfer the Hypermesh model into ABAQUS.

Verify the data entered in Hypermesh is identical to data shown in the ABAQUS ‘.inp’ file.

6.1.3 Test Case 1 Results

Tables 6-4 and 6-5 illustrate the data input into Hypermesh did not change when converted to the ABAQUS ‘ h p ’ file. A condensed version of the Hypermesh input file and the ABAQUS ‘ h p ’ file is shown in the appendix. The test results are acceptable.

4

Page 6: HyperMesh Version 7.0 (Software Validation Plan and Report.)

Node Number

Table 64 . Nodal coordinate Input Comparison

Hypermesh ABAQUS

X-Coord. Y-Coord. X-Coord. Y-Coord.

1,000

1,004

2,000

2,010

0.764 0.00 0.764. 0.00

0.784 0.00 0.784 0.00

0.71 2 0.00 0.712 0.00

0.762 0.00 0.762 0.00

1,048

1,044

2,050

2,040

Inner Barrier Material Properties

0.764 2.453 0.764 2.453

0.784 2.453 0.784 2.453

0.71 2 2.438 0.712 2.438

0.762 2.438 0.762 2.438

Inner Barrier Thermal Conductivity (W/ m-K) I 25.44 I 25.44

Model Parameter Hypermes h

Inner Barrier Thermal Expansion Coefficient (1/K) I 17.5 x I 17.5 x

ABAQUS

Inner Barrier Modulus of Elasticity (Pa) I 124.8 x 10’ I 124.8 x109

~ ~ ~

Element Type

1 Inner Barrier Poisson’s Ratio I 0.27 1 0.27

CAX4T CAX4T

~~~~~~ ~~ ~ ~ ~

Outer Barrier Poisson’s Ratio

I Outer Barrier Thermal Conductivity (W/ rn*K) I 21.63 I 21.63

0.30 0.30

I Outer Barrier Thermal Expansion Coefficient (1/K) I 13.7 I 13.7

I Outer Barrier Modulus of Elasticity (Pa) I 155.8 (lo9) 1 155.8 (lo9)

I Element Type I CAX4T I CAX4T

5

Page 7: HyperMesh Version 7.0 (Software Validation Plan and Report.)

‘W

~ ~ __

Node

2,000

2,010 1,000 1,004

‘(3

_ _ ~ __ __ _ _ _ _ _ ~

Hoop Stress (Pa) Hypermesh Contour Acceptable Data

Plot Range

> 6.40 x I O 6

ABAQUS

1.18 x I O 6 < 1.31 x l o 6 Yes

3.78 x l o 6 > 3.33 x I O 6 Yes -6.76 x 105 < -3.29 x I O 6 Yes 5.27 x i o 5 < 6.40 x I O 6 Yes

>-3.29 x I O 6

6.2 Test Case 2

The Hypermesh graphical display is used to visually display the results of the ABAQUS analysis. Therefore the graphical display will be validated if the color distribution within the plot legend displays a correct range for the data extracted from the ABAQUS ‘.dat’ file.

6.2.1 Test Case 2 Input

Along with the input from Test Case 1, the input for Test Case 2 is extracted from FEM A Case 1 model taken from Software Validation Plan and Report for DTHERM Version 1.2.

6.2.2 Test Case 2 Procedure

Test Case 2 used the following procedure:

. Perform a run using FEM A Case 1 in ABAQUS, and transfer the results into Hypermesh.

Verify the results in Hypermesh agree with the corresponding data from the ABAQUS ‘.dat’ file.

6.2.3 Test Case 2 Results

The data used to generate the two contour plots used for Test Case 2 are the Hoop stress and the Displacement. As shown in Tables 6-6 and 6-7 and Figure 6-1 and 6-2, the results generated in the ABAQUS ‘.dat’ file are correctly displayed within the correct range when translated back into Hypermesh. The nodes identified in the figures are the bottom four bounding nodes of the FEM cross-section that were previously identified in Table 6-1. A condensed version of the ABAQUS ‘.dat’ file is shown in the appendix. The test results are acceptable.

6.3 Validation Test Results Conclusion

The results from this validation indicate the user input converted from Hypermesh into ABAQUS is validated. The Hypermesh graphical display of the results generated from ABAQUS is validated.

I Table 6-6. Contour Plot Data Range Comparison I

6

Page 8: HyperMesh Version 7.0 (Software Validation Plan and Report.)

Table 6-7. Contour Plot Data Range Comparison

Displacement (m) I

Node Hypermesh Contour Acceptable Data Plot Range ABAQUS

2,000

2.01 0

2.95 x 10-3 3.04 x Yes

3.16 x 10-3 > 3.04 x 10-3 Yes

> 2.93 x 10-3

'-1 M,I-l.mams+ax,

W S -

> 3.33~06 < 3.33e*06 < 2,66e*06 I <1.99e*06 a 1.31 0 4 6 < 6.40e45 +32Be*04

Mux - 4.00e+06 Min --3.29s*M

1,000

1,004

I-

2.36 x 10-3 2.48 x 10-3 Yes

2.42 x 1 0 - 3 2.48 x 10-3 Yes

-

2000

I

2010 1000

I I

1004

I Figure 6.1 Hypermesh Hoop Stress Contour Plot

Page 9: HyperMesh Version 7.0 (Software Validation Plan and Report.)

rtapl M A - 1 - I > 3 04603

< 2 a1603

< 3 04603 < 2.93603

< 2 70603 < 2 59603 ? c 2 48603

Max- 3 150-03 Man - 2 48043

2000 2010 1000 1004

I Figure 6.2 Hypermesh Displacement Contour Plot

7 Notes

The files associated with the Hypermesh validation are located on the attached CD. The files are identified as follows:

H ypermesh-Model. hm

Hypermesh-lnput.txt

Hype rmes h-G ra p h i c-Res u I ts . res

ABAQ U S-Results.dat

ABAQUS-I n put .in p

2-D Finite Element Model

Text file that contains the input parameters from the FEM.

The graphic results file that is converted from ABAQUS.

Data file that is generated in ABAQUS using the Hypermesh input parameters.

Input file that is converted from Hypermesh.

8

Page 10: HyperMesh Version 7.0 (Software Validation Plan and Report.)

APPENDIX

Page 11: HyperMesh Version 7.0 (Software Validation Plan and Report.)

'v

Condensed Hwermesh Input File

** ABAQUS Input Deck Generated by t , jperMesh Version : 7.0 ** Generated using HyperMesh-Abaqus Template Version : 7.0

** Template: ABAQUSETANDARD 2D

*NODE

**

**

**

1000, 0.764 , 0.0 1004, 0.784 , 0.0 1044, 0.784 , 2.453 1048, 0.764 , 2.453 2000, 0.712 , 0.0 2010, 0.762 , 0.0 2040, 0.762 , 2.438 2050, 0.712 , 2.438

*ELE M ENT,TY PE=CAX4T, ELSET= I N N ER-BARR1 ER

*SOLID SECTION, ELSET=INNER-BARRIER, MATERIAL=316SS

*SOLID SECTION, ELSET=OUTER-BARRIER, MATERIAL=Alloy22

*MATERIAL, NAME=316SS

*CONDUCTIVITY,TYPE=ISO 25.44 ,O.O

*ELASTIC, MODULI = LONG TERM, TYPE = ISOTROPIC 1.2480E+11,0.27 ,298.0

*EXPANSION, TYPE = IS0 1.7500E-05, 0.0

*MATERIAL, NAME=Alloy22

*CONDUCTIVITY ,TYPE=ISO 21.63 ,O.O

*ELASTIC, MODULI = LONG TERM, TYPE = ISOTROPIC 1.5580E+11,0.3 ,298.0

*EXPANSION, TYPE = IS0 1.3700E-05, 0.0

A-1

Page 12: HyperMesh Version 7.0 (Software Validation Plan and Report.)

Condensed ABAQUS '.inD' File

'NODE 1000, 0.764 1004, 0.784 1044, 0.784 1048, 0.764 2000, 0.712 2010, 0.762 2040, 0.762 2050, 0.712

, 0.0 , 0.0 , 2.453 , 2.453 , 0.0 , 0.0 , 2.438 , 2.438

*SOLID SECTION, ELSET=OUTER-BARRIER-ELSET, MATERIAL=Alloy-22

*SOLID SECTION, ELSET=INNER-BARRIER-ELSET, MATERIAL=SS-316

*MATERIAL, NAME=Alloy-22

*CONDUCTIVITY,TYPE=ISO 21.63,

*ELASTIC, TYPE = ISOTROPIC 1.5580E+11,0.3,

*EXPANSION, TYPE = IS0 13.7E-06, 298,

*MATERIAL, NAME=SS-316

*CONDUCTIVITY,TYPE=ISO 25.44,

'ELASTIC, TYPE = ISOTROPIC 1.2480E+11,0.27,

'EXPANSION, TYPE = IS0 17.5E-06, 298,

A-2

Page 13: HyperMesh Version 7.0 (Software Validation Plan and Report.)

Condensed ABAQUS ‘.dat’ File

E L E M E N T O U T P U T

THE FOLLOWING TABLE IS PRINTED AVERAGED AT THE NODES FOR ELEMENT TYPE CAX4T AND ELEMENT SET RAD-INNER-BARRIER-OUTPUT-R1

NODE FOOT- S11 s22 s33 512 MISES TEMP

2000 -1.67953+05 -2.05563+05 -2413. 1.36733+06 534.4

THE FOLLOWING TABLE IS PRINTED AVERAGED AT THE NODES FOR ELEMENT TYPE CAX4T AND ELEMENT SET RAD-INNER-BARRIER-OUTPUT-R2

NODE FOOT- S11 s22 s3 3 512 MISES TEMP

2010 -4122. 2.56173+06 -1.29193+04 3.34723+06 533.3

THE FOLLOWING TABLE IS PRINTED AVERAGED AT THE NODES FOR ELEMENT TYPE CAX4T AND ELEMENT SET RAD-INNER-BARRIER-OUTPUT-R3

NODE FOOT- S11 s22 s3 3 512 MISES TEMP

1000 4.63443+04 -6.71103+05 - 3.15633+04 7.21813+05 524.0

THE FOLLOWING TABLE IS PRINTED AVERAGED AT THE NODES FOR ELEMENT TYPE W 4 T AND ELEMENT SET RAD-INNER-BARRIER-OUTPUT-R4

NODE FOOT- S11 s22 s33 512 MISES TEMP

1004 -2668. 5.88853+05 8172. 5.63243+05 523.1

N O D E O U T P U T

THE FOLLOWING TABLE IS PRINTED FOR NODES BELONGING TO NODE SET INNER-BARRIER-NODE-OUTPUT

NODE FOOT- U1 u2 UR3

2000 0.

2010 0.

THE FOLLOWING TABLE IS PRINTED FOR NODES BELONGING TO NODE SET OUTER-BARRIER-NODE-OUTPUT

NODE FOOT- U1 u2 uR3

1000 0.

1004 0.

A-3