Hugging Face's logo
Oussema Harbi's picture
1 1 10

Oussema Harbi

Harbous
DualityAI-RebekahBogdanoff's profile picture Mi6paulino's profile picture Juanelopo's profile picture
¡

AI & ML interests

None yet

Recent Activity

reacted to philipp-zettl's post with 👍 3 days ago
I've been cooking something neat over the past weeks 👨‍🍳 We all know that training LLMs requires a lot of resources and especially a lot of compute in form of GPUs, or is super slow and inefficient when done on CPUs. The big players use giant clusters of Nvidia H100s. But if I look at the profiles of my fellow home brewers, all we can get our hands on are those pesky consumer RTX's. If you're lucky you got yourself a 5080 with 16GB VRAM or something. To be frank, I don't have that 1.3k disposable cash laying around ¯\_(ツ)_/¯ But I can write rust and like building ML libraries. So I asked myself the question(s): - can I train SMLs at home on my hardware? - How hard can it be to build a ML library that can stream data between RAM and VRAM on demand, like llama.cpp's unified memory feature [^1]? - how hard can it be to implement bf16 support? The answers are wild, trust me! Image 1: Metrics form last nights build on my "tiny" RTX 2060 (6 GB VRAM) Image 2: Metrics from my most recent build on my RTX 4070 Laptop (8GB VRAM) The majority of my time went into the shared memory, but it's stable and I'm very excited! Here some debug logs, a la "trust me bro" ``` ---- Currently available: 1112735744, attempting to reclaim: 1073741824 --- VRAM STATE [backward pass] --- Driver Used: 6744 MB / 7805 MB Data on GPU: 1641 MB Grads on GPU: 3459 MB CPU Offloaded: 18230 MB --------------------------------- Currently available: 1079181312, attempting to reclaim: 1073741824 --- VRAM STATE [backward pass] --- Driver Used: 6776 MB / 7805 MB Data on GPU: 1561 MB Grads on GPU: 3279 MB CPU Offloaded: 18590 MB ----------------------------- ``` Final models get exported in `safetensors` format and are compatible with PyTorch and `transformers`, for accessibility. - [^1]: https://github.com/ggml-org/llama.cpp/blob/master/docs/build.md#unified-memory
reacted to RakshitAralimatti's post with 👍 2 months ago
Just built my entire AI Engineer portfolio by pasting 2 links (GitHub and LinkedIn) into https://huggingface.co/moonshotai Kimi 2.5. That's it. That's the workflow. Zero coding. Zero iteration. Zero "make the button bigger." See for yourself: https://rakshit2020.github.io/rakshitaralimatti.github.io/ The model: ✅ Scraped my GitHub repos automatically ✅ Pulled my experience from LinkedIn ✅ Designed an Aurora Glass theme ✅ Mapped every skill to projects ✅ Added animations I'd never code myself
reacted to kanaria007's post with 👍 3 months ago
✅ New Article: *Post-Transformer Decision Cores* (v0.1) Title: 🚀 Post-Transformer Decision Cores: Goal-Native Engines Beyond LLMs 🔗 https://huggingface.co/blog/kanaria007/post-tranformer-decision-cores --- Summary: Transformers are powerful—but in SI-Core they’re *not the essence of intelligence*. A *Decision Core* is anything that satisfies the *Jump contracts* (OBS/ETH/MEM/ID/EVAL + RML), and those contracts don’t require next-token prediction. This article sketches what “post-Transformer” looks like in practice: *goal-native, structure-aware controllers* that may use LLMs as tools—but don’t depend on them as the runtime brain. > Don’t relax the contracts. > Replace the engine behind them. --- Why It Matters: • Makes LLMs *optional*: shift them to “genesis / exploration / explanation,” while routine high-stakes Jumps run on structured cores • Improves boring-but-critical properties: *determinism (CAS), fewer inconsistencies (SCI), fewer ETH violations (EAI), better rollback (RBL/RIR)* • Enables gradual adoption via *pluggable Jump engines* and domain-by-domain “primary vs fallback” switching --- What’s Inside: • The architectural inversion: *World → OBS → SIM/SIS → Jump (Decision Core) → RML → Effects* (LLM is just one engine) • Three compatible post-Transformer directions: 1. *World-model + search controllers* (MPC/MCTS/anytime search with explicit GCS + ETH constraints) 2. *Genius-distilled specialized controllers* (distill structure from GeniusTraces; LLM becomes a “genesis tool”) 3. *SIL-compiled Decision Programs* (typed Jump entrypoints, compiler-checked invariants, DPIR/GSPU targeting) • A realistic migration path: LLM-wrapped → Genius library → shadow dual-run → flip primary by domain → SIL-compiled cores • How this connects to “reproducing genius”: GRP provides trace selection/format; this article provides the engine architectures --- 📖 Structured Intelligence Engineering Series
View all activity

Organizations

None yet