Increasing index specificity Sample Clauses

Increasing index specificity. There is an important drawback of evaluating index performance by determining the percent of best partitions identified by index/statistic combinations. Because there is always a global minimum or maximum of these statistics, index/statistic combinations have no specificity. We explored two types of specificity for selected index/global statistic optima pairings. First, we evaluated the ability of a local shape occurring at a statistic’s global optimum to identify cases in which the global optimum correctly chose the best partition. Second, we evaluated the ability of the joint occurrence of two statistics’ global optima to identify cases in which the global optima chose correctly. Local shapes Figure 4.1 gives examples of local shapes that can be found in the plot of an index for a range of partitions: a local minimum, a local maximum, an upward-concave elbow with an overall decrease in index value, a downward-concave elbow with an overall decrease in index value, an upward-concave elbow with an overall increase in index value, a downward-concave elbow with an overall increase in index value. In Figure 4.2, the contingency table on the left shows how local shapes can be used to create specific index usages. In this table, the “test” is that a certain local shape occurs at the same K as a certain statistic’s global optimum of choice. The table on the left depicts the general contingency table for using local shapes to increase specificity, where the global optimum of statistic A is at KA. The table on the right depicts use of local minima to identify cases in which global minima of the Xxxxxx-Xxxxxxx index have chosen correctly. Intersection of global optima In Figure 4.3, the table on the left depicts the general contingency table for using the co-occurrence of two statistics’ global optima to increase specificity, where the global optimum of statistic A is at KA and the global optimum of statistic B is at KB. The table on the right depicts use of joint occurrence of the maximum difference to the left and minimum different to the right to identify cases in which global minima of these statistics for the Calinski-Harabasz index have chosen correctly.
AutoNDA by SimpleDocs

Related to Increasing index specificity

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • ESTIMATED / SPECIFIC QUANTITY CONTRACTS Estimated quantity contracts, also referred to as indefinite delivery / indefinite quantity contracts, are expressly agreed and understood to be made for only the quantities, if any, actually ordered during the Contract term. No guarantee of any quantity is implied or given. With respect to any specific quantity stated in the contract, the Commissioner reserves the right after award to order up to 20% more or less (rounded to the next highest whole number) than the specific quantities called for in the Contract. Notwithstanding the foregoing, the Commissioner may purchase greater or lesser percentages of Contract quantities should the Commissioner and Contractor so agree. Such agreement may include an equitable price adjustment.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Annual Projections No later than thirty (30) days prior to the beginning of each Fiscal Year, the Borrowers shall deliver to Administrative Agent projected balance sheets, statements of income and cash flow for the Borrowers, for each of the twelve (12) months during such Fiscal Year, which shall include the assumptions used therein, together with appropriate supporting details as reasonably requested by Administrative Agent.

  • Class Specifications The Human Resources Division shall determine:

  • Measuring DNS parameters Every minute, every DNS probe will make an UDP or TCP “DNS test” to each of the public-­‐DNS registered “IP addresses” of the name servers of the domain name being monitored. If a “DNS test” result is undefined/unanswered, the tested IP will be considered unavailable from that probe until it is time to make a new test.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ESTIMATED QUANTITIES 1.1 The quantities set forth in the line items and specification document are approximate and represent the estimated requirements for the contract period.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

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