You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once #315 lands, we'll have four different places that we store information about features:
The vars dict CSV file that powers the ccao::vars_dict object, which we use as a crosswalk between the different names for our features in different data sources
The params.yaml file in this repo, whose model$predictor$all array records the canonical list of input features for the model
The README for this repo, which pulls information from all of the above sources to produce the Features Used table and the docs/data-dict.csv object
The fact that feature information is scattered across three different repos makes it confusing and brittle to maintain our features. We should consolidate some of these data sources so that they're easier to maintain. I think the lowest-hanging fruit is probably moving the variable crosswalk to the dbt DAG (related to ccao-data/ccao#30).
The text was updated successfully, but these errors were encountered:
Once #315 lands, we'll have four different places that we store information about features:
ccao::vars_dict
object, which we use as a crosswalk between the different names for our features in different data sourcesmodel/schema.yml
dbt config file, which records descriptions for featuresparams.yaml
file in this repo, whosemodel$predictor$all
array records the canonical list of input features for the modelFeatures Used
table and thedocs/data-dict.csv
objectThe fact that feature information is scattered across three different repos makes it confusing and brittle to maintain our features. We should consolidate some of these data sources so that they're easier to maintain. I think the lowest-hanging fruit is probably moving the variable crosswalk to the dbt DAG (related to ccao-data/ccao#30).
The text was updated successfully, but these errors were encountered: