Skip to content
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

Reconsider requiring the data to have specific column names including location in get_baseline_predictions #6

Open
elray1 opened this issue Sep 10, 2024 · 0 comments

Comments

@elray1
Copy link
Contributor

elray1 commented Sep 10, 2024

In some sense this is actually 2-3 separate issues, all related to columns required in the input target_ts:

  1. Do we need to require that the data has a column containing values of location?
  2. What if my data has another "key" or "stratifying" variable, like age_group?
  3. Do we need to enforce specific names for these columns like time_index and observation, or could we allow for flexibility in these column names, possibly even via a formula interface
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

No branches or pull requests

1 participant