Format Component Library Sample Clauses

Format Component Library. The components or sub-systems must be modelled within the user define component of the GES simulation tool. The models in the library components are described in ASCII files with the following format shown in Table 5. Notation Description  < > Indicates that something must be completed  // text behind is comment  //bold text literally take over Format Explanation //version <lib_name> Version name or number of the component /* Help text */ First comment of the component that can be replayed by pressing on the F1 key of Help button /*Author and revisions */ Under author and revisions specified who the model of the component made and when. It also indicates who and when the model is adjusted, if necessary, provided with an explanation Example: /*Author and revisions X. xxx xxxx 11-10-2013 X. Xxxxxx 20-11-2013 changed emission */ SWBS=<#>; SWBS number of component, see 7.1 for selection type_fuel=1; Indicates that the component generates emissions //Explanation Information of background of the model init_function; //------------------------------ Init function block. The block begins where a previous block ends. This block is calculated once, before all the other calculations and is a part of the model description. More init blocks on several places can be used in the code and are cat automatically pre_function; //------------------------------- Pre function block. The block begins where a previous block ends. This block is calculated every time step, after the init_function blocks and is a part of the model description. More pre blocks on several places can be used in the code and are cat automatically. <e_gate(#)=>or<f_gate(#)=> //------------------------------ Gate description. The block begins where a previous block ends. A hashtag is the gate number of the component with the block description of the flow or effort of the component. See for the definition of effort of flow For every gate one gate block must be defined. post_function; //------------------------------- Post function block. The block begins where a previous block ends. This block is calculated every time step, after the gate blocks and is a part of the model description. More post blocks on several places can be used in the code and are cat automatically. <Include ‘attributes_inomanship.equ’;> Optional can code included to the component to export the attributes variables of the component. Remark. This include file must be worked out. Example is given. Table 5: Typical format and notation w...
AutoNDA by SimpleDocs

Related to Format Component Library

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Hepatitis B Vaccine Where the Hospital identifies high risk areas where employees are exposed to Hepatitis B, the Hospital will provide, at no cost to the employees, a Hepatitis B vaccine.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Preceptor Differential The Hospital shall pay a differential of $1.50 per hour to a nurse who is designated by nursing management to serve as a preceptor to provide on-the-job training to newly hired nurses. One differential will be paid per shift per orientee to the primary preceptor for all hours served as the primary preceptor for that shift. Preceptor will only be paid while the newly hired nurse is in a one-to-one status. Preceptor is a voluntary assignment and the nurse has the option to refuse the preceptor assignment.

  • Operator Materials Operator retains all right, title and interest in and to any and all of Operator’s software, materials, tools, forms, documentation, training and implementation materials and intellectual property (“Operator Materials”). Operator grants to the LEA a personal, nonexclusive license to use the Operator Materials for its own non-commercial, incidental use as set forth in the Service Agreement. Operator represents that it has all intellectual property rights necessary to enter into and perform its obligations in this DPA and the Service Agreement, warrants to the District that the District will have use of any intellectual property contemplated by the Service Agreement free and clear of claims of any nature by any third Party including, without limitation, copyright or patent infringement claims, and agrees to indemnify the District for any related claims.

  • Creative Commons Attribution-Non-Commercial-NoDerivs License The Creative Commons Attribution Non-Commercial-NoDerivs License (CC-BY-NC-ND) permits use, distribution and reproduction in any medium, provided the original work is properly cited, is not used for commercial purposes and no modifications or adaptations are made. (see below) Use by commercial "for-profit" organizations Use of Wiley Open Access articles for commercial, promotional, or marketing purposes requires further explicit permission from Wiley and will be subject to a fee. Further details can be found on Wiley Online Library xxxx://xxxxxxx.xxxxx.xxx/WileyCDA/Section/id-410895.html Other Terms and Conditions:

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

Time is Money Join Law Insider Premium to draft better contracts faster.