Skip to content
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

Support importing GGUF files #1187

Open
richardanaya opened this issue Jan 29, 2024 · 4 comments
Open

Support importing GGUF files #1187

richardanaya opened this issue Jan 29, 2024 · 4 comments
Labels
feature The feature request

Comments

@richardanaya
Copy link

richardanaya commented Jan 29, 2024

I apologize if this seems too far fetched, but it seemed in line with how ONNX generation works.

@antimora
Copy link
Collaborator

If gguf contains the model graph information, then we can use what burn-import ONNX facility. In our burn-import, we convert ONNX graph to IR (intermediate representation) (see this doc). So, it would possible to convert the model graph to IR and generate source code + weights.

If gguf contains only weights, we can go burn-import pytorch route, where we only download weights.

@antimora
Copy link
Collaborator

antimora commented Jan 29, 2024

From my brief research, GGUF format contains metadata + tensor weights. This aligns with burn-import pytorch route and not burn-import/ONNX. This will mean model needs to be constructed in Burn first and use the weights to load.

Here is one Rust lib to parse GGUF file: https://github.com/Jimexist/gguf

@antimora
Copy link
Collaborator

GGUF spec: ggerganov/ggml#302

@antimora
Copy link
Collaborator

Parser in Rust: https://github.com/Jimexist/gguf

@antimora antimora changed the title Support generating burn models from GGUF files? Support importing GGUF files Mar 28, 2024
@antimora antimora added the feature The feature request label Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature The feature request
Projects
None yet
Development

No branches or pull requests

2 participants