{
  "fetched_at": "2026-10-19T22:30:45Z",
  "source_url": "https://www.kaggle.com/competitions/dsg-hackathon/data",
  "pages": [
    {
      "name": "Description",
      "content": "<p>Hosted by <a href=\"http://datascienceglobal.org/member-organizations/data-science-london/\">\r\nData Science London</a> and <a href=\"http://datascienceglobal.org/\">Data Science Global</a> as part of a\r\n<a href=\"http://bigdataweek.com/\">Big Data Week</a> event, and organised by Kaggle, the first ever global data science hackathon will take place at the same time in several cities around the world spanning a 24-hour period. During this time the data scientists\r\n will compete with each other for cash prizes using a large dataset provided by the Cook County, Illinois, local government.</p>\r\n<p>The challenge for the hackathon is to build with better more accurate predictive models of metropolitan air pollution. The EPA’s Air Quality Index is used daily by people suffering from asthma and other respiratory diseases to avoid dangerous levels of outdoor\r\n air pollutants, which can trigger attacks. According to the World Health Organisation there are now estimated to be 235 million people suffering from asthma. Globally, it is now the most common chronic disease among children, with incidence in the US doubling\r\n since 1980.&nbsp; The model we build could be used as the basis for an early warning system that is capable of accurately predicting dangerous levels of air pollutants on an hourly basis.</p>\r\n<p>Data Science Global is a non-profit organization dedicated to bringing together the world’s communities of data scientists, artists, technologists and visionaries.&nbsp; For our inaugural event, we are hosting a global data science hackathon. &nbsp; It will be taking\r\n place simultaneously in cities around the world: London, New York, Boston, Chicago, San Francisco, Melbourne, Canberra, Sydney and Turku, Finland, as well as remote participants competing directly through Kaggle.&nbsp; You can join in the live webcast from the\r\n participating venues at <a href=\"http://www.datascienceglobal.org\">datascienceglobal.org</a></p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Rules",
      "content": "\r\n\t<!-- Begin Base Rules -->\r\n    <h3>One account per participant</h3>\r\n    <p>You cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.</p>\r\n    <h3>No private sharing outside teams</h3>\r\n    <p>\r\n        Privately sharing code or data outside of teams is not permitted.\r\n        It's okay to share code if made available to all participants on the forums.\r\n    </p>\r\n    <h3>Team Mergers</h3>\r\n    <p>\r\n        Team 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.<br/>\r\n    </p>\r\n\r\n    <h3>Team Limits</h3>\r\n    <p>There is no maximum team size.</p>\r\n    <h3>Submission Limits</h3>\r\n    <p>You may submit a maximum of 8 entries per day.</p>\r\n    <p>You may select up to 2 final submissions for judging.</p>\r\n    <h3>Competition Timeline</h3>\r\n    <p>Start Date: <strong>4/28/2012 12:00 PM UTC</strong></p>\r\n    <p>Merger Deadline: <strong>None</strong></p>\r\n    <p>Entry Deadline: <strong>None</strong></p>\r\n    <p>End Date: <strong>4/29/2012 12:00 PM UTC</strong></p>\r\n\t<!-- End Base Rules -->\r\n<ul>\r\n<li>Each team will be able to make 8 submissions on Saturday, and 8 submissions on Sunday (where days are defined as periods from midnight to midnight UTC).\r\n</li><li>We will not allow team mergers after Saturday UTC (but you may form a team with anyone who isn't already in the contest). As usual, we will not merge teams at any point if that would give the resulting team more submissions than it is allowed to have on\r\n Saturday (8). </li><li>We won't be surprised to see discussion of insights into the data in each venue, but remember that you are not allowed to share code or data with anyone who is not on your team (except in public forums that everyone can access).\r\n</li><li>External data may only be used if a request is made in the appropriate forum post, linking to where other participants can find the publicly available data. (In general, requests will be approved unless the requested data has information specific to air\r\n quality sensor readings.) You must not incorporate external data into you modeling (not even models that you keep to yourself) until approval is received.\r\n<strong>Winning models may be checked against previously unreleased data as part of checking for conformity with this rule.</strong>\r\n</li><li>You should not attempt to identify the actual date/time of any data provided or reconstruct the shuffled time series.\r\n</li><li>If an event arises that is not explicitly handled by these rules and that Kaggle, in its sole discretion, believes could have material adverse impact on the final results, Kaggle reserves the right to resolve the dispute using the majority view of an independent\r\n review panel selected by them. </li><li>&nbsp;Do not attempt to identify what particular day each time slice corresponds to\r\n</li><li>Winning solutions must be made public, with code and a description of the method\r\n</li><li>Except when a particular prize-awarding authority decides otherwise, any winning solution must be licensed under an open source license and published on Kaggle\r\n</li></ul>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "<ul>\r\n<li>Submissions will be scored by mean absolute error (MAE) across all values in the evaluation data.\r\n</li></ul>\r\n<p>Both the training and evaluation data sets have missing values, and our intention is to ignore these in calculating MAE. To do this, we have (in the solution file) transformed all NA's to &quot;-1,000,000&quot; and shown you where these occur by providing you with\r\n a sample submission that has these values in all of the correct places, and 0's everywhere else.&nbsp;</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "SubmissionInstructions",
      "content": "<div>Please see the sample submission as a guide to what values you will predict.</div>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Prizes",
      "content": "<p>There is a global first prize which all participants, competing in venues or remotely, are eligible to win.&nbsp; First place will be a cash prize, and there will be additional prizes in the form of Amazon Web Services vouchers.</p>\r\n<p><strong>EMC Data Science Global Hackathon 1st Prize – GBP 1,800 ( USD 2,850)</strong></p>\r\n<p>&nbsp;</p>\r\n<p>Some venues have choosen to sponsor additional venues prizes for their local participants (you must have RSVP'd to the venue and be physically in attendance).&nbsp; Participants in these venues are also eligible to win the global prize</p>\r\n<p><strong>EMC Data Science London Hackathon 1st Prize –&nbsp; GBP 1,200 (USD 1,900)</strong></p>\r\n<p><strong>New York City @ Bloomberg Ventures - $500 USD equivalent in hardware, software and services.</strong></p>\r\n<p>(And an additional $500 for the related Visualization Contest)</p>\r\n<p>And for the Melbourne Venue:</p>\r\n<p><strong>Melbourne Institute: USD $ 1050 </strong></p>\r\n<p><a href=\"http://www.melbourneinstitute.com/\">http://www.melbourneinstitute.com/\r\n</a></p>\r\n<p><strong>Lift Analytic: USD $520</strong></p>\r\n<p><a href=\"http://www.liftanalytics.com.au\">http://www.liftanalytics.com.au </a>\r\n</p>\r\n<p><strong>Huntel Global: USD $210</strong></p>\r\n<p><a href=\"http://huntelglobal.com/\">http://huntelglobal.com/ </a></p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "<p>The data consist of hourly measurements of various quantities (mostly are pollutants), where each row contains the measurements for one hour. Time slices (&quot;chunks&quot;) of 11 days have been created, with the first 8 days of each chunk available in the training\r\n data. You are asked to make pdictions about various points within the following 3 days (1, 2 ,3, 4, 5, 10, 17, 24, 48, and 72 hours after the end of the 8-day training data).<br>\r\n<br>\r\nWithin the training data, you are provided the following:</p>\r\n<ul>\r\n<li>rowID </li><li>chunkID </li><li>position_within_chunk (starts at 1 for each chunk of data, increments by hour)\r\n</li><li>month_most_common (most common month within chunk of data--a number from 1 to 12) weekday (day of the week, as a string)\r\n</li><li>hour (a number from 0 to 23, local time) </li><li>Solar.radiation_64&nbsp; </li><li>WindDirection..Resultant_1 (direction the wind is blowing from given as an angle, e.g. a wind from the east is &quot;90&quot;)\r\n</li><li>WindDirection..Resultant_1018 (direction the wind is blowing from given as an angle, e.g. a wind from the east is &quot;90&quot;)\r\n</li><li>WindSpeed..Resultant_1 (&quot;1&quot; is site number) </li><li>WindSpeed..Resultant_1018 (&quot;1018&quot; is site number) </li><li>Ambient.Max.Temperature_(site number) </li><li>Ambient.Min.Temperature_(site number) </li><li>Sample.Baro.Pressure_(site number) </li><li>Sample.Max.Baro.Pressure_(site number) </li><li>Sample.Min.Baro.Pressure_(site number) </li><li>(39 response variables of the form): target_(target number)_(site number) </li></ul>\r\n<p>The variables described above with &quot;_(site_number)&quot; are available for various sites, and similarly, &quot;_(target_number)&quot; will vary across several targets.</p>\r\n<p>You are provided with the lat/long of each sample site in a separate file.</p>\r\n<p>During the 3-day pdiction periods, you are provided only:</p>\r\n<ul>\r\n<li>rowID </li><li>chunkID </li><li>position_within_chunk (starts at 1 for each chunk of data, increments by hour)\r\n</li><li>month_most_common (most common month within chunk of data--a number from 1 to 12) weekday (day of the week, as a string)\r\n</li><li>hour (a number from 0 to 23, local time) </li></ul>\r\n<p>You should get these from the sample submission file provided.<br>\r\n<br>\r\nYour submission will include:</p>\r\n<ul>\r\n<li>(39 response variables of the form): target_(target number)_(site number) </li></ul>\r\n<p><br>\r\nAll of the &quot;target&quot; variables have been transformed to be approximately on the same scale (each with mean approximately 0 [CORRECTION: only the variance was normalized, not the mean] and variance approximately 1). We will reveal what quantity each target variable\r\n is a measurement of after the competition ends.<br>\r\n<br>\r\nThere are many rows for which some of the measurements are missing. This occurs in both the training and evaluation data. Our intention is to ignore these in calculating your score (MAE). To do achieve that effect, we have (in the solution file) transformed\r\n all NA's to &quot;-1,000,000&quot; and shown you where these occur by providing you with a sample submission that has these values in all of the correct places, and 0's everywhere else. You should make sure your solution has &quot;-1,000,000&quot; in the appropriate places. We\r\n apologize for the inconvenience.</p>",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}