PNNL-13501 - Pacific Northwest National Laboratory

to 1) incorporate three-dimensional models, 2) mix
and match one- and three-dimensional models, and 3)
mix and match UNIX and PC models.
Results and Accomplishments
Expansion of the FRAMES Specifications
We successfully developed a new FRAMES file
specification that will allow us to incorporate two- and
three-dimensional models into the system. The file
specification standardizes the format for passing results
from one model to the next; in this case, from the vadose
zone model (STOMP) to the saturated zone model
(CFEST). The temporal and spatial integrity of the data
were two of the main issues that had to be resolved. We
worked with the CFEST and STOMP developers and
model users to determine what data needed to be passed
between the models and to determine the best format of
that data. The file specification we developed maintains
spatial integrity by use of polygons and fractions to
transfer data between disparate grid systems (Figure 1),
maintains mass balance and temporal integrity (time
stepping issues) by use of cumulative curves (Figure 2),
and is a generic format such that any media can be passed
between models using the same specification (water,
contaminants, energy, salinity). It was necessary to
develop a processor to address the temporal and spatial
integrity issues. The processor reads in the two disparate
grid systems, creates polygons based on the grid points if
necessary, determines the fractions for data transfer, and
develops the cumulative curves needed to meet the file
specification.
Figure 1. Description of polygon fractions used to address
spatial integrity issue
Network Data Exchange
We successfully developed a system that allows
FRAMES to access computer models on different
computers via the Internet. The system consists primarily
of a model client, a model server (both coded in Java),
and a TCP/IP network connection. The obvious
advantage to using Java is that our protocol is platform
independent (i.e., can be used on both PCs and UNIX
platforms). The system contains protocols for dealing
with long model run times and error handling. Also the
model client provides the user with the status of model
runs via a text window. Figure 3 provides the schematic
for our network data exchange protocol.
Figure 2. Description of cumulative curve development
based on polygons described in Figure 1
Figure 3. Schematic of FRAMES system developed to
access models on different platforms (PCs and UNIX) over
networked machines
Integration of STOMP and CFEST
Both STOMP and CFEST were integrated into the system
successfully. The complete functionality of all of the
STOMP and CFEST options was not an objective of this
project. Our objective for the project was to incorporate
the options with enough functionality to run a specific
base case. The integration of both models required us to
develop pre- and post-processors in C++.
Computational Science and Engineering 125