feat: better location model diagnostics

[asiripanich]

How to Use This New Feature

The location model diagnostic requires users to modify the MODELS global variable in the dashboard script. This is because each ActivitySim implementation can have different field names for elements such as the distance column in the skims table.

A YAML setting file that will allow users to specify their specific MODELS is in the plan. :)

Consequently, new fields — skims_variable, land_use_control_variable, and origin_zone_variable — have been added to the location model

• skims_variable refers to the field in the skims table that will be used for generating the distance distribution
• land_use_control_variable refers to the field in the land use table that will be used for generating the differences-to-land-use plot. In the case of the school location model, you might use a field representing the total enrollment in that zone.
• origin_zone_variable refers to the zone column that will be used to merge with the origin column of the skims table.

 "school_location": {
                "table": "persons",
                "result_field": "school_zone_id",
                "filter_expr": pl.col("school_zone_id") > 0,
                "skims_variable": "DIST",
                "land_use_control_variable": "COLLFTE",
                "origin_zone_variable": "home_zone_id",
            },

New plots

Other changes

• New summary table style
  • 
• New column select UI
  •