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

Allow user to specify aggregation period completeness threshold? #216

Open
wdwatkins opened this issue Aug 3, 2017 · 0 comments
Open

Allow user to specify aggregation period completeness threshold? #216

wdwatkins opened this issue Aug 3, 2017 · 0 comments

Comments

@wdwatkins
Copy link
Contributor

wdwatkins commented Aug 3, 2017

For predictSolute.loadReg2, currently the only control over this is the allow.incomplete argument to rloadest::predLoad, which is just a logical:

If allow.incomplete is TRUE, then loads will be computed based on all nonmissing values, otherwise 
missing values NAs will be returned. For this application, missing values includes NAs and gaps in 
the record, except for by set to "total" or user defined groups where missing values only includes 
NAs. For prediction by "day" when there are variable number of unit values per day, allow.incomplete
 must be set to TRUE.

It might be nice in the future for users to specify a threshold for what is deemed 'complete'. There are probably a couple ways this could be done, with varying levels of complexity for different time periods. Challenges would include knowing what data should be there for a complete period, handling different combinations of periods/data frequency, and possibly edge cases with first/last periods. The argument would need to either be a fraction, or perhaps it would be easiest to just be number of measures, relying on the user to know what they want for a given aggregation period.

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