__abadams__
Re:Three Fundamental Flaws of SIMD ISAs (2023)
on Thursday April 24, 2025 @07:12PM (#43788541)
It would be very easy to support 512-bit vectors everywhere, and just emulate them on most systems with a small number of smaller vectors. It's easy for a compiler to generate good code for this. Clang does it well if you use its built-in vector types (which can be any length). Variable-length vectors, on the other hand, are a very challenging problem for compiler devs. You tend to get worse code out than if you just statically picked a size, even if it's not the native size.
Re:Median filtering (2022)
on Tuesday July 23, 2024 @01:15PM (#41048491)
I've found sorting-network-based filters to be faster than these methods up to size 25x25 or so. It has worse computational complexity, but filters up to that size covers a lot of ground in practice. See Figure 10 in https://andrew.adams.pub/fast_median_filters.pdf
Re:The Center of the Pixel is (0.5, 0.5)
on Thursday June 11, 2020 @07:06PM (#23494157)
Placing pixel centers at 0.5, 0.5 is only the obvious choice if you think pixels are little squares rather than point samples. Pixels-as-squares makes intuitive sense to people, especially those raised on pixel art, but it's just one possible choice you can make for your reconstruction function. It's not even a particularly good choice. It doesn't model real sensors or real displays, and it doesn't have particularly nice theoretical properties. The only thing going for it is that it's cheaper to compute some things.
Re:Halide: a language for fast, portable computation on images and ten...
on Thursday December 27, 2018 @09:33PM (#18774469)
Halide is generally good for pipelines that do math on multidimensional arrays, so quite possibly. It has a property that I think would make it hard to use for some applications in scientific computing though - while you can mutate in-place, you can't mutate an array ("Func" in Halide) after it has been used by another pipeline stage. This means that the dependency graph between your pipeline stages has no cycles except for self-cycles, which lets us do lots of clever stuff like bounds inference to guarantee the program is correct regardless of the schedule. I can imagine things like flow simulation having a hard time with that constraint. In the deep learning context this means that CNNs are ideal, but RNNs can be awkward or impossible.
Re:Halide: a language for fast, portable computation on images and ten...
on Thursday December 27, 2018 @08:04PM (#18774072)
You again? The only other time your account has posted was to plug TVM in a different post on Halide. If you're not a Tianqi Chen sockpuppet, then you should apologize to him for making him look like an asshole.
For the benefit of others not aware: TVM took Halide, deleted the half of it they didn't understand, then reimplemented it (copy-pasting large chunks without credit, hacks and all) and claimed it was a revolutionary new deep learning IR. People who already knew Halide were left scratching their heads unable to tell how this wasn't just Halide re-marketed in a different community.
Re:Halide: a language for fast, portable computation on images and ten...
on Thursday December 27, 2018 @07:44PM (#18773961)
The HDR+ siggraph paper (hdrplusdata.org) states that they use Halide, as does the newer siggraph paper on the Pixel's portrait mode (http://graphics.stanford.edu/papers/portrait/wadhwa-portrait...), and the paper on the Pixel's video denoising algorithm (http://www.chiakailiang.org/papers/ehmann_2018_rtv.pdf). The Pixel camera is riddled with Halide code, but of course it's all closed-source.
I can also vouch for the youtube use, having been tangentially involved in it and given permission to state that they use it.
Re:Halide: a language for fast, portable computation on images and ten...
on Thursday December 27, 2018 @05:42PM (#18773292)
It works but still needs a bit of cleanup. I was planning to get back to it after an upcoming conference deadline. Here's the PR: https://github.com/halide/Halide/pull/3220
Re:Halide: a language for fast, portable computation on images and ten...
on Thursday December 27, 2018 @01:02PM (#18771175)
Halide doesn't currently have good ways to handle sparse matrices, unless they have some sort of special structure that lets you pack them into rectangular shapes (e.g. a constant number of non-zeros entries per row). It would be an interesting language extension. The big thing to add would be a way to reduce over the non-zero entries more efficiently than checking them all.
Re:Why Most of America Is Terrible at Making Biscuits
on Sunday November 25, 2018 @02:57AM (#18525884)
What Americans call scones are entirely unlike a British scone. A British scone is closest to an American biscuit.
Re:Differentiable Programming for Image Processing and Deep Learning i...
on Friday September 07, 2018 @04:23PM (#17937357)
I am indeed Andrew. I'd rather not elaborate - it wasn't a huge amount of code, they added attribution when we complained about it, and they've been very careful to credit us appropriately since then. I shouldn't have even mentioned it but the TVM shilling in a Halide post struck a nerve.
Re:Differentiable Programming for Image Processing and Deep Learning i...
on Friday September 07, 2018 @12:21AM (#17931855)
I find it in poor taste to be plugging TVM on a post about Halide, given TVM's history of lifting code from Halide without attribution (well beyond the "improved" fork of the IR).