{
  "id": 3595,
  "title": "Most popular benchmark (different than my calculation)",
  "url": "/competitions/event-recommendation-engine-challenge/discussion/3595",
  "author_name": "",
  "post_date": "2013-01-14T22:25:26.703Z",
  "votes": null,
  "comment_count": 3,
  "views": 1529,
  "content": "<p>I'm looking at the &quot;most popular&quot; benchmark, and it appears different from my calculations.</p>\r\n<p>For example, in python, I do</p>\r\n<p style=\"padding-left:30px\">train = pd.read_csv(my_dir&#43;&quot;train.csv&quot;)</p>\r\n<p style=\"padding-left:30px\">like_counts =&nbsp;train.groupby('event').interested.sum()</p>\r\n<p style=\"padding-left:30px\">like_counts.sort()</p>\r\n<p>&nbsp;</p>\r\n<p>The second most popular event appears to be&nbsp;2529072432 with 94 likes. &nbsp;If this is the 2nd most popular event, I wouldn't expect it to be listed later the 2nd for any user. &nbsp;But we find this is frequently the case. &nbsp;For instance, consider the line</p>\r\n<p>23465780,[955398943L, 602394192L, 2529072432L, 1600413013L, 3017074183L, 2414358105L, 3807695143L]</p>\r\n<p>where it is listed after an event with only 12 likes.</p>\r\n<p>This is just one example, but I'm finding lots of instances like this.</p>",
  "messages": [
    {
      "id": "19306",
      "postDate": "01/14/2013 22:25:26",
      "content": "<p>I'm looking at the &quot;most popular&quot; benchmark, and it appears different from my calculations.</p>\r\n<p>For example, in python, I do</p>\r\n<p style=\"padding-left:30px\">train = pd.read_csv(my_dir&#43;&quot;train.csv&quot;)</p>\r\n<p style=\"padding-left:30px\">like_counts =&nbsp;train.groupby('event').interested.sum()</p>\r\n<p style=\"padding-left:30px\">like_counts.sort()</p>\r\n<p>&nbsp;</p>\r\n<p>The second most popular event appears to be&nbsp;2529072432 with 94 likes. &nbsp;If this is the 2nd most popular event, I wouldn't expect it to be listed later the 2nd for any user. &nbsp;But we find this is frequently the case. &nbsp;For instance, consider the line</p>\r\n<p>23465780,[955398943L, 602394192L, 2529072432L, 1600413013L, 3017074183L, 2414358105L, 3807695143L]</p>\r\n<p>where it is listed after an event with only 12 likes.</p>\r\n<p>This is just one example, but I'm finding lots of instances like this.</p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "19307",
      "postDate": "01/14/2013 22:30:32",
      "content": "<p>[quote=DanB;19306]</p>\r\n<p>I'm looking at the &quot;most popular&quot; benchmark, and it appears different from my calculations.</p>\r\n<p>For example, in python, I do</p>\r\n<p style=\"padding-left:30px\">train = pd.read_csv(my_dir&#43;&quot;train.csv&quot;)</p>\r\n<p style=\"padding-left:30px\">like_counts =&nbsp;train.groupby('event').interested.sum()</p>\r\n<p style=\"padding-left:30px\">like_counts.sort()</p>\r\n<p>&nbsp;</p>\r\n<p>The second most popular event appears to be&nbsp;2529072432 with 94 likes. &nbsp;If this is the 2nd most popular event, I wouldn't expect it to be listed later the 2nd for any user. &nbsp;But we find this is frequently the case. &nbsp;For instance, consider the line</p>\r\n<p>23465780,[955398943L, 602394192L, 2529072432L, 1600413013L, 3017074183L, 2414358105L, 3807695143L]</p>\r\n<p>where it is listed after an event with only 12 likes.</p>\r\n<p>This is just one example, but I'm finding lots of instances like this.</p>\r\n<p>[/quote]The benchmark measures popularity by the number of people indicating that they are attending the event, not the number of people that are interested in an event.</p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "19309",
      "postDate": "01/14/2013 22:41:51",
      "content": "<p>Thanks for the quick response... though that makes me want to verify I understand the metric correctly. &nbsp;The rules say&nbsp;</p>\r\n<p>&quot;<span>Events should be ordered from the ones in which you predict the user will be most interested to those in which the user will be least be interested.&quot;</span></p>\r\n<p>Can I infer from your response that &quot;interested&quot; in the rules refers to the probability of attending, rather than probability of saying they are interested?</p>\r\n<p>Thanks,</p>\r\n<p>Dan</p>\r\n<p><span><br>\r\n</span></p>",
      "rawMarkdown": "",
      "votes": null
    },
    {
      "id": "19311",
      "postDate": "01/14/2013 23:25:15",
      "content": "<p>[quote=DanB;19309]</p>\r\n<p>Thanks for the quick response... though that makes me want to verify I understand the metric correctly. &nbsp;The rules say&nbsp;</p>\r\n<p>&quot;<span>Events should be ordered from the ones in which you predict the user will be most interested to those in which the user will be least be interested.&quot;</span></p>\r\n<p>Can I infer from your response that &quot;interested&quot; in the rules refers to the probability of attending, rather than probability of saying they are interested?</p>\r\n<p>Thanks,</p>\r\n<p>Dan[/quote]No, &quot;interested&quot; refers to whether the user marked that they were interested in it (as shown in train.csv).</p>",
      "rawMarkdown": "",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 19307,
      "author_name": "benhamner",
      "author_url": "",
      "post_date": "01/14/2013 22:30:32",
      "content": "<p>[quote=DanB;19306]</p>\r\n<p>I'm looking at the &quot;most popular&quot; benchmark, and it appears different from my calculations.</p>\r\n<p>For example, in python, I do</p>\r\n<p style=\"padding-left:30px\">train = pd.read_csv(my_dir&#43;&quot;train.csv&quot;)</p>\r\n<p style=\"padding-left:30px\">like_counts =&nbsp;train.groupby('event').interested.sum()</p>\r\n<p style=\"padding-left:30px\">like_counts.sort()</p>\r\n<p>&nbsp;</p>\r\n<p>The second most popular event appears to be&nbsp;2529072432 with 94 likes. &nbsp;If this is the 2nd most popular event, I wouldn't expect it to be listed later the 2nd for any user. &nbsp;But we find this is frequently the case. &nbsp;For instance, consider the line</p>\r\n<p>23465780,[955398943L, 602394192L, 2529072432L, 1600413013L, 3017074183L, 2414358105L, 3807695143L]</p>\r\n<p>where it is listed after an event with only 12 likes.</p>\r\n<p>This is just one example, but I'm finding lots of instances like this.</p>\r\n<p>[/quote]The benchmark measures popularity by the number of people indicating that they are attending the event, not the number of people that are interested in an event.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 19309,
      "author_name": "dansbecker",
      "author_url": "",
      "post_date": "01/14/2013 22:41:51",
      "content": "<p>Thanks for the quick response... though that makes me want to verify I understand the metric correctly. &nbsp;The rules say&nbsp;</p>\r\n<p>&quot;<span>Events should be ordered from the ones in which you predict the user will be most interested to those in which the user will be least be interested.&quot;</span></p>\r\n<p>Can I infer from your response that &quot;interested&quot; in the rules refers to the probability of attending, rather than probability of saying they are interested?</p>\r\n<p>Thanks,</p>\r\n<p>Dan</p>\r\n<p><span><br>\r\n</span></p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 19311,
      "author_name": "benhamner",
      "author_url": "",
      "post_date": "01/14/2013 23:25:15",
      "content": "<p>[quote=DanB;19309]</p>\r\n<p>Thanks for the quick response... though that makes me want to verify I understand the metric correctly. &nbsp;The rules say&nbsp;</p>\r\n<p>&quot;<span>Events should be ordered from the ones in which you predict the user will be most interested to those in which the user will be least be interested.&quot;</span></p>\r\n<p>Can I infer from your response that &quot;interested&quot; in the rules refers to the probability of attending, rather than probability of saying they are interested?</p>\r\n<p>Thanks,</p>\r\n<p>Dan[/quote]No, &quot;interested&quot; refers to whether the user marked that they were interested in it (as shown in train.csv).</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "19306": "",
    "19307": "",
    "19309": "",
    "19311": ""
  },
  "source": "meta"
}