{
  "id": 52566,
  "title": "Evaluation Exception: Submitted values must be in ascending order and not overlapping.",
  "url": "/competitions/data-science-bowl-2018/discussion/52566",
  "author_name": "",
  "post_date": "2018-03-21T05:35:44.884604600Z",
  "votes": null,
  "comment_count": 3,
  "views": 0,
  "content": "<p>Anyone else getting this message and not knowing why? I successfully submitted a number of files and I've only gotten this on my last submission. I run them all through the same pipeline to get the required encoding, so I'm not sure why I'm getting this message now whereas I didn't before. I did run a few checks on my end and everything seems OK. It's a bit hard to debug since there aren't any details on where the error is.</p>",
  "messages": [
    {
      "id": "299899",
      "postDate": "03/21/2018 05:35:44",
      "content": "<p>Anyone else getting this message and not knowing why? I successfully submitted a number of files and I've only gotten this on my last submission. I run them all through the same pipeline to get the required encoding, so I'm not sure why I'm getting this message now whereas I didn't before. I did run a few checks on my end and everything seems OK. It's a bit hard to debug since there aren't any details on where the error is.</p>",
      "rawMarkdown": "Anyone else getting this message and not knowing why? I successfully submitted a number of files and I've only gotten this on my last submission. I run them all through the same pipeline to get the required encoding, so I'm not sure why I'm getting this message now whereas I didn't before. I did run a few checks on my end and everything seems OK. It's a bit hard to debug since there aren't any details on where the error is.",
      "votes": null
    },
    {
      "id": "304647",
      "postDate": "03/27/2018 20:36:41",
      "content": "<p>I have the same problem and I am trying to figure it out. I will let you know if I make progress. </p>",
      "rawMarkdown": "I have the same problem and I am trying to figure it out. I will let you know if I make progress.",
      "votes": null
    },
    {
      "id": "304725",
      "postDate": "03/28/2018 00:03:26",
      "content": "<p>It might mean that the pixel positions in the RLE should be in increasing order.  You might want to check that in your submission.</p>",
      "rawMarkdown": "It might mean that the pixel positions in the RLE should be in increasing order.  You might want to check that in your submission.",
      "votes": null
    },
    {
      "id": "309856",
      "postDate": "04/06/2018 04:01:38",
      "content": "<p>I did check both the increasing part and the overlap part, but I'm still stuck. It's so weird that I'm only getting these errors when I use a specific function to find the outlying pixels and even then, not all the time. I am always using the same function to get them to be non-overlapping (both are standard functions in a well-tested R package) as well as the same code (that I wrote) to get the RLE format.</p>",
      "rawMarkdown": "I did check both the increasing part and the overlap part, but I'm still stuck. It's so weird that I'm only getting these errors when I use a specific function to find the outlying pixels and even then, not all the time. I am always using the same function to get them to be non-overlapping (both are standard functions in a well-tested R package) as well as the same code (that I wrote) to get the RLE format.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 304647,
      "author_name": "datatechap",
      "author_url": "",
      "post_date": "03/27/2018 20:36:41",
      "content": "<p>I have the same problem and I am trying to figure it out. I will let you know if I make progress. </p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 304725,
      "author_name": "robertkag",
      "author_url": "",
      "post_date": "03/28/2018 00:03:26",
      "content": "<p>It might mean that the pixel positions in the RLE should be in increasing order.  You might want to check that in your submission.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 309856,
      "author_name": "siminaboca",
      "author_url": "",
      "post_date": "04/06/2018 04:01:38",
      "content": "<p>I did check both the increasing part and the overlap part, but I'm still stuck. It's so weird that I'm only getting these errors when I use a specific function to find the outlying pixels and even then, not all the time. I am always using the same function to get them to be non-overlapping (both are standard functions in a well-tested R package) as well as the same code (that I wrote) to get the RLE format.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "299899": "Anyone else getting this message and not knowing why? I successfully submitted a number of files and I've only gotten this on my last submission. I run them all through the same pipeline to get the required encoding, so I'm not sure why I'm getting this message now whereas I didn't before. I did run a few checks on my end and everything seems OK. It's a bit hard to debug since there aren't any details on where the error is.",
    "304647": "I have the same problem and I am trying to figure it out. I will let you know if I make progress.",
    "304725": "It might mean that the pixel positions in the RLE should be in increasing order.  You might want to check that in your submission.",
    "309856": "I did check both the increasing part and the overlap part, but I'm still stuck. It's so weird that I'm only getting these errors when I use a specific function to find the outlying pixels and even then, not all the time. I am always using the same function to get them to be non-overlapping (both are standard functions in a well-tested R package) as well as the same code (that I wrote) to get the RLE format."
  },
  "source": "meta"
}