Using Dictionaries to Manage Data Within a Modeling Framework System

Glossary

Application Programming Interface (API)-software that coordinates and manages the input and output between components in a modeling system.

Boundary condition dictionaries-collections of information about data that is transferredbetween or used in common by various components of a system.

Conceptual model-the picture of the real-world problem being modeled.For environmental fate and transport activities, this is also called a conceptual site model.

Consuming model-a software code that simulates real-world activities and that uses (consumes) results of another model as input to function.

Database dictionary-a collection of information associated with the mapping of data between a database and the system.

Datasets-a collection of related data, for example, input for a model.

Dictionaries-files of information about the data being managed in a software system.

Dimensional size-number of dimensions (indices) associated with a parameter.

Domain-the boundaries of the problem being modeled.

Downstream model-a software code that that would run later in an analysis problem.For example, in an environmental fate and transport analysis, a human health impact model would run later than a source term model because the impact model relies on source term data to operate.

Iteration dictionary-a collection of information that defines the current iteration of the simulation.

Iterator dictionaries-a collection of information that defines statistical data associated with the stochastic data; that is, data that can be varied.

Key-attribute of a parameter that indicates whether it has been indicated by the user as being critical to the analysis.For example, a species of concern might be a key to an ecological analysis.

Model-a software code that simulates the activities of a real-world situation.For example, a watershed model might simulate the hydrological cycle within a particular river basin.

Model dictionary-a collection of information about data passed from a producing model to a consuming model.

Module-components that work together to allow a model or database to work within the system.These components may include pre- and post-processors, the model itself, and a user interface.

Module properties dictionary-a collection of information about data on the component and its supporting infrastructure.  Such data might include the point of contact for additional information, input and boundary condition dictionaries consumed and produced, and how the module fits into a modeling scheme.

Module-specific dictionaries-collections of information about data needed to operate a module within FRAMES.

Object-oriented modeling-analyzing problems based on a collection of real-world attributes.

Post-processor-software code that runs after a model executes to facilitate its ability to produce data for a system.

Pre-processor-software code that runs before a model executes to facilitate its ability to receive data from a system.

Producing model-a software code that simulates real-world activities and that generates (produces) results which will be used by another model.

Sampled values dictionary-a collection of information that defines the inputs being sampled as stochastic and available for sampling.

Scalar-number of values associated with a variable for a particular set of indices.

Seed dictionary-a collection of information that defines the starting seed number associated with the random number generator.

Simulation dictionary-a collection of information that allows the reproduction of a particular conceptual model.This information includes model names and identification, dataset names and locations, model and database status, linkages, model locking information, and simulation comments.

Start-up dictionary-a collection of information necessary to set up the FRAMES user interface.

Stochastic dictionary-a collection of information that defines the distribution and attributes associated with parameters that can be varied.

Summary values dictionary-a collection of information that defines the outputs summarized as part of the statistical results.

Upstream model-a software code that would run earlier in an analysis problem.For example, in an environmental fate and transport analysis, a source term model would run earlier than a human health impact model because the impact model requires source term information to operate.