HN user

ag8

2,006 karma

runrl.com

Posts153
Comments52
View on HN
en.wikipedia.org 5mo ago

Gourmand Syndrome

ag8
27pts9
twitter.com 6mo ago

guys why does armenian completely break Claude

ag8
99pts65
cavendishlabs.org 6mo ago

Sampling at negative temperature

ag8
203pts60
www.youtube.com 6mo ago

Perfectly Replicating Coca Cola [video]

ag8
1pts1
po.ta.to 8mo ago

Po.ta.to

ag8
4pts2
www.runrl.com 9mo ago

Scaling pretraining affects RL sample efficiency

ag8
1pts0
theorem.dev 9mo ago

Systematically generating tests that would have caught Anthropic's top‑K bug

ag8
2pts0
2b4fdb18.connectionism.pages.dev 9mo ago

Tinker

ag8
4pts2
www.runrl.com 10mo ago

Training Qwen to answer briefly yet intelligently using feedback control

ag8
4pts0
runrl.com 10mo ago

Launch HN: RunRL (YC X25) – Reinforcement learning as a service

ag8
71pts22
www.runrl.com 1y ago

Generating the Funniest Joke with RL

ag8
1pts0
gravity-chess.andrew.gr 1y ago

Gravity Chess

ag8
2pts1
dynomight.net 1y ago

Please Show Lots of Digits

ag8
32pts17
andrew.gr 2y ago

Implementing an SHA Transformer by Hand

ag8
2pts0
arxiv.org 2y ago

Rebus: A Robust Evaluation Benchmark of Understanding Symbols

ag8
1pts0
www.nature.com 2y ago

Predicting the Future of AI with AI

ag8
2pts0
www.kolaayonrinde.com 2y ago

DeepSpeed's Bag of Tricks for Speed and Scale: Part I

ag8
1pts0
metazooa.com 2y ago

Metazooa

ag8
3pts0
en.wikipedia.org 3y ago

Cielab Color Space

ag8
1pts0
twitter.com 3y ago

An algorithm to determine whether AI can kill

ag8
1pts0
michaelnotebook.com 3y ago

Building a Better Memory System

ag8
3pts0
en.wikipedia.org 3y ago

List of stories set in a future now in the past

ag8
3pts0
ftx.com 3y ago

FTX partners with Reddit to roll out tokenized Community Points

ag8
1pts0
en.wikipedia.org 3y ago

Five-Planet Nice Model

ag8
2pts0
twitter.com 4y ago

Herbert W. Franke has died

ag8
92pts9
us-evolution-simulator.andrew.gr 4y ago

Show HN: A US Evolution Simulator

ag8
7pts4
andrew.gr 4y ago

Gravity Chess Opening Theory

ag8
2pts0
developer.apple.com 4y ago

WeatherKit

ag8
335pts191
arxiv.org 4y ago

The Mathematics of Burger Flipping

ag8
2pts0
en.wikipedia.org 4y ago

Totskoye Nuclear Exercise

ag8
4pts2

I find this paragraph to be odd: "Wavelengths as low as 13.5 nanometers can achieve more precise patterns in a single exposure. In fact, extreme ultraviolet lithography can combine three or four photolithography patterning cycles into a single one on a seven-nanometer node. Without EUV, producing five-nanometer nodes might require as many as one hundred different steps."

But a five-nanometer node has a gate pitch of 45nm and a metal pitch of 20nm! Using different forms of the word "nanometer" in the same paragraph is very confusing...

You're right; I should've been more precise. However, we have tools for dealing with this—that's what quality-adjusted life-years are for! I don't contest that surgeries often significantly increase QALYs, and may do so pretty cost-effectively.

Lol, I just care a lot about saving as many lives as I can; the most effective charities I've been able to find good evidence on save one life for $6–8k. If Watsi had a credible claim at being able to save lives 10x cheaper I would redirect my entire donation budget to them!

That said, once again, Watsi is great. I really appreciate all the hard work they've put into making this happen—this is orders of magnitude more impressive and impactful than most projects I've ever seen!

Watsi seems to be doing great work, but the title—"you helped save 33k lives"—reads as misleading to me. I guess "helped" could be doing a lot of heavy lifting here, but I would be incredibly surprised if the counterfactual number of lives saved was more than 3000. (But don't let this dissuade you from donating; concretely improving someone's life is totally a worthwhile goal, and Watsi seems very good at effecting this)

This is a cool setup, but naively it feels like it would require hundreds of thousands of hours of data to train a decent generalizable model that would be useful for consumers. Are there plans to scale this up, or is there reason to believe that tens of thousands of hours are enough?

Tinker 10 months ago

Yeah, not sure why the HN backend changed it...

A) You could have an additional field in the jsonl file which says which rubric to use; then, your reward function could access this via `kwargs["rubric"]` and return a reward based on that example's preferred rubric;

B) currently, pricing on the deployed API is free, but the startup time is a few minutes and it's run on a small GPU node and is therefore not awfully fast. If you would like more production-level inference, email us at founders@runrl.com and we could set you up with something much faster (where we'd charge per token depending on model size)

Having an RL agent that's really good at search across some space sounds very powerful in general; "proofs-as-search" make this an appealing target. Back in the day, when I did more fundamental RL research, we worked on an extension of SoRB [0] where an additional meta-level target was learning improved heuristics to explore the search space faster; would be exciting to figure out what a good setup for doing things like this in LLM-policy-gradient world is these days!

[0] https://arxiv.org/abs/1906.05253

we should publish some; the high-order effect seems to be that LoRAs significantly hurt small model performance vs FFT, with less of an effect for large models. This is maybe because large models have more built-in skills and thus a LoRA suffices to elicit the existing skill, whereas for small models you need to do more actual learning (holding # parameter updates constant). In general I think it's better to get a performant small model with FFT than a performant large model with a large LoRA, which is why we default to FFT, but I agree that we should publish more details here.

Thanks! Our goal is to make rl "just work" with completely automated GPU provisioning/algorithm selection/SFT-warm up, but giving people the ability to switch away from the defaults if they want to.

The way tools currently work in the beta is you add tools via MCP to the configuration, and they get passed in as additional context for the model; the model might then choose to use a tool during inference; the tool is then automatically called and the output is returned as a tool message. If you really want to you could parse the tool output as part of reward calculation, but I expect you'd usually base the reward just on the model's completion. I could give more details if there's a specific tool setup you're envisioning!

Yeah, for better or worse, the way the median startup interfaces with AI these days is through an LLM API, and that's what all the workflows are built around, so that's what we're targeting. Though, depending on what you're trying to do, I wouldn't discount the use of starting with a pretrained model—there was that famous result from 2022 that showed that pretraining a model on _Wikipedia_ made training on Atari games more than twice as efficient [0]; these days, LLMs have huge amounts of priors about the real world that make them great starting points for a surprisingly diverse set of tasks (e.g. see the chemistry example in our video!)

[0] https://arxiv.org/abs/2201.12122

prompt optimization is very cool, and we use it for certain problems! The main goal with this launch is to democratize access to "the real thing"; in many cases, full RL allows you to get the last few percent in reliability for things like complex agentic workflows where prompt optimization doesn't quite get you far enough.

There's also lots of interesting possibilities such as RLing a model on a bunch of environments and then prompt optimizing it on each specific one, which seems way better than, like, training and hot-swapping many LoRAs. In any case, _someone's_ ought to provide a full RL api, and we're here to do that well!

Regardless of my thoughts on the content, this article is very beautifully written. The word choice is impeccable, and reads like a thoughtfully shot short film of the author's day.