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

effectiveness / averted / etc functionality #2

Open
pearsonca opened this issue Aug 31, 2022 · 1 comment
Open

effectiveness / averted / etc functionality #2

pearsonca opened this issue Aug 31, 2022 · 1 comment
Labels
TODO need to haves

Comments

@pearsonca
Copy link
Owner

pearsonca commented Aug 31, 2022

Typical scenario comparison problem looks like:

  • have a bunch of scenarios, grouping on different elements, with time series of outcomes (some times long format, i.e. two column of outcome and val; sometimes wide on outcome1, outcome2, ...), replicated
  • a subset (often single element, but not necessarily) of those represent the reference case(s)
  • we want to compute the matched differences of the outcomes
  • in a variety of ways (averted, relative averted i.e. effectiveness, cumulative versions of previous, cumulative from a particular point in time)

Desired interface:

  • need data.table + scenario key + replication key + reference scenario identifier + outcome identifier + desired calcs
  • typical calculations should just be implemented
  • want: support for some custom additional calculations
  • want: variable time resolution output (i.e., if input is daily time series, support weekly / monthly / yearly / etc time series outputs)
  • want smart imputing of input needs elements (e.g. from data.table key, date for date, check for a value column => long format)
  • want data.table-like interface
  • want quantile.data.table-ready output (as this is typical next step)
@pearsonca
Copy link
Owner Author

  • reference identifier has to be a 1 to M key of scenario key (with M potentially 1, but generally allowed to be > 1).
  • want: an auxilary function that will take a scenario table, with key, dimension 1, dimension 2, ..., etc columns and then receive a grouping statement (defining how to distinguish reference scenarios) which will extract the 1 to M relationships

@pearsonca pearsonca added the TODO need to haves label Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TODO need to haves
Projects
None yet
Development

No branches or pull requests

1 participant