Dear all,
\n\nwe are approaching the final stage of this competition. We remind the most important dates:
\n\nFinal Submission Deadline on Kaggle: June 10, 2019 23:59 AoE\nNumber of submissions eligible for the final private leaderboard: 2
\n\nFinal Submission Deadline on DCASE Challenge: June 10, 2019 23:59 AoE\nThis submission includes a zip file with the following:\n- system output(s). You are allowed to submit up to 3 submissions: the two for the private Leaderboard on Kaggle, plus an additional submission for the Judges’ Award, according the Judges’ Award rules: \n- systems meta information (one yaml file per submission)\n- one technical report describing the system(s)
\n\nDetails can be found in http://dcase.community/challenge2019/submission including an example of Submission package.
\n\nIMPORTANT NOTE: Update of technical report for DCASE Challenge allowed until June 17, 2019\nAn updated camera-ready version of the technical report can be submitted separately until June 17, 2019 23:59 AoE. Nonetheless, the technical report in the submission package submitted on June 10, 2019 23:59 AoE must contain at least title, authors, and abstract. In this way, we hope you can focus on polishing your systems until June 10, and then you have one more week to write a high quality report, in order to facilitate reproducible research.
\n\nDCASE Workshop deadlines:
\n\nWorkshop paper abstract submission: July 05, 2019
\nWorkshop paper submission: July 12, 2019
\nMore info here: http://dcase.community/workshop2019/
A summary of the submission modes can be found in\nhttps://www.kaggle.com/c/freesound-audio-tagging-2019/overview/submission-modes
\n\nPlease place your questions and comments below in this thread.
\n\nLooking forward to your submissions!
\n\nEduardo, on behalf of the organizing team
", "messages": [ { "id": "546538", "postDate": "06/06/2019 16:55:29", "content": "Dear all,
\n\nwe are approaching the final stage of this competition. We remind the most important dates:
\n\nFinal Submission Deadline on Kaggle: June 10, 2019 23:59 AoE\nNumber of submissions eligible for the final private leaderboard: 2
\n\nFinal Submission Deadline on DCASE Challenge: June 10, 2019 23:59 AoE\nThis submission includes a zip file with the following:\n- system output(s). You are allowed to submit up to 3 submissions: the two for the private Leaderboard on Kaggle, plus an additional submission for the Judges’ Award, according the Judges’ Award rules: \n- systems meta information (one yaml file per submission)\n- one technical report describing the system(s)
\n\nDetails can be found in http://dcase.community/challenge2019/submission including an example of Submission package.
\n\nIMPORTANT NOTE: Update of technical report for DCASE Challenge allowed until June 17, 2019\nAn updated camera-ready version of the technical report can be submitted separately until June 17, 2019 23:59 AoE. Nonetheless, the technical report in the submission package submitted on June 10, 2019 23:59 AoE must contain at least title, authors, and abstract. In this way, we hope you can focus on polishing your systems until June 10, and then you have one more week to write a high quality report, in order to facilitate reproducible research.
\n\nDCASE Workshop deadlines:
\n\nWorkshop paper abstract submission: July 05, 2019
\nWorkshop paper submission: July 12, 2019
\nMore info here: http://dcase.community/workshop2019/
A summary of the submission modes can be found in\nhttps://www.kaggle.com/c/freesound-audio-tagging-2019/overview/submission-modes
\n\nPlease place your questions and comments below in this thread.
\n\nLooking forward to your submissions!
\n\nEduardo, on behalf of the organizing team
", "rawMarkdown": "Dear all, \n\nwe are approaching the final stage of this competition. We remind the most important dates:\n\n**Final Submission Deadline on Kaggle**: June 10, 2019 23:59 AoE\nNumber of submissions eligible for the final private leaderboard: 2\n\n---\n\n---\n\n**Final Submission Deadline on DCASE Challenge**: June 10, 2019 23:59 AoE\nThis submission includes a zip file with the following:\n- system output(s). You are allowed to submit **up to 3 submissions**: the two for the private Leaderboard on Kaggle, plus an additional submission for the Judges’ Award, according the [Judges’ Award rules](https://www.kaggle.com/c/freesound-audio-tagging-2019/overview/judges-award): \n- systems meta information (one yaml file per submission)\n- one technical report describing the system(s)\n\nDetails can be found in [http://dcase.community/challenge2019/submission](http://dcase.community/challenge2019/submission) including an example of Submission package.\n\n**IMPORTANT NOTE**: **Update of technical report for DCASE Challenge allowed until June 17, 2019**\nAn updated camera-ready version of the technical report can be submitted separately until June 17, 2019 23:59 AoE. Nonetheless, the technical report in the submission package submitted on June 10, 2019 23:59 AoE must contain at least title, authors, and abstract. In this way, we hope you can focus on polishing your systems until June 10, and then you have one more week to write a high quality report, in order to facilitate reproducible research.\n\n---\n\n---\n\n**DCASE Workshop deadlines**:\n\nWorkshop paper abstract submission: July 05, 2019 \nWorkshop paper submission: July 12, 2019 \nMore info here: http://dcase.community/workshop2019/\n\n---\n\n---\n\nA summary of the submission modes can be found in\nhttps://www.kaggle.com/c/freesound-audio-tagging-2019/overview/submission-modes\n\nPlease place your questions and comments below in this thread. \n\nLooking forward to your submissions!\n\nEduardo, on behalf of the organizing team", "votes": null }, { "id": "547101", "postDate": "06/07/2019 09:26:56", "content": "\n\n\nFinal Submission Deadline on Kaggle: June 10, 2019 23:59 AoE
\n
In Overview tab, you said \"June 10, 2019 11:59 AM UTC - Final submission deadline\".\nWhich one is really correct, AM or PM?
", "rawMarkdown": "> Final Submission Deadline on Kaggle: June 10, 2019 23:59 AoE\n\nIn Overview tab, you said \"June 10, 2019 11:59 AM UTC - Final submission deadline\".\nWhich one is really correct, AM or PM?", "votes": null }, { "id": "547414", "postDate": "06/07/2019 17:07:28", "content": "Hi,
\n\nEDIT: Indeed this is a matter of confusion!!
\n\nDCASE Challenge submission deadline is June 10, 2019 23:59 AoE (in approx 43 hours). There has been a small confusion with this and the UTC time zone specification, and due to that, the current Kaggle deadline reads 19 hours to go (one day less than what it should).
\n\nWe just realized this, and it will be corrected in the coming hours to make it June 10, 2019 23:59 AoE.
\n\nSorry about that.
", "rawMarkdown": "Hi, \n\nEDIT: Indeed this is a matter of confusion!!\n\n**DCASE Challenge submission deadline is June 10, 2019 23:59 AoE** (in approx 43 hours). There has been a small confusion with this and the UTC time zone specification, and due to that, the current Kaggle deadline reads 19 hours to go (one day less than what it should). \n\nWe just realized this, and it will be corrected in the coming hours to make it **June 10, 2019 23:59 AoE**. \n\nSorry about that.", "votes": null }, { "id": "547450", "postDate": "06/07/2019 18:20:12", "content": "Thank you for answering my question.\nI didn't understand AoE well. Now, I understand that.
", "rawMarkdown": "Thank you for answering my question.\nI didn't understand AoE well. Now, I understand that.", "votes": null }, { "id": "547647", "postDate": "06/08/2019 03:58:11", "content": "Is there a possibility to receive an extension for the whole challenge? This will be very helpful. Training models again will be possible as well to deliver comprehensive analysis.
", "rawMarkdown": "Is there a possibility to receive an extension for the whole challenge? This will be very helpful. Training models again will be possible as well to deliver comprehensive analysis.", "votes": null }, { "id": "547932", "postDate": "06/08/2019 14:30:32", "content": "I'm afraid the DCASE organization has decided not to extend the Challenge deadline.\nHowever, the technical report can be updated until one week after the deadline, as explained above.
", "rawMarkdown": "I'm afraid the DCASE organization has decided **not** to extend the Challenge deadline.\nHowever, the technical report can be updated until one week after the deadline, as explained above.", "votes": null }, { "id": "548757", "postDate": "06/09/2019 20:57:58", "content": "Reply to EDIT
\n\n@eduardofonseca \noh... OK. \nNow, true final Kaggle submission deadline is June 10, 2019 23:59 AoE. Is it means June 11, 2019 11:59 UTC ? Just in case.
\nSince Submission counts are calculated in UTC, do we have two more submissions?
This has now been corrected. The deadline is June 10, 2019 23:59 AoE, which is June 11, 2019 11:59 am UTC.
\n\nSubmissions reset at midnight UTC, therefore even though it's a \"half day\", participants still get 2 more submissions for that day.
\n\nThanks!
", "rawMarkdown": "This has now been corrected. The deadline is June 10, 2019 23:59 AoE, which is June 11, 2019 11:59 am UTC.\n\nSubmissions reset at midnight UTC, therefore even though it's a \"half day\", participants still get 2 more submissions for that day.\n\nThanks!", "votes": null }, { "id": "552417", "postDate": "06/13/2019 23:33:59", "content": "Hello @eduardofonseca ,\nI updated my technical report for DCASE2019 and I noticed in CMT that the \"Edit\" button turned into \"Create Camera Ready Submission\".\nCan you just confirm to me that we shall upload only the updated tech report (no csv file or yaml file)?
", "rawMarkdown": "Hello @eduardofonseca ,\nI updated my technical report for DCASE2019 and I noticed in CMT that the \"Edit\" button turned into \"Create Camera Ready Submission\".\nCan you just confirm to me that we shall upload only the updated tech report (no csv file or yaml file)?", "votes": null }, { "id": "552421", "postDate": "06/13/2019 23:43:07", "content": "Exactly, you only have to update the pdf of the technical report, and that's all. Thanks for submitting to DCASE and for your interesting work!
", "rawMarkdown": "Exactly, you only have to update the pdf of the technical report, and that's all. Thanks for submitting to DCASE and for your interesting work!", "votes": null }, { "id": "552593", "postDate": "06/14/2019 07:05:38", "content": "Thanks @eduardofonseca for clarification
", "rawMarkdown": "Thanks @eduardofonseca for clarification", "votes": null } ], "comments": [ { "id": 547101, "author_name": "d1348k", "author_url": "", "post_date": "06/07/2019 09:26:56", "content": "\n\n\nFinal Submission Deadline on Kaggle: June 10, 2019 23:59 AoE
\n
In Overview tab, you said \"June 10, 2019 11:59 AM UTC - Final submission deadline\".\nWhich one is really correct, AM or PM?
", "votes": null, "replies": [ { "id": 547414, "author_name": "eduardofonseca", "author_url": "", "post_date": "06/07/2019 17:07:28", "content": "Hi,
\n\nEDIT: Indeed this is a matter of confusion!!
\n\nDCASE Challenge submission deadline is June 10, 2019 23:59 AoE (in approx 43 hours). There has been a small confusion with this and the UTC time zone specification, and due to that, the current Kaggle deadline reads 19 hours to go (one day less than what it should).
\n\nWe just realized this, and it will be corrected in the coming hours to make it June 10, 2019 23:59 AoE.
\n\nSorry about that.
", "votes": null, "replies": [] }, { "id": 547450, "author_name": "d1348k", "author_url": "", "post_date": "06/07/2019 18:20:12", "content": "Thank you for answering my question.\nI didn't understand AoE well. Now, I understand that.
", "votes": null, "replies": [] }, { "id": 548757, "author_name": "d1348k", "author_url": "", "post_date": "06/09/2019 20:57:58", "content": "Reply to EDIT
\n\n@eduardofonseca \noh... OK. \nNow, true final Kaggle submission deadline is June 10, 2019 23:59 AoE. Is it means June 11, 2019 11:59 UTC ? Just in case.
\nSince Submission counts are calculated in UTC, do we have two more submissions?
This has now been corrected. The deadline is June 10, 2019 23:59 AoE, which is June 11, 2019 11:59 am UTC.
\n\nSubmissions reset at midnight UTC, therefore even though it's a \"half day\", participants still get 2 more submissions for that day.
\n\nThanks!
", "votes": null, "replies": [] } ] }, { "id": 547647, "author_name": "ankitpshah", "author_url": "", "post_date": "06/08/2019 03:58:11", "content": "Is there a possibility to receive an extension for the whole challenge? This will be very helpful. Training models again will be possible as well to deliver comprehensive analysis.
", "votes": null, "replies": [ { "id": 547932, "author_name": "eduardofonseca", "author_url": "", "post_date": "06/08/2019 14:30:32", "content": "I'm afraid the DCASE organization has decided not to extend the Challenge deadline.\nHowever, the technical report can be updated until one week after the deadline, as explained above.
", "votes": null, "replies": [] } ] }, { "id": 552417, "author_name": "ebouteillon", "author_url": "", "post_date": "06/13/2019 23:33:59", "content": "Hello @eduardofonseca ,\nI updated my technical report for DCASE2019 and I noticed in CMT that the \"Edit\" button turned into \"Create Camera Ready Submission\".\nCan you just confirm to me that we shall upload only the updated tech report (no csv file or yaml file)?
", "votes": null, "replies": [ { "id": 552421, "author_name": "eduardofonseca", "author_url": "", "post_date": "06/13/2019 23:43:07", "content": "Exactly, you only have to update the pdf of the technical report, and that's all. Thanks for submitting to DCASE and for your interesting work!
", "votes": null, "replies": [] }, { "id": 552593, "author_name": "ebouteillon", "author_url": "", "post_date": "06/14/2019 07:05:38", "content": "Thanks @eduardofonseca for clarification
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "546538": "Dear all, \n\nwe are approaching the final stage of this competition. We remind the most important dates:\n\n**Final Submission Deadline on Kaggle**: June 10, 2019 23:59 AoE\nNumber of submissions eligible for the final private leaderboard: 2\n\n---\n\n---\n\n**Final Submission Deadline on DCASE Challenge**: June 10, 2019 23:59 AoE\nThis submission includes a zip file with the following:\n- system output(s). You are allowed to submit **up to 3 submissions**: the two for the private Leaderboard on Kaggle, plus an additional submission for the Judges’ Award, according the [Judges’ Award rules](https://www.kaggle.com/c/freesound-audio-tagging-2019/overview/judges-award): \n- systems meta information (one yaml file per submission)\n- one technical report describing the system(s)\n\nDetails can be found in [http://dcase.community/challenge2019/submission](http://dcase.community/challenge2019/submission) including an example of Submission package.\n\n**IMPORTANT NOTE**: **Update of technical report for DCASE Challenge allowed until June 17, 2019**\nAn updated camera-ready version of the technical report can be submitted separately until June 17, 2019 23:59 AoE. Nonetheless, the technical report in the submission package submitted on June 10, 2019 23:59 AoE must contain at least title, authors, and abstract. In this way, we hope you can focus on polishing your systems until June 10, and then you have one more week to write a high quality report, in order to facilitate reproducible research.\n\n---\n\n---\n\n**DCASE Workshop deadlines**:\n\nWorkshop paper abstract submission: July 05, 2019 \nWorkshop paper submission: July 12, 2019 \nMore info here: http://dcase.community/workshop2019/\n\n---\n\n---\n\nA summary of the submission modes can be found in\nhttps://www.kaggle.com/c/freesound-audio-tagging-2019/overview/submission-modes\n\nPlease place your questions and comments below in this thread. \n\nLooking forward to your submissions!\n\nEduardo, on behalf of the organizing team", "547101": "> Final Submission Deadline on Kaggle: June 10, 2019 23:59 AoE\n\nIn Overview tab, you said \"June 10, 2019 11:59 AM UTC - Final submission deadline\".\nWhich one is really correct, AM or PM?", "547414": "Hi, \n\nEDIT: Indeed this is a matter of confusion!!\n\n**DCASE Challenge submission deadline is June 10, 2019 23:59 AoE** (in approx 43 hours). There has been a small confusion with this and the UTC time zone specification, and due to that, the current Kaggle deadline reads 19 hours to go (one day less than what it should). \n\nWe just realized this, and it will be corrected in the coming hours to make it **June 10, 2019 23:59 AoE**. \n\nSorry about that.", "547450": "Thank you for answering my question.\nI didn't understand AoE well. Now, I understand that.", "547647": "Is there a possibility to receive an extension for the whole challenge? This will be very helpful. Training models again will be possible as well to deliver comprehensive analysis.", "547932": "I'm afraid the DCASE organization has decided **not** to extend the Challenge deadline.\nHowever, the technical report can be updated until one week after the deadline, as explained above.", "548757": "Reply to EDIT \n\n@eduardofonseca \noh... OK. \nNow, true final **Kaggle submission** deadline is **June 10, 2019 23:59 AoE**. Is it means **June 11, 2019 11:59 UTC** ? Just in case. \nSince Submission counts are calculated in UTC, do we have two more submissions?", "548776": "This has now been corrected. The deadline is June 10, 2019 23:59 AoE, which is June 11, 2019 11:59 am UTC.\n\nSubmissions reset at midnight UTC, therefore even though it's a \"half day\", participants still get 2 more submissions for that day.\n\nThanks!", "552417": "Hello @eduardofonseca ,\nI updated my technical report for DCASE2019 and I noticed in CMT that the \"Edit\" button turned into \"Create Camera Ready Submission\".\nCan you just confirm to me that we shall upload only the updated tech report (no csv file or yaml file)?", "552421": "Exactly, you only have to update the pdf of the technical report, and that's all. Thanks for submitting to DCASE and for your interesting work!", "552593": "Thanks @eduardofonseca for clarification" }, "source": "meta" }