EMME Flow support

[bccheung]

EMME Flow provides a very intuitive interface for automating/orchestrating the running of multiple EMME Modeller tools, among other things.

Some relatively minor updates to the TMGToolbox would be required to make its tools usable within EMME Flow. These updates involve integrating tool snapshots (See the EMME Modeller API guide).

[JamesVaughan]

This is a great idea. Do you have a list of tools that you would need in your workflow that we could prioritize?

[bccheung]

Our workflows heavily use network package IO tools, so those would be top of the list.

Afterwards, I would also suggest prioritizing tools useful in results post-processing (i.e., the traffic and transit analysis tools) and input/output (i.e., other import and export tools); basically any tool that would be part of an automated workflow that is used often.

All other tools that are used once in a while (e.g., network editing) would be lower priority, unless people think otherwise.

@JamesVaughan is there a minimum EMME version that the TMGToolbox is designed to support? I don't expect any backwards-compatibility issues associated with the changes to support EMME Flow, but it would be something we have to test out.

[bccheung]

Correction: I meant to say EMME Flow instead of EMME AGENT. The required changes allow the TMGToolbox tools to be used in EMME Flow modelling procedures.

Please note that EMME Flow is available to all EMME users, whereas EMME AGENT requires the AGENT Add-on.