You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MTC uses jurisdiction-specific, form-specific development limits in its developer models, defined in a master config .yaml and referenced in their development model steps (see here for an example). In the spirit of keeping models.py nice and clean, and moving model specifications to config .yaml's and utils.py, it might be a good idea to provide this functionality for MTC and other MPO's out of the box by way of augmenting utils.run_developer() and maybe adding a dev_settings .yaml config.
The text was updated successfully, but these errors were encountered:
MTC uses jurisdiction-specific, form-specific development limits in its developer models, defined in a master config .yaml and referenced in their development model steps (see here for an example). In the spirit of keeping models.py nice and clean, and moving model specifications to config .yaml's and utils.py, it might be a good idea to provide this functionality for MTC and other MPO's out of the box by way of augmenting utils.run_developer() and maybe adding a dev_settings .yaml config.
The text was updated successfully, but these errors were encountered: