{
  "fetched_at": "2026-10-24T02:33:30Z",
  "source_url": "https://www.kaggle.com/competitions/google-cloud-ncaa-march-madness-2020-division-1-mens-tournament/data",
  "pages": [
    {
      "name": "rules",
      "content": "### **Updated March 13, 2020**: The following supersedes the respective terms outlined below.  As a result of COVID-19, this competition will be cancelled with no Kaggle points, Kaggle medals, or monetary prizes. The end date has been updated from April 7, 2020 at 11:59pm UTC to March 19, 2020 at 3:00 am UTC. Please see this [announcement post](https://www.kaggle.com/c/google-cloud-ncaa-march-madness-2020-division-1-mens-tournament/discussion/135404) for more details.\n\n### One account per participant\n\nYou cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.\n\n### Use of Automated Machine Learning Tools (AMLT)\n\nAs further described in the Rules, this Competition permits the use of automated machine learning tool(s) (“AMLT”) in the creation of Submissions. AMLT Teams (as defined in the Rules) are not eligible to win any prizes. \n\n### No private sharing outside teams\n\nPrivately sharing code or data outside of teams is not permitted. It's okay to share code if made available to all participants on the forums.\n\n### Team Mergers\n\nTeam mergers are allowed and can be performed by the team leader. In order to merge, the combined team must have a total submission count less than or equal to the maximum allowed as of the merge date. The maximum allowed is the number of submissions per day multiplied by the number of days the competition has been running. AMLT Teams are not permitted to enter into a Team merger. \n\n### Team Limits\n\nThe maximum team size is 5.\n\n### Submission Limits\n\nYou may submit a maximum of 50 entries per day.\n\nYou may select up to 2 final submissions for judging.\n\n### Competition Timeline\n\nStart Date: February 14, 2020\n\nMerger Deadline: March 19, 2020, 3:00 PM UTC\n\nEntry Deadline: March 19, 2020, 3:00 PM UTC\n\nEnd Date: **April 7, 2020, 11:59 PM EST**\n\n### COMPETITION-SPECIFIC TERMS\n\n**COMPETITION TITLE** (the 'Competition'): Google Cloud & NCAA&reg ML Competition 2020-NCAAM\n\n**COMPETITION SPONSOR**: Google Cloud\n\n**COMPETITION SPONSOR ADDRESS**: 1600 Amphitheatre Parkway, Mountain View, CA 94043\n\n**COMPETITION WEBSITE**: https://www.kaggle.com/c/google-cloud-ncaa-march-madness-2020-division-1-mens-tournament\n\n**PRIZES: $25,000**\n\nFirst Prize: $10,000\n\nSecond Prize: $7,000\n\nThird Prize: $5,000\n\nFourth Prize: $2,000\n\nFifth Prize: $1,000\n\n**WINNER LICENSE TYPE**: Open Source\n\n**DATA ACCESS AND USE**: Competition-Use Only\n\nCompetitions are open to residents of the United States and worldwide, except that if you are a resident of Crimea, Cuba, Iran, Syria, North Korea, Sudan, or are subject to U.S. export controls or sanctions, you may not enter the Competition. Other local rules and regulations may apply to you, so please check your local laws to ensure that you are eligible to participate in skills-based competitions. The Competition Sponsor reserves the right to award alternative Prizes where needed to comply with local laws.\n\n**ENTRY IN THIS COMPETITION CONSTITUTES YOUR ACCEPTANCE OF THESE OFFICIAL COMPETITION RULES.**\n\nThe Competition named above is a skills-based competition to promote and further the field of data science. You must register via the Competition Website to enter. Your competition submissions (\"Submissions\") must conform to the requirements stated on the Competition Website. Your Submissions will be scored based on the evaluation metric described on the Competition Website. Subject to compliance with the Competition Rules, Prizes, if any, will be awarded to participants with the best scores, based on the merits of the data science models submitted. See below for the complete Competition Rules.\n\n### A. COMPETITION-SPECIFIC RULES\n\nIn addition to the provisions of the General Competition Rules below, you understand and agree to these Specific Competition Rules required by the Competition Sponsor:\n\n#### **1.\tWINNER LICENSE**\n\nOpen Source: You will license your winning Submission and the source code used to generate the Submission under an [Open Source Initiative-approved license][1] that in no event limits commercial use of such code or model containing or depending on such code.\n\n#### **2.\tSPECIAL RULES**\n\nA. *NCAA&reg; Data Use*. \n\nYou agree that use of, and access to, the NCAA&reg; data provided for this Competition (the “NCAA&reg; Data”) is provided for the limited purpose of, and in connection with, your participation in the Competition.\n\nYou will not: (a) use or access the NCAA&reg; Data for any commercial, gambling, or illegal purpose; (b) copy, modify, reproduce, license, sublicense, distribute, transmit, republish, exhibit, or display the NCAA&reg; Data (except to the extent copying, modifying, reproducing or displaying is necessary and directly related to your participation in the Competition; (c) remove, obscure, or modify any copyright notices or other notices, designations, or attributions within the NCAA&reg; Data; or (d) use any NCAA&reg; Marks or any copyright or other proprietary rights associated with the NCAA&reg; Data for any purpose without the express written consent of NCAA&reg;.  “NCAA&reg; Marks” means all names, trademarks, logos, symbols, designations, emblems, designs, and trade dress of the NCAA&reg;, together with all identifications, labels, insignia or indicia thereof.\n\nYou agree that the NCAA&reg; is the owner of all right, title and interest in and to the NCAA&reg; Data and the NCAA&reg; Marks throughout the world, and that your use of the NCAA&reg; Data does not change this ownership. \n\nYou will not use NCAA&reg; Data in any production or manner that (a) causes actual or perceived harm to the health, safety, or welfare of NCAA&reg; student-athletes; (b) brings discredit to the purpose, values or principles of the NCAA&reg; or its member institutions; or (c) negatively impacts the best interests of intercollegiate athletics or higher education.\n\nYou will not use NCAA&reg; Data with any other material or content that contains or displays adult content, promotes gambling, involves the sale of tobacco or alcohol, or other illicit substances, including NCAA&reg;-banned substances (e.g., stimulants, anabolic steroids, testosterone products, marijuana), or impermissible nutritional supplements that NCAA&reg; member institutions may not provide to student-athletes (e.g., creatine, amino acids, ginseng, energy drinks) (the list of NCAA&reg;-banned drug classes is available at [www.ncaa.org/drugtesting][2]).\n\nYou will not use NCAA&reg; Data in any product or service that includes the name, image, or likeness of a currently eligible NCAA&reg; student-athlete.\n\nYou will not use NCAA&reg; Data in any product or service that, in the NCAA&reg;’s opinion, is misleading, unfair, defamatory, infringing, libelous, disparaging, obscene, violent, profane, vulgar, offensive, disrespectful or otherwise objectionable to the NCAA&reg;. \n\nYou will not use NCAA&reg; Data in any manner that violates any law or regulation.  \n\nYou will not incorporate NCAA&reg; Data into the brand or name of any product or service.\n\nYou will not use NCAA&reg; Data in any produce or service that are promoted, marketed, or branded with marks, logos, slogans, or designs that are confusingly similar to those of the NCAA&reg; or associated with the NCAA&reg;’s use of the NCAA&reg; Data.\n\nNCAA, Final Four, March Madness and Selection Sunday are trademarks of the National Collegiate Athletic Association. \n\nB. *Competition Submission Special Rules*. \n\nYou may determine game probability predictions as part of a submission by any method you like, including guessing.\n \nYou may not use the test data to cheat on the first stage of the competition. Your approach should only utilize past data when making a prediction.\n\nC. *Eligibility*. The following supersedes section 2.B below - Unless otherwise stated in the Specific Competition Rules above or prohibited by internal policies of the Competition Entities, employees, interns, contractors, officers and directors of Competition Entities may enter and participate in the Competition, but are not eligible to win any Prizes. \"Competition Entities\" means the Competition Sponsor, Kaggle Inc., National Collegiate Athletic Association, CBS Broadcasting, Inc.,  Turner Broadcasting Systems, Inc., and each of their respective parent companies, subsidiaries and affiliates. If you are such a participant from a Competition Entity, you are subject to all applicable internal policies of your employer with respect to your participation.\n\n#### **3. AUTOMATED MACHINE LEARNING TOOLS (AMLT).** \n\nThis competition permits the use of automated machine learning tool(s) (“AMLT”) in the creation of Submissions. Except as described in this section, AMLT are not permitted to be used in the creation of a Submission.\n \n**A. Submission as an AMLT**\n \nAn individual or team may make a Submission as an AMLT (each individual or team making a submission as an AMLT, a “AMLT Team”). The AMLT Team must be authorized to make such Submission by the owner(s) of the AMLT (including all rights in the AMLT). AMLT Teams must declare themselves as such by submitting the following form prior to making a Submission: https://www.kaggle.com/amlt-registration. Submissions made by an AMLT Team will be marked as benchmarks (highlighted and named to match the AMLT Team name) on the Competition’s public leaderboard and, like all Submissions, cannot be removed or revoked once submitted.\n \nThe following provision is added to the end of Section 2 of the General Competition Rules below: “AMLT Teams may enter and participate in the Competition, but are not eligible to win any Prizes.”\n\nThe following provision is added to the end of Section 6 of the General Competition Rules below: “D. AMLT Teams. If you submit a Submission to this Competition as an AMLT Team, you cannot also submit as an individual user or as a team. Violation may result in your disqualification from the Competition and removal from the Competition leaderboard, at Kaggle's sole discretion. AMLT Teams are not permitted to enter into a Team merger.”\n\n**B. Using an AMLT to create a submission**\n \nIndividual participants and Teams may also use an AMLT to create a Submission, provided that the participant ensures that they have an appropriate license to the AMLT and are able to comply with the Rules. An individual participant’s or Team’s use of an AMLT to create a Submission does not require that individual or team declare itself as an AMLT Team as described in Subsection A (Submission as an AMLT Team) above. \n \nThe following provision is added to the end of Section 11 of the General Competition Rules below: “Individual participants and Teams who have not declared themselves as an AMLT Team, but who create a Submission using an AMLT may win a Prize. However, for clarity, the potential winner’s Submission must still meet the requirements of these Rules, including but not limited to Section A.1 (Winners License), Section B.11 (Winners Obligations), and Section B.17 (Warranty, Indemnity, and Release). Additionally, as this Competition requires [an open source] license, a participant may only use AMLTs in the creation of their Submission if they have the unrestricted right to grant the open source license to source code used to generate the Submission, including the AMLT code. Associated disqualification and other consequences as specified in these Rules will apply if this requirement  is not met.”\n\n#### **4.       AGGREGATION OF COMPETITION ENTRIES**\n\nYou acknowledge and agree that any Competition entry you submit may be aggregated with other entries and the resulting aggregate may be used in marketing activities, such as averaging participant predictions or promoting a competition-wide community prediction.\"\n\n\n### B. GENERAL COMPETITION RULES\n#### **1.\tBINDING AGREEMENT.** \n\nTo enter the Competition, you must agree to these Official Competition Rules, which incorporate by reference the provisions and content of the Competition Website and any Specific Competition Rules above (collectively, the \"Rules\"). Please read these Rules carefully before entry to ensure you understand and agree. You further agree that submission of an entry in the Competition constitutes agreement to these Rules. You may not submit an entry to the Competition and are not eligible to receive the prizes associated with this Competition (“Prizes”) unless you agree to these Rules. These Rules form a binding legal agreement between you and the Competition Sponsor with respect to the Competition.\n\n#### **2.\tELIGIBILITY.** \n\nA. To be eligible to enter the Competition, you must be:\n\t(i) a registered account holder at Kaggle.com; \n\t(ii) the older of 18 years old or the age of majority in your jurisdiction of residence (unless otherwise agreed to by Competition Sponsor and appropriate parental/guardian consents have been obtained by Competition Sponsor); \n\t(iii) not a resident of Crimea, Cuba, Iran, Syria, North Korea, or Sudan; and\n\t(iv) not a person or representative of an entity under U.S. export controls or sanctions (see [https://www.treasury.gov/resource-center/sanctions/Programs/Pages/Programs.aspx][1]).\n\nIf you are entering as a representative of a company, educational institution or other legal entity, or on behalf of your employer, these rules are binding on you, individually, and the entity you represent or are an employee. If you are acting within the scope of your employment, as an employee, contractor, or agent of another party, you warrant that such party has full knowledge of your actions and has consented thereto, including your potential receipt of a Prize. You further warrant that your actions do not violate your employer's or entity's policies and procedures.   \n\nThe Competition Sponsor reserves the right to verify eligibility and to adjudicate on any dispute at any time. If you provide any false information relating to the Competition concerning your identity, residency, mailing address, telephone number, email address, ownership of right, or information required for entering the Competition, you may be immediately disqualified from the Competition.\n\nB. Unless otherwise stated in the Specific Competition Rules above or prohibited by internal policies of the Competition Entities, employees, interns, contractors, officers and directors of Competition Entities may enter and participate in the Competition, but are not eligible to win any Prizes. \"Competition Entities\" means the Competition Sponsor, Kaggle Inc., and their respective parent companies, subsidiaries and affiliates. If you are such a participant from a Competition Entity, you are subject to all applicable internal policies of your employer with respect to your participation.\n\n#### **3.\tSPONSOR AND HOSTING PLATFORM.** \n\nThe Competition is sponsored by Competition Sponsor named above. The Competition is hosted on behalf of Competition Sponsor by Kaggle Inc. (\"Kaggle\"). Kaggle is an independent contractor of Competition Sponsor, and is not a party to this or any agreement between you and Competition Sponsor. You understand that Kaggle has no responsibility with respect to selecting the potential Competition winner(s) or awarding any Prizes. Kaggle will perform certain administrative functions relating to hosting the Competition, and you agree to abide by the provisions relating to Kaggle under these Rules. As a Kaggle.com account holder and user of the Kaggle competition platform, remember you have accepted and are subject to the Kaggle Terms of Service at [www.kaggle.com/terms][2] in addition to these Rules.\n\n#### **4.\tCOMPETITION PERIOD.** \n\nFor the purposes of Prizes, the Competition will run from the Start Date and time to the End Date and time (such duration the “Competition Period”). The Competition Timeline is subject to change, and Competition Sponsor may introduce additional hurdle deadlines during the Competition Period. Any updated or additional deadlines will be publicized on the Competition Website. It is your responsibility to check the Competition Website regularly to stay informed of any deadline changes. *YOU ARE RESPONSIBLE FOR DETERMINING THE CORRESPONDING TIME ZONE IN YOUR LOCATION.* \n\n#### **5.\tCOMPETITION ENTRY.** \n\nNO PURCHASE NECESSARY TO ENTER OR WIN. To enter the Competition, you must register on the Competition Website prior to the Entry Deadline, and follow the instructions for developing and entering your Submission through the Competition Website. Your Submissions must be made in the manner and format, and in compliance with all other requirements, stated on the Competition Website (the \"Requirements\"). Submissions must be received before any Submission deadlines stated on the Competition Website. Submissions not received by the stated deadlines will not be eligible to receive a Prize.\n\nSubmissions may not use or incorporate information from hand labeling or human prediction of the validation dataset or test data records.\n\nIf the Competition is a multi-stage competition with temporally separate training and/or test data, one or more valid Submissions may be required during each Competition stage in the manner described on the Competition Website in order for the Submissions to be Prize eligible.\n\nSubmissions are void if they are in whole or part illegible, incomplete, damaged, altered, counterfeit, obtained through fraud, or late. Competition Sponsor reserves the right to disqualify any entrant who does not follow these Rules, including making a Submission that does not meet the Requirements. \n\n#### **6.\tINDIVIDUALS AND TEAMS.** \n\nA. *Individual Account*. You may make Submissions only under one, unique Kaggle.com account. You will be disqualified if you make Submissions through more than one Kaggle account, or attempt to falsify an account to act as your proxy. You may submit up to the maximum number of Submissions per day as specified on the Competition Website. \n\nB. *Teams*. If permitted under the Competition Website guidelines, multiple individuals may collaborate as a team (a \"Team\"); however, you may join or form only one Team. Each Team member must be a single individual with a separate Kaggle account. You must register individually for the Competition before joining a Team. You must confirm your Team membership to make it official by responding to the Team notification message sent to your Kaggle account. Team membership may not exceed the Maximum Team Size stated on the Competition Website.\n\nC. *Team Merger*. Teams may request to merge via the Competition Website. Team mergers may be allowed provided that: (i) the combined Team does not exceed the Maximum Team Size; (ii) the number of Submissions made by the merging Teams does not exceed the number of Submissions permissible for one Team at the date of the merger request; (iii) the merger is completed before the earlier of: any merger deadline or the Competition deadline; and (iv) the proposed combined Team otherwise meets all the requirements of these Rules. \n\n#### **7.\tCOMPETITION DATA.** \n\n\"Competition Data\" means the data or datasets available from the Competition Website for the purpose of use in the Competition, including any prototype or executable code provided on the Competition Website. The Competition Data will contain private and public test sets. Which data belongs to which set will not be made available to participants. \n\nA. *Data Access and Use*. You may access and use the Competition Data only for participating in the Competition and on Kaggle.com forums. The Competition Sponsor reserves the right to disqualify any participant who uses the Competition Data other than as permitted by the Competition Website and these Rules.\n\nB. *Data Security*. You agree to use reasonable and suitable measures to prevent persons who have not formally agreed to these Rules from gaining access to the Competition Data. You agree not to transmit, duplicate, publish, redistribute or otherwise provide or make available the Competition Data to any party not participating in the Competition. You agree to notify Kaggle immediately upon learning of any possible unauthorized transmission of or unauthorized access to the Competition Data and agree to work with Kaggle to rectify any unauthorized transmission or access.\n\nC. *External Data*. You may use data other than the Competition Data (“External Data”) to develop and test your models and Submissions. However, you will (i) ensure the External Data is available to use by all participants of the competition for purposes of the competition at no cost to the other participants and (ii) post such access to the External Data for the participants to the official competition forum prior to the Entry Deadline.\n\n#### **8.\tSUBMISSION CODE REQUIREMENTS.**\n\nA. *Private Code Sharing*. Unless otherwise specifically permitted under the Competition Website or Competition Specific Rules above, during the Competition Period, you are not allowed to privately share source or executable code developed in connection with or based upon the Competition Data or other source or executable code relevant to the Competition (“Competition Code”). This prohibition includes sharing Competition Code between separate Teams, unless a Team merger occurs. Any such sharing of Competition Code is a breach of these Competition Rules and may result in disqualification.\n\nB. *Public Code Sharing*. You are permitted to publicly share Competition Code, provided that such public sharing does not violate the intellectual property rights of any third party. If you do choose to share Competition Code or other such code, you are required to share it on Kaggle.com on the discussion forum or kernels associated specifically with the Competition for the benefit of all competitors. By so sharing, you are deemed to have licensed the shared code under an Open Source Initiative-approved license (see [www.opensource.org][3]) that in no event limits commercial use of such Competition Code or model containing or depending on such Competition Code.\n\nC. *Use of Open Source*. Unless otherwise stated in the Specific Competition Rules above, if open source code is used in the model to generate the Submission, then you must only use open source code licensed under an Open Source Initiative-approved license (see [www.opensource.org][4]) that in no event limits commercial use of such code or model containing or depending on such code.\n\n#### **9.\tDETERMINING WINNERS.** \n\nEach Submission will be scored and ranked by the evaluation metric stated on the Competition Website. During the Competition Period, the current ranking will be visible on the Competition Website's public leaderboard. The potential winner(s) are determined solely by the leaderboard ranking on the private leaderboard, subject to compliance with these Rules. The public leaderboard will be based on the public test set and the private leaderboard will be based on the private test set.\n\nIn the event of a tie, the Submission that was entered first to the Competition will be the winner. In the event a potential winner is disqualified for any reason, the Submission that received the next highest score rank will be chosen as the potential winner.\n\n#### **10.\tNOTIFICATION OF WINNERS & DISQUALIFICATION.**\n\nThe potential winner(s) will be notified by email. \n \nIf a potential winner (i) does not respond to the notification attempt within one (1) week from the first notification attempt or (ii) notifies Kaggle within one week after the End Date that the potential winner does not want to be nominated as a winner or does not want to receive a Prize, then, in each case (i) and (ii) such potential winner will not receive any Prize, and an alternate potential winner will be selected from among all eligible entries received based on the Competition’s judging criteria.\n \nIn case (i) and (ii) above Kaggle may disqualify the participant.  However, in case (ii) above, if requested by Kaggle, such potential winner may provide code and documentation to verify the participant’s compliance with these Rules. If the potential winner provides code and documentation to the satisfaction of Kaggle, the participant will not be disqualified pursuant to this paragraph.\n \nCompetition Sponsor reserves the right to disqualify any participant from the Competition if the Competition Sponsor reasonably believes that the participant has attempted to undermine the legitimate operation of the Competition by cheating, deception, or other unfair playing practices or abuses, threatens or harasses any other participants, Competition Sponsor or Kaggle.\n \nA disqualified participant may be removed from the Competition leaderboard, at Kaggle's sole discretion. If a Participant is removed from the Competition Leaderboard, additional winning features associated with the Kaggle competition platform, for example Kaggle points or medals, may also not be awarded.\n \nThe final leaderboard list will be publicly displayed at Kaggle.com. Determinations of Competition Sponsor are final and binding.\n\n#### **11.\tWINNERS OBLIGATIONS.**\n\nAs a condition to being awarded a Prize, a Prize winner must fulfill the following obligations:\n\n(a) deliver to the Competition Sponsor the final model's software code as used to generate the winning Submission and associated documentation. The delivered software code should follow [these documentation guidelines][5], must be capable of generating the winning Submission, and contain a description of resources required to build and/or run the executable code successfully. If the final model’s software code includes generally commercially available software that is not owned by you, but that can be procured by the Competition Sponsor without undue expense, then instead of delivering the code for that software to the Competition Sponsor, you must identify that software, method for procuring it, and any parameters or other information necessary to replicate the winning Submission;\n\n(b) grant to the Competition Sponsor the license to the winning Submission stated in the Competition Specific Rules above, and represent that you have the unrestricted right to grant that license; \n\n(c) sign and return all Prize acceptance documents as may be required by Competition Sponsor or Kaggle, including without limitation: (i) eligibility certifications; (ii) licenses, releases and other agreements required under the Rules; and (iii) U.S. tax forms (such as IRS Form W-9 if U.S. resident, IRS Form W-8BEN if foreign resident, or future equivalents).\n\n#### **12.\tPRIZES.** \n\nPrize(s) are as described on the Competition Website and are only available for winning during the time period described on the Competition Website. The odds of winning any Prize depends on the number of eligible Submissions received during the Competition Period and the skill of the participants. \n\nAll Prizes are subject to Competition Sponsor's review and verification of the participant’s eligibility and compliance with these Rules, and the compliance of the winning Submissions with the Submissions Requirements. In the event that the Submission demonstrates non-compliance with these Competition Rules, Competition Sponsor may at its discretion take either of the following actions: (i) disqualify the Submission(s); or (ii) require the potential winner to remediate within one week after notice all issues identified in the Submission(s) (including, without limitation, the resolution of license conflicts, the fulfillment of all obligations required by software licenses, and the removal of any software that violates the software restrictions).\n\nA potential winner may decline to be nominated as a Competition winner in accordance with Section 10.\n\nPotential winners must return all required Prize acceptance documents within two (2) weeks following notification of such required documents, or such potential winner will be deemed to have forfeited the prize and another potential winner will be selected. Prize(s) will be awarded within approximately 30 days after receipt by Competition Sponsor or Kaggle of the required Prize acceptance documents. Transfer or assignment of a Prize is not allowed. \n\nYou are not eligible to receive any Prize if you do not meet the Eligibility requirements in Section 2 above.\n\nIf a Team wins a monetary Prize, the Prize money will be allocated in even shares between the eligible Team members, unless the Team unanimously opts for a different Prize split and notifies Kaggle before Prizes are issued.\n\n#### **13.\tTAXES.** \n\nALL TAXES IMPOSED ON PRIZES ARE THE SOLE RESPONSIBILITY OF THE WINNERS. Payments to potential winners are subject to the express requirement that they submit all documentation requested by Competition Sponsor or Kaggle for compliance with applicable state, federal, local and foreign (including provincial) tax reporting and withholding requirements. Prizes will be net of any taxes that Competition Sponsor is required by law to withhold. If a potential winner fails to provide any required documentation or comply with applicable laws, the Prize may be forfeited and Competition Sponsor may select an alternative potential winner. Any winners who are U.S. residents will receive an IRS Form-1099 in the amount of their Prize.\n\n#### **14.\tGENERAL CONDITIONS.**  \n\nAll federal, state, provincial and local laws and regulations apply.   \n\n#### **15.\tPUBLICITY.**\n\nYou agree that Competition Sponsor, Kaggle and its affiliates may use your name and likeness for advertising and promotional purposes without additional compensation, unless prohibited by law.\n\n#### **16.\tPRIVACY.**\n\nYou acknowledge and agree that Competition Sponsor and Kaggle may collect, store, share and otherwise use personally identifiable information provided by you during the Kaggle account registration process and the Competition, including but not limited to, name, mailing address, phone number, and email address (“Personal Information”). Kaggle acts as an independent controller with regard to its collection, storage, sharing, and other use of this Personal Information, and will use this Personal Information in accordance with its Privacy Policy <[www.kaggle.com/privacy][6]>, including for administering the Competition. As a Kaggle.com account holder, you have the right to request access to, review, rectification, portability or deletion of any personal data held by Kaggle about you by logging into your account and/or contacting Kaggle Support at <[www.kaggle.com/contact][7]>.\n\n As part of Competition Sponsor performing this contract between you and the Competition Sponsor, Kaggle will transfer your Personal Information to Competition Sponsor, which acts as an independent controller with regard to this Personal Information. As a controller of such Personal Information, Competition Sponsor agrees to comply with all U.S. and foreign data protection obligations with regard to your Personal Information. Kaggle will transfer your Personal Information to Competition Sponsor in the country specified in the Competition Sponsor Address listed above, which may be a country outside the country of your residence. Such country may not have privacy laws and regulations similar to those of the country of your residence.\n\n#### **17.\tWARRANTY, INDEMNITY AND RELEASE.** \n\nYou warrant that your Submission is your own original work and, as such, you are the sole and exclusive owner and rights holder of the Submission, and you have the right to make the Submission and grant all required licenses.  You agree not to make any Submission that: (i) infringes any third party proprietary rights, intellectual property rights, industrial property rights, personal or moral rights or any other rights, including without limitation, copyright, trademark, patent, trade secret, privacy, publicity or confidentiality obligations, or defames any person; or (ii) otherwise violates any applicable U.S. or foreign state or federal law.\n\nTo the maximum extent permitted by law, you indemnify and agree to keep indemnified Competition Entities at all times from and against any liability, claims, demands, losses, damages, costs and expenses resulting from any of your acts, defaults or omissions and/or a breach of any warranty set forth herein. To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless the Competition Entities from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from: (a) your Submission or other material uploaded or otherwise provided by you that infringes any third party proprietary rights, intellectual property rights, industrial property rights, personal or moral rights or any other rights, including without limitation, copyright, trademark, patent, trade secret, privacy, publicity or confidentiality obligations, or defames any person; (b) any misrepresentation made by you in connection with the Competition; (c) any non-compliance by you with these Rules or any applicable U.S. or foreign state or federal law; (d) claims brought by persons or entities other than the parties to these Rules arising from or related to your involvement with the Competition; and (e) your acceptance, possession, misuse or use of any Prize, or your participation in the Competition and any Competition-related activity.\n\nYou hereby release Competition Entities from any liability associated with: (a) any malfunction or other problem with the Competition Website; (b) any error in the collection, processing, or retention of any Submission; or (c) any typographical or other error in the printing, offering or announcement of any Prize or winners.\n\n#### **18.\tINTERNET.** \n\nCompetition Entities are not responsible for any malfunction of the Competition Website or any late, lost, damaged, misdirected, incomplete, illegible, undeliverable, or destroyed Submissions or entry materials due to system errors, failed, incomplete or garbled computer or other telecommunication transmission malfunctions, hardware or software failures of any kind, lost or unavailable network connections, typographical or system/human errors and failures, technical malfunction(s) of any telephone network or lines, cable connections, satellite transmissions, servers or providers, or computer equipment, traffic congestion on the Internet or at the Competition Website, or any combination thereof, which may limit a participant’s ability to participate.\n\n#### **19.\tRIGHT TO CANCEL, MODIFY OR DISQUALIFY.**\n\nIf for any reason the Competition is not capable of running as planned, including infection by computer virus, bugs, tampering, unauthorized intervention, fraud, technical failures, or any other causes which corrupt or affect the administration, security, fairness, integrity, or proper conduct of the Competition, Competition Sponsor reserves the right to cancel, terminate, modify or suspend the Competition. Competition Sponsor further reserves the right to disqualify any participant who tampers with the submission process or any other part of the Competition or Competition Website.  Any attempt by a participant to deliberately damage any website, including the Competition Website, or undermine the legitimate operation of the Competition is a violation of criminal and civil laws. Should such an attempt be made, Competition Sponsor and Kaggle each reserves the right to seek damages from any such participant to the fullest extent of the applicable law.\n\n#### **20.\tNOT AN OFFER OR CONTRACT OF EMPLOYMENT.**\n\nUnder no circumstances will the entry of a Submission, the awarding of a Prize, or anything in these Rules be construed as an offer or contract of employment with Competition Sponsor or any of the Competition Entities. You acknowledge that you have submitted your Submission voluntarily and not in confidence or in trust. You acknowledge that no confidential, fiduciary, agency, employment or other similar relationship is created between you and Competition Sponsor or any of the Competition Entities by your acceptance of these Rules or your entry of your Submission.\n\n#### **21.\tGOVERNING LAW.** \n\nUnless otherwise provided in the Competition Specific Rules above, all claims arising out of or relating to these Rules will be governed by California law, excluding its conflict of laws rules, and will be litigated exclusively in the Federal or State courts of Santa Clara County, California, USA. The parties consent to personal jurisdiction in those courts. If any provision of these Rules is held to be invalid or unenforceable, all remaining provisions of the Rules will remain in full force and effect.\n\n\n  [1]: https://www.treasury.gov/resource-center/sanctions/Programs/Pages/Programs.aspx\n  [2]: http://www.kaggle.com/terms\n  [3]: http://www.opensource.org\n  [4]: http://www.opensource.org\n  [5]: https://www.kaggle.com/WinningModelDocumentationGuidelines\n  [6]: http://www.kaggle.com/privacy\n  [7]: http://www.kaggle.com/contact",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "# Data Description:\n\n<p>Each season there are thousands of NCAA basketball games played between Division I men's teams, culminating in March Madness&reg;, the 68-team national championship that starts in the middle of March.  We have provided a large amount of historical data about college basketball games and teams, going back many years.  Armed with this historical data, you can explore it and develop your own distinctive ways of predicting March Madness&reg; game outcomes.  You can even evaluate and compare different approaches by seeing which of them would have done best at predicting tournament games from the past.</p>\n<p>If you are unfamiliar with the format and intricacies of the NCAA&reg; tournament, we encourage reading the <a href=\"http://en.wikipedia.org/wiki/NCAA_Men%27s_Division_I_Basketball_Championship\">wikipedia page</a> before diving into the data.  The data description and schema may seem daunting at first, but is not as complicated as it appears.</p>\n<p>As a reminder, you are encouraged to incorporate your own sources of data. We have provided extensive historical data to jump-start the modeling process, and this data is self-consistent (for instance, dates and team ID's are always treated the same way).  Nevertheless, you may also be able to make productive use of external data.  If you head down this path, please be forewarned that many sources have their own distinctive way of identifying the names of teams, and this can make it challenging to link up with our data.  The MTeamSpellings file, which is listed in the bottom section below, may help you map external team references into our own Team ID structure.  You will probably also need to understand exactly how dates work in our data.  Remember as well that you are required to disclose your external sources of data prior to the start of the tournament</p>\n<p>Please also note that we have standardized the spelling of column names and filenames, so if you are re-using code from previous instances of this contest, you may need to adjust for this.  All of the files that are specific to the men’s contest now have a filename prefix of M, so for instance this year the teams file is named MTeams rather than just Teams.</p>\n<p>We extend our gratitude to <a href=\"http://www.masseyratings.com/\">Kenneth Massey</a> for providing much of the historical data.</p>\n<p>Special Acknowledgment to <strong>Jeff Sonas</strong> of Sonas Consulting for his support in assembling the dataset for this competition.</p>\n<h2>What to predict</h2>\n<p><strong>Stage 1</strong> - You should submit predicted probabilities for every possible matchup in the past 5 NCAA&reg; tournaments (seasons 2015-2019).</p>\n<p><strong>Stage 2</strong> - You should submit predicted probabilities for every possible matchup before the 2020 tournament begins.</p>\n<p>Refer to the Timeline page for specific dates. In both stages, the sample submission will tell you which games to predict.</p>\n<h2>File descriptions</h2>\n<p>Below we describe the format and fields of the contest data files. The data will likely be refreshed once in early March while Stage 1 of the competition is running.  Many of the files are only complete through the end of last season.  At the start of Stage 2, we will provide updates to these files to incorporate data from the current season. Right now the MSeasons and MTeamConferences files are the only two files that reference the 2020 season, since those are the only files where the final 2020 data is already finalized; the other files will be updated later on when we provide preliminary data (in early March) and final Stage 2 data (after Selection Sunday) for the current season.</p>\n<hr>\n<h2>Data Section 1 - The Basics</h2>\n<p><strong>This section provides everything you need to build a simple prediction model and submit predictions.</strong></p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">Team ID's and Team Names</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">Tournament seeds since 1984-85 season</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">Final scores of all regular season, conference tournament, and NCAA&reg; tournament games since 1984-85 season</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">Season-level details including dates and region names</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">Example submission file for stage 1</span></li>\n</ul>\n<p><strong>Special note about \"Season\" numbers:</strong> the college basketball season lasts from early November until the national championship tournament that starts in the middle of March.  For instance, this year the first men’s Division I games were played on November 5th, 2019 and the men’s national championship game will be played on April 6th, 2020.  Because a basketball season spans two calendar years like this, it can be confusing to refer to the year of the season.  By convention, when we identify a particular season, we will reference the year that the season ends in, not the year that it starts in.  So for instance, the current season will be identified in our data as the 2020 season, not the 2019 season or the 2019-20 season or the 2019-2020 season, though you may see any of these in everyday use outside of our data.</p>\n<hr>\n<p><strong>Data Section 1 file: MTeams.csv</strong></p>\n<p>This file identifies the different college teams present in the dataset.  Each school is uniquely identified by a 4 digit id number.  You will not see games present for all teams in all seasons, because the games listing is only for matchups where both teams are Division-I teams.  There are 353 teams currently in Division-I, and an overall total of 367 teams in our team listing.  Each year, some teams might start being Division-I programs, and others might stop being Division-I programs, and in fact this year is no exception.  Savannah State (TeamID=1366) is no longer part of Division I and so their data in our dataset stops after the 2019 season, and they are no longer part of the Mid-Eastern Athletic Conference.  To balance this out, Merrimack (TeamID=1467) has just moved to Division I this year, so they show up as a new team in the data and they are now part of the America East Conference.  Other than the teams file and team conferences file, you won't see any data for Merrimack until preliminary 2020 season data starts coming in, as we approach Stage 2 of the contest.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - a 4 digit id number, from 1000-1999, uniquely identifying each NCAA&reg; men's team.  A school's TeamID does not change from one year to the next, so for instance the Duke men's TeamID is 1181 for all seasons.  To avoid possible confusion between the men's data and the women's data, all of the men's team ID's range from 1000-1999, whereas all of the women's team ID's range from 3000-3999.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamName</strong> - a compact spelling of the team's college name, 16 characters or fewer.  There are no commas or double-quotes in the team names, but you will see some characters that are not letters or spaces, e.g., Texas A&M, St Mary's CA, TAM C. Christi, and Bethune-Cookman.  Also note that several teams have had their team names changed slightly since last year: \"Albany NY\" is now \"SUNY Albany\", \"Santa Barbara\" is now \"UC Santa Barbara\", \"VA Commonwealth\" is now \"VCU\", \"Edwardsville\" is now \"SIUE\", \"Cal Poly SLO\" is now \"Cal Poly\", \"IPFW\" is now \"PFW\", \"Long Island\" is now \"LIU Brooklyn\", and \"ULL\" is now \"Louisiana\".</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>FirstD1Season</strong> - the first season in our dataset that the school was a Division-I school.  For instance, FL Gulf Coast (famously) was not a Division-I school until the 2008 season, despite their two wins just five years later in the 2013 NCAA&reg; tourney.  Of course, many schools were Division-I far earlier than 1985, but since we don't have any data included prior to 1985, all such teams are listed with a FirstD1Season of 1985.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>LastD1Season</strong> - the last season in our dataset that the school was a Division-I school.  For any teams that are currently Division-I, they will be listed with LastD1Season=2020, and you can confirm there are 353 such teams.  Since Savannah St is no longer a Division-I school, you can see that their last Division 1 season was 2019 rather than 2020.</span></li>\n</ul>\n<hr>\n<p><strong>Data Section 1 file: MSeasons.csv</strong></p>\n<p>This file identifies the different seasons included in the historical data, along with certain season-level properties.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - indicates the year in which the tournament was played.  Remember that the current season counts as 2020.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>DayZero</strong> - tells you the date corresponding to DayNum=0 during that season. All game dates have been aligned upon a common scale so that (each year) the Monday championship game of the men's tournament is on DayNum=154. Working backward, the national semifinals are always on DayNum=152, the \"play-in\" games are on days 134/135, Selection Sunday is on day 132, the final day of the regular season is also day 132, and so on. All game data includes the day number in order to make it easier to perform date calculations. If you need to know the exact date a game was played on, you can combine the game's \"DayNum\" with the season's \"DayZero\". For instance, since day zero during the 2011-2012 season was 10/31/2011, if we know that the earliest regular season games that year were played on DayNum=7, they were therefore played on 11/07/2011.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>RegionW, RegionX, Region Y, Region Z</strong> - by our contests' convention, each of the four regions in the final tournament is assigned a letter of W, X, Y, or Z. Whichever region's name comes first alphabetically, that region will be Region W. And whichever Region plays against Region W in the national semifinals, that will be Region X. For the other two regions, whichever region's name comes first alphabetically, that region will be Region Y, and the other will be Region Z. This allows us to identify the regions and brackets in a standardized way in other files, even if the region names change from year to year. For instance, during the 2012 tournament, the four regions were East, Midwest, South, and West. Being the first alphabetically, East becomes W. Since the East regional champion (Ohio State) played against the Midwest regional champion (Kansas) in the national semifinals, that makes Midwest be region X. For the other two (South and West), since South comes first alphabetically, that makes South Y and therefore West is Z. So for that season, the W/X/Y/Z are East,Midwest,South,West.  And so for instance, Ohio State, the #2 seed in the East, is listed in the MNCAATourneySeeds file that year with a seed of W02, meaning they were the #2 seed in the W region (the East region).  We will not know the final W/X/Y/Z designations until Selection Sunday, because the national semifinal pairings in the Final Four will depend upon the overall ranks of the four #1 seeds.</span></li>\n</ul>\n<hr>\n<p><strong>Data Section 1 file: MNCAATourneySeeds.csv</strong></p>\n<p>This file identifies the seeds for all teams in each NCAA&reg; tournament, for all seasons of historical data. Thus, there are between 64-68 rows for each year, depending on whether there were any play-in games and how many there were.  In recent years the structure has settled at 68 total teams, with four \"play-in\" games leading to the final field of 64 teams entering Round 1 on Thursday of the first week (by definition, that is DayNum=136 each season).  We will not know the seeds of the respective tournament teams, or even exactly which 68 teams it will be, until Selection Sunday on March 15, 2020 (DayNum=132).</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - the year that the tournament was played in</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Seed</strong> - this is a 3/4-character identifier of the seed, where the first character is either W, X, Y, or Z (identifying the region the team was in) and the next two digits (either 01, 02, ..., 15, or 16) tell you the seed within the region. For play-in teams, there is a fourth character (a or b) to further distinguish the seeds, since teams that face each other in the play-in games will have seeds with the same first three characters.  The \"a\" and \"b\" are assigned based on which Team ID is lower numerically.  As an example of the format of the seed, the first record in the file is seed W01 from 1985, which means we are looking at the #1 seed in the W region (which we can see from the \"MSeasons.csv\" file was the East region).</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this identifies the id number of the team, as specified in the MTeams.csv file</span></li>\n</ul>\n<hr>\n<p><strong>Data Section 1 file: MRegularSeasonCompactResults.csv</strong></p>\n<p>This file identifies the game-by-game results for many seasons of historical data, starting with the 1985 season (the first year the NCAA&reg; had a 64-team tournament). For each season, the file includes all games played from DayNum 0 through 132.  It is important to realize that the \"Regular Season\" games are simply defined to be all games played on DayNum=132 or earlier (DayNum=132 is Selection Sunday, and there are always a few conference tournament finals actually played early in the day on Selection Sunday itself).  Thus a game played on or before Selection Sunday will show up here whether it was a pre-season tournament, a non-conference game, a regular conference game, a conference tournament game, or whatever.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - this is the year of the associated entry in MSeasons.csv (the year in which the final tournament occurs).  For example, during the 2016 season, there were regular season games played between November 2015 and March 2016, and all of those games will show up with a Season of 2016.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>DayNum</strong> - this integer always ranges from 0 to 132, and tells you what day the game was played on. It represents an offset from the \"DayZero\" date in the \"MSeasons.csv\" file. For example, the first game in the file was DayNum=20. Combined with the fact from the \"MSeasons.csv\" file that day zero was 10/29/1984 that year, this means the first game was played 20 days later, or 11/18/1984. There are no teams that ever played more than one game on a given date, so you can use this fact if you need a unique key (combining Season and DayNum and WTeamID). In order to accomplish this uniqueness, we had to adjust one game's date. In March 2008, the SEC postseason tournament had to reschedule one game (Georgia-Kentucky) to a subsequent day because of a tornado, so Georgia had to actually play two games on the same day. In order to enforce this uniqueness, we moved the game date for the Georgia-Kentucky game back to its original scheduled date.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WTeamID</strong> - this identifies the id number of the team that won the game, as listed in the \"MTeams.csv\" file. No matter whether the game was won by the home team or visiting team, or if it was a neutral-site game, the \"WTeamID\" always identifies the winning team.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WScore</strong> - this identifies the number of points scored by the winning team.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>LTeamID</strong> - this identifies the id number of the team that lost the game.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>LScore</strong> - this identifies the number of points scored by the losing team.  Thus you can be confident that WScore will be greater than LScore for all games listed.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WLoc</strong> - this identifies the \"location\" of the winning team. If the winning team was the home team, this value will be \"H\". If the winning team was the visiting team, this value will be \"A\". If it was played on a neutral court, then this value will be \"N\". Sometimes it is unclear whether the site should be considered neutral, since it is near one team's home court, or even on their court during a tournament, but for this determination we have simply used the Kenneth Massey data in its current state, where the \"@\" sign is either listed with the winning team, the losing team, or neither team.  If you would like to investigate this factor more closely, we invite you to explore Data Section 3, which provides the city that each game was played in, irrespective of whether it was considered to be a neutral site.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>NumOT</strong> - this indicates the number of overtime periods in the game, an integer 0 or higher.</span></li>\n</ul>\n<hr>\n<p><strong>Data Section 1 file: MNCAATourneyCompactResults.csv</strong></p>\n<p>This file identifies the game-by-game NCAA&reg; tournament results for all seasons of historical data. The data is formatted exactly like the MRegularSeasonCompactResults data. All games will show up as neutral site (so WLoc is always N). Note that this tournament game data also includes the play-in games (which always occurred on day 134/135) for those years that had play-in games.  Thus each season you will see between 63 and 67 games listed, depending on how many play-in games there were.</p>\n<p>Because of the consistent structure of the NCAA&reg; tournament schedule, you can actually tell what round a game was, depending on the exact DayNum.  Thus:</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=134 or 135 (Tue/Wed) - play-in games to get the tournament field down to the final 64 teams</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=136 or 137 (Thu/Fri) - Round 1, to bring the tournament field from 64 teams to 32 teams </span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=138 or 139 (Sat/Sun) - Round 2, to bring the tournament field from 32 teams to 16 teams </span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=143 or 144 (Thu/Fri) - Round 3, otherwise known as \"Sweet Sixteen\", to bring the tournament field from 16 teams to 8 teams </span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=145 or 146 (Sat/Sun) - Round 4, otherwise known as \"Elite Eight\" or \"regional finals\", to bring the tournament field from 8 teams to 4 teams </span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=152 (Sat) - Round 5, otherwise known as \"Final Four\" or \"national semifinals\", to bring the tournament field from 4 teams to 2 teams </span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\">DayNum=154 (Mon) - Round 6, otherwise known as \"national final\" or \"national championship\", to bring the tournament field from 2 teams to 1 champion team </span></li>\n</ul>\n<p><strong>Special note:</strong> Each year, there are also going to be other games that happened after Selection Sunday, which are not part of the NCAA&reg; Tournament.  This includes tournaments like the postseason NIT, the CBI, the CIT, and the Vegas 16.  Such games are not listed in the Regular Season or the NCAA&reg; Tourney files; they can be found in the \"Secondary Tourney\" data files within Data Section 6.  Although they would not be games you would ever be predicting directly for the NCAA&reg; tournament, and they would not be games you would have data from at the time of predicting NCAA&reg; tournament outcomes, you may nevertheless wish to make use of these games for model optimization, depending on your methodology.  The more games that you can test your predictions against, the better your optimized model might eventually become, depending on how applicable all those games are.  A similar argument might be advanced in favor of optimizing your predictions against conference tournament games, which might be viewed as reasonable proxies for NCAA&reg; tournament games.</p>\n</ul>\n<hr>\n<p><strong>Data Section 1 file: MSampleSubmissionStage1.csv</strong></p>\n<p>This file illustrates the submission file format for Stage 1.  It is the simplest possible submission: a 50% winning percentage is predicted for each possible matchup.</p>\n<p>A submission file lists every possible matchup between tournament teams for one or more years.  During Stage 1, you are asked to make predictions for all possible matchups from the past five NCAA&reg; tournaments (seasons 2015, 2016, 2017, 2018, 2019).  In Stage 2, you will be asked to make predictions for all possible matchups from the current NCAA&reg; tournament (season 2020).</p>\n<p>When there are 68 teams in the tournament, there are 68*67/2=2,278 predictions to make for that year, so a Stage 1 submission file will have 2,278*5=11,390 data rows.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>ID</strong> - this is a 14-character string of the format SSSS_XXXX_YYYY, where SSSS is the four digit season number, XXXX is the four-digit TeamID of the lower-ID team, and YYYY is the four-digit TeamID of the higher-ID team.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Pred</strong> - this contains the predicted winning percentage for the first team identified in the ID field, the one represented above by XXXX.</span></li>\n</ul>\n<p>Example #1: You want to make a prediction for Duke (TeamID=1181) against Arizona (TeamID=1112) in the 2017 tournament, with Duke given a 53% chance to win and Arizona given a 47% chance to win.  In this case, Arizona has the lower numerical ID so they would be listed first, and the winning percentage would be expressed from Arizona's perspective (47%):</p>\n<p><strong>2017_1112_1181,0.47</strong></p>\n<p>Example #2: You want to make a prediction for Duke (TeamID=1181) against North Carolina (TeamID=1314) in the 2018 tournament, with Duke given a 51.6% chance to win and North Carolina given a 48.4% chance to win.  In this case, Duke has the lower numerical ID so they would be listed first, and the winning percentage would be expressed from Duke's perspective (51.6%):</p>\n<p><strong>2018_1181_1314,0.516</strong></p>\n<p>Also note that a single prediction row serves as a prediction for each of the two teams' winning chances.  So for instance, in Example #1, the submission row of \"2017_1112_1181,0.47\" specifically gives a 47% chance for Arizona to win, and doesn't explicitly mention Duke's 53% chance to win.  However, our evaluation utility will automatically infer the winning percentage in the other direction, so a 47% prediction for Arizona to win also means a 53% prediction for Duke to win. And similarly, because the submission row in Example #2 gives Duke a 51.6% chance to beat North Carolina, we will automatically figure out that this also means North Carolina has a 48.4% chance to beat Duke.</p>\n<hr>\n<h2>Data Section 2 - Team Box Scores</h2>\n<p><strong>This section provides game-by-game stats at a team level (free throws attempted, defensive rebounds, turnovers, etc.) for all regular season, conference tournament, and NCAA&reg; tournament games since the 2002-03 season.</strong></p>\n<p>Team Box Scores are provided in \"Detailed Results\" files rather than \"Compact Results\" files.  However, the two files are strongly related.  \n<p>In a Detailed Results file, the first eight columns (<strong>Season, DayNum, WTeamID, WScore, LTeamID, LScore, WLoc, and NumOT</strong>) are exactly the same as a Compact Results file.  However, in a Detailed Results file, there are many additional columns.  The column names should be self-explanatory to basketball fans (as above, \"W\" or \"L\" refers to the winning or losing team):</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFGM</strong> - field goals made (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFGA</strong> - field goals attempted (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFGM3</strong> - three pointers made (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFGA3</strong> - three pointers attempted (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFTM</strong> - free throws made (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFTA</strong> - free throws attempted (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WOR</strong> - offensive rebounds (pulled by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WDR</strong> - defensive rebounds (pulled by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WAst</strong> - assists (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WTO</strong> - turnovers committed (by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WStl</strong> - steals (accomplished by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WBlk</strong> - blocks (accomplished by the winning team)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WPF</strong> - personal fouls committed (by the winning team)</span></li>\n</ul>\n<p>(and then the same set of stats from the perspective of the losing team: <strong>LFGM</strong> is the number of field goals made by the losing team, and so on up to <strong>LPF</strong>).</p>\n<p><strong>Note: </strong>by convention, \"field goals made\" (either WFGM or LFGM) refers to the total number of fields goals made by a team, a combination of both two-point field goals and three-point field goals.  And \"three point field goals made\" (either WFGM3 or LFGM3) is just the three-point fields goals made, of course.  So if you want to know specifically about two-point field goals, you have to subtract one from the other (e.g., WFGM - WFGM3).  And the total number of points scored is most simply expressed as 2*FGM + FGM3 + FTM.</p>\n<hr>\n<p><strong>Data Section 2 file: MRegularSeasonDetailedResults.csv</strong></p>\n<p>This file provides team-level box scores for many regular seasons of historical data, starting with the 2003 season.  All games listed in the MRegularSeasonCompactResults file since the 2003 season should exactly be present in the MRegularSeasonDetailedResults file.</p>\n<hr>\n<p><strong>Data Section 2 file: MNCAATourneyDetailedResults.csv</strong></p>\n<p>This file provides team-level box scores for many NCAA&reg; tournaments, starting with the 2003 season.  All games listed in the MNCAATourneyCompactResults file since the 2003 season should exactly be present in the MNCAATourneyDetailedResults file.</p>\n<hr>\n<h2>Data Section 3 - Geography</h2>\n<p><strong>This section provides city locations of all regular season, conference tournament, and NCAA&reg; tournament games since the 2009-10 season</strong></p>\n<hr>\n<p><strong>Data Section 3 file: Cities.csv</strong></p>\n<p>This file provides a master list of cities that have been locations for games played. Please notice that the Cities and Conferences files are the only two that don't start with an M; this is because the data files are identical between men's and women's data, so you don't need to maintain separate listings of cities or conferences across the two contests.  Also note that if you created any supplemental data last year on cities (latitude/longitude, altitude, etc.), the CityID's match between last year and this year, so you should be able to re-use that information.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>CityID</strong> - a four-digit ID number uniquely identifying a city.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>City</strong> - the text name of the city.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>State</strong> - the state abbreviation of the state that the city is in.  In a few rare cases, the game location is not inside one of the 50 U.S. states and so other abbreviations are used.  For instance Cancun, Mexico has a state abbreviation of MX.</span></li>\n</ul>\n<hr>\n<p><strong>Data Section 3 file: MGameCities.csv</strong></p>\n<p>This file identifies all games, starting with the 2010 season, along with the city that the game was played in.  Games from the regular season, the NCAA&reg; tourney, and other post-season tournaments, are all listed together.  There should be no games since the 2010 season where the CityID is not known.  Games from the 2009 season and before are not listed in this file.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season, DayNum, WTeamID, LTeamID</strong> - these four columns are sufficient to uniquely identify each game.  Additional data, such as the score of the game and other stats, can be found in the corresponding Compact Results and/or Detailed Results file.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>CRType</strong> - this can be either <strong>Regular</strong> or <strong>NCAA</strong> or <strong>Secondary</strong>.  If it is <strong>Regular</strong>, you can find more about the game in the MRegularSeasonCompactResults.csv and MRegularSeasonDetailedResults.csv files.  If it is <strong>NCAA</strong>, you can find more about the game in the MNCAATourneyCompactResults.csv and MNCAATourneyDetailedResults.csv files.  If it is <strong>Secondary</strong>, you can find more about the game in the MSecondaryTourneyCompactResults file.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>CityID</strong> - the ID of the city where the game was played, as specified by the CityID column in the Cities.csv file.</span></li>\n</ul>\n<hr>\n<h2>Data Section 4 - Public Rankings</h2>\n<p><strong>This section provides weekly team rankings for dozens of top rating systems - Pomeroy, Sagarin, RPI, ESPN, etc., since the 2002-2003 season</strong></p>\n<hr>\n<p><strong>Data Section 4 file: MMasseyOrdinals.csv</strong></p>\n<p>This file lists out rankings (e.g. #1, #2, #3, ..., #N) of teams going back to the 2002-2003 season, under a large number of different ranking system methodologies.  The information was gathered by Kenneth Massey and provided on his <a href=\"https://www.masseyratings.com/cb/compare.htm\">College Basketball Ranking Composite page</a>.</p>\n<p>Note that a rating system is more precise than a ranking system, because a rating system can provide insight about the strength gap between two adjacently-ranked teams.  A ranking system will just tell you who is #1 or who is #2, but a rating system might tell you whether the gap between #1 and #2 is large or small.  Nevertheless, it can be hard to compare two different rating systems that are expressed in different scales, so it can be very useful to express all the systems in terms of their ordinal ranking (1, 2, 3, ..., N) of teams.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - this is the year of the associated entry in MSeasons.csv (the year in which the final tournament occurs)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>RankingDayNum</strong> - this integer always ranges from 0 to 133, and is expressed in the same terms as a game's DayNum (where DayZero is found in the MSeasons.csv file).  The RankingDayNum is intended to tell you the first day that it is appropriate to use the rankings for predicting games.  For example, if RankingDayNum is 110, then the rankings ought to be based upon game outcomes up through DayNum=109, and so you can use the rankings to make predictions of games on DayNum=110 or later.  The final pre-tournament rankings each year have a RankingDayNum of 133, and can thus be used to make predictions of the games from the NCAA&reg; tournament, which start on DayNum=134 (the Tuesday after Selection Sunday).</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>SystemName</strong> - this is the (usually) 3-letter abbreviation for each distinct ranking system.  These systems may evolve from year to year, but as a general rule they retain their meaning across the years.  Near the top of the Massey composite page, you can find slightly longer labels describing each system, along with links to the underlying pages where the latest rankings are provided (and sometimes the calculation is described).</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this is the ID of the team being ranked, as described in MTeams.csv.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>OrdinalRank</strong> - this is the overall ranking of the team in the underlying system.  Most systems from recent seasons provide a complete ranking from #1 through #351, but sometimes there are ties and sometimes only a smaller set of rankings is provided, as with the AP's top 25.  This year and last year they will typically go up to #353 because two new teams were added to Division I last year.</span></li>\n</ul>\n<p><strong>Disclaimer: </strong>you ought to be careful about your methodology when using or evaluating these ranking systems.  They are presented on a weekly basis, and given a consistent date on the Massey Composite page that typically is a Sunday; that is how the ranking systems can be compared against each other on this page.  However, these systems each follow their own timeline and some systems may be released on a Sunday and others on a Saturday or Monday or even Tuesday.  You should remember that if a ranking is released on a Tuesday, and was calculated based on games played through Monday, it will make the system look unusually good at predicting if you use that system to forecast the very games played on Monday that already inform the rankings.  To avoid this methodological trap, we have typically used a conservative RankingDayNum of Wednesday to represent the rankings that were released at approximately the end of the weekend, a few days before, even though those rankings are represented on the composite page as being on a Sunday.  For some of the older years, a more precise timestamp was known for each ranking system that allowed a more precise assignment of a RankingDayNum.  By convention, the final pre-tournament rankings are always expressed as RankingDayNum=133, even though sometimes the rankings for individual systems are not released until Tuesday (DayNum=134) or even Wednesday or Thursday.  If you decide to use some rankings from these Massey Ordinals to inform your predictions, be forewarned that we have no control over when they are released, and not all systems may turn out to be available in time to make pre-tournament predictions by our submission deadline.  In such a situation, you may wish to use the rankings from DayNum=128 or you may need to dig into the details of the actual source of the rankings, by following the respective links on the Massey Composite Page.  We may also be able to provide partial releases of the final pre-tournament Massey Ordinals on the forums, so that as systems come in on Monday or Tuesday you can use them right away.</p>\n<hr>\n<h2>Data Section 5 - Play-by-play</h2>\n<p><strong>This section provides play-by-play event logs for more than 99.5% of each year's regular season, NCAA&reg; tournament, and secondary tournament games since the 2014-15 season - including plays by individual players.</strong></p>\n<hr>\n<p>This year we are transitioning to a different play-by-play source, which includes data since the 2014-2015 season rather than since the 2009-2010 season (that's what we had previously for men's data).  However, we are now able to provide play-by-play for both men's and women's data, and there is locational play-by-play detail starting with games from the 2018-2019 season.  This includes an X/Y location (ranging from 0 to 100 in each dimension) on the court for each shot attempt, turnover, and foul for many games, as well as an overall categorization of the area on the court that the shot or turnover or foul occurred in (inside left wing, outside right wing, under the basket, etc.)  Some games in these recent seasons still lack the locational detail.  The data from last year (2019 season) matches what you can expect for the current year (2020 season) as we approach the postseason.  Despite the 99.5% coverage, there are still a few games missing annually, and we will try to bring those in as well, if possible.</p>\n<hr>\n<p><strong>Data Section 5 file: MEvents2015.csv, MEvents2016.csv, MEvent2017.csv, MEvents2018.csv, MEvents2019.csv</strong></p>\n<p>Each MEvents file lists the play-by-play event logs for more than 99.5% of games from that season.  Each event is assigned to either a team or a single one of the team's players.  Thus if a basket is made by one player and an assist is credited to a second player, that would show up as two separate records.  The players are listed by PlayerID within the MPlayers.csv file.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>EventID</strong> - this is a unique ID for each logged event.  The EventID's are different within each year and uniquely identify each play-by-play event.  They ought to be listed in chronological order for the events within their game.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season, DayNum, WTeamID, LTeamID</strong> - these four columns are sufficient to uniquely identify each game.  The games are a mix of Regular Season, NCAA&reg; Tourney, and Secondary Tourney games.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WFinalScore, LFinalScore</strong> - these two columns match the WScore and LScore numbers as found elsewhere in the Compact Results and Detailed Results files.  They are provided here to indicate the final score at the end of the game.  Note that the event-by-event totals are not guaranteed to add up to the final scores, due to possible data recording errors in the play-by-play.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WCurrentScore, LCurrentScore</strong> - whenever a scoring play happens (1 point, 2 points, or 3 points) the updated score is provided, from the perspective of the winning team (WPoints) and the losing team (LPoints), although of course during the game we didn't know yet that they were the winning team or losing team.  Note that in the earlier years of the play-by-play data from this source, the running WCurrentScore and LCurrentScore were not calculated, and so they show up as zero throughout the event log for those years.  However, they can still be calculated manually when looping through the game events that are present, by watching for rows like \"made1\", \"made2\", and \"made3\" that represent scoring events.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>ElapsedSeconds</strong> - this is the number of seconds that have elapsed from the start of the game until the event occurred.  With a 20-minute half, that means that an ElapsedSeconds value from 0 to 1200 represents an event in the first half, a value from 1200 to 2400 represents an event in the second half, and a value above 2400 represents an event in overtime.  For example, since overtime periods are five minutes long (that's 300 seconds), a value of 2699 would represent one second left in the first overtime.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>EventTeamID</strong> - this is the ID of the team that the event is logged for, which will either be the WTeamID or the LTeamID.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>EventPlayerID</strong> - this is the ID of the player that the event is logged for, as described in the MPlayers.csv file.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>EventType, EventSubType</strong> - these indicate the type of the event that was logged (see listing below).</span></li>\n</ul>\n<p>Event Types and Subtypes:</p>\n<ul>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>assist</strong> - an assist was credited on a made shot</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>block</strong> - a blocked shot was recorded</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>steal</strong> - a steal was recorded</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>sub</strong> - a substitution occurred, with one of the following subtypes:\n      in=player entered the game; \n      out=player exited the game; \n      start=player started the game</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>timeout</strong> - a timeout was called, with one of the following subtypes:\n      unk=unknown type of timeout; \n      comm=commercial timeout; \n      full=full timeout; \n      short= short timeout</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>turnover</strong> - a turnover was recorded, with one of the following subtypes:\n      unk=unknown type of turnover; \n      10sec=10 second violation; \n      3sec=3 second violation; \n      5sec=5 second violation; \n      bpass=bad pass turnover; \n      dribb=dribbling turnover; \n      lanev=lane violation; \n      lostb=lost ball; \n      offen=offensive turnover (?); \n      offgt=offensive goaltending; \n      other=other type of turnover; \n      shotc=shot clock violation; \n      trav=travelling</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>foul</strong> - a foul was committed, with one of the following subtypes:\n      unk=unknown type of foul; \n      admT=administrative technical; \n      benT=bench technical; \n      coaT=coach technical; \n      off=offensive foul; \n      pers=personal foul; \n      tech=technical foul</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>fouled</strong> - a player was fouled</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>reb</strong> - a rebound was recorded, with one of the following subtypes:\n      deadb=a deadball rebound; \n      def=a defensive rebound; \n      defdb=a defensive deadball rebound; \n      off=an offensive rebound; \n      offdb=an offensive deadball rebound</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>made1, miss1</strong> - a one-point free throw was made or missed, with one of the following subtypes:\n      1of1=the only free throw of the trip to the line; \n      1of2=the first of two free throw attempts; \n      2of2=the second of two free throw attempts; \n      1of3=the first of three free throw attempts; \n      2of3=the second of three free throw attempts; \n      3of3=the third of three free throw attempts; \n      unk=unknown what the free throw sequence is</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>made2, miss2</strong> - a two-point field goal was made or missed, with one of the following subtypes:\n      unk=unknown type of two-point shot; \n      dunk=dunk; \n      lay=layup; \n      tip=tip-in; \n      jump=jump shot; \n      alley=alley-oop; \n      drive=driving layup; \n      hook=hook shot; \n      stepb=step-back jump shot; \n      pullu=pull-up jump shot; \n      turna=turn-around jump shot; \n      wrong=wrong basket</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>made3, miss3</strong> - a three-point field goal was made or missed, with one of the following subtypes:\n      unk=unknown type of three-point shot; \n      jump=jump shot; \n      stepb=step-back jump shot; \n      pullu=pull-up jump shot; \n      turna=turn-around jump shot; \n      wrong=wrong basket</span></li>\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>jumpb</strong> - a jumpball was called or resolved, with one of the following subtypes:\n      start=start period; \n      block=block tie-up; \n      heldb=held ball; \n      lodge=lodged ball; \n      lost=jump ball lost; \n      outof=out of bounds; \n      outrb=out of bounds rebound; \n      won=jump ball won</span></li>\n</ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>X, Y</strong> - for games where it is available, this describes an X/Y position on the court where the lower-left corner of the full court is (0,0), the upper-right corner of the full court is (100,100), the exact middle of the full court (where the initial jump ball happens) is (50,50), and so on.  The X/Y position is provided for fouls, turnovers, and field-goal attempts (either 2-point or 3-point).</span></li>\n\n<p>This is the diagram provided by the play-by-play source:</p>\n<img src=\"https://developer.geniussports.com/warehouse/rest/basketball_coords.png\">\n\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Area</strong> - for events where an X/Y position is provided, this position is more generally categorized into one of 13 \"areas\" of the court, as follows: \n1=under basket; \n2=in the paint; \n3=inside right wing; \n4=inside right; \n5=inside center; \n6=inside left; \n7=inside left wing; \n8=outside right wing; \n9=outside right; \n10=outside center; \n11=outside left; \n12=outside left wing; \n13=backcourt</span></li>\n<hr>\n<p>Here is a diagram of these regions on a typical court:</p>\n<img src=\"https://developer.geniussports.com/warehouse/rest/basketball_courtmap.png\">\n\n<p>And you may also have noticed that the three-point-arc is different this year in college basketball.  The width of the court is still 15.2 m (50 ft) and the length of the court is still 28.7 m (94 feet), but the distance to the arc has changed from 6.32 m (20 feet 9 inches) to 6.75 m (22.15 feet).</p>\n\n<p>Here is a diagram of the old court, which would apply for play-by-play in seasons 2019 and before:</p>\n<img src=\"https://developer.geniussports.com/warehouse/rest/basketball_court-2_(NCAAOld).svg\">\n\n<p>And here is a diagram of the new court, which only applies for season 2020:</p>\n<img src=\"https://developer.geniussports.com/warehouse/rest/basketball_court-3_(NCAANew).svg\">\n\n<hr>\n<p><strong>Data Section 5 file: MPlayers.csv</strong></p>\n\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>PlayerID</strong> - this is a unique ID for each distinct player name/team combination.  If the same player name spelling appears on a team for multiple seasons, it should stay as one player record rather than a separate one for each year.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>LastName, FirstName</strong> - these are the player's last and first names.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this is the TeamID of the player's team, as described in MTeams.csv.</span></li>\n</ul>\n<p>Note: there are data collection errors within the events, in that they don't necessarily add up to the final stats for the game.  In addition, the player name spellings may vary over the course of a season or career for the same player, which would lead to the same player showing up with different PlayerID values.  Nevertheless, this was the highest quality data we could manage for play-by-play with the near-complete set of games.</p>\n<hr>\n<h2>Data Section 6 - Supplements</h2>\n<p><strong>This section contains additional supporting information, including coaches, conference affiliations, alternative team name spellings, bracket structure, and game results for NIT and other postseason tournaments.</strong></p>\n<hr>\n<p><strong>Data Section 6 file: MTeamCoaches.csv</strong></p>\n<p>This file indicates the head coach for each team in each season, including a start/finish range of DayNum's to indicate a mid-season coaching change.  For scenarios where a team had the same head coach the entire season, they will be listed with a DayNum range of 0 to 154 for that season.  For head coaches whose term lasted many seasons, there will be many rows listed, most of which have a DayNum range of 0 to 154 for the corresponding season.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - this is the year of the associated entry in MSeasons.csv (the calendar year in which the final tournament occurs)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this is the TeamID of the team that was coached, as described in MTeams.csv.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>FirstDayNum, LastDayNum</strong> - this defines a continuous range of days within the season, during which the indicated coach was the head coach of the team.  In most cases, a data row will either have FirstDayNum=0 (meaning they started the year as head coach) and/or LastDayNum=154 (meaning they ended the year as head coach), but in some cases there were multiple new coaches during a team's season, or a head coach who went on leave and then returned (in which case there would be multiple records in that season for that coach, indicating the continuous ranges of days when they were the head coach).</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>CoachName</strong> - this is a text representation of the coach's full name, in the format first_last, with underscores substituted in for spaces.</span></li>\n</ul>\n<hr>\n<p><strong>Data Section 6 file: Conferences.csv</strong></p>\n<p>This file indicates the Division I conferences that have existed over the years since 1985.  Each conference is listed with an abbreviation and a longer name.  There has been no attempt to link up conferences who merged with other conferences, or whose names changed over time.  Thus you will see, for instance, a \"Pacific-10\" conference up through the 2011 season, and then a \"Pacific-12\" conference starting in the 2012 season, and these look like different conferences in the data, even though it was still mostly the same teams. Please notice that the Cities and Conferences files are the only two that don't start with an M; this is because the data files are identical between men's and women's data, so you don't need to maintain separate listings of cities or conferences across the two contests. However, the Team Conferences data differs slightly between men's and women's, so those files do have the prefixes.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>ConfAbbrev</strong> - this is a short abbreviation for each conference; the abbreviation is used in some other files to indicate the parent conference of a team or of a conference tournament.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Description</strong> - this is a longer text name for the conference.</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MTeamConferences.csv</strong></p>\n<p>This file indicates the conference affiliations for each team during each season.  Some conferences have changed their names from year to year, and/or changed which teams are part of the conference.  This file tracks this information historically.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - this is the year of the associated entry in MSeasons.csv (the year in which the final tournament occurs)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this identifies the TeamID (as described in MTeams.csv).</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>ConfAbbrev</strong> - this identifies the conference (as described in Conferences.csv).</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MConferenceTourneyGames.csv</strong></p>\n<p>This file indicates which games were part of each year's post-season conference tournaments (all of which finished on Selection Sunday or earlier), starting from the 2001 season.  Many of these conference tournament games are held on neutral sites, and many of the games are played by tournament-caliber teams just a few days before the NCAA&reg; tournament.  Thus these games could be considered as very similar to NCAA&reg; tournament games, and (depending on your methodology) may be of use in optimizing your predictions.  However, this is NOT a new listing of games; these games are already present within the MRegularSeasonCompactResults and MRegularSeasonDetailedResults files.  So this file simply helps you to identify which of the \"regular season\" games since the 2001 season were actually conference tournament games, in case that is useful information.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>ConfAbbrev</strong> - this identifies the conference (as described in Conferences.csv) that the tournament was for.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season, DayNum, WTeamID, LTeamID</strong> - these four columns are sufficient to uniquely identify each game.  Further details about the game, such as the final score and other stats, can be found in the associated data row of the MRegularSeasonCompactResults and/or MRegularSeasonDetailedResults files.</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MSecondaryTourneyTeams.csv</strong></p>\n<p>This file identifies the teams that participated in post-season tournaments other than the NCAA&reg; Tournament (such events would run in parallel with the NCAA&reg; Tournament).  These are teams that were not invited to the NCAA&reg; Tournament and instead were invited to some other tournament, of which the NIT is the most prominent tournament, but there have also been the CBI, CIT, and Vegas 16 (V16) at various points in recent years.  Depending on your methodology, you might find it useful to have these additional game results, above and beyond what is available from the NCAA&reg; Tournament results.  Many of these teams, especially in the NIT, were \"bubble\" teams of comparable strength to several NCAA&reg; Tournament invitees, and so these games may be of use in model optimization for predicting NCAA&reg; Tournament results.  Also note that this information could be determined just from inspecting the MSecondaryTourneyCompactResults file, but is presented in this file as well, for your convenience.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - this is the year of the associated entry in MSeasons.csv (the year in which the post-season tournament was played)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>SecondaryTourney</strong> - this is the abbreviation of the tournament, either NIT, CBI, CIT, or V16 (which stands for Vegas 16).</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this identifies the TeamID that participated in the tournament (as described in MTeams.csv).</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MSecondaryTourneyCompactResults.csv</strong></p>\n<p>This file indicates the final scores for the tournament games of \"secondary\" post-season tournaments: the NIT, CBI, CIT, and Vegas 16.  The detailed results (team box scores) have not been assembled for these games.  For the most part, this file is exactly like other Compact Results listings, although it also has a column for Secondary Tourney. Also note that because these games are played after DayNum=132, they are NOT listed in the MRegularSeasonCompactResults file.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>SecondaryTourney</strong> - this is the abbreviation of the tournament, either NIT, CBI, CIT, or V16 (which stands for Vegas 16).</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MTeamSpellings.csv</strong></p>\n<p>This file indicates alternative spellings of many team names.  It is intended for use in associating external spellings against our own TeamID numbers, thereby helping to relate the external data properly with our datasets.  Over the years we have identified various external spellings of different team names (as an example, for Ball State we have seen \"ball st\", and \"ball st.\", and \"ball state\", and \"ball-st\", and \"ball-state\").  Other teams have had more significant changes to their names over the years; for example, \"Texas Pan-American\" and \"Texas-Rio Grande Valley\" are actually the same school.  The current list is obviously not exhaustive, and we encourage participants to identify additional mappings and upload extended versions of this file to the forums.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamNameSpelling</strong> - this is the spelling of the team name.  It is always expressed in all lowercase letters - e.g. \"ball state\" rather than \"Ball State\" - in order to emphasize that any comparisons should be case-insensitive when matching.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>TeamID</strong> - this identifies the TeamID for the team that has the alternative spelling (as described in MTeams.csv).</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MNCAATourneySlots</strong></p>\n<p>This file identifies the mechanism by which teams are paired against each other, depending upon their seeds, as the tournament proceeds through its rounds. It can be of use in identifying, for a given historical game, what round it occurred in, and what the seeds/slots were for the two teams (the meaning of \"slots\" is described below).  Because of the existence of play-in games for particular seed numbers, the pairings have small differences from year to year.  You may need to know these specifics if you are trying to represent/simulate the exact workings of the tournament bracket.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Season</strong> - this is the year of the associated entry in MSeasons.csv (the year in which the final tournament occurs)</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Slot</strong> - this uniquely identifies one of the tournament games. For play-in games, it is a three-character string identifying the seed fulfilled by the winning team, such as W16 or Z13. For regular tournament games, it is a four-character string, where the first two characters tell you which round the game is (R1, R2, R3, R4, R5, or R6) and the second two characters tell you the expected seed of the favored team. Thus the first row is R1W1, identifying the Round 1 game played in the W bracket, where the favored team is the 1 seed. As a further example, the R2W1 slot indicates the Round 2 game that would have the 1 seed from the W bracket, assuming that all favored teams have won up to that point. Even if that R2W1 slot were actually a game between the W09 and W16 teams, it is still considered to be the R2W1 slot.  The slot names are different for the final two rounds, where R5WX identifies the national semifinal game between the winners of regions W and X, and R5YZ identifies the national semifinal game between the winners of regions Y and Z, and R6CH identifies the championship game. The \"slot\" value is used in other columns in order to represent the advancement and pairings of winners of previous games.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>StrongSeed</strong> - this indicates the expected stronger-seeded team that plays in this game. For Round 1 games, a team seed is identified in this column (as listed in the \"Seed\" column in the MNCAATourneySeeds.csv file), whereas for subsequent games, a slot is identified in this column. In the first record of this file (slot R1W1), we see that seed W01 is the \"StrongSeed\", which during the 1985 tournament would have been Georgetown. Whereas for games from Round 2 or later, rather than a team seed, we will see a \"slot\" referenced in this column. So in the 33rd record of this file (slot R2W1), it tells us that the winners of slots R1W1 and R1W8 will face each other in Round 2. Of course, in the last few games of the tournament - the national semifinals and finals - it's not really meaningful to talk about a \"strong seed\" or \"weak seed\", since you would have #1 seeds favored to face each other, but those games are nevertheless represented in the same format for the sake of consistency.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>WeakSeed</strong> - this indicates the expected weaker-seeded team that plays in this game, assuming all favored teams have won so far. For Round 1 games, a team seed is identified in this column (as listed in the \"Seed\" column in the MNCAATourneySeeds.csv file), whereas for subsequent games, a slot is identified in this column.</span></li>\n</ul><hr>\n<p><strong>Data Section 6 file: MNCAATourneySeedRoundSlots.csv</strong></p>\n<p>This file helps to represent the bracket structure in any given year.  No matter where the play-in seeds are located, we can always know, for a given tournament seed, exactly what bracket slot they would be playing in, on each possible game round, and what the possible DayNum values would be for that round.  Thus, if we know when a historical game was played, and what the team's seed was, we can identify the slot for that game.  This can be useful in representing or simulating the tournament bracket structure.</p>\n<ul>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>Seed</strong> - this is the tournament seed of the team.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>GameRound</strong> - this is the round during the tournament that the game would occur in, where Round 0 (zero) is for the play-in games, Rounds 1/2 are for the first weekend, Rounds 3/4 are for the second weekend, and Rounds 5/6 are the national semifinals and finals.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>GameSlot</strong> - this is the game slot that the team would be playing in, during the given GameRound.  The naming convention for slots is described above, in the definition of the MNCAATourneySlots file.</span></li>\n<li><span style=\"font-size: 1em; line-height: 1.5em;\"><strong>EarlyDayNum, LateDayNum</strong> - these fields describe the earliest possible, and latest possible, DayNums that the game might be played on.</span></li>\n</ul>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "## Update: this competition has been cancelled on account of the COVID-19 pandemic.\n\n<p> As a result of the continued collaboration between Google Cloud and the NCAA®, the <i>seventh</i> annual Kaggle-backed March Madness® competition is underway! Another year, another chance to anticipate the upsets, call the probabilities, and put your bracketology skills to the leaderboard test. Kagglers will join the millions of fans who attempt to forecast the outcomes of March Madness during this year's NCAA Division I Men’s and Women’s Basketball Championships. But unlike most fans, you will pick your bracket using a combination of NCAA’s historical data and your computing power, while the ground truth unfolds on national television.\n\n</p>\n<p><img src=\"https://storage.googleapis.com/kaggle-media/competitions/march-madness-2018/lockup_cloud.png\" alt=\"March Madness Imagery\" style=\"float: right\"></p>\n\n<p>In the first stage of the competition, Kagglers will rely on results of past tournaments to build and test models. We encourage you to post any useful external data as a <a href=\"https://www.kaggle.com/datasets?modal=true\">dataset</a>.</p>\n\n<p>In the second stage, competitors will forecast outcomes of all possible matchups in the 2020 NCAA Division I Men’s and Women’s Basketball Championships. You don't need to participate in the first stage to enter the second. The first stage exists to incentivize model building and provide a means to score predictions. The real competition is forecasting the 2020 results.</p>\n\n<p>As the official public cloud provider of the NCAA, Google is proud to provide a competition to help participants strengthen their knowledge of basketball, statistics, data modeling, and cloud technology. As part of its journey to the cloud, the NCAA has migrated 80+ years of historical and play-by-play data, from 90 championships and 24 sports, to Google Cloud Platform (GCP). The NCAA has tapped into decades of historical basketball data using BigQuery, Cloud Spanner, Datalab, Cloud Machine Learning and Cloud Dataflow, to power the analysis of team and player performance. The mission of the NCAA has long been about serving the needs of schools, their teams and students. Google Cloud is proud to support that mission by helping the NCAA use data and machine learning to better engage with its millions of fans, 500,000 student-athletes, and more than 19,000 teams. Game on! </p>\n\n<p><i>This page is for the NCAA Division I Men's tournament. Check out the <a href=\"https://www.kaggle.com/c/google-cloud-ncaa-march-madness-2020-division-1-womens-tournament\">NCAA Division I Women's tournament here</a>.  If you want to extend your analysis then try out our Analytics Competition <a href=\"https://www.kaggle.com/c/march-madness-analytics-2020\">here</a></p></i>\n",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>Submissions are scored on the log loss:</p>\n<p>$$<br>\\textrm{LogLoss} = - \\frac{1}{n} \\sum_{i=1}^n \\left[ y_i \\log(\\hat{y}_i) + (1 - y_i) \\log(1 - \\hat{y}_i)\\right],<br>$$</p>\n<p>where</p>\n<ul>\n<li>n is the number of games played</li>\n<li>\\\\( \\hat{y}_i \\\\) is the predicted probability of team 1 beating team 2</li>\n<li>\\\\( y_i \\\\) is 1 if team 1 wins, 0 if team 2 wins</li>\n<li>\\\\( log() \\\\) is the natural (base e) logarithm</li>\n</ul>\n<p>The use of the logarithm provides extreme punishments for being both confident and wrong. In the worst possible case, a prediction that something is true when it is actually false will add an infinite amount to your error score. In order to prevent this, predictions are bounded away from the extremes by a small value.</p>\n<h2>Submission File</h2>\n<p>The file you submit will depend on whether the competition is in stage 1 (historical model building) or stage 2 (the 2020 tournament). Sample submission files will be provided for both stages. The format is a list of every possible matchup between the tournament teams. Since team1 vs. team2 is the same as team2 vs. team1, we only include the game pairs where team1 has the lower team id. For example, in a tournament of 68 teams (64 + 4 play-in teams), you will predict (68*67)/2  = 2,278 matchups. </p>\n<p>Each game has a unique id created by concatenating the season in which the game was played, the team1 id, and the team2 id. For example, \"2015_1107_1112\" indicates team 1107 potentially played team 1112 in the year 2015. You must predict the probability that the team with the lower id beats the team with the higher id.</p>\n<p>The resulting submission format looks like the following, where \"pred\" represents the predicted probability that the first team will win:</p>\n<pre>id,pred<br>2015_1107_1112,0.5<br>2015_1107_1116,0.5<br>2015_1107_1124,0.5<br>...</pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Timeline",
      "content": "**Updated March 13, 2020**: The following supersedes the respective terms outlined below.  As a result of COVID-19, this competition will be cancelled with no Kaggle points, Kaggle medals, or monetary prizes. The end date has been updated from April 7, 2020 at 11:59pm UTC to March 19, 2020 at 3:00 am UTC. Please see this [announcement post](https://www.kaggle.com/c/google-cloud-ncaa-march-madness-2020-division-1-mens-tournament/discussion/135404) for more details.\n------\n<h2>Stage 1 - Model Building</h2>\n<ul>\n<li><strong>Saturday, Mar 14</strong>&nbsp;- Prior to this deadline, competitors build and test models on historical data. The leaderboard shows the model performance on historical tournament outcomes.</li>\n</ul>\n<h2>Stage 2 - Championship</h2>\n<ul>\n<li><strong>Sunday, Mar 15&nbsp;</strong>- Selection Sunday® (68 teams announced)</li>\n<li><strong>Monday, Mar 16&nbsp;</strong>- Kaggle begins to accept 2020 predictions. Release of up-to-date 2019-2020 season data.</li>\n<li><strong>Thursday, Mar 19 3PM UTC&nbsp;</strong>- Final deadline to submit 2020 predictions.</li>\n<li><strong>Mar 19&nbsp;onward&nbsp;</strong>- Watch your tournament results play out! The Kaggle Team will refresh the leaderboard throughout the competition as games are finalized.</li>\n</ul>\n<p>All deadlines are at 11:59 PM UTC on the corresponding day unless otherwise noted. The organizers reserve the right to update the contest timeline if they deem it necessary.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Prizes",
      "content": "### **Updated March 13, 2020**: The following supersedes the respective terms outlined below.  As a result of COVID-19, this competition will be cancelled with no Kaggle points, Kaggle medals, or monetary prizes. The end date has been updated from April 7, 2020 at 11:59pm UTC to March 19, 2020 at 3:00 am UTC. Please see this [announcement post](https://www.kaggle.com/c/google-cloud-ncaa-march-madness-2020-division-1-mens-tournament/discussion/135404) for more details.\n\n* 1st Place - $10,000\n* 2nd Place - $7,000\n* 3rd Place - $5,000\n* 4th Place - $2,000\n* 5th Place - $1,000\n\n<p><b>Stage 1</b> will not count towards Kaggle rankings/points.</p>\n<p><b>Stage 2</b> will count toward Kaggle rankings/points.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "FAQs",
      "content": "<p><strong>Is one tournament enough to decide the best basketball algorithm?</strong><br>It's better to be lucky than good! Besides, when was the last time your office held a cross validation pool?</p>\n<p><strong>Can I update my predictions after the tournament starts?</strong><br>No changes are permitted once the tournament begins.</p>\n<p><strong>How is the leaderboard going to work when the event being scored hasn't yet happened?</strong><br>You won't submit after the tournament starts. We'll update the solution file as the games occur, which will cause the ranks on the leaderboard to change.</p>\n<p><strong>Why do we have to predict every match up? Why 68 teams and not 64? </strong><br>This was done for timing purposes. Predicting every possible matchup for the 68 teams announced on Selection Sunday gives participants the most time to get their current year predictions ready in time. There is a small \"play-in\" round, sometimes called the first round, where the 68 are narrowed to 64. While you are asked to predict these games (and you may be predicting them after they occur), we will not be scoring them.</p>\n<p><strong>Why don't predictions in later rounds count for more?</strong><br>While it is possible to weight the later games, we chose to keep scoring simple and count all games equally. Any weights we pick would be mostly arbitrary (how many first-round games is a championship game worth?). Also, weighting any game increases the role that luck plays in determining a winner.&nbsp;We've also structured the competition so that people can still be in the running even if there are early-round upsets.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}