Complaint date information and fake today needs to be fixed
- Dominant language
- Python
- Stars
- 56
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
For complaints, at a minimum, we have three dates: occurrence date, report date, and finding date.
Currently, when we generate (predictor) features we include the incident if the occurrence date is before the fake today. If the report date (or finding date) is not also before the fake today, this information should not be included in the (predictor) features because at the point of the fake today we don't actually know that the incident occurred.
An improvement would be to only include incidents after they are reported (and/or the finding) date. This will also interact with Issue number 8 in the police-eis-private repo (referencing Nashville staging population).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the complaint predictor-feature generation and the fake-today date filtering. Trace how occurrence, report, and finding dates are handled, and review the interaction with Issue 8 in the police-eis-private repository. Done means future report or finding information is excluded from predictor features at the fake today, with coverage for the relevant date combinations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100