| ▼NDB | |
| ▼NApi | |
| ►NCollections | |
| CAdjacencies | |
| CAssemblies | |
| CAssemblyInstances | |
| CBookmarks | |
| CBuildingBlocks | |
| CBuildings | |
| CCategories | |
| CCfdAceRegions | |
| CCfdLogEntries | |
| CCfdMonitorCellEntries | |
| CCfdMonitorCellNames | |
| CComponentBlocks | |
| CComponentBlockSurfaces | |
| CDataObjects | |
| CDxfLayers | |
| CErrors | |
| CFields | |
| CGbXmlConstructions | |
| CGbXmlIntersectingSpaces | |
| CGbXmlLayers | |
| CGbXmlMaterials | |
| CGbXmlSolarHeatGainCoefficients | |
| CGbXmlWindowTypes | |
| CHardAttributes | |
| CHoles | |
| CHvacComponents | |
| CHvacHeatingCoolingUnits | |
| CHvacLoops | |
| CHvacOperationRanges | |
| CHvacOperationSchemes | |
| CHvacSubComponents | |
| CHvacZoneGroups | |
| CHvacZones | |
| COpenGlExtensions | |
| COpenings | |
| CPlanes | |
| CPolygons | |
| CRecords | |
| CSimpleHvacComponents | |
| CSolarCollectors | |
| CSurfaces | |
| CVertices | |
| CWarnings | |
| CZones | |
| ►NContracts | |
| CIEnvironment | |
| CIVersionInfo | |
| ►NExceptions | |
| CDesignBuilderException | |
| CEnvironmentException | |
| CAdjacency | Class to handle zone surface adjacencies. A zone surface is composed of one or a number of adjacencies where each adjacency is an area of the surface which is either adjacent to another zone or the exterior of the building |
| CApplicationComponents | Class to handle DB components. Components include various tables of data including constructions, glazing data, profiles, etc |
| CApplicationTemplates | Class to handle DB templates. Templates include various tables of template data including activity templates, glazing templates, etc |
| CAssembly | Class to handle model assemblies. An assembly is a collection of component blocks that form a re-usable model component. An assembly can be used to model building occupants, furnishings, staircases, etc. Once an assembly has been defined it can then be placed in the form of 'instances' within the model |
| CAssemblyInstance | Class to handle model assembly 'instances'. An assembly is a collection of component blocks that form a re-usable model component. An assembly can be used to model building occupants, furnishings, staircases, etc. Once an assembly has been defined it can then be placed in the form of 'instances' within the model |
| CAssemblyLibrary | Class to handle model assembly libraries. An assembly library is used to house a number of pre-defined assemblies. An assembly is a collection of component blocks that form a re-usable model component. An assembly can be used to model building occupants, furnishings, staircases, etc. Once an assembly has been defined it can then be placed in the form of 'instances' within the model. Each DB model has an associated assembly library. Assemblies may be exported and imported using library functions |
| CBoundingBox2d | Class to handle a 2D bounding box. A 2D bounding box is essentially an object that can be used to define the range of a 2D plane within a DB model |
| CBoundingBox3d | Class to handle a 3D bounding box. A 3D bounding box is essentially an object that can be used to define the range of a 3D region within a DB model |
| CBuilding | Class to handle a DB model building object. A DB model building object is housed within the model Site object as one of a list of buildings. The building object is primarily composed of a set of building blocks (BuildingBlock objects) but also houses various other model components including component blocks, assembly instances, etc |
| CBuildingBlock | Class to handle a DB model building block object. The building block object is the main geometric component of a DB model and together with other building blocks forms a model building object. A building block may be partitioned into a number of zones and may contain other model components including voids, component blocks, assembly instances, etc |
| CCfdGridStatistics | The CFD grid statistics class applies to standard CFD only and not CFD+ |
| CCfdResiduals | Class to handle CFD simulation variable residuals. After each iteration of a CFD simulation, residuals are extracted from the dependent variable equation sets and these residual values may be used as an indicator of the degree to which the calculation has converged to a solution |
| CCfdStatus | Class to handle the status of a CFD simulation |
| CCommand | Instantiates list of Command objects using the associated Sketch command strings |
| CCommandObject | Class to handle a command object. A command object provides DB with the status of a Sketch command |
| CComponentBlock | Class to handle model component blocks. Component blocks may be used to model various components such as occupants, furnishings, shading devices, etc. Component blocks are also used to compose model assemblies |
| CComponentBlockSurface | Class to handle component block surfaces |
| CDataObject | The DataObject class is used to access the SketchDDataObject which is the class used to house a Sketch model attribute. A model attribute is an object with an assigned name and value that can be associated with any of the Sketch model objects (buildings, building blocks, components, etc.). Attributes are used to associate various data items with model objects (e.g. setpoint temperatures with zones). An inheritance mechanism is built into DB which enables the values of attributes to be inherited from higher levels of decomposition (site->building->building block...) or hard-set at specific levels |
| CDxfFile | The DxfFile class provides access to the Sketch DXF file object. A DXF file can be imported into Sketch in the form of line segments allowing model objects to be traced |
| CDxfLayer | The DxfLayer object enables access to the Sketch DXF file object layers allowing layers to be switched off prior to import. The Sketch DXF file object layers correspond to conventional DXF file layers |
| ►CEnvironment | Class to handle the Sketch operating environment. The class incorporates methods to set and retrieve the active Sketch command to enable control over the various Sketch operations including drawing model elements, copying, moving, rotating elements, view control, etc. The class also incorporates model navigation methods (changing levels of model decomposition) as well as methods to return API and software versions as well as the various folders used |
| CCfdOps | Class to handle the CFD application operating environment. The class incorporates methods to control CFD processes such as calculations (standard CFD and CFD+), meshing (CFD+) and event handling |
| CDocumentFileOps | Class to handle project file processes |
| CDrawingBitmapOps | Class to handle drawing bitmap file processes. Drawing bitmaps can be loaded into Sketch as BMP files to enable building object outlines to be traced |
| CDxfFileOps | Class to handle DXF drawing file processes. DXF files can be loaded into Sketch to enable building object outlines to be traced. The DXF objects are imported as line strings allowing the various keypoint snaps to me made to the line segments |
| CEvents | Class to handle Sketch events |
| CFactory | Class to handle various Sketch object creation processes |
| CGbXmlFileOps | Class to handle gbXML model file operations. DB can import and export gbXML model files. Refer to GbXmlFile class for import method |
| CHvacOps | Class to handle detailed HVAC operations |
| CModelOps | Class to handle various model operations |
| CRendererOps | Class to handle rendering operations |
| CError | Class to handle Sketch errors |
| CGbXmlConstruction | Class to handle Sketch gbXML constructions |
| CGbXmlFile | Class to handle Sketch gbXML file data and processes |
| CGbXmlFileStats | Class to handle imported gbXML file information (refer to GbXmlFile FileStatistics method) |
| CGbXmlLayer | Class to handle Sketch gbXML layers |
| CGbXmlMaterial | Class to handle Sketch gbXML materials |
| CGbXmlWindowType | Class to handle Sketch gbXML window types |
| CHvacComponent | Class to handle detailed HVAC component. The detailed HVAC component class is used to model the various components available in EnergyPlus.
|
| CHvacIndices | Class to handle setting and retrieving the various HVAC object current indices |
| CHvacLoop | Class to handle detailed HVAC loops. Loops are a basic element of EnergyPlus HVAC systems. Components are linked together to form various loops within the simulation. Thus, the output node from one component also serves as the inlet node to the next component and so on. There are four basic loop types: air loops, plant lops, condenser loops and VRF loops (refer to the HvacLoopType class) |
| CHvacNetwork | Class to handle detailed HVAC network object. The detailed HVAC network object is used to model an EnergyPlus HVAC network and is configured to closely match the structure of an EnergyPlus network in the form of loops, sub-loops and associated components |
| CHvacOperationRange | Class to handle HVAC loop operating scheme ranges. Plant and condenser loop operating schemes are a mechanism for controlling the operation of the loop and for specifying which items of equipment are available under what conditions. More than one operation scheme may be defined for a loop to enable different items of equipment to be switched on/off under different operating conditions. Each operation scheme has the type of operation scheme, its identifying name, and the schedule that defines its availability. Each scheme also contains a number of ranges which allows only specific items from the scheme equipment list to operate within specific load ranges |
| CHvacOperationScheme | Class to handle HVAC loop operating scheme ranges. Plant and condenser loop operating schemes are a mechanism for controlling the operation of the loop and for specifying which items of equipment are available under what conditions. More than one operation scheme may be defined for a loop to enable different items of equipment to be switched on/off under different operating conditions. Each operation scheme has the type of operation scheme, its identifying name, and the schedule that defines its availability. Each scheme also contains a number of ranges which allows only specific items from the scheme equipment list to operate within specific load ranges |
| CHvacSubLoop | Class to handle detailed HVAC sub-loops. Loops are a basic element of EnergyPlus HVAC systems. Components are linked together to form various loops within the simulation. Thus, the output node from one component also serves as the inlet node to the next component and so on. There are four basic loop types: air loops, plant lops, condenser loops and VRF loops (refer to the HvacLoopType class). Each HVAC loop comprises a demand side sub-loop (typically containing zone HVAC equipment such as radiators, air distrubution units, etc.) and a supply sub-loop that incorporates the equipment required to supply the deamnd side (e.g. boilers, chillers, etc.) |
| CHvacZone | Class to handle HVAC zones. A zone group is a DB construct that allows zones that contain similar configurations of HVAC components to be grouped together. While the number and types of items of equipment has to be the same for each constituent zone, the equipment can have different operating parameters (e.g. heating output, etc.). The HVAC zone class allows attributes for individual zones within the group to be edited and also allows access to items of zone equipment |
| CHvacZoneGroup | Class to handle HVAC zone groups. A zone group is a DB construct that allows zones that contain similar configurations of HVAC components to be grouped together. While the number and types of items of equipment has to be the same for each constituent zone, the equipment can have different operating parameters (e.g. heating output, etc.) |
| CModelIndices | Class to handle the various current model object indices (indices of objects throughout the model hierarchy above and including the currently selected object) |
| COpenGlInfo | Class to handle information relating to the installed version of OpenGL |
| COpening | Class to handle surface openings (windows, doors, vents, holes and CFD surface boundary conditions) |
| CPlane | Class to handle plane objects |
| CPoint2d | Class for 2D points (i.e. points with an x, y coordinate) |
| CPoint3d | Class to handle 3D points (i.e. points with x, y and z coordinates) |
| CPolygon | Class to handle polygon objects |
| CRecord | Class to handle DB table records |
| CSimpleHvacComponent | Class to handle simple HVAC components. Simple HVAC components as distinct from detailed HVAC components are not included within a network but are basic components to which attributes can be assigned in order to model HVAC components such as boilers, chillers and AHUs |
| CSite | Class to handle the site object. The site is the highest level object in the Sketch model object hierarchy. The model hierarchy runs from site down to zone surface openings which lie at the bottom of the hierarchy. Sites contain building objects. Building objects can contain component blocks, assembly instances and building blocks. Building blocks can contain component blocks, assembly instances and zones. Zones are comprised of surfaces and surfaces incorporate openings. By default, attribute data can be inherited from the site level down to zone surface opening level but may be overridden at any level in the hierarchy. This class incorporates methods to access objects within the hierarchy and to manipulate attribute data and data stored in tables |
| CSurface | Class to handle zone surfaces |
| CTable | Class to handle data in the form of tables. Tables comprise a specified number of fields (columns) and any number of records (rows). Tables are used by DB for both results and intermediate storage as well as providing a mechanism for DB data table files (.DAT files) which are used to house various databases such as materials and constructions. Tables used to house the .DAT files require the data files to use a specific format whereby the field of each record is delimited using # character, the first record contains field categories and the second record contains the field names. In contrast, tables used for results and intermediate storage don't have the same requirement for the first two records and data is accessed exclusively by index |
| CVersionInfo | Class for API version information |
| CWarning | Class to handle Sketch warnings. If a warning condition is encountered by Sketch, it will issue a warning event. Once a warning event is received by DB, details of the warning(s) can be obtained using the Warning class |
| CZone | Class to handle building zones |
| CZoneBridgingLengths | Class used to handle zone thermal bridging lengths. Thermal bridging lengths for all building zones may be calculated using the Building object CreateThermalBridgingSurfaceEdgeList method. After calling this method, the bridging lengths may be retrieved using the Zone object ThermalBridgingLengths method which returns the bridging lengths in the form of a ZoneBridgingLengths object |
1.9.7