Support for Running The GlueX Experiment Sample Clauses

Support for Running The GlueX Experiment. The CUA group will assure that the magnet and monitoring systems are maintained once these systems are installed. We will serve as experts on call for various parts of the photon beam facility as well as performing normal shift
AutoNDA by SimpleDocs
Support for Running The GlueX Experiment. During the running of the experiment the IHEP group will participate in commissioning the detector, provide manpower needed for data taking, provide available expertise to diagnose and repair problems with the subsystems that fall under the responsibility of the IHEP group and also provide manpower to evaluate data in real time.
Support for Running The GlueX Experiment. The UConn group assumes shared responsibility within the context of the GlueX Photon Beam Working Group for the installation and commission- ing of all aspects of the hall d photon beam. Particular responsibility is assumed for installation of the collimators and associated shielding and instrumentation in the collimator area, and for the tagger focal plane instru- mentation, with coordination and assistance to be provided by Jefferson Lab staff.
Support for Running The GlueX Experiment. The UofR group will provide manpower support as a member of GlueX, in general, and as the group responsible for the operation of the BCAL and its components in particular, as well as software support for the elements the group has assumed responsibility for. The overall support will reflect efforts by faculty members, research scientists, post- doctoral fellows and graduate students.

Related to Support for Running The GlueX Experiment

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Loop Provisioning Involving IDLC 2.16.1 Where TWTC has requested an Unbundled Loop and AT&T uses IDLC systems to provide the local service to the customer and AT&T has a suitable alternate facility available, AT&T will make such alternative facilities available to TWTC. If a suitable alternative facility is not available, then to the extent it is technically feasible, AT&T will implement one of the following alternative arrangements for TWTC (e.g., hairpinning):

  • CONTRACTOR TO PACKAGE DELIVERABLES The Contractor will package deliverables in accordance with good commercial practice and shall include a packing list showing the description of each item, the quantity and unit price unless otherwise provided in the Specifications or Supplemental Terms and Conditions, each shipping container shall be clearly and permanently marked as follows: (a) The Contractor's name and address, (b) the City’s name, address and purchase order or purchase release number and the price agreement number if applicable, (c) Container number and total number of containers, e.g. box 1 of 4 boxes, and (d) the number of the container bearing the packing list. The Contractor shall bear cost of packaging. Deliverables shall be suitably packed to secure lowest transportation costs and to conform to all the requirements of common carriers and any applicable specification. The City's count or weight shall be final and conclusive on shipments not accompanied by packing lists.

  • Development cooperation 1. The Parties recognise that development cooperation is a crucial element of their Partnership and an essential factor in the realisation of the objectives of this Agreement as laid down in Article 1. This cooperation can take financial and non-financial forms.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

  • Project Team Cooperation Partnering 1.1.3 Constitutional Principles Applicable to State Public Works Projects.

  • Traditional Medicine Cooperation 1. The aims of Traditional Medicine cooperation will be: (a) to build on existing agreements or arrangements already in place for Traditional Medicine cooperation; and (b) to promote information exchanges on Traditional Medicine between the Parties. 2. In pursuit of the objectives in Article 149 (Objectives), the Parties will encourage and facilitate, as appropriate, the following activities, including, but not limited to: (a) encouraging dialogue on Traditional Medicine policies and promotion of respective Traditional Medicine; (b) raising awareness of active effects of Traditional Medicine; (c) encouraging exchange of experience in conservation and restoration of Traditional Medicine; (d) encouraging exchange of experience on management, research and development for Traditional Medicine; (e) encouraging cooperation in the Traditional Medicine education field, mainly through training programs and means of communication; (f) having a consultation mechanism between the Parties' Traditional Medicine authorities; (g) encouraging cooperation in Traditional Medicine therapeutic services and products manufacturing; and (h) encouraging cooperation in research in the fields of Traditional Medicine in order to contribute in efficacy and safety assessments of natural resources and products used in health care.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

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