Anyone else notice the WCurrentScore and LCurrentScore in the play by play data is inaccurate? There are alot of games where the running total for both teams is zero throughout the entire game.
", "messages": [ { "id": "760028", "postDate": "02/29/2020 19:01:17", "content": "Anyone else notice the WCurrentScore and LCurrentScore in the play by play data is inaccurate? There are alot of games where the running total for both teams is zero throughout the entire game.
", "rawMarkdown": "Anyone else notice the WCurrentScore and LCurrentScore in the play by play data is inaccurate? There are alot of games where the running total for both teams is zero throughout the entire game.", "votes": null }, { "id": "760059", "postDate": "02/29/2020 19:49:41", "content": "Yes it is only present for the 2019 and (eventually) 2020 seasons. I mentioned this in the Data page, that you would need to calculate it yourself for earlier years.
", "rawMarkdown": "Yes it is only present for the 2019 and (eventually) 2020 seasons. I mentioned this in the Data page, that you would need to calculate it yourself for earlier years.", "votes": null }, { "id": "760139", "postDate": "02/29/2020 22:28:40", "content": "Jeff, Thanks for the quick response. There are actually alot of spots in the 2019 play by play data where the WCurrentScore and LCurrentScore are not correct.
", "rawMarkdown": "Jeff, Thanks for the quick response. There are actually alot of spots in the 2019 play by play data where the WCurrentScore and LCurrentScore are not correct.", "votes": null }, { "id": "766761", "postDate": "03/08/2020 16:46:09", "content": "Hi @jeffsonas, can you add the play-by-play before 2015? I understand some of the location and area variables are missing for older seasons, but perhaps we could just have these be missing. No worries if you don't have time, just thought I would ask. I did it myself with last year's available data, but the EventType and EventSubType variables seem to be structured a bit differently and not positive I used the same classification rules
", "rawMarkdown": "Hi @jeffsonas, can you add the play-by-play before 2015? I understand some of the location and area variables are missing for older seasons, but perhaps we could just have these be missing. No worries if you don't have time, just thought I would ask. I did it myself with last year's available data, but the EventType and EventSubType variables seem to be structured a bit differently and not positive I used the same classification rules", "votes": null }, { "id": "766840", "postDate": "03/08/2020 20:23:23", "content": "I noticed the same thing. Also, each game isn't sorted by ElapsedSeconds anymore. For example, for season 2019, the ElapsedSeconds is out of order around EventID = \"10444936\". This was causing a bug in my code; I probably should have realized to sort the data though.
", "rawMarkdown": "I noticed the same thing. Also, each game isn't sorted by ElapsedSeconds anymore. For example, for season 2019, the ElapsedSeconds is out of order around EventID = \"10444936\". This was causing a bug in my code; I probably should have realized to sort the data though.", "votes": null } ], "comments": [ { "id": 760059, "author_name": "jeffsonas", "author_url": "", "post_date": "02/29/2020 19:49:41", "content": "Yes it is only present for the 2019 and (eventually) 2020 seasons. I mentioned this in the Data page, that you would need to calculate it yourself for earlier years.
", "votes": null, "replies": [ { "id": 766761, "author_name": "sdsufan", "author_url": "", "post_date": "03/08/2020 16:46:09", "content": "Hi @jeffsonas, can you add the play-by-play before 2015? I understand some of the location and area variables are missing for older seasons, but perhaps we could just have these be missing. No worries if you don't have time, just thought I would ask. I did it myself with last year's available data, but the EventType and EventSubType variables seem to be structured a bit differently and not positive I used the same classification rules
", "votes": null, "replies": [] } ] }, { "id": 760139, "author_name": "darrentriplett", "author_url": "", "post_date": "02/29/2020 22:28:40", "content": "Jeff, Thanks for the quick response. There are actually alot of spots in the 2019 play by play data where the WCurrentScore and LCurrentScore are not correct.
", "votes": null, "replies": [ { "id": 766840, "author_name": "sdsufan", "author_url": "", "post_date": "03/08/2020 20:23:23", "content": "I noticed the same thing. Also, each game isn't sorted by ElapsedSeconds anymore. For example, for season 2019, the ElapsedSeconds is out of order around EventID = \"10444936\". This was causing a bug in my code; I probably should have realized to sort the data though.
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "760028": "Anyone else notice the WCurrentScore and LCurrentScore in the play by play data is inaccurate? There are alot of games where the running total for both teams is zero throughout the entire game.", "760059": "Yes it is only present for the 2019 and (eventually) 2020 seasons. I mentioned this in the Data page, that you would need to calculate it yourself for earlier years.", "760139": "Jeff, Thanks for the quick response. There are actually alot of spots in the 2019 play by play data where the WCurrentScore and LCurrentScore are not correct.", "766761": "Hi @jeffsonas, can you add the play-by-play before 2015? I understand some of the location and area variables are missing for older seasons, but perhaps we could just have these be missing. No worries if you don't have time, just thought I would ask. I did it myself with last year's available data, but the EventType and EventSubType variables seem to be structured a bit differently and not positive I used the same classification rules", "766840": "I noticed the same thing. Also, each game isn't sorted by ElapsedSeconds anymore. For example, for season 2019, the ElapsedSeconds is out of order around EventID = \"10444936\". This was causing a bug in my code; I probably should have realized to sort the data though." }, "source": "meta" }