Hi Kagglers,
\nWe’re happy to announce the conclusion of the Open Problems – Single-Cell Perturbations competition. Thank you everyone for your participation!
\nThis competition ended with 6766 registrations and 1318 participants on 1097 teams. We had 25529 submissions from 85 countries. For 338 users (including 28 in the top 100!), this was their first competition. Thank you all for your hard work in this competition and congratulations to our winners and to those who gained a new ranking!
\nThe top potential winning teams will be contacted via email for the next steps. We look forward to learning more about their winning solutions.
\nWe've cleaned the leaderboard and disqualified some teams that have violated the rules. If you think you were removed by mistake, or believe you have evidence that suggests another team cheated, please contact compliance. Please fill in all the fields honestly.
\nWe highly encourage you to post a solution write-up about your approach and solution in the forums. We’re awarding swag to the 50 teams with the most upvotes on their solution write-ups two weeks after the competition’s final submission deadline.
\nTo be eligible, the solution write-ups must be linked as an official writeup (see instructions) and the write-up should meet the criteria outlined in our new quality rubric. We’re using upvotes as a measure of quality and helpfulness, please be sure you keep this in mind when upvoting others' work. Evidence of upvote gaming will result in disqualification and/or account banning. Details can be found here.
\nThanks for continuing to make Kaggle a great place to learn, practice, and test data science techniques!
\nHappy Modeling!
\nKaggle Team
Hi Kagglers,
\nWe’re happy to announce the conclusion of the Open Problems – Single-Cell Perturbations competition. Thank you everyone for your participation!
\nThis competition ended with 6766 registrations and 1318 participants on 1097 teams. We had 25529 submissions from 85 countries. For 338 users (including 28 in the top 100!), this was their first competition. Thank you all for your hard work in this competition and congratulations to our winners and to those who gained a new ranking!
\nThe top potential winning teams will be contacted via email for the next steps. We look forward to learning more about their winning solutions.
\nWe've cleaned the leaderboard and disqualified some teams that have violated the rules. If you think you were removed by mistake, or believe you have evidence that suggests another team cheated, please contact compliance. Please fill in all the fields honestly.
\nWe highly encourage you to post a solution write-up about your approach and solution in the forums. We’re awarding swag to the 50 teams with the most upvotes on their solution write-ups two weeks after the competition’s final submission deadline.
\nTo be eligible, the solution write-ups must be linked as an official writeup (see instructions) and the write-up should meet the criteria outlined in our new quality rubric. We’re using upvotes as a measure of quality and helpfulness, please be sure you keep this in mind when upvoting others' work. Evidence of upvote gaming will result in disqualification and/or account banning. Details can be found here.
\nThanks for continuing to make Kaggle a great place to learn, practice, and test data science techniques!
\nHappy Modeling!
\nKaggle Team
Could you tell us why our team was removed? We just went through everything we did and found no rule violations any of us are aware of. We also are just in the last steps of preparing our writeup and already set up connected public notebooks with which you can fully reproduce our results here https://www.kaggle.com/code/raki21/4th-place-magic-postprocessing/notebook.
", "rawMarkdown": "Could you tell us why our team was removed? We just went through everything we did and found no rule violations any of us are aware of. We also are just in the last steps of preparing our writeup and already set up connected public notebooks with which you can fully reproduce our results here https://www.kaggle.com/code/raki21/4th-place-magic-postprocessing/notebook.", "votes": null }, { "id": "2550357", "postDate": "12/06/2023 02:01:14", "content": "Thanks @raki21! Please feel free to contact compliance. Thanks!
", "rawMarkdown": "Thanks @raki21! Please feel free to contact [compliance](https://www.kaggle.com/compliance). Thanks!", "votes": null }, { "id": "2550954", "postDate": "12/06/2023 12:36:12", "content": "Hello! thank you for organising the competition.
\n@danielburkhardt will the full dataset be released? It would be interesting to learn what are the counts for validation data (similar content to adata_train.parquet).
", "rawMarkdown": "Hello! thank you for organising the competition.\n\n@danielburkhardt will the full dataset be released? It would be interesting to learn what are the counts for validation data (similar content to adata_train.parquet).", "votes": null }, { "id": "2554781", "postDate": "12/09/2023 12:02:14", "content": "Hi! Worry about your team. How it goes, did they provide a reason, a least? Your solution seems great and fair, sorry for the exclusion from the lb.
", "rawMarkdown": "Hi! Worry about your team. How it goes, did they provide a reason, a least? Your solution seems great and fair, sorry for the exclusion from the lb.", "votes": null }, { "id": "2555069", "postDate": "12/09/2023 16:44:40", "content": "Hi thanks for your sympathy! We are still writing with the admins, I hope we can resolve it soon and give an update.
", "rawMarkdown": "Hi thanks for your sympathy! We are still writing with the admins, I hope we can resolve it soon and give an update.", "votes": null } ], "comments": [ { "id": 2550126, "author_name": "raki21", "author_url": "", "post_date": "12/05/2023 19:49:05", "content": "Could you tell us why our team was removed? We just went through everything we did and found no rule violations any of us are aware of. We also are just in the last steps of preparing our writeup and already set up connected public notebooks with which you can fully reproduce our results here https://www.kaggle.com/code/raki21/4th-place-magic-postprocessing/notebook.
", "votes": null, "replies": [ { "id": 2550357, "author_name": "ashleychow", "author_url": "", "post_date": "12/06/2023 02:01:14", "content": "Thanks @raki21! Please feel free to contact compliance. Thanks!
", "votes": null, "replies": [] }, { "id": 2554781, "author_name": "antoninadolgorukova", "author_url": "", "post_date": "12/09/2023 12:02:14", "content": "Hi! Worry about your team. How it goes, did they provide a reason, a least? Your solution seems great and fair, sorry for the exclusion from the lb.
", "votes": null, "replies": [ { "id": 2555069, "author_name": "raki21", "author_url": "", "post_date": "12/09/2023 16:44:40", "content": "Hi thanks for your sympathy! We are still writing with the admins, I hope we can resolve it soon and give an update.
", "votes": null, "replies": [] } ] } ] }, { "id": 2550954, "author_name": "blazej0", "author_url": "", "post_date": "12/06/2023 12:36:12", "content": "Hello! thank you for organising the competition.
\n@danielburkhardt will the full dataset be released? It would be interesting to learn what are the counts for validation data (similar content to adata_train.parquet).
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "2550080": "Hi Kagglers,\n\nWe’re happy to announce the conclusion of the Open Problems – Single-Cell Perturbations competition. Thank you everyone for your participation!\n\nThis competition ended with 6766 registrations and 1318 participants on 1097 teams. We had 25529 submissions from 85 countries. For 338 users (including 28 in the top 100!), this was their first competition. Thank you all for your hard work in this competition and congratulations to our winners and to those who gained a new ranking! \n\nThe top potential winning teams will be contacted via email for the next steps. We look forward to learning more about their winning solutions.\n\nWe've cleaned the leaderboard and disqualified some teams that have violated the rules. If you think you were removed by mistake, or believe you have evidence that suggests another team cheated, please contact [compliance](https://www.kaggle.com/compliance). Please fill in all the fields honestly.\n\nWe highly encourage you to post a solution write-up about your approach and solution in the forums. We’re awarding swag to the 50 teams with the most upvotes on their solution write-ups two weeks after the competition’s final submission deadline.\n\nTo be eligible, the solution write-ups must be linked as an official writeup (see [instructions](https://www.kaggle.com/discussions/product-feedback/373153)) and the write-up should meet the criteria outlined in our [new quality rubric](https://www.kaggle.com/solution-write-up-documentation). We’re using upvotes as a measure of quality and helpfulness, please be sure you keep this in mind when upvoting others' work. Evidence of upvote gaming will result in disqualification and/or account banning. Details can be found [here](https://www.kaggle.com/discussions/general/427114).\n\nThanks for continuing to make Kaggle a great place to learn, practice, and test data science techniques!\n\nHappy Modeling!\nKaggle Team", "2550126": "Could you tell us why our team was removed? We just went through everything we did and found no rule violations any of us are aware of. We also are just in the last steps of preparing our writeup and already set up connected public notebooks with which you can fully reproduce our results here https://www.kaggle.com/code/raki21/4th-place-magic-postprocessing/notebook.", "2550357": "Thanks @raki21! Please feel free to contact [compliance](https://www.kaggle.com/compliance). Thanks!", "2550954": "Hello! thank you for organising the competition.\n\n@danielburkhardt will the full dataset be released? It would be interesting to learn what are the counts for validation data (similar content to adata_train.parquet).", "2554781": "Hi! Worry about your team. How it goes, did they provide a reason, a least? Your solution seems great and fair, sorry for the exclusion from the lb.", "2555069": "Hi thanks for your sympathy! We are still writing with the admins, I hope we can resolve it soon and give an update." }, "source": "meta" }