HN user

vrm

79 karma

CTO @ TensorZero, previously worked on RL, fusion, and robotics at Carnegie Mellon, data & analytics at KKR, and robot learning at Stanford

virajm.com

Posts11
Comments27
View on HN

good luck running a 2.4T model on any local hardware. it’s not gonna happen. the arrow is to specialized hardware at least for the smartest models

If you don't need a ton of throughput I think `absurd` (and our Rust derivative `durable`) are very nice options that keep the client side extremely simple. It's also lightweight enough that a coding agent can keep the entire thing in its head easily and just run queries to look up state as needed.

It’s really not a concept you can express in idiomatic Python very easily. This comes from the actual generated assembly involving copies from global GPU memory into registers (slow, bandwidth saturates quickly) and back in between the cosines. If you can avoid the intermediate roundtrip that cuts the cost approximately in half.

This is neat! I think in general there are really deep connections between semantically meaningful diffs (across modalities) and supervision of AI models. You might imagine a human-in-the-loop workflow where the human makes edits to a particular generation and then those edits are used as supervision for a future implementation of that thing. We did some related work here: https://www.tensorzero.com/blog/automatically-evaluating-ai-... on the coding use case but I'm interested in all the different approaches to the problem and especially on less structured domains.

I definitely see different prompts based on what I'm doing in the app. As we mentioned there are different prompts for if you're asking questions, doing Cmd-K edits, working in the shell, etc. I'd also imagine that they customize the prompt by model (unobserved here, but we can also customize per-model using TensorZero and A/B test).

we're doing the latter! Cursor lets you configure the OpenAI base URL so we were able to have Cursor call Ngrok -> Nginx (for auth) -> TensorZero -> LLMs. We explain in detail in the blog post.

wireshark would work for seeing the requests from the desktop app to Cursor’s servers (which make the actual LLM requests). But if you’re interested in what the actual requests to LLMs look like from Cursor’s servers you have to set something like this up. Plus, this lets us modify the request and A/B test variations!

OP here: I saw the spinlaunch video and got really excited that this was completely tractable in simplified form with basic physics. So I did the math expecting to see a huge savings in fuel mass and....it was basically negligible. I'm curious if anyone on HN (maybe even from Spinlaunch!) could explain where I go wrong. Otherwise you might find it interesting to read. Thanks!

will repost my comment from the other one:

Papers I would recommend from our collaboration on control of normalized plasma pressure: https://papers.nips.cc/paper/2019/hash/7876acb66640bad41f1e1...

plasma profile transport modeling: https://iopscience.iop.org/article/10.1088/1741-4326/abe08d/...

hybrid dynamical modeling of gross plasma quantities: https://arxiv.org/abs/2006.12682

uncertainty quantification for plasma dynamics: https://arxiv.org/abs/2011.09588

It's still early days for this work and for us but we're looking at pushing reinforcement learning in methods and engineering to solve this problem.

I need to redo my website, just getting into the more public part of my PhD. Papers I would recommend from our collaboration on

control of normalized plasma pressure: https://papers.nips.cc/paper/2019/hash/7876acb66640bad41f1e1...

plasma profile transport modeling: https://iopscience.iop.org/article/10.1088/1741-4326/abe08d/...

hybrid dynamical modeling of gross plasma quantities: https://arxiv.org/abs/2006.12682

uncertainty quantification for plasma dynamics: https://arxiv.org/abs/2011.09588

It's still early days for this work and for us but we're looking at pushing reinforcement learning in methods and engineering to solve this problem

like I said above, we certainly hope so! It has been slow progress so far but applying modern ML / control techniques to tokamaks is one of the truly exciting applications of the current generation of AI in my opinion. Biased because this is literally what I do all day

I'm a PhD student in robotics at Carnegie Mellon working on exactly this. It's extremely challenging for a few reasons:

- the dataset is a mess. The experiments that have been conducted on the tokamak that we have access to were done for very many different reasons and under many different configurations of the machine so there is not a clear method for disambiguating what dynamical changes are due to differences in the system vs underlying dynamical truths

- the simulators available are very slow and not that accurate

- the physics is hard enough that it's not possible to develop a controller in closed form (obviously)

This implies that we need a version of reinforcement learning or model-predictive control that is substantially more robust and sample-efficient than currently exists. We're working on that but obviously it's an open research problem.