Repository navigation
Add SimReady Central search in env gen #1513
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
Open
xyao-nv
wants to merge
9
commits into
main
Choose a base branch
from
xyao/feature/simready-central
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
41af2a8
Add single-body SimReady Central asset search
xyao-nv 847ba2e
Note future Newton support for SimReady Central
xyao-nv d291faf
Add SimReady source lists and Central scene example
xyao-nv 1108208
Define the tabletop egg-tray scene in YAML
xyao-nv 801fed4
Remove pinned asset inputs from environment generation
xyao-nv 18b1efc
Name SimReady helpers by their operations
xyao-nv 3cd7a77
Remove SimReady report files and CLI doc changes
xyao-nv 48da72d
Split SimReady backends and update Central example
xyao-nv 512bebf
Remove Central scene capture from documentation
xyao-nv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Two hits for one object collapse into one
With two sources selected,
"egg"can get a hit from the GA library and one from Central, and both survive this merge. In_extend_catalogue_with_simready,register_searched_simready_objectnames the asset after the phrase only, so the second call gets the first class back.As a result:
simready_eggentries;_simready_usd_pathskeeps only the last path;max_results_per_object > 1already had this problem, but with two sources it now happens at the default setting.Could we keep only the first candidate per phrase here, in source order? Or give each candidate its own registry name, such as
simready_egg_2? An agent-level test with two candidates for one phrase would catch this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1. keeping only one is ok, but we should make the choice explicit/documented.