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

Create separate splitter workflow to specify a number of enumerators #59

Open
spwoodcock opened this issue Oct 23, 2024 · 0 comments
Open
Labels
effort:medium Likely a day or two enhancement New feature or request priority:low Backlog of tasks that will be addressed in time

Comments

@spwoodcock
Copy link
Member

Is your feature request related to a problem? Please describe.

  • Current workflow is based of average number of buildings required.
  • Sometimes the team has a number of enumerators / mappers, and would like a number of tasks to match that.

Describe the solution you'd like

  • We should have a separate workflow, that is wrapped in the same split_by_sql function but with a different param.
  • The param should be num_of_enumerators.
  • If specified, the SQL will ensure we get exactly that number of tasks, then split up the tasks based on an approximate even distribution of features, also factoring the roads/rivers as usual.

Additional context

  • To facilitate this we probably need modular functions.
  • We should have some common logic defined in one place, that is reused across multiple workflows:
    • num buildings
    • num enumerators
@spwoodcock spwoodcock added the enhancement New feature or request label Oct 23, 2024
@spwoodcock spwoodcock added priority:low Backlog of tasks that will be addressed in time effort:medium Likely a day or two labels Oct 29, 2024
@spwoodcock spwoodcock added this to the Modularlisation milestone Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:medium Likely a day or two enhancement New feature or request priority:low Backlog of tasks that will be addressed in time
Projects
Development

No branches or pull requests

1 participant