HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
achael
eht-imaging
Python2019–2026
achael / eht-imaging

eht-imaging

Imaging, analysis, and simulation software for radio interferometry

15Distinct people
19Mentions
0Explicit recommenders
5.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Imaging, analysis, and simulation software for radio interferometry

GitHub

Where it is used

No documented product use was verified in the last source check.

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, 3:56:07 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 year19 dated mentions

Observed mentions: 2019-04-10 23:59:20 UTC to 2026-07-27 20:10:55 UTC.

0510152019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 16 mentions; 3 submissions, 13 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC16313
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

19 sources
So in your opinion, the primary thing that makes this a physically accurate simulation is that you've calculated the bending of light rays, and the structure, colouration and brightness of the accretion disk doesn't matter at all? >As for colormapping: I follow the by-far-dominant approach in scientific literature, where color mapping choice is completely unrelated to physical accuracy of the plotted observations or simulations. Having a preference for different color schemes is a matter of taste; suggesting a linear intensity->pixel mapping is a reasonable feature request, but far from a bug or inaccuracy. It is not true at all that this is the dominant approach in the literature, the event horizon telescope does not use this approach in their papers. I linked a comment from them elsewhere about this in a github PR Specifically: https://
Read the rest
github.com/achael/eht-imaging/issues/85 >Unfortunately, vanilla afmhot does remain the current default in the eht-imaging library for historical reasons, but this could change soon. *Rest assured we thought of this issue and the paper images are indeed perceptually uniform!* I would welcome an attempt for you to create a scale, that maps the output pixel brightness to the underlying physical luminance, which I think would show why the mapping is such a problem here from an accuracy perspective, but you're absolutely not correct that you're following the literature here. People are much more careful about presenting accurate data, and your approach would result in a correction being put out
In Show HN: Physically accurate black hole you can put in your room
>I don't see "simplified" as being opposite to "accurate". Are black hole accretion disks generally red in real astrophysical cases? They're most accurately represented as being blue. Red is fine for visualisations because it looks cool (which is fine!), but blue is the physically accurate colour. Visualisations claiming to be accurate like this presenting red black holes is becoming an increasingly large science communication problem The way that the colour and brightness are mapped together is also not correlated correctly, and some of the equations just aren't right. The doppler isn't correct at all here, partly because its simulated incorrectly (with the camera problems), and partly because the mapping done at the end doesn't correlate to any reasonable brightness Stuff like this: Its not accurate at all. It isn't simplified, its just
Read the rest
wrong - which is totally fine for a visualisation, if that's the intent. But: >scales like logarithmic are very common in scientific images. Sure. What scale are you using for the doppler brightness here? Because as far as I can tell, its a piecewise mapping of the form ~pow(x, 2.2), after being run through a non smooth function `afmhot` - a function which doesn't have a linear brightness response. So the brightness in this image doesn't really correspond to anything related to doppler or brightness, and the colour also doesn't correspond to anything involving colour (or the doppler). The entire image's look is basically accidental Here's a specific comment from the event horizon telescope talking about exactly this problem with specifically the afmhot transform being used, because its important for visualisation: https://github.com/achael/eht-imaging/issues/85 Which shows some of the problems here
In Show HN: Physically accurate black hole you can put in your room
To make it clear...They did not "take a picture" of a Blackhole the first time, at least not in the way most people think of "taking a picture" as in the sense of visual evidence like in imaging the moon, galaxies on long exposure, planets etc... The team multiple times used terms like we have "visual evidence", "photons" and "telescopes" when referring to their radio telescopes. They did something great, no doubt about it. Still, as we confront other science challenges like demonstrating safety of vaccines, evidence for human impact on the planet and as it causes global warming, I do not think science teams should push that much the use of certain words and concepts in the context of making their work more accessible. Its demeaning to the "general public" who actually is probably quite well educated and does not need these word plays.
Read the rest
They scanned the sky using an existing technique ( VLBI ), processed the data through a series of very innovative and smart data algorithms and created a synthetic image using these libraries: https://github.com/achael/eht-imaging Then, the data was given to four different teams who come up with 4 different "blackhole pictures". Then they averaged it and published their "photo" while calling it "visual evidence", their words not mine. As these libraries have different color profiles ... https://github.com/liamedeiros/ehtplot/blob/docs/docs/COLORM... they could have gone for the violet profile ;-) But then they would have more difficulty calling it the "blackhole photo" instead of what it is: A synthetic image that it is made from 230 Ghz radio data and very smart statistic inference algorithms. Naturally using the yellow color tone it easier to call it a "blackhole picture". It looks like something in Space... No science journalist questioned them on that, and now they are getting even more "creative" with their imaging techniques: https://projects.iq.harvard.edu/files/styles/os_files_xxlarg... They could have just said: We measured the size of the shadow, plus or minus, and we "think" its a blackhole but it could also be other object in the universe that looks like this. As they had to admit here at 1h.00.45 in reply to a question: "What other objects in the universe could look like this?" https://youtu.be/q6ZnAdNQNVo?t=3644
In Event Horizon Telescope captures ‘beautiful’ images of second black hole’s jet
It's very easy to see that this is a publicity stunt (and a quite sexist one, at that). Allegations have been made that Andrew Chael contributed 850kloc, but this is clearly bizzare. Analyzing the git repo[1] shows that this enormous contribution was actually data used to train the probabilistic imaging model used in creating the image. Chael has also addressed this attack campaign on his twitter [2], making it clear that Katie Bouman played a vital role in the EHT project. [1] https://github.com/achael/eht-imaging/graphs/contributors [2] https://twitter.com/thisgreyspirit/status/111651854496183091...
In [dead]
I'm reluctant to even dignify this kind of low-effort drivel with a response. There's a bunch of other commits linked from that very same user profile, related to -- and this will blow your mind -- image reconstruction: https://github.com/achael/eht-imaging/commits?author=klbouma... Even if that were not true, scientific code often does not end up public, let alone on github. Not to mention that Dr. Bouman is the first author of a closely-related paper at CVPR, which is one of the most prestigious meetings in a field of study called "computer vision": https://arxiv.org/abs/1512.01413 Obviously this was a massive team effort, but PR frenzies happen to good people all the time and I don't see anyone scrutinizing public commit counts when it's a man in a similar context.
In Katie Bouman, the computer scientist behind the first black hole image
I think you're looking in the wrong place. I don't see anywhere in the eat github repository where there is code similar to the CHIRP algorithm (correct me if I'm wrong). I'd be interested in seeing the actual code used to generate the image (certainly the eat repo was used, but it doesn't look to be the main algorithm?) It looks more plausible that the algorithm is in eht-imaging (https://github.com/achael/eht-imaging), but I haven't looked deeply enough yet. She contributed a lot more to that repo. And having said all that, # lines/commits isn't as important as the algorithm
In Katie Bouman, the computer scientist behind the first black hole image
Citation definitely needed. The software is "ehtim", here are the contributors: https://github.com/achael/eht-imaging/graphs/contributors He says: > I wrote ehtim (eht-imaging) as a python framework for implementing regularized maximum likelihood imaging methods on EHT data. In the last two years, it has evolved into a flexible environment for manipulating, simulating, analyzing, and imaging interferometric data and is a workhorse of the EHT’s data analysis pipeline. Source: https://achael.github.io/_pages/software/ At first I thought the image was being disingenuous by cherry-picking commits to highlight, but take a look for yourself, she really did mostly just modify plotting, add options and fix bugs: https://github.com/achael/eht-imaging/commits?author=klbouma... There's nothing wrong with that, but claiming that she is "behind the so
Read the rest
ftware" is just bullshit.
In Katie Bouman, the computer scientist behind the first black hole image

Showing the 15 most recent of 19 sources. Enable JavaScript to search and browse every indexed mention.

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.