-
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
ELEX-2763: Estimandizer update #73
Conversation
Hi @lennybronner , I'm stuck and need help with the integration tests The one failing is this one:
The issue is that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks v good! Though atm the integration tests are failing. Also when I run a historical election all subunits are unexpected.
Thanks! Sorry about the failing integration tests. I have a question about that in a comment for you (above) because I'm confused about how we're expecting that test to work 🤔 In regards to the unexpected subunits, can you provide an example for that that I can look into? 🤔 |
oh oops, sorry I missed that. How was this test passing earlier? 🤔 Here is an example of all units being unexpected:
|
Description
The changes in this PR refine the changes made in PR #59. Hopefully the code and logic are much cleaner now. Thanks to @lennybronner for making most of these changes lol and the helpful feedback 😄 🙌🏻
Note that, as a result of these changes, a change will need to be made to the test bed; specifically, in
modeltestbed/redo.py
,include_results_estimand=True
will need to be added to the constructor. Previously, I was trying to avoid having to modify the test bed, but that lead to some ugliness 🙈. But this change is extremely minimal and the rest of the code is much cleaner now, so IMO, it's worth it.Jira Ticket
ELEX-2763
Test Steps
tox
and you can also modify the test bed per the above (until the test bed itself is modified, of course). Thanks!