Correlated Binary Data Sample Clauses

Correlated Binary Data. A variety of approaches have been proposed for generating longitudinally corre- lated binary data (see [29] for a summary). One such approach was proposed by Xxxxxx(2003) [67], who introduced a multivariate binary distribution to easily and ef- ficiently simulate correlated binary variables with a given marginal mean vector and correlation matrix. Let Y = (Y1, . . . , YT )T denote a sequence of T binary responses. Further, let the marginal mean of Yt be E (Yt) = Pr (Yt = 1) = µt. The proposed approach is then implemented by generating a binary sequence using the conditional distribution for Yt given (Y1, . . . , Yt−1), where t = 2, . . . , n. Specifically, Xxxxxx defines ∑ t−1 λt = P (Yt = 1|Y1, . . . , Yt−1) = µt + bjt (Yj − µj) , where bjt reflects the generic correlation structure. Xxxxxx’x approach is computation- ally efficient for large T, while offering the flexibility to accommodate non-stationary data and unpatterned correlation. In addition, when compared to other methods for common stationary processes, the proposed approach allows for a wider range of correlation parameters.
Sample 1
AutoNDA by SimpleDocs

Related to Correlated Binary Data

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Optional Daily Usage File Upon written request from <<customer_name>>, BellSouth will provide the Optional Daily Usage File (ODUF) service to <<customer_name>> pursuant to the terms and conditions set forth in this section.

  • DISCLOSURE OF TBS ACCESS CODE TO THIRD PARTY (a) The Account Holder must exercise all care to ensure that the TBS Access Code is not disclosed to any person and shall take all steps to prevent forgery or fraud in connection with the use of his TBS Access Code and/or the operation of the TBS. If the TBS Access Code is disclosed to any person, the Account Holder must forthwith give the Bank written notice thereof, thereupon the Account Holder shall immediately cease to use the TBS Access Code. (b) Unless and until the Bank receives such written notice of disclosure, the Account Holder shall be fully liable and be bound by all transactions effected by the use of such TBS, with or without his consent or knowledge.

  • Enhanced Optional Daily Usage File Upon written request from <<customer_name>>, BellSouth will provide the Enhanced Optional Daily Usage File (EODUF) service to <<customer_name>> pursuant to the terms and conditions set forth in this section. EODUF will only be sent to existing ODUF subscribers who request the EODUF option.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks 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, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Safeguarding Customer Information The Servicer has implemented and will maintain security measures designed to meet the objectives of the Interagency Guidelines Establishing Standards for Safeguarding Customer Information published in final form on February 1, 2001, 66 Fed. Reg. 8616 and the rules promulgated thereunder, as amended from time to time (the “Guidelines”). The Servicer shall promptly provide the Master Servicer, the Trustee and the NIMS Insurer information reasonably available to it regarding such security measures upon the reasonable request of the Master Servicer, the Trustee and the NIMS Insurer which information shall include, but not be limited to, any Statement on Auditing Standards (SAS) No. 70 report covering the Servicer’s operations, and any other audit reports, summaries of test results or equivalent measures taken by the Servicer with respect to its security measures to the extent reasonably necessary in order for the Seller to satisfy its obligations under the Guidelines.

  • Optional Daily Usage File (ODUF 11.1 The Optional Daily Usage File (ODUF) Agreement with terms and conditions is included in this Attachment as Exhibit D. Rates for ODUF are as set forth in Exhibit F of this Attachment. 11.2 BellSouth will provide ODUF service upon written request to its Account Manager stating a requested activation date.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!