Skip to content

Explicitly pick out used columns #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 6, 2021
Merged

Explicitly pick out used columns #104

merged 1 commit into from
Apr 6, 2021

Conversation

eujing
Copy link
Contributor

@eujing eujing commented Apr 6, 2021

Upon loading RDS files downloaded from the S3 bucket, explicitly picks out the expected columns from each RDS file before the rbind.

Addresses #102, in case evalcast produces extra unexpected columns for any of the RDS files again.

@eujing eujing requested a review from kateharwood April 6, 2021 18:11

# Pick out expected columns only
covCols = paste0("cov_", COVERAGE_INTERVALS)
expectedCols = c("ahead", "geo_value", "forecaster", "forecast_date",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Worth noting that we don't use all of these columns when processing the data later on (for instance, we don't need "data_source", and we don't currently use "forecast_date"), but might still be a good idea to keep them in, just in case.

@eujing eujing merged commit edafff2 into dev Apr 6, 2021
@kateharwood kateharwood deleted the dev-explicit-cols branch May 4, 2021 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants