{
  "fetched_at": "2026-10-25T00:29:22Z",
  "source_url": "https://www.kaggle.com/competitions/credit-card-defaults/data",
  "pages": [
    {
      "name": "rules",
      "content": "\n\t<!-- Begin Base Rules -->\n    <h3>One account per participant</h3>\n    <p>You cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.</p>\n    <h3>No private sharing outside teams</h3>\n    <p>\n        Privately sharing code or data outside of teams is not permitted.\n        It's okay to share code if made available to all participants on the forums.\n    </p>\n    <h3>Team Mergers</h3>\n    <p>Team mergers are not allowed in this competition.</p>\n\n    <h3>Team Limits</h3>\n    <p>Each team is limited to have no more than <strong>3</strong> persons.</p>\n    <h3>Submission Limits</h3>\n    <p>You may submit a maximum of 5 entries per day.</p>\n    <p>You may select up to 3 final submissions for judging.</p>\n    <h3>Competition Timeline</h3>\n    <p>Start Date: <strong>Nov. 21, 2018</strong></p>\n    <p>Merger Deadline: <strong>None</strong></p>\n    <p>Entry Deadline: <strong>None</strong></p>\n    <p>End Date: <strong>Dec. 28, 2018</strong></p>\n\t<!-- End Base Rules -->\n<p>The rules page is a bit special: it will auto-update the text based on the parameters of the competition. The rules you need to add here are any additional rules relating to dataset usage. You may also put grading information here.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "<p>The data files contain information on default payments, demographic factors, credit data, history of payment, and bill statements of credit card clients in Taiwan from April 2005 to September 2005.</p>\n\n<h2>File descriptions</h2>\n<ul>\n<li><strong>Credit_Card_train.csv</strong> - the training set</li>\n<li><strong>Credit_Card_test.csv</strong> - the test set</li>\n<li><strong>sampleSubmission.csv</strong> - a sample submission file in the correct format</li>\n</ul>\n\n<h2>Data fields</h2>\n<p>There are 25 variables:</p>\n<ul>\n<li><strong>ID</strong> - ID of each client</li>\n<li><strong>LIMIT_BAL</strong> - Amount of given credit in NT dollars (includes individual and family/supplementary credit</li>\n<li><strong>SEX</strong> - Gender (1=male, 2=female)</li>\n<li><strong>EDUCATION</strong> - (1=graduate school, 2=university, 3=high school, 4=others, 5=unknown, 6=unknown)</li>\n<li><strong>MARRIAGE</strong> - Marital status (1=married, 2=single, 3=others)</li>\n<li><strong>AGE</strong> - Age in years</li>\n<li><strong>PAY_0</strong> - Repayment status in September, 2005 (-1=pay duly, 1=payment delay for one month, 2=payment delay for two months, ... 8=payment delay for eight months, 9=payment delay for nine months and above)</li>\n<li><strong>PAY_2</strong> - Repayment status in August, 2005 (scale same as above)</li>\n<li><strong>PAY_3</strong> - Repayment status in July, 2005 (scale same as above)</li>\n<li><strong>PAY_4</strong> - Repayment status in June, 2005 (scale same as above)</li>\n<li><strong>PAY_5</strong> - Repayment status in May, 2005 (scale same as above)</li>\n<li><strong>PAY_6</strong> - Repayment status in April, 2005 (scale same as above)</li>\n<li><strong>BILL_AMT1</strong> - Amount of bill statement in September, 2005 (NT dollar)</li>\n<li><strong>BILL_AMT2</strong> - Amount of bill statement in August, 2005 (NT dollar)</li>\n<li><strong>BILL_AMT3</strong> - Amount of bill statement in July, 2005 (NT dollar)</li>\n<li><strong>BILL_AMT4</strong> - Amount of bill statement in June, 2005 (NT dollar)</li>\n<li><strong>BILL_AMT5</strong> - Amount of bill statement in May, 2005 (NT dollar)</li>\n<li><strong>BILL_AMT6</strong> - Amount of bill statement in April, 2005 (NT dollar)</li>\n<li><strong>PAY_AMT1</strong> - Amount of previous payment in September, 2005 (NT dollar)</li>\n<li><strong>PAY_AMT2</strong> - Amount of previous payment in August, 2005 (NT dollar)</li>\n<li><strong>PAY_AMT3</strong> - Amount of previous payment in July, 2005 (NT dollar)</li>\n<li><strong>PAY_AMT4</strong> - Amount of previous payment in June, 2005 (NT dollar)</li>\n<li><strong>PAY_AMT5</strong> - Amount of previous payment in May, 2005 (NT dollar)</li>\n<li><strong>PAY_AMT6</strong> - Amount of previous payment in April, 2005 (NT dollar)</li>\n<li><strong>default.payment.next.month</strong> - Default payment (1=yes, 0=no)</li>\n</ul>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "<p>This competition is an in-class competition for the course \"Artificial Intelligence and Machine Learning\". The competition is to predict the default payments of credit card clients based on the clients' demographic information and payment history.</p>\n",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<p>The evaluation metric for this competition is <a href=\"https://www.kaggle.com/wiki/MeanFScore\"> Mean F1-Score</a>. The F1 score, commonly used in information retrieval, measures accuracy using the statistics precision p and recall r. Precision is the ratio of true positives (tp) to all predicted positives (tp + fp). Recall is the ratio of true positives to all actual positives (tp + fn). The F1 score is given by:</p>\n<p>\\[ F1 = 2\\frac{p \\cdot r}{p+r}\\ \\ \\mathrm{where}\\ \\ p = \\frac{tp}{tp+fp},\\ \\ r = \\frac{tp}{tp+fn} \\]</p>\n<p>The F1 metric weights recall and precision equally, and a good retrieval algorithm will maximize both precision and recall simultaneously. Thus, moderately good performance on both will be favored over extremely good performance on one and poor performance on the other.</p>\n<h2>Submission Format</h2>\n<p><strong>For every client in the dataset</strong>, submission files should contain two columns: client_ID and default_payment_next_month.\n<p>The file should contain a header and have the following format:</p>\n<pre>ID,default.payment.next.month<br />20001,1<br /><span style=\"font-size: 14px; line-height: 1.4em;\">20002,0<br />20003,0<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">20004,0<br /></span><span style=\"font-size: 14px; line-height: 1.4em;\">......</span></pre>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}