HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vthommeret
mathtocode
JavaScript2020–2020
vthommeret / mathtocode

mathtocode

Discover this repository through its Hacker News conversations.

2Distinct people
6Mentions
0Explicit recommenders
254GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour6 dated mentions

Observed mentions: 2020-06-13 22:38:32 UTC to 2020-06-14 15:26:37 UTC.

012020-06-13 22:00:00 UTC to 2020-06-13 23:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 13, 22:002020-06-13 23:00:00 UTC to 2020-06-14 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-06-14 00:00:00 UTC to 2020-06-14 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 01:00:00 UTC to 2020-06-14 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 02:00:00 UTC to 2020-06-14 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 03:00:00 UTC to 2020-06-14 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 04:00:00 UTC to 2020-06-14 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 05:00:00 UTC to 2020-06-14 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-06-14 06:00:00 UTC to 2020-06-14 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 14, 06:002020-06-14 07:00:00 UTC to 2020-06-14 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 08:00:00 UTC to 2020-06-14 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-06-14 09:00:00 UTC to 2020-06-14 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 10:00:00 UTC to 2020-06-14 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 11:00:00 UTC to 2020-06-14 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-06-14 12:00:00 UTC to 2020-06-14 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 13:00:00 UTC to 2020-06-14 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 14:00:00 UTC to 2020-06-14 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-14 15:00:00 UTC to 2020-06-14 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 14, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 13, 22:002020-06-13 22:00:00 UTC2020-06-13 23:00:00 UTC101
Jun 13, 23:002020-06-13 23:00:00 UTC2020-06-14 00:00:00 UTC101
Jun 14, 00:002020-06-14 00:00:00 UTC2020-06-14 01:00:00 UTC000
Jun 14, 01:002020-06-14 01:00:00 UTC2020-06-14 02:00:00 UTC000
Jun 14, 02:002020-06-14 02:00:00 UTC2020-06-14 03:00:00 UTC000
Jun 14, 03:002020-06-14 03:00:00 UTC2020-06-14 04:00:00 UTC000
Jun 14, 04:002020-06-14 04:00:00 UTC2020-06-14 05:00:00 UTC000
Jun 14, 05:002020-06-14 05:00:00 UTC2020-06-14 06:00:00 UTC101
Jun 14, 06:002020-06-14 06:00:00 UTC2020-06-14 07:00:00 UTC000
Jun 14, 07:002020-06-14 07:00:00 UTC2020-06-14 08:00:00 UTC000
Jun 14, 08:002020-06-14 08:00:00 UTC2020-06-14 09:00:00 UTC101
Jun 14, 09:002020-06-14 09:00:00 UTC2020-06-14 10:00:00 UTC000
Jun 14, 10:002020-06-14 10:00:00 UTC2020-06-14 11:00:00 UTC000
Jun 14, 11:002020-06-14 11:00:00 UTC2020-06-14 12:00:00 UTC101
Jun 14, 12:002020-06-14 12:00:00 UTC2020-06-14 13:00:00 UTC000
Jun 14, 13:002020-06-14 13:00:00 UTC2020-06-14 14:00:00 UTC000
Jun 14, 14:002020-06-14 14:00:00 UTC2020-06-14 15:00:00 UTC000
Jun 14, 15:002020-06-14 15:00:00 UTC2020-06-14 16:00:00 UTC101

What Hacker News says

6 sources
Skulpt does support the Python 3.7.3 grammar [0], but it's a work in progress. I have it enabled here: https://github.com/vthommeret/mathtocode/blob/0d5f780be4f218... Is there something specific that did work for you? I tried all the examples on Python 3.7.3 and they worked for me. One notable thing that's missing is that the @ operator for matrix multiplication, but I hope to add that in the future. [0] http://skulpt.org Python 3 Grammar. The master branch is now building and running using the grammar for Python 3.7.3. There are still lots of things to implement under the hood, but we have made a huge leap forward in Python 3 compatibility. We will still support Python 2 as an option going forward for projects that rely on it.
In Show HN: Math to Code – Interactive NumPy tutorial for engineers
That's close, but basically you need to take the square of each element first, e.g. `m * * 2` [0]. This keeps the shape of the matrix while `m.prod()` returns a single number (multiplying each element together). So it should look something like this: `np.sqrt((m * * 2).sum())` Re: The error message, it looks like it's occurring because `sum` doesn't normally take any parameters and interprets the argument as an "axis" parameter — https://numpy.org/doc/1.18/reference/generated/numpy.sum.htm... Order of operations is tricky and I could do a better job breaking it down. Still plan to add the Show Solution button but need to get some sleep :-). In the meantime you can see all the possible solutions in the repo! https://github.com/vthommeret/mathtocode/tree/master/questio... [0] Remove the space between the asterisks / I had to add it since HN
Read the rest
interprets them as italics.
In Show HN: Math to Code – Interactive NumPy tutorial for engineers
Math to Code is an interactive Python tutorial (all client-side) to teach engineers how to implement math in papers. I was inspired to create it while taking the Fast.ai course and seeing Jeremy Howard share [0] how a "complicated" Frobenius norm equation could be implemented in a single line of Python. Math to Code uses the Skulpt library to interpret Python in JavaScript. It's open source here: https://github.com/vthommeret/mathtocode I would appreciate any and all feedback! [0] https://youtu.be/4u8FxNEDUeg?t=1390 > It's time to start reading papers. And papers look something like this, which if you're anything like me, that's terrifying. And I'm not going to lie, it's still the case when I start looking at a new paper, every single time, I think, I'm not smart enough to understand this. I just can't get past that immediate reaction. So
Read the rest
I just look at this stuff and I go, that's not something I understand. > But then I remember, this is the Adam paper and you've all seen Adam implemented in one cell of Microsoft Excel. > 1. Even familiar stuff looks complex in a paper! > 2. Papers are important for deep learning beyond the basics, but hard to read. > 3. Learn to pronounce Greek letters.
In Show HN: Math to Code – Interactive NumPy tutorial for engineers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.