Pruning Algorithm Sample Clauses

Pruning Algorithm. The cells that need to be retrieved from the server after pruning consists of 1) can- didate cells which may include the RkNN answers, and 2) influence cells for each candidate cell in order to verify if the points in the candidate cells are indeed the RkNN answers. We describe in detail below how to compute the candidate cells and influence cells for each candidate cell. Candidate cells are all non-empty cells that may include the answer to a RkNN query if the actual coordinate of points in them become available. As illustrated in Figure 4.8, our pruning phase accesses the cells around the query in clockwise order and checks each cell against a set of candidate cells to see whether (a) (b) (c) Figure 4.9: Computing influence cells for the candidate cell < 5, 4 > they are pruned (line 7-25 of the Algorithm 3). At the beginning, the candidate set CNDc is empty or includes the query cell Q if it is non-empty. As pruning phase continues, any cell which is not pruned k times by candidate cells is added to the set. We keep track of the number of times a cell is pruned by incorporating the number of data points in pruning cells. It means, if a candidate cell cnd which has 3 points prunes c with regard to the query q, we record c is pruned 3 times (c.pruned = 3). If all of the cells in a layer around the query are pruned k times, the search stops, otherwise, pruning phase continues to assess upper layers. After retrieving all of candidate cells, the pruning phase is continued by computing influence cells. Influence cells for every candidate cell is the set of all non-empty cells that do not prune candidate cells, however, if the actual coordinate of points in them are realized, they may prune the points in the candidate cell. We compute a set of influence cells INFc for every candidate cell cnd as follows. First, we probe the cells around cnd and retrieve every cell c that does not prune the candidate cell, but satisfies the following condition [65].
AutoNDA by SimpleDocs

Related to Pruning Algorithm

  • Scaling “Scaling,” as used herein, involves:

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Revenue Metering The Connecting Transmission Owner’s revenue metering will be located on the generator side of the 115kV breaker at the Xxxxx Solar Collector Substation and will consist of: • three (3) combination current/voltage transformer (“CT/VT”) units (manufacturer and model ABB/Xxxxxxx KXM-550, GE Grid Solutions KOTEF 000.XX, or other equivalent specified by Connecting Transmission Owner); and • one (1) revenue meter. The ratios of the CTs and VTs will be provided by Connecting Transmission Owner upon its review of the Interconnection Customer’s design documents. (Note: Connecting Transmission Owner’s revenue metering CTs and VTs cannot be used to feed the Interconnection Customer’s check meter.) SERVICE AGREEMENT NO. 2556

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

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

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