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

nobrainer dataset API rework #261

Merged
merged 27 commits into from
Aug 31, 2023
Merged

nobrainer dataset API rework #261

merged 27 commits into from
Aug 31, 2023

Conversation

ohinds
Copy link
Contributor

@ohinds ohinds commented Aug 30, 2023

Types of changes

  • Bug fix (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 change)

Summary

Major rework of the nobrainer dataset API. This provides much more flexibility in creating and manipulating datasets, e.g. for augmentation, shuffling, repeating, and arbitrary mapping.

Fixes #244 and #254.

Checklist

  • I have added tests to cover my changes
  • I have updated documentation (if necessary)

Acknowledgment

  • I acknowledge that this contribution will be available under the Apache 2 license.

@ohinds
Copy link
Contributor Author

ohinds commented Aug 30, 2023

Note that there is a parallel PR in the nobrainer-book repo that updates the guide with the dataset workflow represented here.
neuronets/nobrainer-book#8

Copy link
Contributor

@satra satra left a comment

Choose a reason for hiding this comment

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

Overall looks like a nice refactor. Tests are failing though. I'm going to tag this PR for a release, so that once this is green and merged, it will create a release.

@ohinds ohinds merged commit f91b693 into master Aug 31, 2023
9 checks passed
@ohinds ohinds deleted the ohinds-nb-dataset branch August 31, 2023 19:57
@satra
Copy link
Contributor

satra commented Sep 2, 2023

@ohinds - this created a major release. i should have checked the existing labels before tagging a release. i was hoping to avoid major till we settled on api.

@ohinds
Copy link
Contributor Author

ohinds commented Sep 2, 2023 via email

@satra
Copy link
Contributor

satra commented Sep 4, 2023

undo requires a set of steps but we will never be able to release a 1.0.0 since pypi doesn't allow replacing a version that has been released. let's just go with what has happened.

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.

Calling map() on a nobrainer-created dataset discards nobrainer-specific members
2 participants