# Technical Working Group DeAI **URL:** \ **Category:** Developers\ **Created:** [November 12, 2023, 4:34pm UTC](https://forum.dfinity.org/t/technical-working-group-deai/24621 "2023-11-12T16:34:10Z")\ **Posts on this page:** 1\ **Showing post:** 101
**Author:** ![ulan](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/ulan/32/2705_2.png) [@ulan](https://forum.dfinity.org/u/ulan)\ **Post date:** [April 18, 2024, 7:37am UTC](https://forum.dfinity.org/t/technical-working-group-deai/24621/101 "2024-04-18T07:37:21Z")
@jeshli, @mnl: Raheel and Dominic pointed me to this thread and the discussion about ONNX runtimes: Tract and Burn. I thought it might be useful for the community to share my findings: - I managed to get the upstream Tract working on IC without any changes (i.e. without forking). - The approach relies on the [wasi2ic](https://github.com/wasm-forge/wasi2ic) community project. - I first compile Tract to `wasm32-wasi` and then use `wasi2ic` to convert the binary to `wasm32-unknown-unknown` that is compatible with the IC. - Example usage: [code](https://github.com/dfinity/examples/blob/master/rust/image-classification/src/backend/Cargo.toml#L19) - Build steps of the example: [code](https://github.com/dfinity/examples/blob/6c38a5d4def5da7308ae1c7b61de62045876868a/rust/image-classification/dfx.json#L9) Did anyone manage to compile Burn to IC? I would be curious to compare its performance with Tract. --- _[View the full topic](https://forum.dfinity.org/t/technical-working-group-deai/24621)._