- ACS year: 2023
- DCWS year(s): 2015-2024
Distribution-ready files are in to_distro. CSV file for
populating website’s community profiles is in website.
Starting December 2025, the DCWS data is from the multi-year MRP
estimates rather than single
years from crosstabs.
levelName
1 .
2 ¦--fetch_data
3 ¦ ¦--acs_basic_2023_fetch_all.rds
4 ¦ ¦--mrp_estimates_2015_2024_town_profiles.csv
5 ¦ °--mrp_moe_tbl.csv
6 ¦--output_data
7 ¦ ¦--acs_nhoods_by_city_2023.rds
8 ¦ ¦--acs_town_basic_profile_2023.csv
9 ¦ ¦--acs_town_basic_profile_2023.rds
10 ¦ ¦--cws_basic_indicators_2015_2024.rds
11 ¦ °--cws_basic_indicators_2024.rds
12 °--to_distro
13 ¦--bridgeport_acs_basic_neighborhood_2023.csv
14 ¦--hartford_acs_basic_neighborhood_2023.csv
15 ¦--new_haven_acs_basic_neighborhood_2023.csv
16 ¦--stamford_acs_basic_neighborhood_2023.csv
17 °--town_acs_basic_distro_2023.csv
Several global functions and other objects are loaded when each script
sources utils/pkgs_utils.R, including all loaded libraries. There are
two global variables for years: yr and cws_yr, for the ACS endyear
and the CWS year, respectively. Those are both set within a config file,
and can be taken as positional arguments by pkgs_utils.R.
To build the full project in the proper order, on the command line run:
snakemake allor rebuild just one piece of it, e.g. snakemake prep_distro.
Calling snakemake testvars will verify what years are being used by
sourcing just utils/pkgs_utils.R.
Additionally, this repo has a release of data in order to have a single source of the year’s ACS data for other projects. To create and upload the release, run:
snakemake releaseBuilding DAG of jobs...
