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

api_demo: set different app_id depending on what demo is being run #1125

Closed
Tracked by #1119
teh-cmc opened this issue Feb 7, 2023 · 5 comments · Fixed by #2599
Closed
Tracked by #1119

api_demo: set different app_id depending on what demo is being run #1125

teh-cmc opened this issue Feb 7, 2023 · 5 comments · Fixed by #2599
Assignees
Labels
examples Issues relating to the Rerun examples 🏎️ Quick Issue Can be fixed in a few hours or less

Comments

@teh-cmc
Copy link
Member

teh-cmc commented Feb 7, 2023

What the title says.

  • Avoids a poor user experience where one ends up with a bunch of zombie space views
  • Provides interesting analytics for official examples
@teh-cmc teh-cmc added the examples Issues relating to the Rerun examples label Feb 7, 2023
@Wumpf
Copy link
Member

Wumpf commented Feb 15, 2023

went in!

@Wumpf Wumpf closed this as completed Feb 15, 2023
@teh-cmc
Copy link
Member Author

teh-cmc commented Feb 15, 2023

lies!

@teh-cmc teh-cmc reopened this Feb 15, 2023
@emilk
Copy link
Member

emilk commented Feb 28, 2023

I don't understand this issues.

What does "active demo/recording/scene" refer to? The currently open recording in the viewer?

When should app_id take it into account? When the example sets the app_it in init? In analytics?

@teh-cmc
Copy link
Member Author

teh-cmc commented Feb 28, 2023

What does "active demo/recording/scene" refer to? The currently open recording in the viewer?

It refers to the application-specific notion of "what's the current dataset", e.g.:

  • For objectron, the app_id should change depending on the dataset being visualized (e.g. book vs bike)
  • For api_demo, the app_id should change depending on the --demo flag
  • etc

@emilk
Copy link
Member

emilk commented Jun 12, 2023

I don't agree on the objectron example - it is the same application regardless of what you visualize, and you should expect to have the same blueprint regardless if you are "scanning" a book or a bike.

For api_demo: for this one I agree (though it is not really an example, and we should either turn it into many small examples or make it into a test)

@emilk emilk changed the title Examples: app_id should take into account active demo/recording/scene apid_demo: set different app_id depending on what demo is being run Jun 12, 2023
@emilk emilk added the 🏎️ Quick Issue Can be fixed in a few hours or less label Jun 12, 2023
@emilk emilk changed the title apid_demo: set different app_id depending on what demo is being run api_demo: set different app_id depending on what demo is being run Jun 15, 2023
@emilk emilk self-assigned this Jul 4, 2023
emilk added a commit that referenced this issue Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
examples Issues relating to the Rerun examples 🏎️ Quick Issue Can be fixed in a few hours or less
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants