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

Fix edge case issue in uniform_temporal_sampling #114

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

yassersouri
Copy link

@yassersouri yassersouri commented Sep 7, 2021

Motivation and Context

Current behavior of the uniform_temporal_sampling function has an undesirable property when dealing with smaller than num_samples input.

For example:

uniform_temporal_subsample(torch.arange(4), num_samples=4, temporal_dim=0)
# tensor([0, 1, 2, 3])  (looks good)

uniform_temporal_subsample(torch.arange(4), num_samples=5, temporal_dim=0)
# tensor([0, 0, 1, 2, 3]) (looks good)

uniform_temporal_subsample(torch.arange(4), num_samples=6, temporal_dim=0)
# tensor([0, 0, 1, 1, 2, 3]) (looks good)

uniform_temporal_subsample(torch.arange(4), num_samples=7, temporal_dim=0)
# tensor([0, 0, 1, 1, 2, 2, 3]) (looks good)

uniform_temporal_subsample(torch.arange(4), num_samples=8, temporal_dim=0)
# tensor([0, 0, 0, 1, 1, 2, 2, 3]) (ISSUE: should be [0, 0, 1, 1, 2, 2, 3, 3])

uniform_temporal_subsample(torch.arange(4), num_samples=9, temporal_dim=0)
# tensor([0, 0, 0, 1, 1, 1, 2, 2, 3])  (ISSUE: should be [0, 0, 0, 1, 1, 2, 2, 3, 3])

How Has This Been Tested

I have tested the implementation myself, but I have not created a test for it.

Types of changes

  • Docs change / refactoring / dependency upgrade
  • 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)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have completed my CLA (see CONTRIBUTING)
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@facebook-github-bot
Copy link
Contributor

Hi @yassersouri!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 7, 2021
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants