{
  "id": 248359,
  "title": "Question on Transaction Dates, Roster Dates",
  "url": "/competitions/mlb-player-digital-engagement-forecasting/discussion/248359",
  "author_name": "",
  "post_date": "2021-06-23T10:08:28.534695Z",
  "votes": 1,
  "comment_count": 1,
  "views": 0,
  "content": "<p>Is there a possible issue with time zones on how some of the dates in the competition data are set? like cutoffs so East Coast maybe ends up in the following day sometimes?</p>\n<p>e.g. Transactions entry date and effective date 2021-04-06 for playerId==596059 is a Trade from Texas Rangers to NY Yankees<br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-06     596059  33.198776   67.894131   65.396599   100.000000  <br>\nbut that would had to have been predicted on 2021-04-05 before transaction is known. <br>\nPrior to that date the player has no roster data or player box data for the regular season, so the likelihood of what is in targets is to do with the transaction. Or of course external information on it.<br>\nIn contrast for the same player Transactions entry date and effective date 2021-04-10 is activated from the 10 day injured list <br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-11     596059  20.290423   100.000000  97.099416   41.940076<br>\nFirst game for player in the regular season 2021-04-11 and rosters Status A Active on that date.<br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-12     596059  11.260309   72.776264   17.031415   97.493163</p>\n<p>Similarly Transaction entry date and effective date 2021-04-29 for playerId==663556 recalled to Tampa Bay Rays from Rays Alt Training Site. <br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-29     663556  0.378364    80.557629   1.452418    19.653179 <br>\nbut that would had to have been predicted on 2021-04-28 before transaction is known. <br>\nAnd for this player, although the starting pitcher in gameDate 2021-04-29, (and the only game played in the regular season in train) is not Status A Active in rosters until 2021-04-30.</p>",
  "messages": [
    {
      "id": "1362257",
      "postDate": "06/23/2021 10:08:28",
      "content": "<p>Is there a possible issue with time zones on how some of the dates in the competition data are set? like cutoffs so East Coast maybe ends up in the following day sometimes?</p>\n<p>e.g. Transactions entry date and effective date 2021-04-06 for playerId==596059 is a Trade from Texas Rangers to NY Yankees<br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-06     596059  33.198776   67.894131   65.396599   100.000000  <br>\nbut that would had to have been predicted on 2021-04-05 before transaction is known. <br>\nPrior to that date the player has no roster data or player box data for the regular season, so the likelihood of what is in targets is to do with the transaction. Or of course external information on it.<br>\nIn contrast for the same player Transactions entry date and effective date 2021-04-10 is activated from the 10 day injured list <br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-11     596059  20.290423   100.000000  97.099416   41.940076<br>\nFirst game for player in the regular season 2021-04-11 and rosters Status A Active on that date.<br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-12     596059  11.260309   72.776264   17.031415   97.493163</p>\n<p>Similarly Transaction entry date and effective date 2021-04-29 for playerId==663556 recalled to Tampa Bay Rays from Rays Alt Training Site. <br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-29     663556  0.378364    80.557629   1.452418    19.653179 <br>\nbut that would had to have been predicted on 2021-04-28 before transaction is known. <br>\nAnd for this player, although the starting pitcher in gameDate 2021-04-29, (and the only game played in the regular season in train) is not Status A Active in rosters until 2021-04-30.</p>",
      "rawMarkdown": "Is there a possible issue with time zones on how some of the dates in the competition data are set? like cutoffs so East Coast maybe ends up in the following day sometimes?\n\ne.g. Transactions entry date and effective date 2021-04-06 for playerId==596059 is a Trade from Texas Rangers to NY Yankees\nNextDayPlayerEngagement has targets1-4\n2021-04-06 \t596059 \t33.198776 \t67.894131 \t65.396599 \t100.000000 \t\nbut that would had to have been predicted on 2021-04-05 before transaction is known. \nPrior to that date the player has no roster data or player box data for the regular season, so the likelihood of what is in targets is to do with the transaction. Or of course external information on it.\nIn contrast for the same player Transactions entry date and effective date 2021-04-10 is activated from the 10 day injured list \nNextDayPlayerEngagement has targets1-4\n2021-04-11 \t596059 \t20.290423 \t100.000000 \t97.099416 \t41.940076\nFirst game for player in the regular season 2021-04-11 and rosters Status A Active on that date.\nNextDayPlayerEngagement has targets1-4\n2021-04-12 \t596059 \t11.260309 \t72.776264 \t17.031415 \t97.493163\n\nSimilarly Transaction entry date and effective date 2021-04-29 for playerId==663556 recalled to Tampa Bay Rays from Rays Alt Training Site. \nNextDayPlayerEngagement has targets1-4\n2021-04-29 \t663556 \t0.378364 \t80.557629 \t1.452418 \t19.653179 \nbut that would had to have been predicted on 2021-04-28 before transaction is known. \nAnd for this player, although the starting pitcher in gameDate 2021-04-29, (and the only game played in the regular season in train) is not Status A Active in rosters until 2021-04-30.",
      "votes": null
    },
    {
      "id": "1363601",
      "postDate": "06/24/2021 08:06:37",
      "content": "<p>Another example for player 457803 Transaction retired 2021-04-18 from NY Yankees, last game played 2021-04-14     <br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-17     457803  0.022688    3.684189    0.018567    3.822878    <br>\n2021-04-18     457803  20.329371   49.753314   66.310123   100.000000  <br>\n2021-04-19     457803  10.862424   23.414702   37.803658   71.112503</p>\n<p>what is in 2021-04-18 would had to have been predicted 2021-04-17 before transaction is known.</p>\n<p>Think transactions has some valuable information but not if the dates are wrong. </p>",
      "rawMarkdown": "Another example for player 457803 Transaction retired 2021-04-18 from NY Yankees, last game played 2021-04-14 \t\nNextDayPlayerEngagement has targets1-4\n2021-04-17 \t457803 \t0.022688 \t3.684189 \t0.018567 \t3.822878 \t\n2021-04-18 \t457803 \t20.329371 \t49.753314 \t66.310123 \t100.000000 \t\n2021-04-19 \t457803 \t10.862424 \t23.414702 \t37.803658 \t71.112503\n\nwhat is in 2021-04-18 would had to have been predicted 2021-04-17 before transaction is known.\n\nThink transactions has some valuable information but not if the dates are wrong.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1363601,
      "author_name": "something4kag",
      "author_url": "",
      "post_date": "06/24/2021 08:06:37",
      "content": "<p>Another example for player 457803 Transaction retired 2021-04-18 from NY Yankees, last game played 2021-04-14     <br>\nNextDayPlayerEngagement has targets1-4<br>\n2021-04-17     457803  0.022688    3.684189    0.018567    3.822878    <br>\n2021-04-18     457803  20.329371   49.753314   66.310123   100.000000  <br>\n2021-04-19     457803  10.862424   23.414702   37.803658   71.112503</p>\n<p>what is in 2021-04-18 would had to have been predicted 2021-04-17 before transaction is known.</p>\n<p>Think transactions has some valuable information but not if the dates are wrong. </p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1362257": "Is there a possible issue with time zones on how some of the dates in the competition data are set? like cutoffs so East Coast maybe ends up in the following day sometimes?\n\ne.g. Transactions entry date and effective date 2021-04-06 for playerId==596059 is a Trade from Texas Rangers to NY Yankees\nNextDayPlayerEngagement has targets1-4\n2021-04-06 \t596059 \t33.198776 \t67.894131 \t65.396599 \t100.000000 \t\nbut that would had to have been predicted on 2021-04-05 before transaction is known. \nPrior to that date the player has no roster data or player box data for the regular season, so the likelihood of what is in targets is to do with the transaction. Or of course external information on it.\nIn contrast for the same player Transactions entry date and effective date 2021-04-10 is activated from the 10 day injured list \nNextDayPlayerEngagement has targets1-4\n2021-04-11 \t596059 \t20.290423 \t100.000000 \t97.099416 \t41.940076\nFirst game for player in the regular season 2021-04-11 and rosters Status A Active on that date.\nNextDayPlayerEngagement has targets1-4\n2021-04-12 \t596059 \t11.260309 \t72.776264 \t17.031415 \t97.493163\n\nSimilarly Transaction entry date and effective date 2021-04-29 for playerId==663556 recalled to Tampa Bay Rays from Rays Alt Training Site. \nNextDayPlayerEngagement has targets1-4\n2021-04-29 \t663556 \t0.378364 \t80.557629 \t1.452418 \t19.653179 \nbut that would had to have been predicted on 2021-04-28 before transaction is known. \nAnd for this player, although the starting pitcher in gameDate 2021-04-29, (and the only game played in the regular season in train) is not Status A Active in rosters until 2021-04-30.",
    "1363601": "Another example for player 457803 Transaction retired 2021-04-18 from NY Yankees, last game played 2021-04-14 \t\nNextDayPlayerEngagement has targets1-4\n2021-04-17 \t457803 \t0.022688 \t3.684189 \t0.018567 \t3.822878 \t\n2021-04-18 \t457803 \t20.329371 \t49.753314 \t66.310123 \t100.000000 \t\n2021-04-19 \t457803 \t10.862424 \t23.414702 \t37.803658 \t71.112503\n\nwhat is in 2021-04-18 would had to have been predicted 2021-04-17 before transaction is known.\n\nThink transactions has some valuable information but not if the dates are wrong."
  },
  "source": "meta"
}