Skip to content

Project Meeting 2018.10.15

stefancoe edited this page Oct 17, 2018 · 6 revisions

Attendees:

  • Mark, Hana, Stefan, Peter, Brice, Mike

Purpose

  • First project meeting with full team to discuss resumption of UrbanSim 2 development
  • Discuss development priorities- Developer Model, Allocation, Sampling

Developer Model:

  • Issues with existing UrbanSim 2 developer model:
    • Multiple proposals- for a given project, multiple proposals should be available during the selection process, not just the one with the highest ROI.
    • Competition between types- Proposals during selection process should not be limited to either residential or non-residential when zoning supports both uses. Mixed use should also be supported.
    • More detail in Hana's Denver presentation. Will add link.
  • Some of these Issues have been addressed in UDST's Developer repository: https://github.com/UDST/developer

Allocation Mode:

  • PSRC's Urbansim implementation allows for control totals to be applied at sub-regional geographies.
  • PSRC's Landuse forecasts are created using allocation mode to meet jurisdictional growth targets.
  • This is a must have for UrbanSim 2.
  • Current implementation runs allocation mode every five years to ensure control totals are met. Allocation mode basically runs, in a loop, an Urbansim instance for each jurisdictional control total.
  • Give us an opportunity to think of a better implementation, perhaps run for every simulation year.

Sampling:

  • Need to support targeted sampling:
    • For example- in the hlcm, use household income group to sample alternatives that meet a min and max price range for each income group.
    • Explore possible ways to implement this, including how Urbansim currently does it.

Next Steps:

  • Focus on Developer model:
    • Some work has been done on the Multiple Proposals issue- https://github.com/UDST/developer/tree/keep-suboptimal
    • Hana has reached out to Eddie Janowicz at UDST to see if this work will get merged with the trunk. Sounds like this will happen.
    • Hana, with help from team will look into this code, figure out what is there, what is missing, possibly pull code and start working on it. Start a 'sprint' to implement functional developer model.
  • Start specifying allocation mode:
    • Project Team will start thinking about this. Possibly borrow some ideas from ActivitySim multi-processing work.
  • Sampling:
    • Some work was done on this, but never merged back into Urbansim repo. Let's revisit this as time allows.