int_submit(SessionID, Workflow) Method Sample Clauses

int_submit(SessionID, Workflow) Method. The int_submit function is provided for submitting workflows though GUI authoring and submission environments such as the LONI Pipeline. GUI authoring and submission environments provide mechanisms for users to author workflows, to submit them and to track progress interactively. Due to continuous monitoring of the workflow there are some differences in the functionality of this method compared to batch_submit. GUI environments will be primarily used to create new workflows or customize existing ones and execute them to determine their behaviour. GUI environments will also be used to debug existing workflows. The workflow author will determine the workflow correctness by checking the output of each stage of the workflow execution, and in case of errors check the logs to determine errors. For this reason the workflow planner is not used in the int_submit function. The Workflow Planner, due to its optimization strategies, may change the workflow structure and may eliminate the execution of certain tasks based on data availability. This optimization may disrupt the workflow authoring process. To author a new workflow or correct existing ones, the workflow that is executed on a Grid, should be identical to the workflow that was authored. Once the workflow is deemed to be complete and frozen, then workflow optimization can be applied through the submit function. The sequence chart is shown in Figure 3. Figure 3: Sequence Diagram from int_submit Function Steps 1-4: Users first author a workflow in the environment and invoke submission. The Workflow authoring environment will first register a new sessionID from the Pipeline Service.
AutoNDA by SimpleDocs

Related to int_submit(SessionID, Workflow) Method

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Acceptance Tests 11.1 If the Contract provides acceptance tests for Goods and/or the result of Services after their completion and/or delivery to the Purchaser, the acceptance shall only be considered as definitive when such tests have demonstrated the compliance of the Goods and/or the result of the Services to the requirements in the Contract. 11.2 Where the Contract provides for an acceptance procedure in the presence of both parties, at the successful completion of such procedure, the Purchaser shall issue the Supplier with an acceptance certificate which shall authorise the Supplier to invoice the Purchaser for any payment due on such acceptance. 11.3 The Purchaser shall at its discretion be entitled to issue and acceptancecertificate with reserves. The Supplier shall be obliged to remedy any non-conformities within the period set out in the acceptance certificate. Any payment which would otherwise have been due on acceptance may be withheld by the Purchaser in whole or part until the non- conformities underlying the reserves have been remedied.

  • Follow-up Testing An employee shall submit to unscheduled follow-up drug and/or alcohol testing if, within the previous 24-month period, the employee voluntarily disclosed drug or alcohol problems, entered into or completed a rehabilitation program for drug or alcohol abuse, failed or refused a preappointment drug test, or was disciplined for violating the provisions of this Agreement and Employer work rules. The Employer may require an employee who is subject to follow-up testing to submit to no more than six unscheduled drug or alcohol tests within any 12 month period.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act. (B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S. (C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.

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

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

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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