Protocol for the Arctic ice loss experiments Sample Clauses

Protocol for the Arctic ice loss experiments. The starting idea was to favour a simple forced (AMIP-type) protocol for the core sea-ice loss experiments (remembering that they have to be performed at both LR and HR). The suggested protocol was aiming at a simple framework where we prescribe the observed sea- ice decline for 1979-2015 with climatological SSTs and constant external forcing (for instance at values typical of the early 1980s) and compare that with a reference experiment. A consultation has been performed across all WP5 partners to discuss the protocol for sea- ice loss experiments. A lot of different protocols based on both forced and coupled frameworks have been documented in the literature. Key findings are the following: - In case where one is interested in the influence of the recent (since 1979) impact of Arctic sea-ice loss on the global and European climate based on AMIP-type ensembles of atmospheric simulations, a number of studies have demonstrated that the signal-to-noise ratio is likely to be low, requiring a very large number of atmospheric members to significantly detect the signal due to sea-ice loss. - In studies looking at isolating the effect of sea-ice at the end of the 21st century under the RCP8.5 scenario, the use of a coupled framework (as in Deser et al. 2016, Xxxxx et al. 2016, Xxxxxxxxx et Xxxxxxx 2016) has been shown to give different results than those based on the standard time-slice atmospheric protocol. Here is a short summary of the key recommendations emerging from the consultation:
Sample 1
AutoNDA by SimpleDocs

Related to Protocol for the Arctic ice loss experiments

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • 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.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work.

  • Test Samples The Contractor is responsible for providing Samples of sufficient size for test purposes and for coordinating such tests with the Work Progress Schedule to avoid delay.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Diagnostic Assessment 6.3.1 Boards shall provide a list of pre-approved assessment tools consistent with their Board improvement plan for student achievement and which is compliant with Ministry of Education PPM (PPM 155: Diagnostic Assessment in Support of Student Learning, date of issue January 7, 2013).

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