Hugging Face's logo
Salma Mayorquin's picture

Salma Mayorquin PRO

salma-remyx
28 24 494
Johnnycno's profile picture sequelbox's profile picture alamgirian's profile picture
·
https://remyx.ai

AI & ML interests

None yet

Recent Activity

reacted to dipankarsarkar's post with 🔥 about 19 hours ago
Privacy is moving ad decisions onto the device. The auction runs locally, next to the context it scores. The budget still lives on a server. So every device bids against the balance it saw at its last sync. Between syncs, campaigns spend money they no longer have. I simulated how much that costs: 50 devices, 36 campaigns, about 300,000 auctions per run, 30 seeds per cell, budgets frozen before evaluation. Even pacing, second-score payment: - Sync every tick: spend lands 18% over budget (32% with iPinYou-calibrated values). - Sync every 10 ticks: 5.8 times the budget. - Sync every 50 ticks: 17.7 times the budget (10.1 times with iPinYou-calibrated values). Zero-lag sync stays within about 1%. The lag alone does the damage. The incentive side runs the other way. With second-score payment and zero lag, 98% of auctions are manipulable (92% with iPinYou values). Switch the payment rule to critical-bid and that drops to 0 at every sync interval, in both setups. Sync fixes the budget. The payment rule, not the sync interval, is what removes manipulability. All 12 result sets are on the Hub, plus the 50,808 context labels every run samples from. Paper: https://huggingface.co/papers/2609.33312 Dataset: https://huggingface.co/datasets/skelfresearch/on-device-auction-audit Code: https://github.com/sarkar-dipankar/on-device-auction-audit If your ads stack moves on device, how often does the device learn its budget?
reacted to SoulInPsyAbstract's post with 🔥 3 days ago
Eval · EXP-046 A LoRA Specialist Beat Zero-Shot on Every Group. Merging 3 of Them Gave Most of the Gain Back. Three Qwen2.5-7B LoRA specialists, one per risk group (vulnerability, deletion, sensitive_publication), trained to predict how likely a causal chain actually completes to its harmful outcome. Each one genuinely beat its own zero-shot baseline: * vulnerability: MAE 0.098 → 0.085 * deletion: MAE 0.144 → 0.113 * sensitive_publication: MAE 0.134 → 0.100 This wasn't a task already saturated zero-shot (unlike a same-day decomposition-classifier tune, EXP-045, where the base model was already at 100% before any training). Real signal, real improvement, on a task with actual headroom. Then the equal-weight merge of all three specialists into one adapter — same convention that held up cleanly on a binary refusal task back in EXP-031 (6 specialists merged, -1pp swing, noise) — landed within 0.001–0.004 MAE of the unspecialized base model on every group. Not "close to the best specialist." Close to zero fine-tuning at all. Likely mechanism: merging LoRAs that each shift a continuous number in group-specific directions cancels out under linear combination, in a way merging LoRAs that enforce a shared binary behavior doesn't. Not investigated yet: whether a routed combination (pick the right specialist per group at inference, not blend weights) holds the gain a flat merge loses. One bug caught before writing this up, not after: the eval script's output filename only encoded before/after, not which adapter — the merged-eval run silently overwrote each specialist's own result file. Caught by checking the downloaded file's own recorded adapter path against what was expected, not by trusting the script's own success message. Fixed, specialists re-run cleanly under distinct filenames — numbers matched within sampling noise. Adapters, raw eval data (before / each specialist / merged, 9 files), and the full writeup are up.
reacted to dipankarsarkar's post with 🔥 3 days ago
I audited one of my own evaluations. The ranking did not hold up the way I expected. Eight open models, one task: infer the structure of a prompt. Then ask again with the identical call. Caching off. - Agreement between repeated identical calls (mean Jaccard) ranged from 0.39 to 0.96 across models. - Only 35 of 127 prompt-model cells were perfectly reproducible on every run. - I bootstrapped the reproducibility ranking over prompts. The two least reproducible models kept their rank in 99% and 86% of resamples. The middle four kept theirs in 27% to 48%. So the table reliably finds the worst model. It does not reliably find the best. Reproducible is also not the same as correct. F1 against gold annotations ran from 0.56 to 0.99. By the audit date, 4 of the 8 model variants had been retired (HTTP 410). The study as specified can no longer be re-run. The saved outputs are what survives, so I published all of them: every inferred structure, every run, the prompts and the annotations. Paper: https://huggingface.co/papers/2609.30074 Dataset: https://huggingface.co/datasets/dipankarsarkar/llm-evaluation-self-audit Code: https://github.com/sarkar-dipankar/llm-evaluation-self-audit How many of the leaderboard rankings you rely on would survive re-running the same calls?
View all activity

Organizations

Remyx AI's profile picture