Input data format #25464
Merged
Input data format #25464
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The documentation is not available anymore as the PR was closed or merged. |
amyeroberts
force-pushed
the
input-data-format
branch
from
c950341 to
8aef2a0
Compare
amyeroberts
force-pushed
the
input-data-format
branch
from
276cce5 to
e113320
Compare
amyeroberts
force-pushed
the
input-data-format
branch
from
e113320 to
3c5a39d
Compare
sgugger
approved these changes
Aug 16, 2023
| **kwargs, | ||
| ) -> np.ndarray: | ||
| """ | ||
| Resize the image to the given size. Size can be `min_size` (scalar) or `(height, width)` tuple. If size is an | ||
| int, smaller edge of the image will be matched to this number. | ||
|
|
||
| Args: |
| Image to resize. | ||
| size (`Dict[str, int]`): | ||
| The size of the output image. | ||
| size_divisor (`int`, *optional*, defaults to `0`): |
There was a problem hiding this comment.
Nit:
Suggested change
| size_divisor (`int`, *optional*, defaults to `0`): | |
| size_divisor (`int`, *optional*, defaults to 0): |
| Image to resize. | ||
| size (`Dict[str, int]`): | ||
| The size of the output image. | ||
| size_divisor (`int`, *optional*, defaults to `0`): |
There was a problem hiding this comment.
Suggested change
| size_divisor (`int`, *optional*, defaults to `0`): | |
| size_divisor (`int`, *optional*, defaults to 0): |
( may have missed some so worth doing a quick search!)
This was referenced Aug 16, 2023
Closed
5 tasks
4 tasks
blbadger
pushed a commit
to blbadger/transformers
that referenced
this pull request
Nov 8, 2023
* Add copied from statements for image processors * Move out rescale and normalize to base image processor * Remove rescale and normalize from vit (post rebase) * Update docstrings and tidy up * PR comments * Add input_data_format as preprocess argument * Resolve tests and tidy up * Remove num_channels argument * Update doc strings -> default ints not in code formatting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds the
input_data_formatargument to all of the image processor methods.This allows for passing in of images with an unusual number of channels, or ones where it's difficult to infer because of ambiguity e.g size (3, 3, 3).
This is an alternative to #24577
Fixes issues like:
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.