Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Model Repository

In this section, detailed specifications for the different components and layers of CAPE-ModE will be presented. The main components of CAPE-ModE can be summarized as Model Repository in UME, Model Management System (MMS), Modeling User Interface (MUI) using Model Manipulation Eanguage (MME), Model Query Eanguage (MQE), Model Translator (MT), and Application Programming Interface routines (APIs). [Pg.83]

The proposed model repository is composed of model base and metamodel base (Modelbase - MB / Metamodelbase - MMB). Example of the metamodel element from the plant design could be a class that represents the behavior of fluids (Gabbar [a], 2000), while pump class [Pg.83]


Useful Resources and Webpages to Assemble Information on Kinetic Models, Including Pathway Databases and Model Repositories... [Pg.145]

D. Nickerson, C. Stevens, M. Halstead, P. Hunter, and P. Nielsen, Toward a curated CellML model repository. Conf. Proc. IEEE Eng. Med. Biol. Soc. 1, 4237 4240 (2006). [Pg.243]

Based on VeDa, implementation models for the model repository ROME [463] and the modeling environment ModKit [52, 54], both described in Sect. 5.3, have been developed. In this context, VeDa was refined and extended. While most of these changes were implementation-specific and therefore did not become part of the conceptual model, some were incorporated in VeDa, like for example detailed taxonomies of physico-chemical phenomena and physical properties. [Pg.96]

Model maintenance and archival along the lifecycle of process design must be supported. The model repository ROME [24] provides functionality for model management and archival. ROME accesses proprietary modeling tools in order to extract information about the models being maintained. ROME stores only metadata about the models being archived and can therefore easily reference models in a variety of representations, open-form or closed-form as well as declarative or procedural models. [Pg.480]

Instead, the metadata abstraction stored in the model repository is traversed... [Pg.484]

In order to realize the Polyamide-6 scenario problem presented in Subsect. 5.3.2, a process description is defined using ModKit+. The elementary models for the reaction section, the separator, and the extruder, already imported into ROME, are added as submodels of the overall process. Further, a mixer is defined in order to combine feed and recycle streams corresponding mass balances are added to the elementary mixer model. After this modeling activity the model repository ROME contains all necessary models for the overall Polyamide-6 process. The model behavior is partly described by equations (for the mixer) and partly described by model implementations in the form of input files for the modeling tools Aspen Plus, gPROMS, and MOREX. [Pg.488]

These setup files can also be exported from an existing model specification in ModKit+. In this case ModKit + acts as a mediator between the user, the model repository ROME, and the simulation framework CHEOPS. ModKit+ then provides specifications of the problem, the simulation setup, and correct references to the models which must be imported as files (cf. Subsect. 5.3.3). [Pg.490]

The integrated simulation of the Polyamide-6 process involves models originating from the modeling tools Aspen Plus, gPROMS, and MOREX as presented in Subsect. 5.3.2. The first step is to import these existing models into the model repository ROME. This import should be done by the various modelers as soon as their models have reached a useful and stable state. [Pg.491]

The input files for all models are imported by a tool that is invoked via the command line of the Windows operating system shell. Based on the file extension of the model input file, this tool decides which wrapper to run. The wrapper will then inspect the given file and determine the metadata to be transferred to the model repository. Most notably, this concerns the connection points of the model itself and the variables describing these connection points. This information is at least necessary in order to permit connection to other models in the modeling tool ModKit- -. [Pg.491]

CHEOPS obtains this setup file in XML format from ModKit-l-. Tool wrappers are started according to this XML file. The input files required for the modeling tools Aspen Plus and gPROMS are obtained from the model repository ROME. CHEOPS applies a sequential-modular simulation strategy implemented as a solver component because all tool wrappers are able to provide closed-form model representations. The iterative solution process invokes the model evaluation functionality of each model representation, which refers to the underljdng tool wrapper to invoke the native computation in the modeling tool the model originated from. Finally, the results of all stream variables are written to a Microsoft Excel table when the simulation has terminated. [Pg.491]

M. C. Peitsch. Large scale protein modelling and model repository. Ismb. 1997, 5, 234-236. [Pg.242]

SWISS-MODEL Repository http //swissmodel.expasy.org/repository Annotated 3D protein structure models... [Pg.596]

Each type of analysis requires dissimilar models and methods. Our role is to enhance the link between each activity and its integration in a SDE. The goal of each step is to generate new knowledge or to automatically create new models for various analyses. This knowledge is joined to the model repository realising the centralisation of information in an MBSE method. The aim of the whole process is to trace the impacts of failures on the system performances and reliability requirements. [Pg.128]

The methodology is also required to provide guidelines for addressing organizational issues, and to support the development and maintenance of a modeling repository, which accumulates information about decisirMi-making processes. [Pg.91]

In this work, Comos FT (innotec, 2002), a tool holding design data, has been integrated with the model repository Rome (von Wedel, Marquardt, 2002) which is capable of storing and organizing the models which are created and used during process design activities. [Pg.31]

Rome is implemented using an object-oriented database (Versant, 2000) which can be accessed via CORBA middleware (Object Management Group, 2000) to ensure that the model repository is easily integrated with in-house or commercial software in a chemical engineering company s intranet, for example. Functionality such as importing. [Pg.31]

Based on the conceptual data model CLiP, the integration of the design data management tool Comos PT and the model repository ROME has been presented. The... [Pg.33]

In this work we propose a framework of the process model knowledge repository (PMKR) to store and exchange three kinds of process model information neutral process model, neutral process data and related process rules. When the operation process change, the different process models are modified to adapt to the new environment aided by PMKR. The process model repository is illustrated in figurel. [Pg.601]


See other pages where Model Repository is mentioned: [Pg.7]    [Pg.124]    [Pg.146]    [Pg.215]    [Pg.242]    [Pg.246]    [Pg.481]    [Pg.481]    [Pg.483]    [Pg.486]    [Pg.488]    [Pg.645]    [Pg.610]    [Pg.654]    [Pg.129]    [Pg.129]    [Pg.62]    [Pg.63]    [Pg.64]    [Pg.97]    [Pg.104]    [Pg.31]    [Pg.33]    [Pg.33]    [Pg.603]    [Pg.1]    [Pg.3]    [Pg.3]    [Pg.11]    [Pg.15]    [Pg.77]   


SEARCH



Repository

© 2024 chempedia.info