{
  "id": 76049,
  "title": "Presenting the analysis in slides and kernels",
  "url": "/competitions/NFL-Punt-Analytics-Competition/discussion/76049",
  "author_name": "",
  "post_date": "2018-12-28T20:27:12.132512400Z",
  "votes": 3,
  "comment_count": 2,
  "views": 0,
  "content": "<p>I would like a little help with understanding how the submission is supposed to work. What is the difference between the kernel and the powerpoint? How do we divide up the analysis properly? If it isn't done correctly, then one of them becomes redundant which I want to avoid. Thanks in advance for the help!</p>",
  "messages": [
    {
      "id": "446880",
      "postDate": "12/28/2018 20:27:12",
      "content": "<p>I would like a little help with understanding how the submission is supposed to work. What is the difference between the kernel and the powerpoint? How do we divide up the analysis properly? If it isn't done correctly, then one of them becomes redundant which I want to avoid. Thanks in advance for the help!</p>",
      "rawMarkdown": "I would like a little help with understanding how the submission is supposed to work. What is the difference between the kernel and the powerpoint? How do we divide up the analysis properly? If it isn't done correctly, then one of them becomes redundant which I want to avoid. Thanks in advance for the help!",
      "votes": null
    },
    {
      "id": "446895",
      "postDate": "12/28/2018 20:54:03",
      "content": "<p>Well I was about to do the same kind of topic so I'll ask my questions there :\nAs said in the submission instructions :</p>\n\n<blockquote>\n  <p>A valid submission will include: <br>\n  Summary Slides: A summary of the proposed rule change presented in\n  slide format and delivered as either a PDF or PPT file. Kernels </p>\n  \n  <p>Analysis: At least one kernel containing the analysis to support your\n  proposal. All kernels submitted must be made public on or before the\n  submission deadline to be eligible. If submitting as a team, all team\n   members must be listed as collaborators on all kernels submitted.</p>\n</blockquote>\n\n<p>I have a few questions regarding this instructions :  </p>\n\n<ul>\n<li><p>What should be put in the kernel, and what should be in the summary ?</p>\n\n<ul><li>Should kernels be graph only as giving clues to what you've decided as rule changes in it will go <br>\npublic ?  </li>\n<li>Should the summary explain the reflexion which led to such rule changes proposal or just contain the rule changes and explain them ?</li></ul></li>\n<li><p>Isn't it a problem that kernels have to be published publicly <strong>before</strong> the deadline, can't Kaggle just set every kernel related to this competition to public mode on release date with the link that they get in the submission form for example ? <br>\nI love watching what people decide to share during competitions (be it scripts, cheat sheets, insights, graphs) to get some inspiration, and I think they should not be forced to share their entire submission before the deadline, because it will have an impact on other participants.</p></li>\n<li><p>And as said <a href=\"/pluto1717\">@pluto1717</a> how to avoid redundancy ?</p></li>\n</ul>",
      "rawMarkdown": "Well I was about to do the same kind of topic so I'll ask my questions there :\nAs said in the submission instructions :\n\n&gt; A valid submission will include:  \n&gt; Summary Slides: A summary of the proposed rule change presented in\n&gt; slide format and delivered as either a PDF or PPT file. Kernels \n&gt;  \n&gt; Analysis: At least one kernel containing the analysis to support your\n&gt; proposal. All kernels submitted must be made public on or before the\n&gt;submission deadline to be eligible. If submitting as a team, all team\n&gt;  members must be listed as collaborators on all kernels submitted.\n\nI have a few questions regarding this instructions :  \n\n- What should be put in the kernel, and what should be in the summary ?\n  - Should kernels be graph only as giving clues to what you've decided as rule changes in it will go  \n     public ?  \n  - Should the summary explain the reflexion which led to such rule changes proposal or just contain the rule changes and explain them ?\n\n- Isn't it a problem that kernels have to be published publicly **before** the deadline, can't Kaggle just set every kernel related to this competition to public mode on release date with the link that they get in the submission form for example ?  \nI love watching what people decide to share during competitions (be it scripts, cheat sheets, insights, graphs) to get some inspiration, and I think they should not be forced to share their entire submission before the deadline, because it will have an impact on other participants.\n\n- And as said @pluto1717 how to avoid redundancy ?",
      "votes": null
    },
    {
      "id": "449269",
      "postDate": "01/02/2019 22:09:20",
      "content": "<p>We don't have any guidelines for how you use Kernels or presentation slides, it's totally up to you. If it were me, I would probably use the slides to tell my story and communicate my results while using Kernels to crunch numbers and support my claims.</p>",
      "rawMarkdown": "We don't have any guidelines for how you use Kernels or presentation slides, it's totally up to you. If it were me, I would probably use the slides to tell my story and communicate my results while using Kernels to crunch numbers and support my claims.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 446895,
      "author_name": "mdolres",
      "author_url": "",
      "post_date": "12/28/2018 20:54:03",
      "content": "<p>Well I was about to do the same kind of topic so I'll ask my questions there :\nAs said in the submission instructions :</p>\n\n<blockquote>\n  <p>A valid submission will include: <br>\n  Summary Slides: A summary of the proposed rule change presented in\n  slide format and delivered as either a PDF or PPT file. Kernels </p>\n  \n  <p>Analysis: At least one kernel containing the analysis to support your\n  proposal. All kernels submitted must be made public on or before the\n  submission deadline to be eligible. If submitting as a team, all team\n   members must be listed as collaborators on all kernels submitted.</p>\n</blockquote>\n\n<p>I have a few questions regarding this instructions :  </p>\n\n<ul>\n<li><p>What should be put in the kernel, and what should be in the summary ?</p>\n\n<ul><li>Should kernels be graph only as giving clues to what you've decided as rule changes in it will go <br>\npublic ?  </li>\n<li>Should the summary explain the reflexion which led to such rule changes proposal or just contain the rule changes and explain them ?</li></ul></li>\n<li><p>Isn't it a problem that kernels have to be published publicly <strong>before</strong> the deadline, can't Kaggle just set every kernel related to this competition to public mode on release date with the link that they get in the submission form for example ? <br>\nI love watching what people decide to share during competitions (be it scripts, cheat sheets, insights, graphs) to get some inspiration, and I think they should not be forced to share their entire submission before the deadline, because it will have an impact on other participants.</p></li>\n<li><p>And as said <a href=\"/pluto1717\">@pluto1717</a> how to avoid redundancy ?</p></li>\n</ul>",
      "votes": null,
      "replies": []
    },
    {
      "id": 449269,
      "author_name": "crawford",
      "author_url": "",
      "post_date": "01/02/2019 22:09:20",
      "content": "<p>We don't have any guidelines for how you use Kernels or presentation slides, it's totally up to you. If it were me, I would probably use the slides to tell my story and communicate my results while using Kernels to crunch numbers and support my claims.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "446880": "I would like a little help with understanding how the submission is supposed to work. What is the difference between the kernel and the powerpoint? How do we divide up the analysis properly? If it isn't done correctly, then one of them becomes redundant which I want to avoid. Thanks in advance for the help!",
    "446895": "Well I was about to do the same kind of topic so I'll ask my questions there :\nAs said in the submission instructions :\n\n&gt; A valid submission will include:  \n&gt; Summary Slides: A summary of the proposed rule change presented in\n&gt; slide format and delivered as either a PDF or PPT file. Kernels \n&gt;  \n&gt; Analysis: At least one kernel containing the analysis to support your\n&gt; proposal. All kernels submitted must be made public on or before the\n&gt;submission deadline to be eligible. If submitting as a team, all team\n&gt;  members must be listed as collaborators on all kernels submitted.\n\nI have a few questions regarding this instructions :  \n\n- What should be put in the kernel, and what should be in the summary ?\n  - Should kernels be graph only as giving clues to what you've decided as rule changes in it will go  \n     public ?  \n  - Should the summary explain the reflexion which led to such rule changes proposal or just contain the rule changes and explain them ?\n\n- Isn't it a problem that kernels have to be published publicly **before** the deadline, can't Kaggle just set every kernel related to this competition to public mode on release date with the link that they get in the submission form for example ?  \nI love watching what people decide to share during competitions (be it scripts, cheat sheets, insights, graphs) to get some inspiration, and I think they should not be forced to share their entire submission before the deadline, because it will have an impact on other participants.\n\n- And as said @pluto1717 how to avoid redundancy ?",
    "449269": "We don't have any guidelines for how you use Kernels or presentation slides, it's totally up to you. If it were me, I would probably use the slides to tell my story and communicate my results while using Kernels to crunch numbers and support my claims."
  },
  "source": "meta"
}