![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F863665%2F4c58bb54ea77edb383ac58fcf406a13b%2FScreenshot%202020-08-20%20at%2010.49.25.png?generation=1598433656634922&alt=media\")
Dear all,
\nI am writing this post to reach out to the hosts and the kaggle team.
\nI worked for several months on the competition. Both of my solutions are compliant. After the final leaderboard was revealed, I found myself winning the competition (# 1/2245). However, I quickly noticed a bug. My old scores were simply NOT updated because my notebooks were not reran on the new dataset for some reason. That is why my scores were higher than they should be. For more details and proof, please read my post about this bug
\nhttps://www.kaggle.com/c/global-wheat-detection/discussion/175927
For fairness, I immediately contacted about this bug to @philculliton , after which they simply removed me from the competition with no explanations. I emailed the kaggle team several times asking why I was removed from the competition, and why they would not just rerun my notebooks, and put me in the leaderboard no matter if I win a medal or not. Never heard back. I have filed 2 Kaggle Compliance reports already, with no answers as well (Not sure how many days it takes them to process the reports though).
\nI showed fairness, and in return I expect fairness and at least explanations from the kaggle team and the hosts. @philculliton @maggiemd @bendvd @stavness
\nUPD: https://www.kaggle.com/c/global-wheat-detection/discussion/176973
", "messages": [ { "id": 981065, "postDate": "2020-08-22T06:32:16.153Z", "content": "Dear all,
\nI am writing this post to reach out to the hosts and the kaggle team.
\nI worked for several months on the competition. Both of my solutions are compliant. After the final leaderboard was revealed, I found myself winning the competition (# 1/2245). However, I quickly noticed a bug. My old scores were simply NOT updated because my notebooks were not reran on the new dataset for some reason. That is why my scores were higher than they should be. For more details and proof, please read my post about this bug
\nhttps://www.kaggle.com/c/global-wheat-detection/discussion/175927
For fairness, I immediately contacted about this bug to @philculliton , after which they simply removed me from the competition with no explanations. I emailed the kaggle team several times asking why I was removed from the competition, and why they would not just rerun my notebooks, and put me in the leaderboard no matter if I win a medal or not. Never heard back. I have filed 2 Kaggle Compliance reports already, with no answers as well (Not sure how many days it takes them to process the reports though).
\nI showed fairness, and in return I expect fairness and at least explanations from the kaggle team and the hosts. @philculliton @maggiemd @bendvd @stavness
\nUPD: https://www.kaggle.com/c/global-wheat-detection/discussion/176973
", "rawMarkdown": "Dear all,\n\nI am writing this post to reach out to the hosts and the kaggle team. \n\nI worked for several months on the competition. Both of my solutions are compliant. After the final leaderboard was revealed, I found myself winning the competition (# 1/2245). However, I quickly noticed a bug. My old scores were simply NOT updated because my notebooks were not reran on the new dataset for some reason. That is why my scores were higher than they should be. For more details and proof, please read my post about this bug \nhttps://www.kaggle.com/c/global-wheat-detection/discussion/175927\n\nFor fairness, I immediately contacted about this bug to @philculliton , after which they simply removed me from the competition with no explanations. I emailed the kaggle team several times asking why I was removed from the competition, and why they would not just rerun my notebooks, and put me in the leaderboard no matter if I win a medal or not. Never heard back. I have filed 2 Kaggle Compliance reports already, with no answers as well (Not sure how many days it takes them to process the reports though). \n\nI showed fairness, and in return I expect fairness and at least explanations from the kaggle team and the hosts. @philculliton @maggiemd @bendvd @stavness \n\nUPD: https://www.kaggle.com/c/global-wheat-detection/discussion/176973", "votes": 321 }, { "id": 981855, "postDate": "2020-08-22T18:41:31.580Z", "content": "@philculliton @maggiemd @bendvd @stavness be fair!
", "rawMarkdown": "@philculliton @maggiemd @bendvd @stavness be fair!", "votes": 22 }, { "id": 982397, "postDate": "2020-08-23T10:35:28.793Z", "content": "I've already thought that all the problems in this competition are exhausted. So I was wrong. The hosts spawned a lot of problems such as the dirty train dataset, ambiguity with Yolov5, and the sudden rerun of the private dataset. However, I really respect them that they weren't afraid to solve all these problems. To be honest, I didn't believe that they would remove all the Yolov5 submissions but they did. Dear, hosts, you should understand that you have to do the job to the end and every mistake you do won't be ignored. You should show us your courage and make the right decision.
", "rawMarkdown": "I've already thought that all the problems in this competition are exhausted. So I was wrong. The hosts spawned a lot of problems such as the dirty train dataset, ambiguity with Yolov5, and the sudden rerun of the private dataset. However, I really respect them that they weren't afraid to solve all these problems. To be honest, I didn't believe that they would remove all the Yolov5 submissions but they did. Dear, hosts, you should understand that you have to do the job to the end and every mistake you do won't be ignored. You should show us your courage and make the right decision.", "votes": 13 }, { "id": 981120, "postDate": "2020-08-22T07:23:29.720Z", "content": "My team was also removed without any explanations, we just got two errors in the submersion page. What is the status and error messages of your selected two?
", "rawMarkdown": "My team was also removed without any explanations, we just got two errors in the submersion page. What is the status and error messages of your selected two?", "votes": 10 }, { "id": 981153, "postDate": "2020-08-22T08:10:35.230Z", "content": "", "rawMarkdown": "@inversion ", "votes": 7 }, { "id": 981148, "postDate": "2020-08-22T07:56:01.087Z", "content": "What a noble deed👍
", "rawMarkdown": "What a noble deed👍", "votes": 7 }, { "id": 981146, "postDate": "2020-08-22T07:53:44.387Z", "content": "Fairness to this guy!
", "rawMarkdown": "Fairness to this guy!", "votes": 8 }, { "id": 986195, "postDate": "2020-08-26T09:22:27.760Z", "content": "Hey @philculliton @maggiemd @bendvd @stavness,
\nMe and my teammate appreciate the effort put into removing the Yolov5 submissions.
Having said that, we cannot find ourselves on the leaderboard. Both of our submissions seem to have been invalidated with a failed final private rerun error message. We have used the MIT-compliant EfficientDet for both submissions with different ensembling methods. As of 19/08/2020, we could find our submissions on the leaderboard but they have been removed since then. We are also sure that the runtime of our models is <6h because we have made multiple submissions (80+) before our final submission.
We submitted a complaint to the compliance team on 20/08/2020 and have not gotten a response yet. What is your timeline for handling these complaints?
\nWe'd appreciate your help in the matter because like many other participants here, we have put in multiple months of effort and worked only on compliant solutions.
\n
With the update to the new test data there were some kernels that failed to run or failed to complete. We tried several times and the kernels did not work so there was nothing to report back to the leaderboard.
", "rawMarkdown": "With the update to the new test data there were some kernels that failed to run or failed to complete. We tried several times and the kernels did not work so there was nothing to report back to the leaderboard. ", "votes": 2 } ] }, { "id": 992153, "postDate": "2020-08-31T01:49:55.787Z", "content": "I can feel the same sadness as you, because our team encountered the same situation. But from another point of view, you are also lucky, because both of your posts have been replied by the kaggle official team (I think because their popularity has reached the top of the kaggle discussion forum). But for us, all the posts (six or seven) published by our team have not received any reply from kaggle. This feeling is really bad.
\nIf possible, I hope anyone who sees this discussion can also have a look to our situation here
", "rawMarkdown": "I can feel the same sadness as you, because our team encountered the same situation. But from another point of view, you are also lucky, because both of your posts have been replied by the kaggle official team (I think because their popularity has reached the top of the kaggle discussion forum). But for us, all the posts (six or seven) published by our team have not received any reply from kaggle. This feeling is really bad.\n\nIf possible, I hope anyone who sees this discussion can also have a look to [our situation here](https://www.kaggle.com/c/global-wheat-detection/discussion/177757)", "votes": 6 }, { "id": 981661, "postDate": "2020-08-22T16:05:09.800Z", "content": "Hopefully you will be back in the leaderboard.
", "rawMarkdown": "Hopefully you will be back in the leaderboard.", "votes": 6 }, { "id": 981212, "postDate": "2020-08-22T09:24:23.303Z", "content": "Kaggle team and hosts MUST take action in such unfair situation! Rerun the submissions and return Aidyn to the leaderboard
", "rawMarkdown": "Kaggle team and hosts MUST take action in such unfair situation! Rerun the submissions and return Aidyn to the leaderboard", "votes": 6 }, { "id": 982296, "postDate": "2020-08-23T08:30:27.893Z", "content": "This is so unfair. Kaggle must take immediate action in such cases. After working for months and then getting removed without any reason is unacceptable.
", "rawMarkdown": "This is so unfair. Kaggle must take immediate action in such cases. After working for months and then getting removed without any reason is unacceptable. ", "votes": 3 }, { "id": 981393, "postDate": "2020-08-22T12:18:11.860Z", "content": "It would be great if there is a list of all removed teams and the reasons.
", "rawMarkdown": "It would be great if there is a list of all removed teams and the reasons.", "votes": 3, "replies": [ { "id": 981711, "postDate": "2020-08-22T16:40:31Z", "content": "I know right? I've been contacting Kaggle too since the great purge through multiple avenues and have insofar been met with the same stonewalling. It's one thing to get DQ'd because you did something wrong. It's another thing to get DQ'd for apparently no fault of your own, and then get completely ignored. That's hurtful.
", "rawMarkdown": "I know right? I've been contacting Kaggle too since the great purge through multiple avenues and have insofar been met with the same stonewalling. It's one thing to get DQ'd because you did something wrong. It's another thing to get DQ'd for apparently no fault of your own, and then get completely ignored. That's hurtful.", "votes": 5 } ] }, { "id": 981354, "postDate": "2020-08-22T11:41:03.330Z", "content": "It's always sad to hear that someone is being removed from the competition, though he didn’t violate any rules. I hope that Kaggle team will deal with it as soon as possible, since it not only undermines beliefs in fairness of these competitions, but forces people to behave dishonesty
", "rawMarkdown": "It's always sad to hear that someone is being removed from the competition, though he didn’t violate any rules. I hope that Kaggle team will deal with it as soon as possible, since it not only undermines beliefs in fairness of these competitions, but forces people to behave dishonesty ", "votes": 3, "replies": [ { "id": 981719, "postDate": "2020-08-22T16:45:53.757Z", "content": "There is one more con: since they're delaying this much (today is the 18th day after the original competition end date), even if they do reinstate the LB positions of those people who were incorrectly removed, it would result in some other people now losing their medals or minimally positions. So it's not just hurtful towards the people who were mistakenly removed, but also hurtful to the entire LB since a lot of people will drop ranks (and points) after the erroneously removed submissions are reinstated. Justice delayed is justice denied.
", "rawMarkdown": "There is one more con: since they're delaying this much (today is the 18th day after the original competition end date), even if they do reinstate the LB positions of those people who were incorrectly removed, it would result in some other people now losing their medals or minimally positions. So it's not just hurtful towards the people who were mistakenly removed, but also hurtful to the entire LB since a lot of people will drop ranks (and points) after the erroneously removed submissions are reinstated. Justice delayed is justice denied.", "votes": 2 } ] }, { "id": 997069, "postDate": "2020-09-03T18:15:40.747Z", "content": "Hi all,
\nKaggle wants to acknowledge this post and provide some background on what you can expect in situations like this.
\nThe participant contacted Kaggle to let us know there was an issue. We responded by thanking them for their email.
\nUnfortunately, their notebooks could not be successfully re-run before the close of the competition. Their notebooks (and any other selected notebooks that failed) were re-run 6 times in an attempt to make sure any external factors were controlled. We have evidence that the user removed their datasets immediately after running the notebooks. This ensured the code could not be re-run properly. In the end, their selected submissions were invalidated because they could not be rescored on the updated test set. With all of their submissions invalidated, they no longer appeared on the leaderboard.
\nAll selected notebooks went through the exact same process, and were subjected to the same level of scrutiny. All notebooks that failed for any reason were re-run. In the event those notebooks could not ultimately be rescored against the updated test set, their submissions were invalidated.
\nThe participant contacted Kaggle compliance, and went through our compliance process. Their complaints were investigated and their request was answered. This is the standard process for competition complaints.
\nPlease note that contacting individual Kaggle team members is not the standard process and there is no guarantee that we will see your issue. Please contact Kaggle compliance to ensure that your issue is seen by our team. Also, we ask that you give us some time to respond to your requests. We take compliance requests very seriously and sometimes they take us some time to respond. Thank you for your understanding and support.
", "rawMarkdown": "Hi all,\n\nKaggle wants to acknowledge this post and provide some background on what you can expect in situations like this.\n\nThe participant contacted Kaggle to let us know there was an issue. We responded by thanking them for their email.\n\nUnfortunately, their notebooks could not be successfully re-run before the close of the competition. Their notebooks (and any other selected notebooks that failed) were re-run 6 times in an attempt to make sure any external factors were controlled. We have evidence that the user removed their datasets immediately after running the notebooks. This ensured the code could not be re-run properly. In the end, their selected submissions were invalidated because they could not be rescored on the updated test set. With all of their submissions invalidated, they no longer appeared on the leaderboard.\n\nAll selected notebooks went through the exact same process, and were subjected to the same level of scrutiny. All notebooks that failed for any reason were re-run. In the event those notebooks could not ultimately be rescored against the updated test set, their submissions were invalidated.\n\nThe participant contacted Kaggle compliance, and went through our compliance process. Their complaints were investigated and their request was answered. This is the standard process for competition complaints.\n\nPlease note that contacting individual Kaggle team members is _not_ the standard process and there is no guarantee that we will see your issue. Please contact Kaggle compliance to ensure that your issue is seen by our team. Also, we ask that you give us some time to respond to your requests. We take compliance requests very seriously and sometimes they take us some time to respond. Thank you for your understanding and support.\n", "votes": 4 }, { "id": 984228, "postDate": "2020-08-25T01:00:57.263Z", "content": "This platform needs more people like you and instead of being punished you should be commended.
", "rawMarkdown": "This platform needs more people like you and instead of being punished you should be commended.", "votes": 4 }, { "id": 982329, "postDate": "2020-08-23T09:07:51.493Z", "content": "My friend's team was also removed from the LB. He contacted the Kaggle compliance team and complained about the low-quality of host & data in the post-competition survey. Guess what? His account was blocked in the name of \"cheating\". He's still trying to argue with the compliance team to get his account reinstalled…Given on his experience, I'd suggest you just let it go….
", "rawMarkdown": "My friend's team was also removed from the LB. He contacted the Kaggle compliance team and complained about the low-quality of host & data in the post-competition survey. Guess what? His account was blocked in the name of \"cheating\". He's still trying to argue with the compliance team to get his account reinstalled...Given on his experience, I'd suggest you just let it go....", "votes": 4 }, { "id": 981418, "postDate": "2020-08-22T12:37:01.863Z", "content": "@philculliton @maggiemd @bendvd @stavness! Please respond.
", "rawMarkdown": "@philculliton @maggiemd @bendvd @stavness! Please respond. ", "votes": 4 }, { "id": 981175, "postDate": "2020-08-22T08:37:11.527Z", "content": "Justice for this guy
", "rawMarkdown": "Justice for this guy", "votes": 4 }, { "id": 986764, "postDate": "2020-08-26T19:02:26.097Z", "content": "Did you try contacting kaggle through any other means, other than emails?
", "rawMarkdown": "Did you try contacting kaggle through any other means, other than emails?", "votes": 1, "replies": [ { "id": 1051831, "postDate": "2020-10-17T01:12:34.507Z", "rawMarkdown": "", "isDeleted": true } ] }, { "id": 982570, "postDate": "2020-08-23T13:43:55.570Z", "content": "This is pretty sad and unfair tbh.
", "rawMarkdown": "This is pretty sad and unfair tbh.", "votes": 1 }, { "id": 981605, "postDate": "2020-08-22T15:30:35.593Z", "content": "This is not fair! Your submit records are simply wiped out. I can't imagine how this could happen in a Kaggle competition?
", "rawMarkdown": "This is not fair! Your submit records are simply wiped out. I can't imagine how this could happen in a Kaggle competition?", "votes": 1, "replies": [ { "id": 982101, "postDate": "2020-08-23T04:15:01.290Z", "rawMarkdown": "", "votes": 3, "isDeleted": true }, { "id": 982108, "postDate": "2020-08-23T04:32:53.587Z", "content": "Thanks for response. Just try to keep this post atop.
", "rawMarkdown": "Thanks for response. Just try to keep this post atop.", "votes": 1 } ] }, { "id": 984017, "postDate": "2020-08-24T19:09:59.497Z", "content": "I'm sorry to see this. I think some work on resolution to keep a dedicated Kaggle user in the running would make sense. I am glad you shared with us so that we can watch out for this on our own work.
", "rawMarkdown": "I'm sorry to see this. I think some work on resolution to keep a dedicated Kaggle user in the running would make sense. I am glad you shared with us so that we can watch out for this on our own work.", "votes": 2 }, { "id": 982484, "postDate": "2020-08-23T12:08:22.953Z", "content": "@aidynub This is absolutely unacceptable ! Why none of the Kaggle moderators are involved ?!
", "rawMarkdown": "@aidynub This is absolutely unacceptable ! Why none of the Kaggle moderators are involved ?!", "votes": 2 }, { "id": 982346, "postDate": "2020-08-23T09:40:06.143Z", "content": "The act of honesty is enough for them to follow suit and not just kick the young man of the competition. That's really bad and uncalled for.
\n@philculliton @maggiemd @bendvd @stavness you four should have a rethink about this.
", "rawMarkdown": "The act of honesty is enough for them to follow suit and not just kick the young man of the competition. That's really bad and uncalled for. \n\n@philculliton @maggiemd @bendvd @stavness you four should have a rethink about this.", "votes": 2 }, { "id": 981442, "postDate": "2020-08-22T12:52:57.713Z", "content": "It's sad. You could have won that competition.
", "rawMarkdown": "It's sad. You could have won that competition.", "votes": 2, "replies": [ { "id": 981716, "postDate": "2020-08-22T16:43:42.340Z", "content": "I don't know about winning—but he should at least be ranked.
", "rawMarkdown": "I don't know about winning—but he should at least be ranked.", "votes": 2 } ] }, { "id": 981176, "postDate": "2020-08-22T08:37:14.877Z", "content": "Justice for this guy
", "rawMarkdown": "Justice for this guy", "votes": 2 }, { "id": 982288, "postDate": "2020-08-23T08:21:51.013Z", "content": "@philculliton @maggiemd @bendvd @stavness! Please respond.
", "rawMarkdown": "@philculliton @maggiemd @bendvd @stavness! Please respond.", "votes": 1 }, { "id": 983016, "postDate": "2020-08-24T00:32:48.360Z", "content": "I responded to you directly with the details.
", "rawMarkdown": "I responded to you directly with the details. ", "replies": [ { "id": 983217, "postDate": "2020-08-24T05:40:21.803Z", "content": "I sent you an email with exhaustive details. Please look into it …
", "rawMarkdown": "I sent you an email with exhaustive details. Please look into it ...", "votes": 4 } ] }, { "id": 981607, "postDate": "2020-08-22T15:30:55.017Z", "content": "That is sad but you should contact Kaggle support teams in such a situation. They might help you.
", "rawMarkdown": "That is sad but you should contact Kaggle support teams in such a situation. They might help you.", "votes": -9, "replies": [ { "id": 982099, "postDate": "2020-08-23T04:13:28.063Z", "content": "Please, read carefully what he is writing. He already tried to contact them many times, but couldn't reach.
", "rawMarkdown": "Please, read carefully what he is writing. He already tried to contact them many times, but couldn't reach.", "votes": 2 } ] }, { "id": 995599, "postDate": "2020-09-02T15:45:22.063Z", "content": "I hope anyone who sees the discussion
", "rawMarkdown": "I hope anyone who sees the discussion", "votes": -2 }, { "id": 995591, "postDate": "2020-09-02T15:38:40.493Z", "content": "Nice people here.. hello to everybody
", "rawMarkdown": "Nice people here.. hello to everybody", "votes": -1 }, { "id": 995590, "postDate": "2020-09-02T15:38:38.180Z", "content": "Nice people here.. hello to everybody
", "rawMarkdown": "Nice people here.. hello to everybody", "votes": -1 }, { "id": 991248, "postDate": "2020-08-30T09:08:01.113Z", "content": "Hello awesome people
", "rawMarkdown": "Hello awesome people ", "votes": -3 }, { "id": 988231, "postDate": "2020-08-27T22:40:35.563Z", "content": "Thank you for your perspective Aidyn, as we discussed we ended up with limited choices and appreciate your post here.
", "rawMarkdown": "Thank you for your perspective Aidyn, as we discussed we ended up with limited choices and appreciate your post [here.](https://www.kaggle.com/c/global-wheat-detection/discussion/176973) ", "votes": -12 }, { "id": 1000293, "postDate": "2020-09-06T12:53:56.987Z", "content": "Looking forward to learn.
", "rawMarkdown": "Looking forward to learn. " }, { "id": 999979, "postDate": "2020-09-06T07:17:34.093Z", "content": "Kaggle should give justification this
", "rawMarkdown": "Kaggle should give justification this\n" }, { "id": 999566, "postDate": "2020-09-05T18:59:41.233Z", "content": "I'm sure it will all work out💕
", "rawMarkdown": "I'm sure it will all work out💕" }, { "id": 997587, "postDate": "2020-09-04T05:53:00.933Z", "content": "super
", "rawMarkdown": "super" }, { "id": 997349, "postDate": "2020-09-04T01:32:21.763Z", "content": "nice job 👍👍👍👍
", "rawMarkdown": "nice job 👍👍👍👍" }, { "id": 995869, "postDate": "2020-09-02T22:19:26.647Z", "content": "Sad to hear. I hope Kaggle team will solve your problem as soon as possible. Keep up the good work!
", "rawMarkdown": "Sad to hear. I hope Kaggle team will solve your problem as soon as possible. Keep up the good work!" }, { "id": 995177, "postDate": "2020-09-02T08:04:49.990Z", "content": "it's osm i liked it
", "rawMarkdown": "it's osm i liked it" }, { "id": 994746, "postDate": "2020-09-01T22:30:31.863Z", "content": "How frustrating. Please update us if a resolution is reached, because it sounds like others have had similar problems in this competition.
", "rawMarkdown": "How frustrating. Please update us if a resolution is reached, because it sounds like others have had similar problems in this competition." }, { "id": 994303, "postDate": "2020-09-01T14:06:55.353Z", "content": "Sad to hear
", "rawMarkdown": "Sad to hear" }, { "id": 994025, "postDate": "2020-09-01T10:07:33.613Z", "content": "looking forward to learn
", "rawMarkdown": "looking forward to learn" }, { "id": 993630, "postDate": "2020-09-01T04:45:36.563Z", "content": "I'm also suffer for same
", "rawMarkdown": "I'm also suffer for same" }, { "id": 993533, "postDate": "2020-09-01T02:15:30.627Z", "content": "nice very nice
", "rawMarkdown": "nice very nice" }, { "id": 993499, "postDate": "2020-09-01T01:26:06.927Z", "content": "You did a great job Aidyn, and you should be rewarded for your hard working. We can win by cheating but we can only gain skills by honesty and hard working. Good luck👍
", "rawMarkdown": "You did a great job Aidyn, and you should be rewarded for your hard working. We can win by cheating but we can only gain skills by honesty and hard working. Good luck👍" }, { "id": 993359, "postDate": "2020-08-31T21:29:34.283Z", "content": "Kaggle need more people like you who are honest and they should not have removed you from the competition
", "rawMarkdown": "Kaggle need more people like you who are honest and they should not have removed you from the competition" }, { "id": 992860, "postDate": "2020-08-31T13:39:34.287Z", "content": "Beyond offering you my sympathies, I can't offer any other help other than asking Kaggle staff to look into this and compensate in some way. You missed out on a good opportunity.
", "rawMarkdown": "Beyond offering you my sympathies, I can't offer any other help other than asking Kaggle staff to look into this and compensate in some way. You missed out on a good opportunity." }, { "id": 992603, "postDate": "2020-08-31T09:19:56.190Z", "content": "It's not fair
", "rawMarkdown": "\nIt's not fair" }, { "id": 991724, "postDate": "2020-08-30T16:11:15.277Z", "content": "Keep up the good work!
", "rawMarkdown": "Keep up the good work!" }, { "id": 991461, "postDate": "2020-08-30T12:28:57.790Z", "content": "I'm sorry to hear this. Hope you can have some sort of reimbursement at a later stage. Thanks for sharing your experience, I think this will ring a bell to everyone for later competitions
", "rawMarkdown": "I'm sorry to hear this. Hope you can have some sort of reimbursement at a later stage. Thanks for sharing your experience, I think this will ring a bell to everyone for later competitions" }, { "id": 990990, "postDate": "2020-08-30T03:06:41.317Z", "content": "Fairness !
", "rawMarkdown": "Fairness !" }, { "id": 990941, "postDate": "2020-08-30T01:30:49.030Z", "content": "That's really sucks ! I hope all ended up well. Thank you for share all of this mate ! You are a good guy !
", "rawMarkdown": "That's really sucks ! I hope all ended up well. Thank you for share all of this mate ! You are a good guy !" }, { "id": 990418, "postDate": "2020-08-29T15:32:17.977Z", "content": "I'm sorry to see this
", "rawMarkdown": "I'm sorry to see this" }, { "id": 990232, "postDate": "2020-08-29T12:59:25.050Z", "content": "This is bad. They shouldn't do this to you. We should appreciate the good things.
", "rawMarkdown": "This is bad. They shouldn't do this to you. We should appreciate the good things. " }, { "id": 989412, "postDate": "2020-08-28T19:09:14.933Z", "content": "You would have worked really hard for that. I guess that's not fair in the Data Science community, where doing new things is data is the prime motto. You will achieve what you deserve
", "rawMarkdown": "You would have worked really hard for that. I guess that's not fair in the Data Science community, where doing new things is data is the prime motto. You will achieve what you deserve " }, { "id": 989010, "postDate": "2020-08-28T13:50:33.227Z", "content": "Dear @aidynub,
\nIt is shocking to new kagglers who wanna jump into the competition and get motivated based on results announced.
\nGood, you pointed out, Faith must be restored.
i hope they help you !
", "rawMarkdown": "i hope they help you !" }, { "id": 987608, "postDate": "2020-08-27T11:47:03.860Z", "content": "Please help me, I don't know how to do this into executable work.
", "rawMarkdown": "Please help me, I don't know how to do this into executable work." }, { "id": 986835, "postDate": "2020-08-26T20:25:41.330Z", "content": "If that's true it's really upsetting! Hopefully they will put you at scoreboard at least!
", "rawMarkdown": "If that's true it's really upsetting! Hopefully they will put you at scoreboard at least!" }, { "id": 986330, "postDate": "2020-08-26T11:40:40.563Z", "content": "got really sad after reading this
", "rawMarkdown": "got really sad after reading this" }, { "id": 986011, "postDate": "2020-08-26T06:35:33.620Z", "content": "After a lot of hard work, this is simply not fair. I hope you get back in the leaderboard.
", "rawMarkdown": "After a lot of hard work, this is simply not fair. I hope you get back in the leaderboard." }, { "id": 985780, "postDate": "2020-08-26T02:28:39.957Z", "content": "I'm sorry to hear that.
", "rawMarkdown": "I'm sorry to hear that." }, { "id": 985660, "postDate": "2020-08-25T23:05:46.983Z", "content": "I'm sorry to hear this. Thanks for sharing.
", "rawMarkdown": "I'm sorry to hear this. Thanks for sharing." }, { "id": 985339, "postDate": "2020-08-25T16:54:53.893Z", "content": "very sorry to see this
", "rawMarkdown": "very sorry to see this" }, { "id": 984377, "postDate": "2020-08-25T04:21:39.877Z", "content": "Yeah, sure there must be an explaination from the kaggle.
\n@philculliton @maggiemd @bendvd @stavness please rethink
This was sad to hear, you got any response yet ? 😅
", "rawMarkdown": "This was sad to hear, you got any response yet ? 😅" }, { "id": 983382, "postDate": "2020-08-24T08:59:18.597Z", "content": "Yes, I feel this needs some attention from the moderators.
", "rawMarkdown": "Yes, I feel this needs some attention from the moderators." }, { "id": 983174, "postDate": "2020-08-24T05:07:37.440Z", "content": "……………………………..
", "rawMarkdown": "..................................." }, { "id": 983019, "postDate": "2020-08-24T00:34:34.923Z", "content": "Well that definitely doesn't seem right to me.
", "rawMarkdown": "Well that definitely doesn't seem right to me." }, { "id": 1000446, "postDate": "2020-09-06T14:29:03.127Z", "rawMarkdown": "", "votes": -1, "isDeleted": true }, { "id": 994067, "postDate": "2020-09-01T10:46:40.487Z", "rawMarkdown": "", "isDeleted": true }, { "id": 993273, "postDate": "2020-08-31T19:45:52.810Z", "rawMarkdown": "", "isDeleted": true }, { "id": 987678, "postDate": "2020-08-27T12:43:55.340Z", "rawMarkdown": "", "isDeleted": true }, { "id": 983018, "postDate": "2020-08-24T00:33:59.627Z", "rawMarkdown": "", "isDeleted": true }, { "id": 982962, "postDate": "2020-08-23T21:57:34.347Z", "rawMarkdown": "", "votes": 1, "isDeleted": true }, { "id": 981832, "postDate": "2020-08-22T18:19:39.243Z", "rawMarkdown": "", "votes": -4, "isDeleted": true }, { "id": 988691, "postDate": "2020-08-28T07:51:38.640Z", "content": "Thanks for sharing.
", "rawMarkdown": "Thanks for sharing." }, { "id": 987262, "postDate": "2020-08-27T05:58:29.087Z", "content": "…………Thanks for sharing.
", "rawMarkdown": "............Thanks for sharing." }, { "id": 984639, "postDate": "2020-08-25T07:45:31.527Z", "content": "thank for us
", "rawMarkdown": "thank for us" } ], "comments": [ { "id": 981855, "author_name": "Yury Kashnitsky", "author_url": "", "post_date": "2020-08-22T18:41:31.580000", "content": "@philculliton @maggiemd @bendvd @stavness be fair!
", "votes": 22, "replies": [] }, { "id": 982397, "author_name": "Vadim Timakin", "author_url": "", "post_date": "2020-08-23T10:35:28.793000", "content": "I've already thought that all the problems in this competition are exhausted. So I was wrong. The hosts spawned a lot of problems such as the dirty train dataset, ambiguity with Yolov5, and the sudden rerun of the private dataset. However, I really respect them that they weren't afraid to solve all these problems. To be honest, I didn't believe that they would remove all the Yolov5 submissions but they did. Dear, hosts, you should understand that you have to do the job to the end and every mistake you do won't be ignored. You should show us your courage and make the right decision.
", "votes": 13, "replies": [] }, { "id": 981120, "author_name": "Qingyuan Wang", "author_url": "", "post_date": "2020-08-22T07:23:29.720000", "content": "My team was also removed without any explanations, we just got two errors in the submersion page. What is the status and error messages of your selected two?
", "votes": 10, "replies": [] }, { "id": 981153, "author_name": "Artyom Palvelev", "author_url": "", "post_date": "2020-08-22T08:10:35.230000", "content": "", "votes": 7, "replies": [] }, { "id": 981148, "author_name": "Zhanseri Ikram", "author_url": "", "post_date": "2020-08-22T07:56:01.087000", "content": "What a noble deed👍
", "votes": 7, "replies": [] }, { "id": 981146, "author_name": "Jin (Jimmy) Yamazaki", "author_url": "", "post_date": "2020-08-22T07:53:44.387000", "content": "Fairness to this guy!
", "votes": 8, "replies": [] }, { "id": 986195, "author_name": "Vaibhav Mehrotra", "author_url": "", "post_date": "2020-08-26T09:22:27.760000", "content": "Hey @philculliton @maggiemd @bendvd @stavness,
\nMe and my teammate appreciate the effort put into removing the Yolov5 submissions.
Having said that, we cannot find ourselves on the leaderboard. Both of our submissions seem to have been invalidated with a failed final private rerun error message. We have used the MIT-compliant EfficientDet for both submissions with different ensembling methods. As of 19/08/2020, we could find our submissions on the leaderboard but they have been removed since then. We are also sure that the runtime of our models is <6h because we have made multiple submissions (80+) before our final submission.
We submitted a complaint to the compliance team on 20/08/2020 and have not gotten a response yet. What is your timeline for handling these complaints?
\nWe'd appreciate your help in the matter because like many other participants here, we have put in multiple months of effort and worked only on compliant solutions.
\n
With the update to the new test data there were some kernels that failed to run or failed to complete. We tried several times and the kernels did not work so there was nothing to report back to the leaderboard.
", "votes": 2, "replies": [] } ] }, { "id": 992153, "author_name": "Dapeng", "author_url": "", "post_date": "2020-08-31T01:49:55.787000", "content": "I can feel the same sadness as you, because our team encountered the same situation. But from another point of view, you are also lucky, because both of your posts have been replied by the kaggle official team (I think because their popularity has reached the top of the kaggle discussion forum). But for us, all the posts (six or seven) published by our team have not received any reply from kaggle. This feeling is really bad.
\nIf possible, I hope anyone who sees this discussion can also have a look to our situation here
", "votes": 6, "replies": [] }, { "id": 981661, "author_name": "SubhamNagar", "author_url": "", "post_date": "2020-08-22T16:05:09.800000", "content": "Hopefully you will be back in the leaderboard.
", "votes": 6, "replies": [] }, { "id": 981212, "author_name": "Maksim Zhdanov", "author_url": "", "post_date": "2020-08-22T09:24:23.303000", "content": "Kaggle team and hosts MUST take action in such unfair situation! Rerun the submissions and return Aidyn to the leaderboard
", "votes": 6, "replies": [] }, { "id": 982296, "author_name": "Anurag Mishra", "author_url": "", "post_date": "2020-08-23T08:30:27.893000", "content": "This is so unfair. Kaggle must take immediate action in such cases. After working for months and then getting removed without any reason is unacceptable.
", "votes": 3, "replies": [] }, { "id": 981393, "author_name": "Dmitry Fomin", "author_url": "", "post_date": "2020-08-22T12:18:11.860000", "content": "It would be great if there is a list of all removed teams and the reasons.
", "votes": 3, "replies": [ { "id": 981711, "author_name": "عثمان", "author_url": "", "post_date": "2020-08-22T16:40:31", "content": "I know right? I've been contacting Kaggle too since the great purge through multiple avenues and have insofar been met with the same stonewalling. It's one thing to get DQ'd because you did something wrong. It's another thing to get DQ'd for apparently no fault of your own, and then get completely ignored. That's hurtful.
", "votes": 5, "replies": [] } ] }, { "id": 981354, "author_name": "Ivan", "author_url": "", "post_date": "2020-08-22T11:41:03.330000", "content": "It's always sad to hear that someone is being removed from the competition, though he didn’t violate any rules. I hope that Kaggle team will deal with it as soon as possible, since it not only undermines beliefs in fairness of these competitions, but forces people to behave dishonesty
", "votes": 3, "replies": [ { "id": 981719, "author_name": "عثمان", "author_url": "", "post_date": "2020-08-22T16:45:53.757000", "content": "There is one more con: since they're delaying this much (today is the 18th day after the original competition end date), even if they do reinstate the LB positions of those people who were incorrectly removed, it would result in some other people now losing their medals or minimally positions. So it's not just hurtful towards the people who were mistakenly removed, but also hurtful to the entire LB since a lot of people will drop ranks (and points) after the erroneously removed submissions are reinstated. Justice delayed is justice denied.
", "votes": 2, "replies": [] } ] }, { "id": 997069, "author_name": "Phil Culliton", "author_url": "", "post_date": "2020-09-03T18:15:40.747000", "content": "Hi all,
\nKaggle wants to acknowledge this post and provide some background on what you can expect in situations like this.
\nThe participant contacted Kaggle to let us know there was an issue. We responded by thanking them for their email.
\nUnfortunately, their notebooks could not be successfully re-run before the close of the competition. Their notebooks (and any other selected notebooks that failed) were re-run 6 times in an attempt to make sure any external factors were controlled. We have evidence that the user removed their datasets immediately after running the notebooks. This ensured the code could not be re-run properly. In the end, their selected submissions were invalidated because they could not be rescored on the updated test set. With all of their submissions invalidated, they no longer appeared on the leaderboard.
\nAll selected notebooks went through the exact same process, and were subjected to the same level of scrutiny. All notebooks that failed for any reason were re-run. In the event those notebooks could not ultimately be rescored against the updated test set, their submissions were invalidated.
\nThe participant contacted Kaggle compliance, and went through our compliance process. Their complaints were investigated and their request was answered. This is the standard process for competition complaints.
\nPlease note that contacting individual Kaggle team members is not the standard process and there is no guarantee that we will see your issue. Please contact Kaggle compliance to ensure that your issue is seen by our team. Also, we ask that you give us some time to respond to your requests. We take compliance requests very seriously and sometimes they take us some time to respond. Thank you for your understanding and support.
", "votes": 4, "replies": [] }, { "id": 984228, "author_name": "Rishi Damarla", "author_url": "", "post_date": "2020-08-25T01:00:57.263000", "content": "This platform needs more people like you and instead of being punished you should be commended.
", "votes": 4, "replies": [] }, { "id": 982329, "author_name": "豆柴金鯱", "author_url": "", "post_date": "2020-08-23T09:07:51.493000", "content": "My friend's team was also removed from the LB. He contacted the Kaggle compliance team and complained about the low-quality of host & data in the post-competition survey. Guess what? His account was blocked in the name of \"cheating\". He's still trying to argue with the compliance team to get his account reinstalled…Given on his experience, I'd suggest you just let it go….
", "votes": 4, "replies": [] }, { "id": 981418, "author_name": "Issagali Konysbayev [dsmlkz]", "author_url": "", "post_date": "2020-08-22T12:37:01.863000", "content": "@philculliton @maggiemd @bendvd @stavness! Please respond.
", "votes": 4, "replies": [] }, { "id": 981175, "author_name": "Nurzhan Kabdyrakhmanov", "author_url": "", "post_date": "2020-08-22T08:37:11.527000", "content": "Justice for this guy
", "votes": 4, "replies": [] }, { "id": 986764, "author_name": "Dev Narula", "author_url": "", "post_date": "2020-08-26T19:02:26.097000", "content": "Did you try contacting kaggle through any other means, other than emails?
", "votes": 1, "replies": [ { "id": 1051831, "author_name": "", "author_url": "", "post_date": "2020-10-17T01:12:34.507000", "content": "", "votes": 0, "replies": [] } ] }, { "id": 982570, "author_name": "Kevin Dsouza", "author_url": "", "post_date": "2020-08-23T13:43:55.570000", "content": "This is pretty sad and unfair tbh.
", "votes": 1, "replies": [] }, { "id": 981605, "author_name": "alan chen", "author_url": "", "post_date": "2020-08-22T15:30:35.593000", "content": "This is not fair! Your submit records are simply wiped out. I can't imagine how this could happen in a Kaggle competition?
", "votes": 1, "replies": [ { "id": 982101, "author_name": "", "author_url": "", "post_date": "2020-08-23T04:15:01.290000", "content": "", "votes": 3, "replies": [] }, { "id": 982108, "author_name": "alan chen", "author_url": "", "post_date": "2020-08-23T04:32:53.587000", "content": "Thanks for response. Just try to keep this post atop.
", "votes": 1, "replies": [] } ] }, { "id": 984017, "author_name": "Baron Smith", "author_url": "", "post_date": "2020-08-24T19:09:59.497000", "content": "I'm sorry to see this. I think some work on resolution to keep a dedicated Kaggle user in the running would make sense. I am glad you shared with us so that we can watch out for this on our own work.
", "votes": 2, "replies": [] }, { "id": 982484, "author_name": "Daniboy370", "author_url": "", "post_date": "2020-08-23T12:08:22.953000", "content": "@aidynub This is absolutely unacceptable ! Why none of the Kaggle moderators are involved ?!
", "votes": 2, "replies": [] }, { "id": 982346, "author_name": "Ezeoke Godswill", "author_url": "", "post_date": "2020-08-23T09:40:06.143000", "content": "The act of honesty is enough for them to follow suit and not just kick the young man of the competition. That's really bad and uncalled for.
\n@philculliton @maggiemd @bendvd @stavness you four should have a rethink about this.
", "votes": 2, "replies": [] }, { "id": 981442, "author_name": "Nahian Rifaat", "author_url": "", "post_date": "2020-08-22T12:52:57.713000", "content": "It's sad. You could have won that competition.
", "votes": 2, "replies": [ { "id": 981716, "author_name": "عثمان", "author_url": "", "post_date": "2020-08-22T16:43:42.340000", "content": "I don't know about winning—but he should at least be ranked.
", "votes": 2, "replies": [] } ] }, { "id": 981176, "author_name": "Nurzhan Kabdyrakhmanov", "author_url": "", "post_date": "2020-08-22T08:37:14.877000", "content": "Justice for this guy
", "votes": 2, "replies": [] }, { "id": 982288, "author_name": "Shaurya Sinha", "author_url": "", "post_date": "2020-08-23T08:21:51.013000", "content": "@philculliton @maggiemd @bendvd @stavness! Please respond.
", "votes": 1, "replies": [] }, { "id": 983016, "author_name": "Maggie", "author_url": "", "post_date": "2020-08-24T00:32:48.360000", "content": "I responded to you directly with the details.
", "votes": 0, "replies": [ { "id": 983217, "author_name": "Aidyn Ubingazhibov", "author_url": "", "post_date": "2020-08-24T05:40:21.803000", "content": "I sent you an email with exhaustive details. Please look into it …
", "votes": 4, "replies": [] } ] }, { "id": 981607, "author_name": "", "author_url": "", "post_date": "2020-08-22T15:30:55.017000", "content": "", "votes": -9, "replies": [ { "id": 982099, "author_name": "", "author_url": "", "post_date": "2020-08-23T04:13:28.063000", "content": "", "votes": 2, "replies": [] } ] }, { "id": 995599, "author_name": "", "author_url": "", "post_date": "2020-09-02T15:45:22.063000", "content": "", "votes": -2, "replies": [] }, { "id": 995591, "author_name": "", "author_url": "", "post_date": "2020-09-02T15:38:40.493000", "content": "", "votes": -1, "replies": [] }, { "id": 995590, "author_name": "", "author_url": "", "post_date": "2020-09-02T15:38:38.180000", "content": "", "votes": -1, "replies": [] }, { "id": 991248, "author_name": "", "author_url": "", "post_date": "2020-08-30T09:08:01.113000", "content": "", "votes": -3, "replies": [] }, { "id": 988231, "author_name": "", "author_url": "", "post_date": "2020-08-27T22:40:35.563000", "content": "", "votes": -12, "replies": [] }, { "id": 1000293, "author_name": "", "author_url": "", "post_date": "2020-09-06T12:53:56.987000", "content": "", "votes": 0, "replies": [] }, { "id": 999979, "author_name": "", "author_url": "", "post_date": "2020-09-06T07:17:34.093000", "content": "", "votes": 0, "replies": [] }, { "id": 999566, "author_name": "", "author_url": "", "post_date": "2020-09-05T18:59:41.233000", "content": "", "votes": 0, "replies": [] }, { "id": 997587, "author_name": "", "author_url": "", "post_date": "2020-09-04T05:53:00.933000", "content": "", "votes": 0, "replies": [] }, { "id": 997349, "author_name": "", "author_url": "", "post_date": "2020-09-04T01:32:21.763000", "content": "", "votes": 0, "replies": [] }, { "id": 995869, "author_name": "", "author_url": "", "post_date": "2020-09-02T22:19:26.647000", "content": "", "votes": 0, "replies": [] }, { "id": 995177, "author_name": "", "author_url": "", "post_date": "2020-09-02T08:04:49.990000", "content": "", "votes": 0, "replies": [] }, { "id": 994746, "author_name": "", "author_url": "", "post_date": "2020-09-01T22:30:31.863000", "content": "", "votes": 0, "replies": [] }, { "id": 994303, "author_name": "", "author_url": "", "post_date": "2020-09-01T14:06:55.353000", "content": "", "votes": 0, "replies": [] }, { "id": 994025, "author_name": "", "author_url": "", "post_date": "2020-09-01T10:07:33.613000", "content": "", "votes": 0, "replies": [] }, { "id": 993630, "author_name": "", "author_url": "", "post_date": "2020-09-01T04:45:36.563000", "content": "", "votes": 0, "replies": [] }, { "id": 993533, "author_name": "", "author_url": "", "post_date": "2020-09-01T02:15:30.627000", "content": "", "votes": 0, "replies": [] }, { "id": 993499, "author_name": "", "author_url": "", "post_date": "2020-09-01T01:26:06.927000", "content": "", "votes": 0, "replies": [] }, { "id": 993359, "author_name": "", "author_url": "", "post_date": "2020-08-31T21:29:34.283000", "content": "", "votes": 0, "replies": [] }, { "id": 992860, "author_name": "", "author_url": "", "post_date": "2020-08-31T13:39:34.287000", "content": "", "votes": 0, "replies": [] }, { "id": 992603, "author_name": "", "author_url": "", "post_date": "2020-08-31T09:19:56.190000", "content": "", "votes": 0, "replies": [] }, { "id": 991724, "author_name": "", "author_url": "", "post_date": "2020-08-30T16:11:15.277000", "content": "", "votes": 0, "replies": [] }, { "id": 991461, "author_name": "", "author_url": "", "post_date": "2020-08-30T12:28:57.790000", "content": "", "votes": 0, "replies": [] }, { "id": 990990, "author_name": "", "author_url": "", "post_date": "2020-08-30T03:06:41.317000", "content": "", "votes": 0, "replies": [] }, { "id": 990941, "author_name": "", "author_url": "", "post_date": "2020-08-30T01:30:49.030000", "content": "", "votes": 0, "replies": [] }, { "id": 990418, "author_name": "", "author_url": "", "post_date": "2020-08-29T15:32:17.977000", "content": "", "votes": 0, "replies": [] }, { "id": 990232, "author_name": "", "author_url": "", "post_date": "2020-08-29T12:59:25.050000", "content": "", "votes": 0, "replies": [] }, { "id": 989412, "author_name": "", "author_url": "", "post_date": "2020-08-28T19:09:14.933000", "content": "", "votes": 0, "replies": [] }, { "id": 989010, "author_name": "", "author_url": "", "post_date": "2020-08-28T13:50:33.227000", "content": "", "votes": 0, "replies": [] }, { "id": 988308, "author_name": "", "author_url": "", "post_date": "2020-08-28T01:03:28.733000", "content": "", "votes": 0, "replies": [] }, { "id": 987608, "author_name": "", "author_url": "", "post_date": "2020-08-27T11:47:03.860000", "content": "", "votes": 0, "replies": [] }, { "id": 986835, "author_name": "", "author_url": "", "post_date": "2020-08-26T20:25:41.330000", "content": "", "votes": 0, "replies": [] }, { "id": 986330, "author_name": "", "author_url": "", "post_date": "2020-08-26T11:40:40.563000", "content": "", "votes": 0, "replies": [] }, { "id": 986011, "author_name": "", "author_url": "", "post_date": "2020-08-26T06:35:33.620000", "content": "", "votes": 0, "replies": [] }, { "id": 985780, "author_name": "", "author_url": "", "post_date": "2020-08-26T02:28:39.957000", "content": "", "votes": 0, "replies": [] }, { "id": 985660, "author_name": "", "author_url": "", "post_date": "2020-08-25T23:05:46.983000", "content": "", "votes": 0, "replies": [] }, { "id": 985339, "author_name": "", "author_url": "", "post_date": "2020-08-25T16:54:53.893000", "content": "", "votes": 0, "replies": [] }, { "id": 984377, "author_name": "", "author_url": "", "post_date": "2020-08-25T04:21:39.877000", "content": "", "votes": 0, "replies": [] }, { "id": 984136, "author_name": "", "author_url": "", "post_date": "2020-08-24T21:28:48.440000", "content": "", "votes": 0, "replies": [] }, { "id": 983382, "author_name": "", "author_url": "", "post_date": "2020-08-24T08:59:18.597000", "content": "", "votes": 0, "replies": [] }, { "id": 983174, "author_name": "", "author_url": "", "post_date": "2020-08-24T05:07:37.440000", "content": "", "votes": 0, "replies": [] }, { "id": 983019, "author_name": "", "author_url": "", "post_date": "2020-08-24T00:34:34.923000", "content": "", "votes": 0, "replies": [] }, { "id": 1000446, "author_name": "", "author_url": "", "post_date": "2020-09-06T14:29:03.127000", "content": "", "votes": -1, "replies": [] }, { "id": 994067, "author_name": "", "author_url": "", "post_date": "2020-09-01T10:46:40.487000", "content": "", "votes": 0, "replies": [] }, { "id": 993273, "author_name": "", "author_url": "", "post_date": "2020-08-31T19:45:52.810000", "content": "", "votes": 0, "replies": [] }, { "id": 987678, "author_name": "", "author_url": "", "post_date": "2020-08-27T12:43:55.340000", "content": "", "votes": 0, "replies": [] }, { "id": 983018, "author_name": "", "author_url": "", "post_date": "2020-08-24T00:33:59.627000", "content": "", "votes": 0, "replies": [] }, { "id": 982962, "author_name": "", "author_url": "", "post_date": "2020-08-23T21:57:34.347000", "content": "", "votes": 1, "replies": [] }, { "id": 981832, "author_name": "", "author_url": "", "post_date": "2020-08-22T18:19:39.243000", "content": "", "votes": -4, "replies": [] }, { "id": 988691, "author_name": "", "author_url": "", "post_date": "2020-08-28T07:51:38.640000", "content": "", "votes": 0, "replies": [] }, { "id": 987262, "author_name": "", "author_url": "", "post_date": "2020-08-27T05:58:29.087000", "content": "", "votes": 0, "replies": [] }, { "id": 984639, "author_name": "", "author_url": "", "post_date": "2020-08-25T07:45:31.527000", "content": "", "votes": 0, "replies": [] } ], "raw_markdown_by_id": { "981065": "Dear all,\n\nI am writing this post to reach out to the hosts and the kaggle team. \n\nI worked for several months on the competition. Both of my solutions are compliant. After the final leaderboard was revealed, I found myself winning the competition (# 1/2245). However, I quickly noticed a bug. My old scores were simply NOT updated because my notebooks were not reran on the new dataset for some reason. That is why my scores were higher than they should be. For more details and proof, please read my post about this bug \nhttps://www.kaggle.com/c/global-wheat-detection/discussion/175927\n\nFor fairness, I immediately contacted about this bug to @philculliton , after which they simply removed me from the competition with no explanations. I emailed the kaggle team several times asking why I was removed from the competition, and why they would not just rerun my notebooks, and put me in the leaderboard no matter if I win a medal or not. Never heard back. I have filed 2 Kaggle Compliance reports already, with no answers as well (Not sure how many days it takes them to process the reports though). \n\nI showed fairness, and in return I expect fairness and at least explanations from the kaggle team and the hosts. @philculliton @maggiemd @bendvd @stavness \n\nUPD: https://www.kaggle.com/c/global-wheat-detection/discussion/176973", "981855": "#YouMeAidyn", "981143": "@philculliton @maggiemd @bendvd @stavness be fair!", "982397": "I've already thought that all the problems in this competition are exhausted. So I was wrong. The hosts spawned a lot of problems such as the dirty train dataset, ambiguity with Yolov5, and the sudden rerun of the private dataset. However, I really respect them that they weren't afraid to solve all these problems. To be honest, I didn't believe that they would remove all the Yolov5 submissions but they did. Dear, hosts, you should understand that you have to do the job to the end and every mistake you do won't be ignored. You should show us your courage and make the right decision.", "981120": "My team was also removed without any explanations, we just got two errors in the submersion page. What is the status and error messages of your selected two?", "981153": "@inversion ", "981148": "What a noble deed👍", "981146": "Fairness to this guy!", "986195": "Hey @philculliton @maggiemd @bendvd @stavness,\nMe and my teammate appreciate the effort put into removing the Yolov5 submissions. \n\nHaving said that, we cannot find ourselves on the leaderboard. Both of our submissions seem to have been invalidated with a failed `final private rerun` error message. We have used the MIT-compliant EfficientDet for both submissions with different ensembling methods. As of 19/08/2020, we could find our submissions on the leaderboard but they have been removed since then. We are also sure that the runtime of our models is <6h because we have made multiple submissions (80+) before our final submission. \n\nWe submitted a complaint to the compliance team on 20/08/2020 and have not gotten a response yet. What is your timeline for handling these complaints?\n\nWe'd appreciate your help in the matter because like many other participants here, we have put in multiple months of effort and worked only on compliant solutions.\n\n", "992153": "I can feel the same sadness as you, because our team encountered the same situation. But from another point of view, you are also lucky, because both of your posts have been replied by the kaggle official team (I think because their popularity has reached the top of the kaggle discussion forum). But for us, all the posts (six or seven) published by our team have not received any reply from kaggle. This feeling is really bad.\n\nIf possible, I hope anyone who sees this discussion can also have a look to [our situation here](https://www.kaggle.com/c/global-wheat-detection/discussion/177757)", "981661": "Hopefully you will be back in the leaderboard.", "981212": "Kaggle team and hosts MUST take action in such unfair situation! Rerun the submissions and return Aidyn to the leaderboard", "982296": "This is so unfair. Kaggle must take immediate action in such cases. After working for months and then getting removed without any reason is unacceptable. ", "981393": "It would be great if there is a list of all removed teams and the reasons.", "981354": "It's always sad to hear that someone is being removed from the competition, though he didn’t violate any rules. I hope that Kaggle team will deal with it as soon as possible, since it not only undermines beliefs in fairness of these competitions, but forces people to behave dishonesty ", "997069": "Hi all,\n\nKaggle wants to acknowledge this post and provide some background on what you can expect in situations like this.\n\nThe participant contacted Kaggle to let us know there was an issue. We responded by thanking them for their email.\n\nUnfortunately, their notebooks could not be successfully re-run before the close of the competition. Their notebooks (and any other selected notebooks that failed) were re-run 6 times in an attempt to make sure any external factors were controlled. We have evidence that the user removed their datasets immediately after running the notebooks. This ensured the code could not be re-run properly. In the end, their selected submissions were invalidated because they could not be rescored on the updated test set. With all of their submissions invalidated, they no longer appeared on the leaderboard.\n\nAll selected notebooks went through the exact same process, and were subjected to the same level of scrutiny. All notebooks that failed for any reason were re-run. In the event those notebooks could not ultimately be rescored against the updated test set, their submissions were invalidated.\n\nThe participant contacted Kaggle compliance, and went through our compliance process. Their complaints were investigated and their request was answered. This is the standard process for competition complaints.\n\nPlease note that contacting individual Kaggle team members is _not_ the standard process and there is no guarantee that we will see your issue. Please contact Kaggle compliance to ensure that your issue is seen by our team. Also, we ask that you give us some time to respond to your requests. We take compliance requests very seriously and sometimes they take us some time to respond. Thank you for your understanding and support.\n", "984228": "This platform needs more people like you and instead of being punished you should be commended.", "982329": "My friend's team was also removed from the LB. He contacted the Kaggle compliance team and complained about the low-quality of host & data in the post-competition survey. Guess what? His account was blocked in the name of \"cheating\". He's still trying to argue with the compliance team to get his account reinstalled...Given on his experience, I'd suggest you just let it go....", "981418": "@philculliton @maggiemd @bendvd @stavness! Please respond. ", "981175": "Justice for this guy", "986764": "Did you try contacting kaggle through any other means, other than emails?", "982570": "This is pretty sad and unfair tbh.", "981605": "This is not fair! Your submit records are simply wiped out. I can't imagine how this could happen in a Kaggle competition?", "984017": "I'm sorry to see this. I think some work on resolution to keep a dedicated Kaggle user in the running would make sense. I am glad you shared with us so that we can watch out for this on our own work.", "982484": "@aidynub This is absolutely unacceptable ! Why none of the Kaggle moderators are involved ?!", "982346": "The act of honesty is enough for them to follow suit and not just kick the young man of the competition. That's really bad and uncalled for. \n\n@philculliton @maggiemd @bendvd @stavness you four should have a rethink about this.", "981442": "It's sad. You could have won that competition.", "981176": "Justice for this guy", "982288": "@philculliton @maggiemd @bendvd @stavness! Please respond.", "983016": "I responded to you directly with the details. ", "981607": "That is sad but you should contact Kaggle support teams in such a situation. They might help you.", "995599": "I hope anyone who sees the discussion", "995591": "Nice people here.. hello to everybody", "995590": "Nice people here.. hello to everybody", "991248": "Hello awesome people ", "988231": "Thank you for your perspective Aidyn, as we discussed we ended up with limited choices and appreciate your post [here.](https://www.kaggle.com/c/global-wheat-detection/discussion/176973) ", "1000293": "Looking forward to learn. ", "999979": "Kaggle should give justification this\n", "999566": "I'm sure it will all work out💕", "997587": "super", "997349": "nice job 👍👍👍👍", "995869": "Sad to hear. I hope Kaggle team will solve your problem as soon as possible. Keep up the good work!", "995177": "it's osm i liked it", "994746": "How frustrating. Please update us if a resolution is reached, because it sounds like others have had similar problems in this competition.", "994303": "Sad to hear", "994025": "looking forward to learn", "993630": "I'm also suffer for same", "993533": "nice very nice", "993499": "You did a great job Aidyn, and you should be rewarded for your hard working. We can win by cheating but we can only gain skills by honesty and hard working. Good luck👍", "993359": "Kaggle need more people like you who are honest and they should not have removed you from the competition", "992860": "Beyond offering you my sympathies, I can't offer any other help other than asking Kaggle staff to look into this and compensate in some way. You missed out on a good opportunity.", "992603": "\nIt's not fair", "991724": "Keep up the good work!", "991461": "I'm sorry to hear this. Hope you can have some sort of reimbursement at a later stage. Thanks for sharing your experience, I think this will ring a bell to everyone for later competitions", "990990": "Fairness !", "990941": "That's really sucks ! I hope all ended up well. Thank you for share all of this mate ! You are a good guy !", "990418": "I'm sorry to see this", "990232": "This is bad. They shouldn't do this to you. We should appreciate the good things. ", "989412": "You would have worked really hard for that. I guess that's not fair in the Data Science community, where doing new things is data is the prime motto. You will achieve what you deserve ", "989010": "Dear @aidynub, \nIt is shocking to new kagglers who wanna jump into the competition and get motivated based on results announced.\nGood, you pointed out, Faith must be restored.", "988308": "i hope they help you !", "987608": "Please help me, I don't know how to do this into executable work.", "986835": "If that's true it's really upsetting! Hopefully they will put you at scoreboard at least!", "986330": "got really sad after reading this", "986011": "After a lot of hard work, this is simply not fair. I hope you get back in the leaderboard.", "985780": "I'm sorry to hear that.", "985660": "I'm sorry to hear this. Thanks for sharing.", "985339": "very sorry to see this", "984377": "Yeah, sure there must be an explaination from the kaggle.\n@philculliton @maggiemd @bendvd @stavness please rethink", "984136": "This was sad to hear, you got any response yet ? 😅", "983382": "Yes, I feel this needs some attention from the moderators.", "983174": "...................................", "983019": "Well that definitely doesn't seem right to me.", "1000446": "", "994067": "", "993273": "", "987678": "", "983018": "", "982962": "", "981832": "", "988691": "Thanks for sharing.", "987262": "............Thanks for sharing.", "984639": "thank for us" } }