Chiosa
Research collection

Machine Learning

Research on Machine Learning: explanations, evidence, limitations and connections between papers.

79 results

  1. Guided lessonMachine Learning

    Match parallel generation to the work that slows it down

    A phone agent can wait at every screen action, while a text generator can spend time proposing, checking, or reconstructing its output. Parallel work helps when it reaches the costly part of that particular workflow. Across these studies, moving or overlapping work produces reported throughput or latency gains in specific workloads and serving setups. JetSpec++ also reports a serving gain, while its predictions of future context remain estimates until verification. The results support judging each method by its local outcome, without forming a shared speed ranking.

  2. Guided lessonMachine Learning

    Match routing decisions to the evidence available at each step

    An agent may need to choose a model for a home-control step, decide how to ask owners of separate tables for an answer, or send a question to a larger model. Each choice can consume additional computation, yet each exposes different evidence about where that work may help. A useful first answer is to match the routing decision to the variation the system can observe: a known step, a dependency between owners, or a question-level confidence signal. These studies test those choices in different settings, so their outcomes guide conditional decisions rather than a shared performance ranking.

  3. Guided lessonMachine Learning

    Match judging evidence to the outcome and its cost

    A panel of judges can give more consistent scores after its instructions are clarified, yet show no detectable improvement against expert ratings. A response can also look relevant without answering the request. These cases make “better judging” an incomplete goal until the outcome is named. The studies support choosing evidence for the claim at hand: clarify criteria to study consensus, inspect an answer’s substance to assess request matching, and observe an application in use when its behavior matters. Each choice has a tested scope and a cost; a budget planner depends on how well its pilot represents deployment.