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

Hard Coded Person Types in CDAP #356

Closed
danielsclint opened this issue Nov 4, 2020 · 3 comments
Closed

Hard Coded Person Types in CDAP #356

danielsclint opened this issue Nov 4, 2020 · 3 comments

Comments

@danielsclint
Copy link

danielsclint commented Nov 4, 2020

The CDAP model contains hard coded person type (ptype) values for workers and children.

For the ARC implementation this causes problems in the tour scheduling components where the children ptypes are further subdivided beyond the values in the hard-coded expression. We would ideally like to be able to define 9 as another child person type for tour scheduling, but this would break the upstream CDAP components.

Preferably, the ptypes should be asserted in the settings.yaml or one of the model configuration yaml files.

WORKER_PTYPES = [1, 2]
CHILD_PTYPES = [6, 7, 8]

@bstabler
Copy link
Contributor

bstabler commented Nov 10, 2020

@danielsclint
Copy link
Author

This feature is not available on the develop branch at this point in time, so I didn't incorporate it. I did just issue a pull request to address the ARC specific issue this issue relates.

@bstabler
Copy link
Contributor

this is in the release version now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants