{
  "id": 540509,
  "title": "New format of the time series API ?",
  "url": "/competitions/jane-street-real-time-market-data-forecasting/discussion/540509",
  "author_name": "",
  "post_date": "2024-10-15T00:46:32.250830Z",
  "votes": 4,
  "comment_count": 4,
  "views": 0,
  "content": "<p>It might just be due to my lack of experience, but it seems that the specifications of the time series API have been updated.</p>\n<p>In previous competitions, I was able to run about five batches trial submissions, so I could debug to some extent. However, with this format, it feels like debugging has become more difficult.</p>\n<p>On the other hand, I think the issue that we had struggled with before—where we had to reset everything when an error occurred after running the code—has been improved with this new API. And this is the merit of the new time series API, and becomes more simple.</p>\n<p>How can we make debugging more efficient on this new time series API ?<br>\nIs there anyone who has any advice?</p>",
  "messages": [
    {
      "id": "3017464",
      "postDate": "10/15/2024 00:46:32",
      "content": "<p>It might just be due to my lack of experience, but it seems that the specifications of the time series API have been updated.</p>\n<p>In previous competitions, I was able to run about five batches trial submissions, so I could debug to some extent. However, with this format, it feels like debugging has become more difficult.</p>\n<p>On the other hand, I think the issue that we had struggled with before—where we had to reset everything when an error occurred after running the code—has been improved with this new API. And this is the merit of the new time series API, and becomes more simple.</p>\n<p>How can we make debugging more efficient on this new time series API ?<br>\nIs there anyone who has any advice?</p>",
      "rawMarkdown": "It might just be due to my lack of experience, but it seems that the specifications of the time series API have been updated.\n\nIn previous competitions, I was able to run about five batches trial submissions, so I could debug to some extent. However, with this format, it feels like debugging has become more difficult.\n\nOn the other hand, I think the issue that we had struggled with before—where we had to reset everything when an error occurred after running the code—has been improved with this new API. And this is the merit of the new time series API, and becomes more simple.\n\nHow can we make debugging more efficient on this new time series API ?\nIs there anyone who has any advice?",
      "votes": null
    },
    {
      "id": "3018552",
      "postDate": "10/15/2024 21:00:11",
      "content": "<p>Yes, the time series API has been replaced with a new evaluation API. Can you elaborate on the difficulties you're having with debugging?</p>",
      "rawMarkdown": "Yes, the time series API has been replaced with a new evaluation API. Can you elaborate on the difficulties you're having with debugging?",
      "votes": null
    },
    {
      "id": "3020571",
      "postDate": "10/17/2024 16:54:57",
      "content": "<p><a href=\"https://www.kaggle.com/sohier\" target=\"_blank\">@sohier</a> Thank you for your response.</p>\n<p>First, in this case, understanding how the lag works is quite difficult. Since it only appears when time_id = 0, if we try to define the lag elsewhere in the function, it results in an error. ( \"It says that the lag needs to be made global, but this is quite confusing.)<br>\nFuthermore, it's hard to verify this behavior in practice, which makes it challenging to fully grasp.</p>\n<p>It makes it hard to tell if the lag is actually switching as intended, leaving uncertainty when submitting.</p>\n<p>That said, after spending a whole day on this, I feel like I’ve gained a much better understanding, so I’m thinking of publishing a notebook for explanation purposes later.</p>",
      "rawMarkdown": "sohier Thank you for your response.\n\nFirst, in this case, understanding how the lag works is quite difficult. Since it only appears when time_id = 0, if we try to define the lag elsewhere in the function, it results in an error. ( \"It says that the lag needs to be made global, but this is quite confusing.)\nFuthermore, it's hard to verify this behavior in practice, which makes it challenging to fully grasp.\n\nIt makes it hard to tell if the lag is actually switching as intended, leaving uncertainty when submitting.\n\nThat said, after spending a whole day on this, I feel like I’ve gained a much better understanding, so I’m thinking of publishing a notebook for explanation purposes later.",
      "votes": null
    },
    {
      "id": "3020580",
      "postDate": "10/17/2024 16:59:49",
      "content": "<p>Please add more dummy data to the api.</p>",
      "rawMarkdown": "Please add more dummy data to the api.",
      "votes": null
    },
    {
      "id": "3024009",
      "postDate": "10/21/2024 08:44:44",
      "content": "<p>Yes pls more dummy data </p>",
      "rawMarkdown": "Yes pls more dummy data",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 3018552,
      "author_name": "sohier",
      "author_url": "",
      "post_date": "10/15/2024 21:00:11",
      "content": "<p>Yes, the time series API has been replaced with a new evaluation API. Can you elaborate on the difficulties you're having with debugging?</p>",
      "votes": null,
      "replies": [
        {
          "id": 3020571,
          "author_name": "chumajin",
          "author_url": "",
          "post_date": "10/17/2024 16:54:57",
          "content": "<p><a href=\"https://www.kaggle.com/sohier\" target=\"_blank\">@sohier</a> Thank you for your response.</p>\n<p>First, in this case, understanding how the lag works is quite difficult. Since it only appears when time_id = 0, if we try to define the lag elsewhere in the function, it results in an error. ( \"It says that the lag needs to be made global, but this is quite confusing.)<br>\nFuthermore, it's hard to verify this behavior in practice, which makes it challenging to fully grasp.</p>\n<p>It makes it hard to tell if the lag is actually switching as intended, leaving uncertainty when submitting.</p>\n<p>That said, after spending a whole day on this, I feel like I’ve gained a much better understanding, so I’m thinking of publishing a notebook for explanation purposes later.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 3020580,
          "author_name": "yuanzhezhou",
          "author_url": "",
          "post_date": "10/17/2024 16:59:49",
          "content": "<p>Please add more dummy data to the api.</p>",
          "votes": null,
          "replies": [
            {
              "id": 3024009,
              "author_name": "simonveitner",
              "author_url": "",
              "post_date": "10/21/2024 08:44:44",
              "content": "<p>Yes pls more dummy data </p>",
              "votes": null,
              "replies": []
            }
          ]
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "3017464": "It might just be due to my lack of experience, but it seems that the specifications of the time series API have been updated.\n\nIn previous competitions, I was able to run about five batches trial submissions, so I could debug to some extent. However, with this format, it feels like debugging has become more difficult.\n\nOn the other hand, I think the issue that we had struggled with before—where we had to reset everything when an error occurred after running the code—has been improved with this new API. And this is the merit of the new time series API, and becomes more simple.\n\nHow can we make debugging more efficient on this new time series API ?\nIs there anyone who has any advice?",
    "3018552": "Yes, the time series API has been replaced with a new evaluation API. Can you elaborate on the difficulties you're having with debugging?",
    "3020571": "sohier Thank you for your response.\n\nFirst, in this case, understanding how the lag works is quite difficult. Since it only appears when time_id = 0, if we try to define the lag elsewhere in the function, it results in an error. ( \"It says that the lag needs to be made global, but this is quite confusing.)\nFuthermore, it's hard to verify this behavior in practice, which makes it challenging to fully grasp.\n\nIt makes it hard to tell if the lag is actually switching as intended, leaving uncertainty when submitting.\n\nThat said, after spending a whole day on this, I feel like I’ve gained a much better understanding, so I’m thinking of publishing a notebook for explanation purposes later.",
    "3020580": "Please add more dummy data to the api.",
    "3024009": "Yes pls more dummy data"
  },
  "source": "meta"
}