-
Notifications
You must be signed in to change notification settings - Fork 6
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
Preprocessed data handler superclass #147
Conversation
can you please include a few elexmodel commands you tried? |
…nto preprocessed-data-handler-superclass
Sure! I just ran this:
I did it on |
ok, thanks. I'm curious, does the historical flag still work at all? |
Yup, so, our integration tests work, and also this works:
And this works:
For using |
The historical flag works in the example you sent and shows the same output as dev? |
Actually this is really interesting. If I run this command multiple times on
I get different results every time. And somewhat dramatically so. For the
Sometimes it'll be closer to 2k:
Or
Is this to be expected...? 🤔 🤔 |
yes, the reporting counties are randomly selected every time. you need to set |
OMG right, I'm so sorry, I totally forgot about that 🙈 Ok, if I change that command to |
…nto preprocessed-data-handler-superclass
Description
Hi! The changes in this PR create a
BasePreprocessedDataHander
superclass that data handlers that work with preprocessed model input data now inherit from. This should help reduce some code redundancy. Thanks! 🎉This code was previously part of #145 👍🏻
Jira Ticket
Test Steps
tox
,elexmodel
commands, test bed 🎉