ivansavz (u/ivansavz)

ivansavz commented on An interactive version of Byrne's The Elements of Euclid (1847) c82.net/euclid/... · Posted by u/tzury

amadeuspagel · 6 days ago

Beautiful, and would be so much more beautiful if it used a modern font, without these weird cs and fs. I actually had to copy-paste "reproduction" to convince myself that this is a c character, and I'm not reading something in some ancient version of english with characters that I've never seen.

ivansavz · 6 days ago

There is a menu from the top bar to change the "Modern English."

ivansavz commented on How HTML changes in ePub htmhell.dev/adventcalenda... · Posted by u/raybb

robin_reala · a month ago

Author here, happy to answer any questions / clarify anything.

ivansavz · a month ago

Thanks for all the explanations. I always thought it was regular HTML, but now I know to watch out for the differences.

Can you say a few more words about the library https://github.com/standardebooks/tools ? Can it generate ePub3 from markdown files or do I have to feed it HTML already. Any repo with usage examples of the `--white-label` option would be nice.

ivansavz commented on Go Gray, Not Cray: Why You Should Grayscale Your Phone sami.eljabali.org/go-gray... · Posted by u/samieljabali

ivansavz · a month ago

I've been in Grayscale for some time now (almost a month), and it's great. I always wanted to have a phone with an eInk display, and this is pretty close feeling (aesthetically).

Scrolling is no longer interesting, and food looks un-appetizing. Making the digital reality look boring is a good deal to make the real world look more exciting.

Thanks to comments from @jtbaker and @SkyPuncher I just added a shortcut to the "pull out" menu so I can now turn off when I need to work with pictures where colors are important.

ivansavz commented on "No Bullshit Guide to Statistics" Book nobsstats.com/intro.html... · Posted by u/gregsadetsky

ivansavz · 2 months ago

Thanks Greg for posting!

The website has all the notebooks from the book, as well as well as the complete tutorials on the tech stack (Python, Pandas, Seaborn).

For everyone interested, check out the extended preview PDFs:

- Part 1: DATA and PROBABILITY https://minireference.com/static/excerpts/noBSstats_part1_pr...

- Part 2: STATISTICAL INFERENCE https://minireference.com/static/excerpts/noBSstats_part2_pr...

ivansavz commented on In Defense of Matlab Code runmat.org/blog/in-defens... · Posted by u/finbarr1987

Aerolfos · 2 months ago

> To make `Z` a column vector, we would need something like `Z = (Y @ X)[:,np.newaxis]`.

Doesn't just (Y @ X)[None] work? None adding an extra dimension works in practice but I don't know if you're "supposed" to do that

ivansavz · 2 months ago

It seems `(Y @ X)[None]` produces a row vector of shape (1,3),

   (Y @ X)[None]
   
   # array([[14, 32, 50]])

but `(Y @ X)[None].T` works as you described:

   (Y @ X)[None].T
   
   # array([[14],
   #        [32],
   #        [50]])

I don't know either RE supposed to or not, though I know np.newaxis is an alias for None.

ivansavz commented on In Defense of Matlab Code runmat.org/blog/in-defens... · Posted by u/finbarr1987

fph · 2 months ago

Actually, I just tried Y @ X in Numpy and it works just fine.

It's because in Python 1-dimensional arrays are actually a thing, unlike in Matlab. That line of code is a non-example; it is easier to make it work in Python than in Matlab.

ivansavz · 2 months ago

The result of `Y @ X` has shape (3,), so the next line (concatenate as columns) fails.

To make `Z` a column vector, we would need something like `Z = (Y @ X)[:,np.newaxis]`.

Although, I'm not sure why the author is using `concatenate` when the more idiomatic function would be stack, so the change you suggest works and is pretty clean:

   Z = Y @ X
   np.stack([Z, Z], axis=1)
   # array([[14, 14],
   #        [32, 32],
   #        [50, 50]])

with convention that vectors are shape (3,) instead of (3,1).

ivansavz commented on In Defense of Matlab Code runmat.org/blog/in-defens... · Posted by u/finbarr1987

NoahZuniga · 2 months ago

> # We must reshape X to be a column vector (3,1)

> # or rely on broadcasting rules carefully.

> Z = Y @ X.reshape(3, 1)

Why not use X.transpose()?

ivansavz · 2 months ago

I thought so too, but it doesn't seem to work since X has shape (3,).

This seems to work,

   Z = Y @ X[:,np.newaxis]

thought it is arguably more complicated than calling the `.reshape(3,1)` method.

ivansavz commented on The "confident idiot" problem: Why AI needs hard rules, not vibe checks steerlabs.substack.com/p/... · Posted by u/steer_dev

mfalcon · 2 months ago

I had been working on NLP, NLU mostly, some years before LLMs. I've tried the universal sentence encoder alongside many ML "techniques" in order to understand user intentions and extract entities from text.

The first time I tried chatgpt that was the thing that surprised me most, the way it understood my queries.

I think that the spotlight is on the "generative" side of this technology and we're not giving the query understanding the deserved credit. I'm also not sure we're fully taking advantage of this funcionality.

ivansavz · 2 months ago

Yes, I was (and still am) similarly impressed with LLMs ability to understand the intent of my queries and requests.

I've tried several times to understand the "multi-head attention" mechanism that powers this understanding, but I'm yet to build a deep intuition.

Is there any research or expository papers that talk about this "understanding" aspect specifically? How could we measure understand without generation? Are there benchmarks out there specifically designed to test deep/nuanced understanding skills?

Any pointers or recommended reading would be much appreciated.