kukanani

Joined 9 years ago

Karma
67
Submissions
30
Member since
Aug 26
Adam Allevato. AI/Robotics developer with broad experience in industry and academia

X/Twitter: @AdamAllevato

View on Hacker News

Recent submissions

Comment · 1 month ago
Comment · 1 month ago
Comment · 2 months ago
Comment · 3 months ago
Make that N=2, the one person I know who suffers from phone-induced motion sickness says that having this feature on makes the sickness worse.
Comment · 6 months ago
Apologies - the source code was shared with me in confidence, dropping it on GitHub was explicitly one of the things I would not do with it. Will update you if that stance changes!
Comment · 6 months ago
The personality also comes from the system prompt, but I’ll grant you, it’s pretty minor.

I’m looking forward to a future where everyone could have their own personality model that is actually fine tuned at the weight level. Plus if we come up with better ways to do lifelong learning, personality could emerge from the robot’s experiences

Comment · 6 months ago
Local inference is definitely a good way to go here. Latency when talking to an embodied robot is extremely noticeable though, and pauses during voice chats are way worse than during text chats.

It’s something I’m exploring - stay tuned :)

Comment · 1 year ago
Are you perhaps thinking of torch.matmul? torch.mul (and torch.multiply, and the * operator) perform element-wise multiplication.

torch.matmul was one of the first functions I implemented on WhyTorch and it uses and highlights rows and columns as you would expect.

I’d love to hear any feedback or outcomes from your training session, please feel free to reach out - email in profile.

Comment · 1 year ago
An open source website I built to explain tensor functions in PyTorch: https://whytorch.org

It makes tricky functions like torch.gather and torch.scatter more intuitive by showing element-level relationships between inputs and outputs.

For any function, you can click elements in the result to see where they came from, or elements in the inputs to see how they contribute to the result to see exactly how it contributes to the result. I found that visually tracing tensor operations clarifies indexing, slicing, and broadcasting in ways reading that the docs can't.

You can also jump straight to WhyTorch from the PyTorch docs pages by modifying the base URL directly.

I launched a week or two back and now have the top post of all time on r/pytorch, which has been pretty fun.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton