asu-trans-ai-lab / DTALite

GNU General Public License v3.0
74 stars 40 forks source link

Software release plan: target date 0701-2023 #12

Open asu-trans-ai-lab opened 1 year ago

asu-trans-ai-lab commented 1 year ago

DTALite Software Release Plan - Key Features: 07/01/2023

  1. Multiple Scenarios: • Enhance the software to support the creation and management of multiple scenarios. • Users can define and switch between different scenarios to analyze various transportation network configurations and demand patterns.
  2. Input: a) Supply Side: • Improve the supply side input functionality to allow users to define and customize various attributes related to the network infrastructure (e.g., nodes, links, capacities, geometries, special link types). • Enhance the input interface to support the specification of supply-side scenarios, such as incidents, road closures, or alternative routes. b) Demand Side: • Enhance the demand side input functionality to enable users to define and input various demand attributes (e.g., origin-destination pairs, volume, mode choice, time periods). • Incorporate the ability to import activity travel and choice set data for activity-based models, enabling more comprehensive analysis and modeling.
  3. Output: a) Link Measures of Effectiveness (MOE): • Improve the link MOE output functionality to provide comprehensive and detailed information about link-level performance metrics (e.g., travel time, speed, volume, congestion levels) for each scenario. • Enhance the visualization and reporting capabilities to present the link MOE data in a clear and user-friendly manner. b) Route Assignment: • Enhance the route assignment output functionality to generate detailed information about the assigned routes for different agents and scenarios. • Provide insights into the volume, tolls, travel time, and distance of each assigned path, as well as the link sequence and time sequence.
  4. Test Example: • Develop a test example that covers a realistic transportation network scenario with multiple supply and demand variations. • Ensure the test example incorporates diverse features, such as different link types, demand patterns, and scenarios, to validate the software's capabilities and performance.
  5. Additional Features - Activity-Based Models: • Extend the software's functionality to support the unified formulation of activity-based models. • Incorporate the input and processing of activity travel and choice set data to enable comprehensive analysis of activity-based travel behavior and decision-making processes. • Provide output features that present the choice sets and associated attributes for each scenario, facilitating in-depth analysis and understanding of mode and route choices.
  6. Link MOE Summary Across Scenarios: • Implement a feature to generate a summary of link MOEs across multiple scenarios. • Enable users to compare and analyze the performance of links across different scenarios, identifying trends and differences in network performance.
  7. System Performance Across Scenarios: • Enhance the system performance analysis functionality to generate comprehensive reports and visualizations that summarize the overall performance of the transportation system across multiple scenarios. • Provide insights into key metrics such as total travel time, congestion levels, mode splits, and efficiency measures.
  8. Documentation and Collaborative Support: • Update the software documentation to include detailed instructions and explanations for the new features. • Provide collaborative support and training materials to assist users in effectively utilizing the multiple scenario, input, and output features. • Encourage collaborative learning and problem-solving through online forums, user communities, and support channels. Release Schedule: • Conduct thorough development and testing of the new features, ensuring their stability and functionality. • Conduct internal testing and gather feedback from a select group of users to validate the effectiveness and usability of the added features. • Incorporate the feedback and make necessary improvements and adjustments. • Plan a beta release for a wider user base, allowing for additional feedback and bug identification. • Address any identified issues and finalize the software for the official release. • Announce and distribute the new release to the user community, providing comprehensive documentation and support resources.
asu-trans-ai-lab commented 1 year ago

Move this feature to future release: Additional Features - Activity-Based Models: • Extend the software's functionality to support the unified formulation of activity-based models. • Incorporate the input and processing of activity travel and choice set data to enable comprehensive analysis of activity-based travel behavior and decision-making processes. • Provide output features that present the choice sets and associated attributes for each scenario, facilitating in-depth analysis and understanding of mode and route choices.