Repository navigation
Add Computational Cost tab to GUI Evaluator - #648
Open
sumitsaraswat362 wants to merge 1 commit into
Open
sumitsaraswat362 wants to merge 1 commit into
sumitsaraswat362 wants to merge 1 commit into
Conversation
Author
|
Hi team! I saw issue #560 was open and decided to tackle it. I've implemented the computational cost tab for Image Detection, Image Segmentation, and LiDAR Segmentation, keeping the UI style consistent with the rest of the evaluator. Please let me know if you'd like me to tweak the layout or add any additional metrics I'm happy to iterate on your feedback! |
This branch has not been deployed
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
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.
Fixes #560.
This PR adds a Computational Cost tab to the Streamlit GUI, achieving parity with the CLI's
computational-costbehavior.Changes
Computational Costinapp.pygui/computational_cost.pyto route to the correct taskruns, andwarm_up_runs.Tested locally, all tabs render correctly and successfully pass arguments to the underlying
Torch*Model.get_computational_cost()methods.