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

Reviewed LogisticRegression #950

Merged

Conversation

Ce11an
Copy link
Contributor

@Ce11an Ce11an commented Nov 27, 2022

What does this PR do?

Reviewed LogisticRegression as part of #839

Still need to do the following before merging:

  • Update tests
  • Discuss the coupling between the Model and the accuracy metric.
  • Discuss the coupling between the Model and the loss function.

Before submitting

  • Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes?
  • Did you write any new necessary tests? [not needed for typos/docs]
  • Did you verify new and existing tests pass locally with your changes?
  • If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

  • Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.

Did you have fun?

Of course 🥳

@github-actions github-actions bot added the model label Nov 27, 2022
@Ce11an
Copy link
Contributor Author

Ce11an commented Nov 27, 2022

Hey all 👋🏻

If I could have an initial review that would be great 😄

Are we happy to keep accuracy within the class? Ideally, I don't want to couple it, so if you have any suggestions/examples of Lighting code that solves this issue?

Also, do you have any recommendations on how to properly unit-test sub-classes of LightningModule?

Thanks!!

Created a new test folder structure for regression tests

Moved tests from `test_classic_ml.py` to `test_logistic_regression.py`
@Ce11an Ce11an marked this pull request as ready for review December 21, 2022 13:05
@stale stale bot added the won't fix This will not be worked on label Mar 18, 2023
@Lightning-Universe Lightning-Universe deleted a comment from stale bot Mar 18, 2023
@stale stale bot removed won't fix This will not be worked on labels Mar 18, 2023
@Borda Borda force-pushed the master branch 2 times, most recently from afdc09a to c5137b4 Compare May 19, 2023 17:15
@mergify mergify bot removed the has conflicts label May 19, 2023
src/pl_bolts/models/regression/logistic_regression.py Outdated Show resolved Hide resolved
src/pl_bolts/models/regression/logistic_regression.py Outdated Show resolved Hide resolved
@Borda Borda enabled auto-merge (squash) May 20, 2023 21:05
@mergify mergify bot added the ready label May 21, 2023
@Borda Borda merged commit 4ef2750 into Lightning-Universe:master May 21, 2023
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants