Project Meeting 2022.06.16

Meeting Notes

Admin Items

• AMPO Conference presentation (October 25 - 28 in Minneapolis) was accepted
  • ACTION ITEM: Jeff to forward paperwork (email) of acceptance to meeting participants
• Discussion of PR #571 Fictional Place Names
  • How do we name and maintain the example model? (issue includes background on reason for pull request)
  • OK with saying it’s based on MTC but to add clear documentation
    • What is the purpose
    • How it was developed (note that it is based on real data but not consistent with a model that is an official, adopted model)
    • How it is different (which no one is 100% sure about at this point)
  • While there isn’t any official/adopted production model available in ActivitySim, there will be one day. Somehow, we should be able to distinguish those that can be picked up and used. Is there some kind of naming scheme that would help us distinguish between test and official models?
    • Using “production” when it is official
  • Suggested name: Example MTC and MTC Extended
    • Other names floated MTC Classic
  • What should be our canonical model? Example MTC is missing a lot.
    • Should we have a kitchen sink model? (Because it’s easier to cut things than add)
    • And then a simple model.
    • Should there be a middle ground model?
• Component Design Philosophy: Technical Subcommittee?
  • Proposal: create a technical team of 3-5 people to discuss and create a plan to bring to the larger group to resolve technical issues. They make the tentative decision to solve various problems and have group vote on their proposed solution.
  • Instead of a switch between versions of components, it could be more of a swap. The downside of that is that there are two code bases for this component – so if someone found a way to enhance CDAP (for example) they’d have to implement it twice, for both versions.
  • ACTION ITEM: Jeff to solicit volunteers, create a list of questions to be answered, and then a month or so to start providing solutions. This is a pilot test for a new approach to resolving technical issues.