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

black formatting and migrated to self.log logging in finetuning example #5229

Merged
merged 7 commits into from
Jan 4, 2021
Merged

black formatting and migrated to self.log logging in finetuning example #5229

merged 7 commits into from
Jan 4, 2021

Conversation

jspaezp
Copy link
Contributor

@jspaezp jspaezp commented Dec 22, 2020

What does this PR do?

As discussed in #5174, it fixes the computer_vision_fine_tuning example.

  1. It currently fails to run due to incorrect argument passing
  2. Throws deprecation warning because it uses the old return {'log': ...} syntax instead of the current self.log(...) syntax.
  3. Syntax does not follow the contributions guidelines (black formatting)

I noticed the changes seem fairly large due to black changing some of the formatting (which is suggested in the contribution guidelines pre-commit). Let me know if you want these changes to be rolled back to preserve the 'blame' of the repository

Let me know if you would like anything to be changed.

Fixes # (issue)

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? Otherwise, we ask you to create a separate PR for every change.
  • Did you make sure to update the documentation with your changes?
  • Did you write any new necessary tests?
  • 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

Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified; Bugfixes should be including in bug-fix release milestones (m.f.X) and features should be included in (m.X.b) releases.

Did you have fun?

Make sure you had fun coding 🙃
I did have fun coding

Kindest wishes,
Sebastian

@codecov
Copy link

codecov bot commented Dec 22, 2020

Codecov Report

Merging #5229 (83ce172) into master (51af395) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5229   +/-   ##
======================================
  Coverage      93%     93%           
======================================
  Files         134     134           
  Lines        9950    9950           
======================================
  Hits         9261    9261           
  Misses        689     689           

Copy link
Member

@awaelchli awaelchli left a comment

Choose a reason for hiding this comment

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

LGTM, perhaps in a follow up one could further simplify by using the metrics api (Accuracy). 🥂

@awaelchli awaelchli added example bug Something isn't working feature Is an improvement or enhancement labels Dec 22, 2020
@awaelchli awaelchli added this to the 1.1.x milestone Dec 22, 2020
@awaelchli awaelchli changed the title black formatting and migrated to self.log logging black formatting and migrated to self.log logging in finetuning example Dec 22, 2020
Borda and others added 2 commits December 23, 2020 09:01
Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>
migrated to accuracy in the metrics package
@pep8speaks
Copy link

pep8speaks commented Dec 24, 2020

Hello @jspaezp! Thanks for updating this PR.

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2021-01-04 12:43:26 UTC

@rohitgr7 rohitgr7 added the ready PRs ready to be merged label Dec 31, 2020
Copy link
Member

@SkafteNicki SkafteNicki left a comment

Choose a reason for hiding this comment

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

LGTM

@SkafteNicki SkafteNicki merged commit 17a0784 into Lightning-AI:master Jan 4, 2021
@jspaezp jspaezp deleted the exmaple/update_cv_fine_tuning branch January 5, 2021 16:09
Borda pushed a commit that referenced this pull request Jan 6, 2021
…le (#5229)

* black formatting and migrated to self.log logging

* Apply suggestions from code review

Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>

* migrated to accuracy in the metrics package

migrated to accuracy in the metrics package

* removed trailing whitespace

* Apply suggestions from code review

Co-authored-by: Jirka Borovec <Borda@users.noreply.github.com>
Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>
Co-authored-by: Nicki Skafte <skaftenicki@gmail.com>
(cherry picked from commit 17a0784)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working example feature Is an improvement or enhancement ready PRs ready to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants