Skip to content
Elizabeth Theocharides edited this page Oct 30, 2019 · 23 revisions

Code Cleaning

Cleaning

  1. Build separate settings files:
  • settings.yaml
  • scenarios.yaml: scen definition, (maybe not much else yet)
  • policy.yaml
  • hazards.yaml (everything on hazards and hazards policy)
  1. Subdivide data directory
  • /data (i.e., still at the top level): README.md,
  • /data/baseyear: baseyear_taz_controls.csv, county_forecast_inputs.csv, deed_restricted_zone_totals.csv, juris_controls.csv (used for overrride, may drop), taz_forecast_inputs.csv, taz2_foreacast_inputs.csv
  • /data/accessibility: all AccessibilityMarkets files, all mandatoryAccessibility files, all nonMandatoryAccessibiity files, logsums.csv(is this still in use?)
  • /data/hazards: parcel_tract_xwalk.csv, all slr files, tract_damage_earthquale.csv
  • /data/policies: all zoning_mods files, vmt_fee_zonecats.csv, abag_targets.csv, rhna_by_juris.csv
  • /data/control_totals/: all employment_controls files, all household_controls files, all regional_controls files, all regional_demographic_forecast files, county_employment_forecast.csv, zone_forecast_inputs.csv, maz_forecast_inputs.csv
  1. Scenarios
  • Remove scenario settings from model logic
  • Remove scenario numbers from model logic (variables okay)
  1. Clean up development projects csv/xls
  • Assess duplicate projects (verify how they're treated)
  • Return to varied scenarios once bug is fixed
  • Fill in missing data ie "city"
  • Create multiple files, or make source of project clear within single file
  1. Overlapping code - clean or document
  • sqft per employee
  • developer profit margin/cap rate
  • household relocation rates (and maybe employee?)

To Edit

To Drop (or move to snippets folder in /scripts)

  • (preprocessing) move_jobs_from_portola_to_san_mateo_county
  • (preprocessing) household_building_id_overrides.csv ???

To Zero Out

To Add

Keep Eye on While Updating Baseyear