Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task: cleanup new pipeline #1015

Open
7 of 11 tasks
nlebovits opened this issue Nov 22, 2024 · 3 comments
Open
7 of 11 tasks

Task: cleanup new pipeline #1015

nlebovits opened this issue Nov 22, 2024 · 3 comments
Assignees
Labels

Comments

@nlebovits
Copy link
Collaborator

nlebovits commented Nov 22, 2024

Pipeline Outstanding Items Checklist

  • Include z-scored density values for KDE outputs (not just percentiles).
    • This ensures continuous, interpretable values for ML and community partners.
  • Set the number of workers dynamically based on machine cores for parallel processing.
    • Avoid hardcoding values based on a single machine's configuration.
  • Add data documentation:
    • Create a DAG.
    • Create a data dictionary.
  • Add a "create date" field for the final dataset.
  • Run ruff formatting and linting, and address all errors.
  • Ensure all code in the pipeline has accurate:
    • Docstrings.
    • Typing.
  • Develop a better method for implementing data QC.
@nlebovits
Copy link
Collaborator Author

In data dictionary, add a known_issues column with notes on known data quality/source issues (e.g., missing polygons in pwd_parcels.

@nlebovits
Copy link
Collaborator Author

Also update the development rank calculation to use the standard KDE function rather than the census bg bins (plus z-score and percentile cuts).

@nlebovits
Copy link
Collaborator Author

  • Consider updating guncrime priority to things 2 std above the mean--or will that be uninterpretable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: To Do
Development

No branches or pull requests

1 participant