Traditional IAA Sample Clauses

Traditional IAA. We measured the Inter-Annotator Agreement (IAA) using Krippendorff’s α, achieving a value of 0.342. This is lower than the recommended threshold of 0.667, but we should note that this value repre- sents the agreement level before curation, and as such, it is more representative of the curation dif- ficulty rather than of the quality of the final con- solidated annotations. We used the IAA during the campaign to allocate curation roles and to remove low-performing annotators. We further studied the IAA by ranking the an- notators by their performance with respect to the ground truth on the subset of documents they xxxx- xxxxx. We split then the annotators into two groups: top and low based on subjective assessment by the curators after the end of the curation campaign, this assessment was then further confirmed numerically (see Annex E for details). Their respective average α were 0.415 and 0.250. Finally, we considered the α of the group of the curators, in order to make an approximate estimation of the coherence of the curated dataset, as we expect these curators to con- sistently curate the data with at least the same coher- ence they had when annotating documents. There are only two such curators, whose α is of 0.588, which is lower but close to the recommended value.
AutoNDA by SimpleDocs

Related to Traditional IAA

  • Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.

  • EXTRADITION Extradition treaty, with exchange of notes. Signed at San Jose December 4, 1982; entered into force October 11, 1991. TIAS Agreement relating to investment guaranties. Signed at San Jose November 22, 1968; en- tered into force October 24, 1969. 20 UST 3001; TIAS 6776; 726 UNTS 157. Agreement regarding the consolidation and re- scheduling of certain debts owed to, guaran- teed or insured by the United States Govern- ment and its agencies, with annexes. Signed at Washington May 18, 1984; entered into force June 22, 1984. NP Agreement regarding the consolidation and re- scheduling of certain debts owed to, guaran- teed by or insured by the United States Gov- ernment and its agencies, with annexes. Signed at San Jose December 16, 1985; entered into force January 29, 1986. NP Agreement regarding the consolidation and re- scheduling of certain debts owed to, guaran- teed by or insured by the United States Gov- ernment and its agencies. Signed at San Jose February 22, 1990; entered into force April 9, 1990. NP Swap agreement among the United States Treasury and the Central Bank of Costa Rica/ Government of Costa Rica. Signed at Wash- ington and San Jose May 18, 1990; entered into force May 18, 1990. TIAS Agreement regarding the consolidation and re- scheduling or refinancing of certain debts owed to, guaranteed by, or insured by the United States Government and its agencies, with annexes. Signed at San Jose February 19, 1992; entered into force April 20, 1992. NP Agreement regarding the consolidation and re- scheduling or refinancing of certain debts owed to, guaranteed by or insured by the United States Government and its agencies, with annexes. Signed at San Jose November 22, 1993; entered into force August 10, 1994. NP Agreement relating to the construction of the inter-American highway within the borders of Costa Rica. Exchange of notes at Washington January 16, 1942; entered into force January 16, 1942. 56 Stat. 1840; EAS 293; 6 Bevans 1068; 23 UNTS 285. Amendment: January 13 and 17, 1951 (2 UST 1844; TIAS 2319; 134 UNTS 215).

  • Provisional Interconnection Service Upon the request of Interconnection Customer, and prior to completion of requisite Interconnection Facilities, Network Upgrades, Local Upgrades, or system protection facilities Interconnection Customer may request limited Interconnection Service at the discretion of Transmission Provider based upon an evaluation that will consider the results of available studies, which terms shall be memorialized in the Interconnection Service Agreement. Consistent with Tariff, Part VI, Subpart B, section 212.4, Interconnection Customer may execute the Interconnection Service Agreement, request dispute resolution or request that the Interconnection Service Agreement be filed unexecuted with the Commission. Transmission Provider shall determine, through available studies or additional studies as necessary, whether stability, short circuit, thermal, and/or voltage issues would arise if Interconnection Customer interconnects without modifications to the Generating Facility or the Transmission System. Transmission Provider shall determine whether any Interconnection Facilities, Network Upgrades, Local Upgrades, or system protection facilities that are necessary to meet the requirements of NERC, or any applicable Regional Entity for the interconnection of a new, modified and/or expanded Generating Facility are in place prior to the commencement of Interconnection Service from the Generating Facility. Where available studies indicate that such Interconnection Facilities, Network Upgrades, Local Upgrades, and/or system protection facilities that are required for the interconnection of a new, modified and/or expanded Generating Facility are not currently in place, Transmission Provider will perform a study, at the Interconnection Customer’s expense, to confirm the facilities that are required for Provisional Interconnection Service. The maximum permissible output of the Generating Facility shall be studied and updated annually and at the Interconnection Customer’s expense. The results will be communicated to the Interconnection Customer in writing upon completion of the study. Interconnection Customer assumes all risk and liabilities with respect to the Provisional Interconnection Service, including changes in output limits and Interconnection Facilities, Network Upgrades, Local Upgrades, and/or system protection facilities cost responsibilities.

  • Shift Trades 6.16.01 Employees may arrange for another employee to work their shift subject to the Manager's approval, consistent with the following: 6.16.01.01 Other than in exceptional circumstances, advice of the trade will be provided to the Manager in writing, in advance, and will be signed by the employees involved. 6.16.01.02 The employee who works a traded shift will be paid for the time worked at his/her rate of pay. 6.16.01.03 Overtime worked prior to or following a traded shift and premium credits on a holiday, in accordance with Article 7.03 and Article 13 respectively, will be credited to the employee who worked the shift as though the shift had been the employee's scheduled shift. 6.16.01.04 All recall credits will be credited to the employee who is recalled. 6.16.01.05 All time debits will be deducted from the employee who agreed to work the shift. 6.16.01.06 Company sick leave provisions will apply to the employee who agreed to work the shift and only to the amount provided for in such regulations. All time not worked in excess of one (1) full shift during a work day shall be debited in accordance with Article 6.16.01.05. 6.16.01.07 Shift trades may only be arranged between employees working in the same location except that, at locations with thirty (30) or less full-time employees, shift trades may be arranged by employees at these locations with employees at other locations within the same base and classification. Such shift trades may be granted subject to the employees concerned being qualified to perform the work function of the other party. 6.16.01.08 An employee's ability to trade shifts is not intended to allow employees to be absent from the work place for extended periods of time nor to take alternate employment. 6.16.01.09 Partial shift trades are permitted provided that no shift is split into more than two (2) parts. No more than two (2) employees may cover a single shift. Partial 6.16.01.10 It will be the sole responsibility of the employees to ensure that the introduction of partial shift trades has absolutely no adverse operational and customer service impact. 6.16.01.11 Under no circumstances shall an employee be allowed to leave his/her assigned duties or work area until their task is completed. His/her “shift trade partner” must be present and ready to take over their next assignment. This transition needs to be seamless to the customer. 6.16.01.12 There will not be additional meal or rest periods assigned to a shift subject to a partial shift trade. Meal and rest periods will be taken as scheduled. 6.16.01.13 A minimum of one (1) hour must be worked by one of the employees involved with a partial shift trade. 6.16.01.14 Any violation of the terms set out herein will result in the immediate suspension of the “partial shift trade privileges” for the employee. Such a measure will be deemed to be of an administrative nature and will not be grievable under any circumstances except as provided below. 6.16.01.15 Notwithstanding the above, the Union may file a grievance only to allege that the violation for which the partial shift trade privileges were revoked did not occur. The Union will bear the onus of the burden of proof in such circumstances. 6.16.01.16 Rules governing such other matters as deadlines for, and approval of, partial shift trade requests will be adopted locally.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • 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.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic County PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than twenty-four (24) hours.

  • PROPOSED MOBILITY PROGRAMME The proposed mobility programme includes the indicative start and end months of the agreed study programme that the student will carry out abroad. The Learning Agreement must include all the educational components to be carried out by the student at the receiving institution (in table A) and it must contain as well the group of educational components that will be replaced in his/her degree by the sending institution (in table B) upon successful completion of the study programme abroad. Additional rows can be added as needed to tables A and B. Additional columns can also be added, for example, to specify the study cycle-level of the educational component. The presentation of this document may also be adapted by the institutions according to their specific needs. However, in every case, the two tables A and B must be kept separated, i.e. they cannot be merged. The objective is to make clear that there needs to be no one to one correspondence between the courses followed abroad and the ones replaced at the sending institutions. The aim is rather that a group of learning outcomes achieved abroad replaces a group of learning outcomes at the sending institution, without having a one to one correspondence between particular modules or courses. A normal academic year of full-time study is normally made up of educational components totalling 60 ECTS* credits. It is recommended that for mobility periods shorter than a full academic year, the educational components selected should equate to a roughly proportionate number of credits. In case the student follows additional educational components beyond those required for his/her degree programme, these additional credits must also be listed in the study programme outlined in table A. When mobility windows are embedded in the curriculum, it will be enough to fill in table B with a single line as described below: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Mobility window … Total: 30 Otherwise, the group of components will be included in Table B as follows: Component code (if any) Component title (as indicated in the course catalogue) at the sending institution Semester [autumn / spring] [or term] Number of ECTS* credits Course x … 10 Module y … 10 Laboratory work … 10 Total: 30 The sending institution must fully recognise the number of ECTS* credits contained in table A if there are no changes to the study programme abroad and the student successfully completes it. Any exception to this rule should be clearly stated in an annex of the Learning Agreement and agreed by all parties. Example of justification for non-recognition: the student has already accumulated the number of credits required for his/her degree and does not need some of the credits gained abroad. Since the recognition will be granted to a group of components and it does not need to be based on a one to one correspondence between single educational components, the sending institution must foresee which provisions will apply if the student does not successfully complete some of the educational components from his study programme abroad. A web link towards these provisions should be provided in the Learning Agreement. The student will commit to reach a certain level of language competence in the main language of instruction by the start of the study period. The level of the student will be assessed after his/her selection with the Erasmus+ online assessment tool when available (the results will be sent to the sending institution) or else by any other mean to be decided by the sending institution. A recommended level has been agreed between the sending and receiving institutions in the inter-institutional agreement. In case the student would not already have this level when he/she signs the Learning Agreement, he/she commits to reach it with the support to be provided by the sending or receiving institution (either with courses that can be funded by the organisational support grant or with the Erasmus+ online tutored courses). All parties must sign the document; however, it is not compulsory to circulate papers with original signatures, scanned copies of signatures or digital signatures may be accepted, depending on the national legislation. * In countries where the "ECTS" system it is not in place, in particular for institutions located in partner countries not participating in the Bologna process, "ECTS" needs to be replaced in all tables by the name of the equivalent system that is used and a weblink to an explanation to the system should be added. The section to be completed during the mobility is needed only if changes have to be introduced into the original Learning Agreement. In that case, the section to be completed before the mobility should be kept unchanged and changes should be described in this section. Changes to the mobility study programme should be exceptional, as the three parties have already agreed on a group of educational components that will be taken abroad, in the light of the course catalogue that the receiving institution has committed to publish well in advance of the mobility periods and to update regularly as ECHE holder. However, introducing changes might be unavoidable due to, for example, timetable conflicts. Other reasons for a change can be the request for an extension of the duration of the mobility programme abroad. Such a request can be made by the student at the latest one month before the foreseen end date. These changes to the mobility study programme should be agreed by all parties within four to seven weeks (after the start of each semester). Any party can request changes within the first two to five-week period after regular classes/educational components have started for a given semester. The exact deadline has to be decided by the institutions. The shorter the planned mobility period, the shorter should be the window for changes. All these changes have to be agreed by the three parties within a two-week period following the request. In case of changes due to an extension of the duration of the mobility period, changes should be made as timely as possible as well. Changes to the study programme abroad should be listed in table C and, once they are agreed by all parties, the sending institution commits to fully recognise the number of ECTS credits as presented in table C. Any exception to this rule should be documented in an annex of the Learning Agreement and agreed by all parties. Only if the changes described in table C affect the group of educational components in the student's degree (table B) that will be replaced at the sending institution upon successful completion of the study programme abroad, a revised version should be inserted and labelled as "Table D: Revised group of educational components in the student's degree that will be replaced at sending institution". Additional rows and columns can be added as needed to tables C and D. All parties must confirm that the proposed amendments to the Learning Agreement are approved. For this specific section, original or scanned signatures are not mandatory and an approval by email may be enough. The procedure has to be decided by the sending institution, depending on the national legislation.

  • 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.

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