You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug/limitation
Currently, the TT-Studio navbar displays all model-related options regardless of whether a deployed model supports them. This can lead to unnecessary clutter and confusion for users.
Expected behavior
The navbar should dynamically adjust based on the Model Type attribute, only showing options relevant to the deployed models.
Steps to reproduce:
Deploy a model that does not support Object Detection; eg any LLM .
Observe that Object Detection icon still appears in the navbar.
Proposed Solution:
Use the Model Type attribute to filter which options are displayed.
Hide irrelevant model icons in the navbar when no supporting model is available.
Additional context:
This will improve usability by keeping the interface cleaner and reducing confusion about the deployed model’s unsupported features.
The text was updated successfully, but these errors were encountered:
We need to update app/api/docker_control/docker_utils.py:get_container_status to propagate the new model_type field in the ModelImpl object to the frontend via the Status view.
The frontend needs to be updated in app/frontend/src/api/modelsDeployedApis.ts to add this additional field.
Describe the bug/limitation
Currently, the TT-Studio navbar displays all model-related options regardless of whether a deployed model supports them. This can lead to unnecessary clutter and confusion for users.
Expected behavior
The navbar should dynamically adjust based on the Model Type attribute, only showing options relevant to the deployed models.
Steps to reproduce:
Proposed Solution:
Additional context:
This will improve usability by keeping the interface cleaner and reducing confusion about the deployed model’s unsupported features.
The text was updated successfully, but these errors were encountered: