Skip to content

Add Model format field to Kitfile#645

Merged
amisevsk merged 1 commit intokitops-ml:mainfrom
amisevsk:model-format
Dec 11, 2024
Merged

Add Model format field to Kitfile#645
amisevsk merged 1 commit intokitops-ml:mainfrom
amisevsk:model-format

Conversation

@amisevsk
Copy link
Copy Markdown
Contributor

@amisevsk amisevsk commented Dec 5, 2024

Description

To make runtime usage simpler, add Kitfile field .model.format. This can be set to store the model's data format (e.g. safetensors, gguf, onnx, etc.).

This information can be used by runtimes to determine how to consume the model (e.g. if the runtime can handle .gguf files)

Linked issues

No issue at the moment

To make runtime usage simpler, add Kitfile field .model.format. This can
be set to store the model's data format (e.g. safetensors, gguf, onnx,
etc.).

This information can be used by runtimes to determine how to consume the
model (e.g. if the runtime can handle .gguf files)
@amisevsk amisevsk requested a review from gorkem December 5, 2024 15:55
@gorkem
Copy link
Copy Markdown
Member

gorkem commented Dec 10, 2024

Do we also need to record the format version some formats like onnx change quite often?

@amisevsk
Copy link
Copy Markdown
Contributor Author

Maybe, but adding that is a backwards-compatible change we can make if we decide we need it. I'd rather not throw fields into the spec unless we know they're going to be used somewhere.

@gorkem
Copy link
Copy Markdown
Member

gorkem commented Dec 11, 2024

the reason I brought this up on the annotations that we had proposed on model specification group, I had it listed as format.name and format.version.

@amisevsk amisevsk merged commit 5914b1e into kitops-ml:main Dec 11, 2024
@amisevsk amisevsk deleted the model-format branch December 11, 2024 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants