Spider Internal Testing Sample Clauses

Spider Internal Testing. The 333 blogs were inserted into a standalone spider service in October 2012. This was done to measure time and success rate of analysing and delivering the new content from the complete list of original blogs. The output was analysed; bugs were declared and issues concerning speed and stability were identified and fixed. The blogs were inserted into a spider with no history log that could influence the machine learning algorithms. Each test lasted 15 hours and included the observation of the capturing process and the analysis of the source blogs. The tests focused on the repeating harvesting processes while monitoring the updated blog sources with new blog posts. In October 2012, the spider captured 79% of the inserted blogs. The same tests were performed in January 2013, when the spider captured 83% of the inserted blogs. For the second round of internal spider testing in January 2013, the spider was emptied to avoid advantages due to machine learning capabilities. Afterwards, an entirely new “initial” capturing was done and repeated with the improved spider software. The two outputs were assessed to evaluate: the improvements; the remaining bugs and issues; and other changes that were needed.
Sample 1
AutoNDA by SimpleDocs

Related to Spider Internal Testing

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

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Health Tests At the time of employment, the Employer shall provide a Tuberculin skin test at no cost to the nurse. In the event of a positive reaction to this test, the Employer will provide a chest x-ray at no cost. Upon request, a routine blood examination and urinalysis will be provided at no cost to the nurse once each year.

  • Meter Testing Company shall provide at least twenty-four (24) hours' notice to Seller prior to any test it may perform on the revenue meters or metering equipment. Seller shall have the right to have a representative present during each such test. Seller may request, and Company shall perform, if requested, tests in addition to the every fifth-year test and Seller shall pay the cost of such tests. Company may, in its sole discretion, perform tests in addition to the fifth year test and Company shall pay the cost of such tests. If any of the revenue meters or metering equipment is found to be inaccurate at any time, as determined by testing in accordance with this Section 10.2 (Meter Testing), Company shall promptly cause such equipment to be made accurate, and the period of inaccuracy, as well as an estimate for correct meter readings, shall be determined in accordance with Section 10.3 (Corrections).

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

  • Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.

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

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

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