Daniel_Van_Zant
Joined 2 years ago
Joined 2 years ago
Systems sciences are ones where each scale has lots of things with unique properties. If you think of “biological things between 2-4m” the amount of unique objects with unique properties and unique interactions is absolutely mind boggling. These sciences generally do not lend themselves to clean highly parsimonious models. The best you can do is coarse-grain a thing as a system (some very roughly defined set of interactions between different things) with certain behavior while accepting that you are losing enormous amounts of predictive power.
I suspect AI will remain worse at systems sciences for a long time because the “possible space” of models for a particular system is much larger than in the reductionist sciences and navigating it takes a human taste and instinct that LLMs don’t seem to have (yet).
My guess is that in formally verifiable domains you can use RL-esque processes to get lots of good high-quality training data with reward signals (does it verify?), but the same does not apply to "scruffier" work. I would also imagine that the data volume of high-quality scientific work in "scruffy" domains is too low for the large language models to have a good manifold for "high-quality biology research". Would love to be proven wrong if anyone knows of anyone doing great scientific work with large language models in non-verifiable domains though.
I'm Daniel, co-founder. Lumen Labs is building the cognitive layer for physical AI. Nearly every major robotics effort today teaches machines by showing them thousands of hours of human teleoperation. We think that paradigm has a ceiling, and we're working on nature-inspired architectures for unstructured environments (construction sites, mining, pipelines, battlefield). Pre-seed, backed by top VC funds and operators from robotics/AI companies.
We're a team of two and hiring teammate #3 to own the hardware and infrastructure that keeps our research platforms running: the ROS2 (Humble) stack across onboard and offboard compute, sensor integration and calibration (LiDAR, depth, IMU, encoders), the safety pipeline during autonomous runs, and getting trained policies onto real hardware. Today that's wheeled navigation; we're dipping our toes into drones and eyeing weirder platforms like pipeline inspection. Where we're at: zero-shot sim2real transfer with a policy that runs at 100Hz on an ESP32 and took under a day to train.
You: hands-on with real mobile robots (UART, encoders, PWM, IMU, LiDAR), strong Python + embedded, comfortable reading code you didn't write, and can debug hardware and firmware at the same time. If "full-stack" to you means firmware, a multimeter, and a ROS node in the same afternoon, you'll fit right in. Visa/relocation support for the right person.
Full posting: https://desert-bearskin-26d.notion.site/Robotics-Engineer-Ro...
Email [email protected], mention HN, and tell us about a project you've built. If you can link to a time you got a trained policy running on real hardware, you go to the top of the pile.
Lumen (https://lumenresearch.ai) is building the cognitive layer for physical AI. Most robotics efforts today learn from thousands of hours of human teleoperation; we think that has a ceiling. White paper: http://lumenresearch.co/paper
Team of two ex-founders — you'd be #3. Pre-seed, runway well into 2027, raising a seed later this year.
We test many model architectures against many sims, and hooking them together is our biggest pain point. We use Gymnasium and Shimmy as the plumbing and upstream useful pieces as open-source contributions. You'd build per-sim adapters to a shared interface contract, bridge single-env vs. GPU-vectorized and sync vs. async paradigms, and own our eval harness.
Looking for: strong Python, Gymnasium (especially the vector API), hands-on experience with Isaac, MuJoCo, or Gazebo, and a track record of getting models running in sims where they didn't before.
Email [email protected] about you and your projects — link one where you got a model working in a sim it wasn't built for and you'll jump the pile.
Full posting: https://desert-bearskin-26d.notion.site/Simulation-Engineer-...
I think values, goals, and constraints are all valuable, but it's a hierarchy. We should create constraints that help us become more aligned with our values. We should create shorter-term goals that make it easy to stay within our constraints.
To support both my point and the authors, here is Benjamin Franklin's "Thirteen Virtues," which seem to be a mix of constraints and values (zero goals): https://fs.blog/the-thirteen-virtues/