05.06.2013 Views

PNNL-13501 - Pacific Northwest National Laboratory

PNNL-13501 - Pacific Northwest National Laboratory

PNNL-13501 - Pacific Northwest National Laboratory

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The three problems were built on one another and<br />

demonstrate the ability to simulate a sequential metal<br />

forming/joining process using simple finite element<br />

models that include the features of larger industrial<br />

manufacturing problems. The three test problems used to<br />

demonstrate research outcomes are described below.<br />

Results and Accomplishments<br />

In keeping with the four focus areas, the results and<br />

accomplishments of this effort are presented below,<br />

followed by a description of the results obtained from the<br />

three test problems that demonstrate the capabilities of the<br />

integrated suite of tools.<br />

Engineering Data Representation<br />

We extended the use of Exodus as a common data format<br />

and provided the capability to store stress/strain data in<br />

addition to deformed geometry and thickness.<br />

We also developed data transformation tools to convert<br />

between the Exodus-based common data format and the<br />

following commercial finite element codes:<br />

• MARC Analysis (output format)<br />

• MARC Analysis (input format)<br />

• PAM-CRASH (input format)<br />

Last, we developed and extended of a number of MARC<br />

“user routines” to ensure that the appropriate data was<br />

accessible to enable the appropriate transformations.<br />

Remeshing/Remapping Capability<br />

We explored the use of commercial remeshing tools<br />

(e.g., Hypermesh) to provide required remeshing<br />

capability with the idea of adding a remapping capability<br />

through some other means. This effort was abandoned<br />

when a NWGrid-based remeshing and remapping<br />

capability appeared feasible.<br />

We also developed data transformation tools to support<br />

translation between common data format and formats<br />

used by NWGrid.<br />

Last, we integrated NWGrid-based remesh/remap<br />

capability into an IMS tool suite to provide the capability<br />

required for the demonstration of test problems 2 and 3<br />

(see below).<br />

180 FY 2000 <strong>Laboratory</strong> Directed Research and Development Annual Report<br />

Data Pedigree Representation<br />

We defined data representations (object representations)<br />

for information that must be captured as part of a data<br />

pedigree during multistep finite element simulation<br />

efforts.<br />

We also explored similar data pedigree efforts on other<br />

projects, including ARM, the regional climate modeling,<br />

Ecce, and the DOE 2000 projects and collaborated with<br />

CPSE projects on the use of WebDAV technologies for<br />

storage of result sets and data pedigree information.<br />

We designed and completed a “model transformation<br />

tool” to invoke data transformation tools and gather<br />

pedigree information from users.<br />

High Performance Computing<br />

We demonstrated that the CDF-to-PAM-CRASH data<br />

transformation tool works for simulations run on the<br />

Zodiac. Currently, we are building on the accomplishments<br />

in these four areas, three test problems were<br />

undertaken to demonstrate the integrated modeling and<br />

simulation capabilities provided.<br />

Test Problem 1—Analysis Restart<br />

The first test problem simulated a two-step stretchforming<br />

of sheet metal between a spherical punch and a<br />

cylindrical die (see Figure 1). At the completion of this<br />

step, the common data format had the capability to store<br />

stress/ strain data, data transformation tools were<br />

completed to convert between the common data format<br />

and Marc input and output formats and, subroutines were<br />

written to transform the model data from the local shell<br />

element system to the global coordinate system for<br />

storage in the Exodus common data format.<br />

Since the element results are based on the shape and<br />

orientation of each element, the element coordinates and<br />

their shape functions were used to perform the data<br />

transformations for each individual element. Figure 2<br />

shows the detailed multiple data transformation steps<br />

associated with this process and the data translators<br />

that were developed to execute this example problem.<br />

This example problem performs a restart analysis<br />

without saving the standard MARC restart file. It<br />

provides, a demonstration of the capability to save<br />

results from MARC into the common data format and

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!