Dominick Wirzba's picture

Dominick Wirzba

Chronuid
1 4
·

AI & ML interests

None yet

Recent Activity

reacted to alexanderbering's post with 🔥 1 day ago
We just put our money where our manifesto is. Our position has been that the layer of an AI system that touches your data should be open and auditable, not something you rent on trust. So instead of asking you to believe that, we made it runnable. The ZenBrain Playground is a static HF Space that executes our open-source memory library, @zensation/algorithms (Apache-2.0, zero-dependency), live in your browser. No install, no backend, no mockup: it runs the actual published code. Four panels drive real functions from the library — Ebbinghaus-style retention curves, Hebbian strengthening/decay, sleep-consolidation replay + pruning, and Bayesian retrievability with confidence intervals. The library is vendored into the page, so what you run is the same code that's published on npm. ZenBrain is a neuroscience-inspired 7-layer memory architecture for AI agents. The open core is the 20-module algorithm library (FSRS, Hebbian, Ebbinghaus, sleep-consolidation, Bayesian confidence, and more). On LongMemEval-500 it reaches 91.3% of a long-context oracle's accuracy at 1/106 of the per-query token budget, and takes the highest mean rank across all 12 system-judge cells (4 systems x 3 LLM judges) against Letta, Mem0, and A-Mem. It ships with 11,589 automated tests. Full details are in the arXiv preprint. If you build agent memory, we'd genuinely like your eyes on it — open the Space, poke the algorithms, read the code, tell us where it breaks. Live demo: https://huggingface.co/spaces/zensation-ai/zenbrain-playground Model: https://huggingface.co/zensation-ai/zenbrain Paper: arXiv:2604.23878
reacted to albertvillanova's post with 🤗 2 days ago
🎉 KTO is now part of the stable TRL API As of Promote KTO to stable API, KTOTrainer and KTOConfig have graduated from trl.experimental to the stable trl API. https://github.com/huggingface/trl/pull/6175 This one closes out a long road. Over the past 6+ months, the "Align KTO with DPO" effort landed ~90 PRs methodically bringing KTO up to the standard we hold for stable trainers, one carefully-scoped change at a time: - Feature parity with DPO: full VLM support (incl. multi-image), sync_ref_model, PEFT + Liger, ZeRO-3 + PEFT dtype fix, pad_to_multiple_of, activation offloading, IterableDataset and dict eval_dataset, remove_unused_columns, and reference-logprob precomputation at init. - Consistency with DPO: aligned method order and signatures, tokenization, _prepare_dataset, PEFT handling, ref-model preparation for distributed training, and config layout — plus a new DataCollatorForKTO and output format. Metrics moved into _compute_loss and simplified to direct averages via the shared _metrics attribute. - Removing legacy baggage: dropped encoder-decoder support, BOS/EOS handling, null_ref_context, generate_during_eval, model_init, preprocess_logits_for_metrics, model/ref adapter names, and several dead config knobs. - Coverage: a full test suite mirroring DPO, text collator tests, VLM tests, and slow tests. - The promotion itself: the experimental → stable move (#6175) and shim cleanup (#6287), handled so downstream users get a clean deprecation path. Honestly, this has been one of the more complex tasks I've taken on since joining the team, not because any single change was hard, but because it demanded sustained consistency across a ~2,000-line trainer, with every branch, comment, and edge case kept in lockstep with DPO. Huge thanks to everyone who reviewed along the way (especially @qgallouedec), the incremental review cadence is exactly what kept this maintainable. KTO now sits on equal footing with our other flagship trainers. 🚀
reacted to albertvillanova's post with 🔥 2 days ago
🎉 KTO is now part of the stable TRL API As of Promote KTO to stable API, KTOTrainer and KTOConfig have graduated from trl.experimental to the stable trl API. https://github.com/huggingface/trl/pull/6175 This one closes out a long road. Over the past 6+ months, the "Align KTO with DPO" effort landed ~90 PRs methodically bringing KTO up to the standard we hold for stable trainers, one carefully-scoped change at a time: - Feature parity with DPO: full VLM support (incl. multi-image), sync_ref_model, PEFT + Liger, ZeRO-3 + PEFT dtype fix, pad_to_multiple_of, activation offloading, IterableDataset and dict eval_dataset, remove_unused_columns, and reference-logprob precomputation at init. - Consistency with DPO: aligned method order and signatures, tokenization, _prepare_dataset, PEFT handling, ref-model preparation for distributed training, and config layout — plus a new DataCollatorForKTO and output format. Metrics moved into _compute_loss and simplified to direct averages via the shared _metrics attribute. - Removing legacy baggage: dropped encoder-decoder support, BOS/EOS handling, null_ref_context, generate_during_eval, model_init, preprocess_logits_for_metrics, model/ref adapter names, and several dead config knobs. - Coverage: a full test suite mirroring DPO, text collator tests, VLM tests, and slow tests. - The promotion itself: the experimental → stable move (#6175) and shim cleanup (#6287), handled so downstream users get a clean deprecation path. Honestly, this has been one of the more complex tasks I've taken on since joining the team, not because any single change was hard, but because it demanded sustained consistency across a ~2,000-line trainer, with every branch, comment, and edge case kept in lockstep with DPO. Huge thanks to everyone who reviewed along the way (especially @qgallouedec), the incremental review cadence is exactly what kept this maintainable. KTO now sits on equal footing with our other flagship trainers. 🚀
View all activity

Organizations

Hugging Face Discord Community's profile picture ML intern explorers's profile picture