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

code cleanups #634

Merged
merged 3 commits into from
Jul 20, 2023
Merged

code cleanups #634

merged 3 commits into from
Jul 20, 2023

Conversation

xhulianoThe1
Copy link
Contributor

Proposed changes

Small code cleanups.

Types of changes

What types of changes does your code introduce to CausalML?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

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.

  • I have read the CONTRIBUTING doc
  • I have signed the CLA
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc. This PR template is adopted from appium.

@xhulianoThe1
Copy link
Contributor Author

@jeongyoonlee updated!

Copy link
Collaborator

@jeongyoonlee jeongyoonlee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution! LGTM except one for tmle.py. If you'd like to keep this PR simple without touching tmle.py, that's fine too.

@@ -126,7 +126,7 @@ def __repr__(self):
self.__class__.__name__, self.model_tau.__repr__(), self.cv
)

def estimate_ate(self, X, treatment, y, p, segment=None, return_ci=False):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, it should follow the signature from causalml.inference.meta.base.BaseLearner.estimate_ate(). Can you update TMLELearner to inherit from BaseLearner and keep the function signatures consistent with other meta learners?

Copy link
Contributor Author

@xhulianoThe1 xhulianoThe1 Jul 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated @jeongyoonlee and will keep this pull request simple. Will open a new one for a deeper dive into tmle.py

@jeongyoonlee jeongyoonlee added the refactoring Code refactoring label Jul 20, 2023
Copy link
Collaborator

@jeongyoonlee jeongyoonlee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

@jeongyoonlee jeongyoonlee merged commit 40c11e8 into uber:master Jul 20, 2023
3 of 6 checks passed
ras44 pushed a commit to ras44/causalml that referenced this pull request Aug 22, 2023
* code cleanups
* lint error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Code refactoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants