ESP-r: Databases
Current capabilities
ESP-r has a core set of constructions
and materials databases which service the building domain and
additional databases which service the other techical domains.
ESP-r databases are as follows:
- materials - thermophysical properties
- constructions - lists of materials making up a construction
- optics - optical properties for constructions
- event profiles - sets of values (typically %) representing a profile over one day
- pressure coefficients - sets of wind pressure coefficient, each at 16 angles
- plant components - descriptions of detailed system components
- electrical components - descriptions of electrical components
- mould - descriptions of micotoxin growth patterns
- icons - icons to be used with network descriptions
The aim of these databases is to hold commonly accessed entities. ESP-r
is distributed with a limited set of databases which are typically
augmented by users. So-called corporate databases are placed where
users have read permission only. Databases related to specific
projects tend to be kept within the model folders.
Work in progress
Many of ESP-r's databases are in a state of flux:
- Plant components are ripe for rationalisation: entries could be held in a similar format
which would also support graphical information for use within
the net tool. Currently we are exploring representations for:
HVAC/flow, electrical, renewables, advanced materials.
- Changes should support large numbers
of individual component instances to be cached and classified and archived,
improving knowledge retention and reducing user input burden.
Primary routines
- esrucom/edatabase.F - I/O facilities for constructions materials and optics
- esruprj/eddb.F - manage database access
- esruprj/edcondb.F - edit materials and constructions
Primary variables
- COMMON/?? - work in progress
Issues arising
Each database tends to follow a different pattern (code and interface)
which increases code overhead and makes the facilities more difficult
to learn and manage.
- Some databases do not support sub-categories
- Databases tend not to provide sufficient space for documentation
- Databases do not support definitions of uncertainty
- The issues are addressed via a parallel database structure which
is under development
Last edited April 2005