mostly- or partly-developed zones and could simulate urban growth boundaries by restricting land availability in outer zones.
The second input parameter affecting the land market was the constant term in the submodel for zonal developer choice to change from one land use type to another. We made available all of these constants for changing from Vacant to Vacant and from Vacant to each of the developed land uses (Industrial, High-Density Commercial, Low-Density Commercial, High-Density Residential, Medium-Density Residential, and Low-Density Residential), or from any developed land use to any other developed land use. The purpose of changing this parameter was to simulate hot markets for certain land uses (new or redeveloped) in certain zones, or to simulate real estate investment biases, such as for low-density housing or for offices.
Several (of the many) model outputs were made readily available in the GUI, including: regionwide VMT (which would also represent mobile emissions and energy use), mode shares, average trip speed, number of trips, population by zone, and employees by type by zone. The user interface made it possible for students to compare all years within the same policy run or the same year across two different policy runs.
Clay was in charge of meeting with the programmer to get the GUI done, during the quarter before the class. This involved about three meetings with both of us and ten with only Clay and the programmer, over a two-month period. The GUI was done a month before the class started and was tested with many combinations of inputs and mis-keying in every way the instructors could devise. After two brief debugging sessions with the programmer, it was believed that the GUI was clean.