activitysim

activitysim copied to clipboard

Related to #335...

@toliwaga said:

Sometimes (e.g. for mtctm1) [two YAML specificiations] will be identical to non_mandatory_tour_destination.yaml it would be nice to have a macro (like inherit_settings) that allows you to say something like:

include_settings: non_mandatory_tour_destination.yaml

this is too cool to resist!

It would probably be best to provide only a limited functionality for this.

There is a lot of opportunity for confusion if this feature were over-used (e.g. endless chains of include files that reference each other...) when all we really need (for now) is to support an include that makes the setting file an alias for anther settings file.

Maybe we insist that a file with an include directive is the 'end of the road' and can't contain or inherit other settings?

Supportive of convenience, but I think we also want to ensure that specifications are transparent and clear / legible.

On Thu, Sep 17, 2020 at 2:01 AM Jeff Doyle [email protected] wrote:

It would probably be best to provide only a limited functionality for this.

There is a lot of opportunity for confusion if this feature were over-used (e.g. endless chains of include files that reference each other...) when all we really need (for now) is to support simple

Maybe we insist that a file with an include directive is the 'end of the road' and can't contain or inherit other settings?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ActivitySim/activitysim/issues/348#issuecomment-694099008, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDVIH6FINI5NUSSO5F4YJTSGHF6XANCNFSM4RPDJPFQ .

#397