INVARIANT STATISTICAL DESCRIPTORS Sample Clauses

INVARIANT STATISTICAL DESCRIPTORS. Invariants, as the name suggests, are a means to aid the creation or measurement of information while reducing inaccuracies and uncertainties in the creation or measurement process. This means that objects will exhibit similar, if not exactly the same, measurements in differing situations. This greatly improves and simplifies the classification and matching process, especially in far field classification tasks where measurement conditions may vary widely. It is often the case, that invariants require significant processing (especially true in appearance­based invariants), to resolve and ensure their invariance. This increases computational cost. Having said this, the cost is normally outweighed by the increase in classification accuracy. It is also true that, given current trends, computer systems will become ever more powerful, thereby allowing the increased cost of using invariants.
Sample 1
AutoNDA by SimpleDocs

Related to INVARIANT STATISTICAL DESCRIPTORS

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • Statistical Analysis 31 F-tests and t-tests will be used to analyze OV and Quality Acceptance data. The F-test is a 32 comparison of variances to determine if the OV and Quality Acceptance population variances 33 are equal. The t-test is a comparison of means to determine if the OV and Quality Acceptance 34 population means are equal. In addition to these two types of analyses, independent verification 35 and observation verification will also be used to validate the Quality Acceptance test results.

  • Statistical Information Any third-party statistical and market-related data included in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus are based on or derived from sources that the Company believes to be reliable and accurate in all material respects.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Usage Statistics The Distributor shall ensure that the Publisher will provide access to both composite system-wide use data and itemized data for the Licensee, the Participating Institutions, individual campuses and labs, on a monthly basis. The statistics shall meet or exceed the most recent project Counting Online Usage of NeTworked Electronic Resources ("COUNTER") Code of Practice Release,3 including but not limited to its provisions on customer confidentiality. When a release of a new COUNTER Code of Practice is issued, the Distributor shall ensure that the Publisher will comply with the implementation time frame specified by COUNTER to provide usage statistics in the new standard format. It is more than desirable that the Standardized Usage Statistics Harvesting Initiative (SUSHI) Protocol4 is available for the Licensee to harvest the statistics.

  • Topic Description Licensee Responsibilities Licensee must:  Take appropriate steps to ensure the security, integrity, and confidentiality of Confidential Information and must comply with all relevant applicable laws and regulations, including laws protecting borrower privacy.  Not disclose Confidential Information to third parties, without Xxxxxx Mae’s prior written approval, except on a need‐to‐know basis to Licensee’s partners, Topic Description affiliates, officers, employees, directors, contractors, counsels, agents or representatives, provided they are subject to confidentiality obligations at least as stringent as those set forth in this Section A3.  Not use Confidential Information in any way that could be viewed as a conflict of interest, a breach of confidentiality or privacy, or the gaining of an unfair advantage from the relationship with Xxxxxx Xxx.  Implement commercially reasonable measures meeting or exceeding industry standards to ensure the security, integrity, and confidentiality of Confidential Information, including using industry‐standard encryption for data in transit and virus checking programs designed to prevent the transmission and receipt of viruses and other malicious code, implementing appropriate disaster recovery and back‐up procedures, implementing appropriate procedures to prevent disclosure of data and other materials to a party other than the intended recipient, and employing methods for securely disposing or destroying such information.  These measures must meet, at least, the same level of protection that the Receiving Party seeks for its own information of a similar nature.  Licensee must collaborate with Xxxxxx Mae in assessing the sufficiency of these measures and Licensee’s information security program, upon reasonable request.  Instruct its Related Parties who may receive Confidential Information about the requirements of this Section A3, and the processes and procedures necessary to comply with them.  Comply with all reasonable security policies and procedures required by Xxxxxx Xxx related to the access and use of Xxxxxx Mae’s systems or any Licensed Materials.  Not transmit to Xxxxxx Mae’s systems any materials that contain bugs, viruses, worms or other functions, routines, devices or instructions which may create any unauthorized access or damage to, or interruption in the functioning of, the Licensed Application or Xxxxxx Mae’s systems. Restrictive Legends  Licensee must abide by and reproduce and include any restrictive legend or proprietary rights notice that appears in or on any Confidential Information of Xxxxxx Xxx or any Third‐Party Licensor (or other third‐party owner) that it is authorized to reproduce.  Licensee also agrees that it will not remove, alter, cover or distort any trademark, trade name, copyright or other proprietary rights notices, legends, symbols or labels appearing on or in any Confidential Information of Xxxxxx Mae or any Third‐Party Licensor (or other third‐party owner). Required Actions in Case of Data Breach  Licensee must address any Data Breach with prompt and effective corrective action, including cooperation with Xxxxxx Xxx in the investigation and remediation of such Data Breach, as well as prompt disclosure and notification where legally required; and  Licensee must promptly notify Xxxxxx Mae of any Data Breach in writing ‐‐ at xxxxxxx_xxxxxxxxxxxx@xxxxxxxxx.xxx ‐‐ and must take all steps reasonably requested by Xxxxxx Xxx to mitigate the consequences of such Data Breach.

  • For More Information To obtain more information concerning the rules governing this Agreement, contact the Prototype Sponsor or Custodian listed on the Adoption Agreement.

  • Streets and Municipal Services 4.1 Off-Site Disturbance Any disturbance to existing off-site infrastructure resulting from the development, including but not limited to, streets, sidewalks, curbs and gutters, street trees, landscaped areas and utilities, shall be the responsibility of the Developer, and shall be reinstated, removed, replaced or relocated by the Developer as directed by the Development Officer, in consultation with the Development Engineer.

  • Technical Requirements for SCPs/Databases 10.5.3.1 BellSouth shall provide physical access to SCPs through the SS7 network and protocols with TCAP as the application layer protocol.

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