-
Notifications
You must be signed in to change notification settings - Fork 44
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
Moving config from ADS to UI for unverified models #976
Conversation
…ence into ODSC-61938/fix_validation_for_gguf_safetensors
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.
are we rolling out the relevant UI changes this week? If that's the case, we can set the target branch to main and release ADS this Thursday. That way, the next NBVM update in a week would have these changes.
ads/aqua/finetuning/finetuning.py
Outdated
logger.info(f"Fetching default fine-tuning config for model: {model_id}") | ||
config = get_finetuning_config_defaults() | ||
logger.info( | ||
f"default fine-tuning config will be used for model: {model_id}" |
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.
this info message can be misleading since user might see this in ads logs and expect some default to be returned, but the defaults are applied outside of ads. Maybe a better phrasing would be "Fine-tuning config for custom model {model_id} is not available." We can also use logger.debug instead, user need not see this message every time.
@mrDzurb thoughts?
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.
Updated
AQUA_MODEL_DEPLOYMENT_CONFIG, | ||
AQUA_MODEL_DEPLOYMENT_CONFIG_DEFAULTS, |
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.
can you please the unused constants and json files/functions that were deprecated here since we're not using them anymore?
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.
Sorry didn't understand this statement. perhaps you a word or two?
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.
I missed the word - " can you please remove or delete the unused constants and json files/functions that were deprecated..." :)
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.
Sure , will update
UI changes are ready. I was under assumption that only embedding changes + adding logs in terminal are part of release this week. But if we plan to release config migration changes as well , we can. Looping @mayoor @NitinMore7 |
Please add more details in the description. It will be helpful for the future maintenance. |
yes, let's switch target to main if we're comfortable with the UI changes to go this week. |
The base branch was changed.
This PR is intended to remove dependency of unverified models default config from ADS.
Currently, the default shapes config for deployment, finetuning and evaluation are hardcoded in ADS. This makes it difficult to make changes ad-hoc with new ADS release.
This info is needed for unverified models only and can be maintained at client side.
Config that needs to be removed are
UTs