Shift Integration into Polaris Sample Clauses

Shift Integration into Polaris. The purpose of this task is to develop the capability to perform lattice physics calculations with the SCALE Monte Carlo code Shift through the established Polaris input and output definitions. This capability shall be able to provide reference solutions for non-LWR fuel designs to generate nodal cross section data for PARCS that are computed via Shift continuous energy (CE) Monte Carlo from the same inputs as the Polaris multigroup (MG) approach. The Polaris code base is designed for MG calculations via the Embedded Self-Shielding Methodology (ESSM) to generate problem-dependent cross sections and a Method of Characteristics (MOC) transport solver to generate flux solutions that are subsequently used to produce nodal core simulator data for PARCS. The current Polaris interface to the MG ESSM and MOC methods is designed for setting the materials, temperatures, problem geometry and MG macroscopic cross sections, a solve method for the MG MOC transport calculation as well as methods to access the MG flux solution. The Shift MC interface will have additional requirements for defining MC sampling parameters as well as tally definitions needed for nodal cross section generation. The construction of the lattice geometry will be updated to create Shift native geometry. The capability to perform Shift XX Xxxxx Carlo calculations from Polaris will be implemented for release in SCALE. Additional work to investigate running Shift MG calculations from Polaris will be performed if resources permit. Expected Level of Effort: 1,750 staff-hours Task 2. Expert Technical Support Technical support and assistance in support of Task 1 of this task order and the operation of the SCALE system shall be provided to NRC staff identified by the NRC COR. For example, assistance with technical issues as arisen from the above Tasks, and may include interaction with ACRS, may be required. It is expected that some of the work required for this task may involve collaborations with other contractors/staff/etc. as appropriate. A road map for the completion of each requested task is to be developed and provided to the PM. Expected Level of Effort: 150 staff-hours Key Personnel Xxxxx Xxxxxx will be the Project Manager, and Xxxx Xxxxxx will be the Principal Investigator for this effort. Other key staff include Xxxxx Xxx and Xxxx Xxxxxxxx. Résumés are attached. Subcontractors/Consultants Information No subcontracting effort is anticipated at this time. Travel The following travel is anticipated...
Sample 1
AutoNDA by SimpleDocs

Related to Shift Integration into Polaris

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Local Switching Interfaces 4.2.13.1 Newcomm shall order ports and associated interfaces compatible with the services it wishes to provide as listed in Exhibit A. BellSouth shall provide the following local switching interfaces:

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Full Integration This Agreement, including the attached Order, is the final written expression and the complete and exclusive statement of all the agreements, conditions, promises, representations, and covenants between the parties with respect to the subject matter hereof, and supercedes all prior or contemporaneous agreements, negotiations, representations, understandings, and discussions between and among the parties, their respective representatives, and any other person or entity, with respect to the subject matter covered hereby.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Subprocessing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the subprocessor which imposes the same obligations on the subprocessor as are imposed on the data importer under the Clauses. Where the subprocessor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the subprocessor's obligations under such agreement.

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