-
Notifications
You must be signed in to change notification settings - Fork 780
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
add BaseLearner() so that other meta learners inherit from it #295
Conversation
125fe47
to
6bd5a49
Compare
6bd5a49
to
4708da2
Compare
causalml/inference/nn/cevae.py
Outdated
pyro_logger = logging.getLogger("pyro") | ||
pyro_logger.setLevel(logging.DEBUG) | ||
if pyro_logger.handlers: | ||
pyro_logger.handlers[0].setLevel(logging.DEBUG) | ||
|
||
|
||
class CEVAE(object): |
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.
Should we inherit the BaseLearner
here?
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.
We can't because currently CEVAE
and DragonNet
don't have estimate_ate()
. I will remove it from DragonNet
as well.
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.
Done.
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.
Thanks, LGTM!
* 757: add return_ci=True in sensitivity * remove if-else logic - resolved in #295 * black
Proposed changes
This PR fixes #294. It adds the
BaseLearner
class with the bootstrapping and interpretability functions so that other meta-learners inherit them from it without duplicated code.Types of changes
What types of changes does your code introduce to CausalML?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
N/A