Skip to content

Hard Coded Person Types in CDAP #356

@danielsclint

Description

@danielsclint

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]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions