Few-Shot-Learning

TL;DR for operators A new user with only a few preference signals does not necessarily need a richer model built from scratch. The stronger design question may be where personalization starts. The paper studies a reward-modeling system that learns from previous users how a new user’s reward weights should be initialized, then adapts only those lightweight weights from limited feedback. Its average accuracy gains are modest but consistent, while the more informative evidence comes from component ablations, few-shot unseen-user tests, worst-user analysis, and parameter scaling. Removing the learned adaptation mechanism causes the largest ablation drop. ...

TL;DR for operators AI systems rarely fail only at the final answer. They fail earlier, in the quiet machinery that decides which evidence is seen, which records are aligned, which identity is protected, and which previous model behaviour is worth reusing. Three recent papers make that point from very different technical worlds. One improves few-shot object detection by correcting the imbalance between base-class and novel-class region proposals. One builds anonymous two-party gradient-boosted decision tree training so parties can align records without exposing shared identifiers. One maps the behavioural geometry of LLMs so jailbreak risk and defences can be predicted or transferred across model populations. ...

Microscopy has a labor problem. Not the photogenic kind where a scientist leans into a glowing instrument and discovers the secret architecture of life before lunch. The duller problem is that modern light sheet fluorescence microscopy can produce rich three-dimensional volumes faster than expert teams can label them. Segmentation requires voxel-level masks. Stain classification requires domain knowledge. Restoration needs paired degraded and high-quality images, which nature, unhelpfully, does not always provide in tidy folders. ...

TL;DR for operators Most attempts to improve CLIP-style image classification with large language models follow a familiar ritual: ask GPT to describe a class, paste those descriptions into prompts, then hope the model pays attention to the useful bits. The problem is that GPT’s descriptions are not stable objects. They vary by query wording, include hedged statements, and sometimes contain features that are hard or impossible to verify visually. “Usually,” “may,” and “often” are not exactly the foundations of a disciplined recognition system. ...