🚀 Feature: Replicate Capabilities of TM1's SetUpModel.bat
#150
Assignees
Milestone
Comments
|
@lmz, @gregerhardt, @FlaviaTsang, @e-lo |
|
Additional requirements per 8/28 chat with @lmz and @FlaviaTsang:
Note: in the existing set up model batch files, the M_DIR contains the persistent, files of records. The modeling machines are transitory and are intended to be erased. Please edit/clarify as needed. CC @gregerhardt |
|
@AshishKuls: will your procedures solve #79? |
When running setup model (see how I did it in this notebook), it writes out a setup_log.log to the model folder created that logs the source of:
|
|
I attempted a complete model run starting from set up model, here are some notes:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story
As a member of the MTC modeling team, I would like to document the configuration of the modeling system, key inputs, parameters, and other important information when beginning a planning study. MTC currently accomplishes this work with a MS-DOS batch file. See this example used for Plan Bay Area 2050. With the shift to
tm2py, the capabilities of theSetUpModelbatch file need to be replicated viatm2pymethods.Progress:
Priority
Medium
Level of Effort
Low
Resolution Ideas
Three possible ideas:
project_config.toml, and use it to specify the necessary references needed by the model set up procedure. These could include the relevant versions oftm2pyandtravel-model-two, the location of the relevant project cards and perhaps tags to grab them, any computer-specific settings to configure the resident passenger Java code, etc. In parameter specific to a scenario can be added to the existingscenario_config.toml. We'll therefore have configuration files specific to the model, the scenario, and the project (defined as a collection of scenarios).travel-model-twoJARfile to the working directory. This option is more attractive if the number of configuration parameters that would be stored inproject_config.tomlis relatively small. This strategy may also allow MTC to scale the scope of the file as needed when project demands become bespoke.SetUpModel.batfile to accommodate TM2. While unattractive in that it relies on MS-DOS batch files rather than Python, it is the lowest cost and simplest solution, in that the relevant features of the existing workflow can be brought over to the new workflow.Project
WSP Task Order Five.
Who should be involved?
Users:
Reviewers:
Risk
The risk here is low as this procedures will not impact any other parts of
tm2py. They are only intended to create a logged environment for the model to run on MTC's computers.Tests
The relevant tests are to launch a series of model runs on MTC's hardware using the procedures to ensure the configuration is working as expected and the logging captures the relevant information.
The text was updated successfully, but these errors were encountered: