Skip to content

Project Meeting 2023.11.14

kadannemiller edited this page Nov 20, 2023 · 7 revisions

Agenda

  • Admin
    • Solicitation for agency ActivitySim experience call with Queensland Dept of Transport and Main Roads
  • Tech
    • Input Checker Update (RSG)
    • Documentation Update (CS)

Meeting Notes

Documentation Update (CS – Vivek Yadev)

  • Previous update:
    • Color-coded status spreadsheet
    • Lists additional files in the utility folder:
      • Only incomplete file: canonical_ids.py
  • Rendered documentation for all components on Github:
    • Models without documentation:
      • Initialize_tours.py
      • Joint_tour_frequency_composition.py
      • Summarize.py
      • Tour_od_choice.py
      • Tour_scheduling_probabilistic.py
  • RSG/WSP Review
    • No specific instructions as of now.
    • “Config Settings and Documentation” pull request.
    • Circle back with Jeff/David/Sijia/Dave. Let the consortium know how the review will be handled, amount of time needed, and the schedule for completion.
  • User Guide
    • To be shared 11/28.
    • No further comments beyond redundancies and Joe C.’s initial comments/requests/suggestions.

Input Checker Update (RSG -David Hensle)

  • Presentation Slides: input_checker_pt6_final.pptx
  • Input Checker Features
  • Previous Implementation
    • Utilizing feedback from CS and WSP, moved away from confusing implementation towards Pandera.
  • How does Pandera Work?
    • Discussion regarding Pandera vs. Pydantic: Pydantic has been left in the code to be used in future implementations (if necessary).
    • Aesthetically cleaner implementation – python code.
    • Pandera handles work under the hood - Speedy, easy syntax, and built-in error reporting
  • “Data Model” Support: enumn.py
    • Data Model Folder
    • Example: production_semcog
  • Input Checker Structure
    • Run ActivitySim normally, with an additional data_model folder.
    • Errors/warnings output to the XX
    • Input_checker.yaml
      • Export the network to a .csv file, which is passed into ActivitySim. Add this step to the documentation, which will live as an ActivitySim documentation “model.”
  • Output Logging
    • ActivtySim logger displays high level details
    • Input checker results displayed neatly in input_checker.log
  • Checks Provided in Examples Include:
    • Checking that all columns exist,
    • Ensure columns have allowed values’ cross-checks within table,
    • Cross-checks between tables,
    • Skims listed in tour_mode_choice.csv are in the skims.omx file, and
    • Can write anything desired using python code.

Further Discussion

  • Oregon is approaching their joint estimation design. In order to move into estimation, Oregon needs to use an instance of ActivitySim.
    • Questions regarding the timing?
    • On the radar: How to manage examples going forward? Break up the code? Spend a few days pulling code, allow a second set of eyes?
  • Solicitation for agency ActivitySim experience call with Queensland Department of Transport and main Roads.

Going Forward

  • Next Week (11/21): Cancelled for week of Thanksgiving.
Clone this wiki locally