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

Adding CLEAR-10 benchmark to Avalanche #965

Merged
merged 4 commits into from
Apr 5, 2022

Conversation

linzhiqiu
Copy link
Contributor

#964 PR for this feature request

@coveralls
Copy link

coveralls commented Apr 1, 2022

Pull Request Test Coverage Report for Build 2077989484

  • 53 of 268 (19.78%) changed or added relevant lines in 5 files are covered.
  • 2 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.9%) to 71.701%

Changes Missing Coverage Covered Lines Changed/Added Lines %
avalanche/benchmarks/classic/clear.py 11 50 22.0%
avalanche/benchmarks/datasets/clear/clear.py 35 211 16.59%
Files with Coverage Reduction New Missed Lines %
avalanche/benchmarks/scenarios/generic_definitions.py 2 85.37%
Totals Coverage Status
Change from base Build 2071800302: -0.9%
Covered Lines: 11688
Relevant Lines: 16301

💛 - Coveralls

Copy link
Collaborator

@lrzpellegrini lrzpellegrini left a comment

Choose a reason for hiding this comment

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

Thank you, the PR looks great! Everything seems to be in order apart from a comment I left regarding transformations.

raise NotImplementedError()

if feature_type is None:
assert isinstance(train_transform, type(None)), "No image transform"
Copy link
Collaborator

Choose a reason for hiding this comment

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

I haven't tried to run the code, but from the main below it seems that non-None transformations should be allowed when feature_type is None...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are right, I should remove the assertion statement (it was a typo). My original purpose is to make sure the user specify a transformation for image, and not inputting a transformation for feature tensors. But on a second thought, I should leave this choice to users!

@linzhiqiu
Copy link
Contributor Author

Made the change by removing assertion statements.

@linzhiqiu linzhiqiu requested a review from lrzpellegrini April 1, 2022 19:45
@AntonioCarta
Copy link
Collaborator

@lrzpellegrini if you are satisfied we can merge the PR.

@AntonioCarta AntonioCarta merged commit a77815a into ContinualAI:master Apr 5, 2022
@AntonioCarta
Copy link
Collaborator

Thanks again @linzhiqiu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants