Skip to content

Hard Coded Specification - Mandatory Tour Scheduling #273

Description

@danielsclint

The specifications for mandatory tour scheduling are hard-coded forcing the school and university specification to use the same specification file. In the Atlanta implementation, school and university use different specifications.

work_spec = simulate.read_model_spec(file_name='tour_scheduling_work.csv')
school_spec = simulate.read_model_spec(file_name='tour_scheduling_school.csv')
segment_specs = {
'work': work_spec,
'school': school_spec,
'univ': school_spec
}

It would nice if the model treated the spec more flexibly similar to the way the the location models define the spec.

model_spec = simulate.read_model_spec(file_name=model_settings['SPEC'])

I could imagine a situation where the mandatory specs are defined in the mandatory_tour_scheduling.yaml as follow:

SPEC:
  work: tour_scheduling_work.csv
  school: tour_scheduling_school.csv
  univ: tour_scheduling_university.csv

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions