Semi-supervised Content AD Sensor Sample Clauses

Semi-supervised Content AD Sensor. We have implemented a content-based AD sensor that represents an adaptation of Xxxxxxx’x ideas [14]. Xxxxxxx proposes an algorithm that incorporates only the most heavily weighted grams to the behavior profile. These grams are the ones that best discriminate between two or more classes of data. Although Xxxxxxx is more expensive than other AD sensors, we chose it because it rapidly captures the significant information of the traffic being exchanged. In our sensor, we consider two classes of data (content): good samples (goodS ) and bad samples (badS ). The content of the traffic exchanged is captured as 3- grams. This choice is less computationally expensive than higher n-grams and appropriately captures the specifics of email traffic (as it will be shown in Section 4.3). The weight (frequency) of each 3-gram observed during training is calcu- lated using Xxxxxxx’x Formula (see Equation 2), where the frequency W of each 3-gram i (W(i)=F(i)×U(i)×A(i)) is expressed as, W (i) = log( xi )×( Ng logNg ΣNg ) j=1 (pij(log( 1 pij
Sample 1
AutoNDA by SimpleDocs

Related to Semi-supervised Content AD Sensor

  • Extra Trips a. Bus Drivers may be absent from driving part and/or all of their regular bus routes to take an extra trip. This will include Kindergarten route, shuttles, and noon Xxxxx Drivers. For Pay purposes the extra trip begins at the end of the driver's regular route. b. Regular Drivers desiring to take trips shall sign up at first Bus Drivers' Meeting held either prior to or on the opening day of school. Any Driver may join or remove themselves from the list at any time. All extra trips (Educational and Athletic/Group) shall be posted on one (1) list. c. Eligible Drivers shall be offered trips at a monthly field trip meeting on a seniority rotating basis. Between monthly meetings, trips shall be offered by phone or radio, on a seniority basis. d. If a Driver cancels a trip they agreed to drive, the trip will be offered to the next driver (who does not have a trip assigned) on a seniority basis from the canceled trip list. e. Drivers may not exchange trips. f. Drivers taking a group trip which involves an admission price and/or parking fee shall be covered by the group sponsoring the trip. g. In the event none of the eligible Drivers on the seniority rotation list are available to take a trip, the Drivers on the as-needed list will be asked. If no regular Drivers are available, then a Sub will be asked. If no Regular or Sub Drivers can take a trip, the Transportation Supervisor will appoint a Driver, starting with the least senior Driver on the DO WANT trips list. h. The Board may use the radio to contact Drivers for trips. Drivers must make the decision to drive or not to drive the offered trip within two (2) hours. i. If at all possible, the trips will be scheduled around two (2) weeks in advance. j. If a Driver shows up for a trip, and has not been notified the trip has been canceled, or a coach/advisor transports students, the Driver will be paid for two (2) regular hours and the driver will not be charged for the trip. k. If a Driver's trip date is changed, the scheduled Driver will stay on the trip. If the trip is canceled completely, the driver will be inserted next up the seniority rotation. The inserted driver shall not be taken out of rotation for forthcoming trips. l. If an Athletic Trip is canceled mid-event, the driver will be paid for the actual number of hours on duty; if rescheduled, the rescheduled event will be a new trip on the rotation list and the driver will be paid for the actual number of hours on duty. m. If a driver is on the insert list and already has a trip on the same day as a newly offered trip, the driver will stay on the insert list until a trip is offered for a day the driver is not already schedule to drive an extra trip. n. Any driver who cancels an extra trip two (2) or more times in a given month shall be skipped in the next rotation. o. Pay for extra trips will begin after the driver’s regular route time and will be at the driver’s regular rate of pay for up to two and one-half (2.5) hours for driver time and pre-trip. The remaining portion of the route will be at the Step 0 base rate. p. Overnight trips shall be considered special trips with reimbursement determined on an individual basis. q. Drivers on Leaves of Absences are not eligible for extra trips. r. Drivers are not eligible for extra trips on days on which they have called in and are off.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

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

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Posting licensed content on any Website The following terms and conditions apply as follows: Licensing material from an Elsevier journal: All content posted to the web site must maintain the copyright information line on the bottom of each image; A hyper-text must be included to the Homepage of the journal from which you are licensing at xxxx://xxx.xxxxxxxxxxxxx.xxx/science/journal/xxxxx or the Elsevier homepage for books at xxxx://xxx.xxxxxxxx.xxx; Central Storage: This license does not include permission for a scanned version of the material to be stored in a central repository such as that provided by Heron/XanEdu. Licensing material from an Elsevier book: A hyper-text link must be included to the Elsevier homepage at xxxx://xxx.xxxxxxxx.xxx . All content posted to the web site must maintain the copyright information line on the bottom of each image.

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters). 2.4.2.2 A UCL-D will be 18,000 feet or less in length and is provisioned according to Resistance Design parameters, may have up to 6,000 feet of bridged tap and will have up to 1300 Ohms of resistance. 2.4.2.3 The UCL-D is a designed circuit, is provisioned with a test point, and comes standard with a DLR. OC is a chargeable option for a UCL-D; however, OC is always required on UCLs where a reuse of existing facilities has been requested by Telepak Networks. 2.4.2.4 These Loops are not intended to support any particular services and may be utilized by Telepak Networks to provide a wide-range of telecommunications services as long as those services do not adversely affect BellSouth’s network. This facility will include a Network Interface Device (NID) at the customer’s location for the purpose of connecting the Loop to the customer’s inside wire. 2.4.2.5 Upon the Effective Date of this Agreement, Unbundled Copper Loop – Long (UCL-L) elements will no longer be offered by BellSouth and no new orders for UCL-L will be accepted. Any existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to the Effective Date of this Agreement. Existing UCL-Ls that were provisioned prior to the Effective Date of this Agreement may remain connected, maintained and repaired according to BellSouth’s TR73600 and may remain connected until such time as they are disconnected by Telepak Networks or BellSouth provides ninety

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