Data Management

Collaboration diagram for Data Management:

Modules
	Static variables for Data functions.
	Data Management function declarations

Detailed Description

Data Management.

Data within COSMOS is managed in a heirarchical structure. At the highest level, separate directories are provided for Nodal information (nodes), and for general software Resources (resources). These two directories can be together in a single COSMOS directory, or in separate locations. Their locations can be defined through the use of environment variables, or through default values. The order of assignment is as follows:

• If the environment variables COSMOSNODES or COSMOSRESOURCES exist, then the directories specified by these variables will be used for nodes or resources.
• If either COSMOSNODES and/or COSMOSRESOURCES is not set, but the environment variable COSMOS is, then nodes or resources will be located in ${COSMOS}/nodes or ${COSMOS}/resources.
• If no environment variable is found, default locations are used, specific to the OS
• Windows: c:/cosmos/nodes and c:/cosmos/resources
• Unix: /usr/local/cosmos/nodes and /usr/local/cosmos/resources
• MacOS: /Applications/cosmos/nodes and /Applications/cosmos/resources
• If these directories are not found, then the software will look up to four levels above the directory it is running in for directories called "nodes" or "cosmosnodes" and "resources" or "cosmosresources". Once this search is completed successfully, the nodes folder for the current Node will be stored internally as "cosmosnodes" and the resources folder as "cosmosresources".

Within "nodes", there is a directory specific to each Node. Each Node specific directory mirrors the Node:Agent arrangement laid down in the JSON Library. A series of initialization files are incldued, as well as a set of directories for Temporary data (temp), Incoming data (incoming), Outgoing data (outgoing), and Archival data (data).

The initialization files include:

• node.ini: Describes the Node type, number of pieces, number of Devices, and number of ports.
• pieces.ini: Describes each Piece, including the number of any related Device.
• devices_general.ini: Describes common elements of each Device.
• devices_specific.ini: Describes any unique of each Device.
• ports.ini: Describes Ports available to each device.
• target.ini: Provides a list of any targets associated with this Node.
• state.ini: Provides a complete state vector for this Node at some specific time.

Each of temp, incoming and outgoing contain sub-directories named after each active Agent. Each agent sub-directory in the "data" directory is further subdivided by first year, then day.

The software resources directory contains directories of files for use in different aspects of COSMOS. The directory "general" contains files of coefficients used for the various models used in COSMOS simulations. The directory "logo" contains any special images used by COSMOS software. The directory "mapping" contains all the DEM's and ancillary files used by the DEM Library. Finally. the directory "qt" contains files, such as UI forms, used by the various Qt based Tools withing COSMOS.

The functions in this library support path discovery and creation, the automatic generation of standard names, and the automatic creation of log files.