-
Notifications
You must be signed in to change notification settings - Fork 120
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
Test inference endpoint model config parsing from path #434
Test inference endpoint model config parsing from path #434
Conversation
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
base_params: | ||
# Pass either model_name, or endpoint_name and true reuse_existing | ||
endpoint_name: "llama-2-7B-lighteval" # needs to be lower case without special characters | ||
reuse_existing: true # defaults to false; if true, ignore all params in instance, and don't delete the endpoint after evaluation |
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.
"and does not"
config["base_params"]["model_dtype"] = config["base_params"].pop("dtype", None) | ||
return cls(**config["base_params"], **config.get("instance", {})) |
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.
Nice and much cleaner! We might have to add this to all model types
@clefourrier I am not sure if you agree in the renaming of the We could address that in a subsequent PR |
Test inference endpoint model config parsing from path.
As a follow-up of this PR:
this PR implements a test of the parsing of the config file for evaluation in inference endpoints.
To do so, the parsing is factorized into a new method:
Additionally, a new
examples/model_configs/endpoint_model_reuse_existing.yaml
is added.Findings:
examples/model_configs/endpoint_model.yaml
, the fieldgeneration.add_special_token
is ignoreddtype
in the config file is named asmodel_dtype
InferenceEndpointModel
attributeQuestion: should we rename it?
dtype
field in the config file withmodel_dtype
model_name
instance
fields calledinstance_type
andinstance_size