torrance

I think you are making exactly his point. Practicing code as a craft, caring about how you do it, how well you do it, and what it’s ultimately used for is, as you correctly point out, not going to bring you profit or employment.

So maybe there’s something wrong with how we organise work?

Well, in Julia, for one.

The simplest way to do this is described here: https://mathworld.wolfram.com/SpherePointPicking.html

Essentially:

1. Generate uniformly random values u,v between 0 and 1.

2. Then find their spherical coordinates as:

theta = 2 pi u; phi = acos(2 v -1)

Honestly I’m unsure why you’d choose a method any more complicated.

If you select "All data" for their user count, you'll notice a sharp shift in the gradient of the user count about a year ago. Any idea what would cause this?

Since no one else has mentioned it, I appreciated the Arrested Development references. Very cute.

These results are promising and hopefully carry over to the upcoming Strix Halo which I’m eagerly awaiting. With a rumoured 40 compute cores and performance on par with a low power (<95W) mobile RTX4070, it would make an exciting small form gaming box.

What about Nextflow?

If your project depends heavily on general purpose GPU programming, you might start one in C++.

This was the case for a project I am working on that was started in the last year. The interop features in rust (and other languages) are simply not as reliable as writing kernels directly in CUDA or HIP or even DPC++. You _can_ attempt to write the GPU code in C++ and call to this from $LANG via ffi, but if you want to preserve data structures and methods to work on both the host and device, its still easier to write it once in C++.

2008.

I’m really unsure why this is front page. For a hacker news audience that has little knowledge of Aotearoa New Zealand history, this is an odd first introduction that has historically been used to vilify Maori and in turn justify colonisation. If this is your first exposure to the history of Maori, please know this emphasis carries its own agenda.

You should read a little more closely before such strong condemnations.

The Julia macros @btime and the more verbose @benchmark are specially designed to benchmark code. They perform warm up iterations, then run hundreds of samples (ensuring there is no inlining) and output mean, median and std deviation.

This is all in evidence if you scroll down a bit, though I’m not sure what has been used to benchmark the Mojo code.

Whilst the Julia version currently beats Mojo, I fully expect both to approach basically the same performance with enough tinkering, and for that performance to be on par with C or Fortran.

A more interesting question is which version is more elegant, ‘obvious’ and maintainable. (Deeply familiar with both, but money is on Julia).

Thanks for that. That’s quite a different meaning.

Not to be confused with the Julia binary building platform of the same name (https://github.com/JuliaPackaging/Yggdrasil)

In case you were wondering like I was:

“The Linux kernel's stateless video decoder interface is used for video decoding where no state needs to be kept between processed video frames and allows for independently decoding each video frame.”

(https://www.phoronix.com/news/Stateless-H264-Out-Of-Staging)

Most of these features were covered at last year’s JuliaCon. Videos are all online - worth checking out!

Interferometry relies on measuring the interference pattern between two points simultaneously measuring incoming radio waves. Each element of a baseline must be measured at the same time.

If we were to allow the Earth to rotate around the Sun and measure components of the same baseline at different times, we would violate this.

I'm confused how the Doppler shift is measured in the case of the continuously modulated frequency? It seems both range and Doppler shift are encoded in the reflected signal - how are they separated?

Edit: or is it the case that a full period of the reflected signal must be detected first before Doppler can be calculated?

No. Carbon credits are meant to create a market for the right to emit carbon dioxide, ideally where the total credits are fixed and reducing per year. What you're talking about are carbon offsets, which in turn increase the the total pool of credits per year. Ideally, these offsets permanently lock an equivalent amount of CO2 away in some form (permanent forests, etc.). But increasingly, they do nothing of the sort.

Your example of handling CO2 emissions from hydrogen reserves is a case in point.

There’s a number of words like this that won’t autocomplete unless it’s seen it first.

Another one: condom.

The same could be said of a lot of modern art: it is heavily influenced/driven by the critics, not the enjoyment/pleasure/surprise of a more general audience (who just don't "get" it). There's a feeling that a refined taste is by definition not a popular taste, or even a learned taste, but instead must be exclusive to art and music schools.

I mean sure, I get that your atonal poem breaks with traditional tonality etc etc, and maybe on some intellectual level that is (was) a fresh move, but I don't _enjoy_ it, no matter how hard I've tried.

Develop against CUDA locally. Port my kernels to ROCm, and occupy a whole HPC node for debugging and performance tuning for a week. It’s terrible.

Edit: I should say that their recommendation is to write the kernels in ‘hip’ which is supposed to be their cross device wrapper for both cuda or ROCm. I’m writing in Julia however so that’s not possible.

I’m not using Frontier, but I am using Setonix which is a large AMD cluster being rolled out in Australia. All of AMD’s teaching materials are about ROCm so this is very much how they’re expecting it to be used.

The real pain for us is that there’s no decent consumer grade chips with ROCm compatibility for us to do development on. AMD have made it very clear they only care about the data centre hardware when it comes to ROCm, but I have no idea what kind of developer workflow they’re expecting there.

I’ve used CUDA and Julia extensively in my work for radio astronomy imaging applications.

I can say it is a delight to work with. All the usual GPU tips and tricks still apply, of course, and you need to pay careful attention to sequential memory accesses and so on (as with all GPU programming). But staying in the one, high level language is a real boon, and having access to native types and methods directly in my kernels is fantastic. I can’t speak highly enough of it.

And for performance comparison, I see between 3-4 orders of magnitude improvement in speed, about as fast as native CUDA.

There are examples of observed galaxies that have apparently separated from their associated dark matter halos - and which rotate like Newtonian gravity would predict. These class of galaxies have always been a thorn in MOND theories, and I think would be an issue here too.

God I had to read 12 paragraphs of nonsense before I found the phrase ‘equidistant azimuthal projection’. That’s all I wanted.

I'm confused by the corrected diff in the README... isn't that cache recreated on each function call to fib(), making the cache pointless?

Strict typing has been the one big feature missing from SQLite, that this presumably brings.

Given that this is precisely what it’s spent the last 30 years coming to understand, it’s baffling that there is only a single paragraph in this article about Modern Monetary Theory. And one at that certainly doesn’t convey the nuance of the theory at all.

For anybody seriously interested in the subject I would recommend the 2019 textbook ‘Macroeconomics’ by Mitchell, Wray & Watts.

Electric fields do the work there. A charged particle in a magnetic field feels a force (Lorenz force) that act perpendicularly to its velocity. But work is only work if the force is applied in the direction of its velocity. Essentially it's changing its direction of momentum, but not its magnitude.

On the other hand, some magnetic fields (not all) can be transformed into electric fields by a change of reference frame. In that case, the electric field can be used to do work. But I don't believe that's possible on these scales.