Test Queries Sample Clauses

Test Queries. Test query set contained a mix of queries from all four topic-classes and represents the possible user queries. Test queries were selected such that there is no over- lap with the sampling queries. The test queries were generated by randomly removing words from camera names, book, movie and music album titles with prob- ability 0.5, similar to the sample queries described in Section 4.1. Number of test queries are varied for dif- ferent topics to obtain the required (0.95) statistical significance.
View SourceView Similar (2)
Test Queries. Google may send a reasonable number of uncompensated (with respect to both Yahoo! and Google) test queries to the Properties at any time as needed to verify Yahoo!’s compliance with the requirements of this Agreement. For avoidance of doubt, (a) Google and Yahoo! will work together to ensure that the test queries will not have a material impact on Yahoo!’s infrastructure and (b) the test queries will not be included in reporting sent to Yahoo!. Yahoo! will use commercially reasonable efforts to provide Google in a reasonable amount of time the means to ensure that AFS test queries generate AFS Queries, such that, for AFS Queries, failure of AFS test queries will be substantially indicative of failures experienced by End Users.
View SourceView Similar (2)
Test Queries. From time to time, the Coordinating Center may issue test Queries (each a “Test Query”) of Network Participant Data in advance of an Administrative or Analytic Query seeking return of either Aggregate Data, De-identified Individual Level Data, a Limited Data Set or Protected Health Information other than in a Limited Data Set for the purpose of beta testing the operability of software programs used in connection with PCORnet and other PCORnet Query enhancements. Depending on the type of Data requested for return, each Test Query shall be subject to the same requirements as set forth above for Administrative Queries, Matching Assessment Queries or Analytic Queries, as applicable. With approval from the CC, Network Participant may elect to return Data containing only simulated Protected Health Information (“Dummy Data”) in response to a Test Query. In such a case, the Dummy Data shall not be subject to the requirements set forth in this Agreement or HIPAA. Pursuant to Section III.a.i (Participation in a Query), participation in Test Queries is at the discretion of Network Participant. Results returned from Test Queries will not be combined with Results from any other Query, or shared with any individual, organization or other entity not a party to this Agreement, except as agreed with Network Participant for specific Queries.
View Source
Test Queries. Such Test Queries are created by the DCC for approved CODI Requests and are tested for accuracy or performance at one or multiple Data Owners before being distributed. Test queries are also used to identify potential data quality issues that could impact the query structure and project. Test Queries may require the return of Aggregate Data or Individual-Level Data and may be shared back with that originating Data Owner for validation or data quality purposes. The Aggregate or Individual-Level Data created from Test Queries will not be shared with other Data Owners or Data Users.
View Source
Test Queries. Yahoo! may conduct test Queries requesting over [*] results per Query on an offline basis (with relaxed SLAs). Yahoo! shall reimburse Microsoft for the Covered Marginal Costs (i) of serving such offline test Queries during non-Peak Time (as defined in Exhibit B) in excess of [*] Queries per second and (ii) [*]. Such test Queries shall use the same means that Microsoft uses internally for its own similar test Queries and shall comprise typical end user Query distribution. Yahoo! may, at any time, lower the maximum Queries per second for Peak Time offline test Queries under subsection (ii) in order to reduce Microsoft’s reimbursable Covered Marginal Costs, [*].
View Source
Test Queries 
View SourceView Similar (4)

Related to Test Queries

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.

  • Signaling protocol 4.1.3.1 SS7 Signaling is AT&T-21STATE’s preferred method for signaling. Where MF signaling is currently used, the Parties agree to use their best efforts to convert to SS7. If SS7 services are provided by AT&T-21STATE, they will be provided in accordance with the provisions of the applicable access tariffs. 4.1.3.2 Where MF signaling is currently used, the Parties agree to interconnect their networks using MF or dual tone MF (DTMF) signaling, subject to availability at the End Office Switch or Tandem Switch at which Interconnection occurs. The Parties acknowledge that the use of MF signaling may not be optimal. AT&T-21STATE will not be responsible for correcting any undesirable characteristics, service problems or performance problems that are associated with MF/SS7 inter-working or the signaling protocol required for Interconnection with CLEC employing MF signaling.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.