{
  "id": 419326,
  "title": "target / signal values",
  "url": "/competitions/ext-market/discussion/419326",
  "author_name": "",
  "post_date": "2023-06-25T10:45:38.351367100Z",
  "votes": null,
  "comment_count": 4,
  "views": 0,
  "content": "<p>It is not a very significant problem. But I tought i should mention it might generally be better to encode target / signals as -1, 0, 1 for down (sell) / flat (keep) / up (buy). It make slightly more sense and allow to deal with the problem as a regression problem (after all down is the opposite of up).  </p>",
  "messages": [
    {
      "id": "2316960",
      "postDate": "06/25/2023 10:45:38",
      "content": "<p>It is not a very significant problem. But I tought i should mention it might generally be better to encode target / signals as -1, 0, 1 for down (sell) / flat (keep) / up (buy). It make slightly more sense and allow to deal with the problem as a regression problem (after all down is the opposite of up).  </p>",
      "rawMarkdown": "It is not a very significant problem. But I tought i should mention it might generally be better to encode target / signals as -1, 0, 1 for down (sell) / flat (keep) / up (buy). It make slightly more sense and allow to deal with the problem as a regression problem (after all down is the opposite of up).",
      "votes": null
    },
    {
      "id": "2317262",
      "postDate": "06/25/2023 14:48:09",
      "content": "<p>Thank you for being here, Lucas! I've updated test and submission files, also checked them: 0s are inside. Also I changed metrics to macro avg f1, because it gives better look at model behavior</p>",
      "rawMarkdown": "Thank you for being here, Lucas! I've updated test and submission files, also checked them: 0s are inside. Also I changed metrics to macro avg f1, because it gives better look at model behavior",
      "votes": null
    },
    {
      "id": "2319802",
      "postDate": "06/27/2023 10:19:33",
      "content": "<p>Thanks, nice for the update. Maybe you want to do that for the target too. <br>\nRegarding the change of metric, I am affraid that kaggle hasn't updated the score… thus I am appearing with my old 0.98 score. (I don't know where to go with this but I'll give kaggle a feed back that they should update scores if metric is updated). </p>",
      "rawMarkdown": "Thanks, nice for the update. Maybe you want to do that for the target too. \nRegarding the change of metric, I am affraid that kaggle hasn't updated the score... thus I am appearing with my old 0.98 score. (I don't know where to go with this but I'll give kaggle a feed back that they should update scores if metric is updated).",
      "votes": null
    },
    {
      "id": "2319933",
      "postDate": "06/27/2023 11:40:43",
      "content": "<p>Hi Lucas. I feel myself really weird, inviting you every time in my competitions, but here I got a new one - <a href=\"https://www.kaggle.com/competitions/shortlong-prediction\" target=\"_blank\">https://www.kaggle.com/competitions/shortlong-prediction</a> </p>\n<p>You know, I decided to go smarter and split my previous competition into a small once: maybe first of all, rather than trying to predict 3 classes, try to predict one as the majority and one (which is now two mitorities combined) as minority. And then among them predict which one is short and which one is long. </p>\n<p>So, url above leads to this second part task, predicting long or short. Probably you are tired of me already, but again, I am always happy to see you in my competitions.</p>\n<p>P.S. Second one - <a href=\"https://www.kaggle.com/competitions/anomaly-class-detection\" target=\"_blank\">https://www.kaggle.com/competitions/anomaly-class-detection</a></p>",
      "rawMarkdown": "Hi Lucas. I feel myself really weird, inviting you every time in my competitions, but here I got a new one - https://www.kaggle.com/competitions/shortlong-prediction \n\nYou know, I decided to go smarter and split my previous competition into a small once: maybe first of all, rather than trying to predict 3 classes, try to predict one as the majority and one (which is now two mitorities combined) as minority. And then among them predict which one is short and which one is long. \n\nSo, url above leads to this second part task, predicting long or short. Probably you are tired of me already, but again, I am always happy to see you in my competitions.\n\nP.S. Second one - https://www.kaggle.com/competitions/anomaly-class-detection",
      "votes": null
    },
    {
      "id": "2321061",
      "postDate": "06/28/2023 08:51:35",
      "content": "<p>Hey nice; i'll look into them. Dont be ashamed, that's infinitely better than doing nothing. <br>\nI think you should mention the competition somewhere (better visibility, organisation feedback), maybe in the discussion forum ? </p>",
      "rawMarkdown": "Hey nice; i'll look into them. Dont be ashamed, that's infinitely better than doing nothing. \nI think you should mention the competition somewhere (better visibility, organisation feedback), maybe in the discussion forum ?",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 2317262,
      "author_name": "",
      "author_url": "",
      "post_date": "06/25/2023 14:48:09",
      "content": "<p>Thank you for being here, Lucas! I've updated test and submission files, also checked them: 0s are inside. Also I changed metrics to macro avg f1, because it gives better look at model behavior</p>",
      "votes": null,
      "replies": [
        {
          "id": 2319802,
          "author_name": "lucasmorin",
          "author_url": "",
          "post_date": "06/27/2023 10:19:33",
          "content": "<p>Thanks, nice for the update. Maybe you want to do that for the target too. <br>\nRegarding the change of metric, I am affraid that kaggle hasn't updated the score… thus I am appearing with my old 0.98 score. (I don't know where to go with this but I'll give kaggle a feed back that they should update scores if metric is updated). </p>",
          "votes": null,
          "replies": [
            {
              "id": 2319933,
              "author_name": "",
              "author_url": "",
              "post_date": "06/27/2023 11:40:43",
              "content": "<p>Hi Lucas. I feel myself really weird, inviting you every time in my competitions, but here I got a new one - <a href=\"https://www.kaggle.com/competitions/shortlong-prediction\" target=\"_blank\">https://www.kaggle.com/competitions/shortlong-prediction</a> </p>\n<p>You know, I decided to go smarter and split my previous competition into a small once: maybe first of all, rather than trying to predict 3 classes, try to predict one as the majority and one (which is now two mitorities combined) as minority. And then among them predict which one is short and which one is long. </p>\n<p>So, url above leads to this second part task, predicting long or short. Probably you are tired of me already, but again, I am always happy to see you in my competitions.</p>\n<p>P.S. Second one - <a href=\"https://www.kaggle.com/competitions/anomaly-class-detection\" target=\"_blank\">https://www.kaggle.com/competitions/anomaly-class-detection</a></p>",
              "votes": null,
              "replies": [
                {
                  "id": 2321061,
                  "author_name": "lucasmorin",
                  "author_url": "",
                  "post_date": "06/28/2023 08:51:35",
                  "content": "<p>Hey nice; i'll look into them. Dont be ashamed, that's infinitely better than doing nothing. <br>\nI think you should mention the competition somewhere (better visibility, organisation feedback), maybe in the discussion forum ? </p>",
                  "votes": null,
                  "replies": []
                }
              ]
            }
          ]
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "2316960": "It is not a very significant problem. But I tought i should mention it might generally be better to encode target / signals as -1, 0, 1 for down (sell) / flat (keep) / up (buy). It make slightly more sense and allow to deal with the problem as a regression problem (after all down is the opposite of up).",
    "2317262": "Thank you for being here, Lucas! I've updated test and submission files, also checked them: 0s are inside. Also I changed metrics to macro avg f1, because it gives better look at model behavior",
    "2319802": "Thanks, nice for the update. Maybe you want to do that for the target too. \nRegarding the change of metric, I am affraid that kaggle hasn't updated the score... thus I am appearing with my old 0.98 score. (I don't know where to go with this but I'll give kaggle a feed back that they should update scores if metric is updated).",
    "2319933": "Hi Lucas. I feel myself really weird, inviting you every time in my competitions, but here I got a new one - https://www.kaggle.com/competitions/shortlong-prediction \n\nYou know, I decided to go smarter and split my previous competition into a small once: maybe first of all, rather than trying to predict 3 classes, try to predict one as the majority and one (which is now two mitorities combined) as minority. And then among them predict which one is short and which one is long. \n\nSo, url above leads to this second part task, predicting long or short. Probably you are tired of me already, but again, I am always happy to see you in my competitions.\n\nP.S. Second one - https://www.kaggle.com/competitions/anomaly-class-detection",
    "2321061": "Hey nice; i'll look into them. Dont be ashamed, that's infinitely better than doing nothing. \nI think you should mention the competition somewhere (better visibility, organisation feedback), maybe in the discussion forum ?"
  },
  "source": "meta"
}