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

Add support for selecting/excluding group slices #5198

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

Conversation

brimoor
Copy link
Contributor

@brimoor brimoor commented Dec 1, 2024

Change log

  • Adds a select_group_slices(..., flat=False) syntax for selecting group slices w/o flattening
  • Adds a exclude_group_slices() method for excluding group slices (also w/o flattening, as this is the only behavior that makes sense when excluding group slices in general)

TODO

  • Update App to use view.group_slices/view.group_media_types rather than dataset.group_slices/dataset.group_media_types, as the former may no longer always match the latter

Example usage

import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart-groups")
session = fo.launch_app(dataset)
view1 = dataset.select_group_slices(["left", "right"], flat=False)

assert view1.media_type == "group"
assert view1.group_slices == ["left", "right"]

# TODO: respect `view1.group_slices` in App
session.view = view1
view2 = dataset.exclude_group_slices("pcd")

assert view2.media_type == "group"
assert view2.group_slices == ["left", "right"]

# TODO: respect `view2.group_slices` in App
session.view = view2

@brimoor brimoor added the feature Work on a feature request label Dec 1, 2024
Copy link
Contributor

coderabbitai bot commented Dec 1, 2024

Warning

Rate limit exceeded

@brimoor has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 8820555 and 73a775b.

📒 Files selected for processing (7)
  • docs/source/user_guide/groups.rst (3 hunks)
  • fiftyone/__public__.py (1 hunks)
  • fiftyone/core/collections.py (6 hunks)
  • fiftyone/core/dataset.py (2 hunks)
  • fiftyone/core/stages.py (16 hunks)
  • fiftyone/core/view.py (13 hunks)
  • tests/unittests/group_tests.py (2 hunks)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Base automatically changed from release/v1.1.0 to main December 6, 2024 15:31
@brimoor brimoor changed the title [HOLD] Add support for selecting/excluding group slices Add support for selecting/excluding group slices Dec 9, 2024
@brimoor brimoor changed the base branch from main to develop December 9, 2024 05:50
@brimoor brimoor marked this pull request as ready for review December 9, 2024 05:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Work on a feature request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant