Model Development and Documentation Sample Clauses

Model Development and Documentation. A major aim of the community is to systematically further develop the regional climate model COSMO-CLM through continuously improving individual model components and by extending additional process modules. In this section, general rules are summarized, which have to be fulfilled by code developers. An additional document “COSMO Standards for Source Code Development” (Xxxxxxxxx, 2011) explains the rules in more detail.1
Sample 1
AutoNDA by SimpleDocs
Model Development and Documentation. A major aim of the CLM-Community is to develop the CLM-Community models sys- tematically by continuously improving individual model components and by extending the CLM-Community models with additional process modules. All members are allowed to change the code of the CLM-Community models for test purposes, for required adaptations and extensions as well as for the general im- provements of the model quality. But the procedure of model development in the community has to follow certain rules to prevent double or redundant work. These rules guide the member from the first idea to a new version of a CLM-Community model. They are explicitly described in the currently valid version of the COSMO Standards for Source Code Development7.‌
Sample 1
Model Development and Documentation. A major aim of the CLM-Community is to develop the CLM-Community models systematically by continuously improving individual model components and by extending the CLM-Community models with additional process modules. All members are allowed to change the code of the CLM-Community models for test purposes, for required adaptations and extensions as well as for the general improvements of the model quality. However, the procedure of model development in the community has to follow certain rules to prevent double or redundant work. These rules guide the member from the first idea to a new version of a CLM-Community model. They are explicitly described in the currently valid version of the “COSMO Standards for Source Code Development5” for COSMO and in the “Development partnership agreement between DWD and the CLM-Community with respect to the ICON software”1 (Appendix C) for ICON.
Sample 1

Related to Model Development and Documentation

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its Reliability Planning Process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Short-Term Reliability Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the STAR or Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Short-Term Reliability Process Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Program Development NWESD agrees that priority in the development of new applications services by XXXXX shall be in accordance with the expressed direction of the XXXXX Board of Directors operating under their bylaws.

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement. a. Develop a Work Breakdown Structure (WBS) for each project. b. Evaluate Scope Statement to develop a preliminary cost estimate and determinate whether project be vendor bid or be executed under a Job Order Contract (JOC).

  • Staff Development As part of their induction, new staff will be made aware of this policy and will be asked to ensure compliance with its procedures at all times.

  • Project Implementation The Borrower shall:

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!