I wonder how much of that is scale rather than danger. Really large objects can feel unsettling even when you know they're harmless. VR seems especially good at triggering that response.
I remember like 10 years ago when Occulus first came out there was that space simulation demo where you could go around the solar system in VR. You could also "fast travel" by zooming in towards a planet, moon, blackhole.
Yeah, that was the day I learned I have a deep, crippling phobia of large objects. And Melanoheliophobia, which is fear of black holes. The only other time I've felt that way was snorkeling once near a giant 3 story tall bait ball of swirling fish, which was so disorienting and panic inducing that I vomited.
I did a 'swim with sharks' thing at Sea World (or whatever the Queensland equivalent is) with a few human-safe species of sharks, a few rays, and a selection of other fish. One of the other fish was, as far as I recall, some kind of giant grouper which, as far as my memory tells me, was huge, unmoving, and had it's mouth open the whole time, and it's mouth hole would have been big enough to put my entire head inside (this is according to my memory anyway).
I was nervous beforehand, but once I was in (and had accepted the inevitability of my own death) it was surprisingly calm / calming floating around and having these frickin' aquatic alien species just going about their dailies around me. I went close to the massive grouper just to get the scale right (not that I can really remember, it was 26 years ago). I even looked through the perspex so I could see the non-human-safe sharks in the tank next door.
After the (awesome) experience, I went and looked at the grouper from the outside (one of those underground big perspex viewing rooms) and I was back to being awed / scared by its size, and somewhat refusing to believe that I'd been in there with it. The memory of it is scarier to me than what I remember feeling when actually doing it. It's weird.
It's Sea World in Queensland, but confusingly I think the company is unrelated to the American Sea World, iirc they bought a license to the name back when it was probably a lot more positive than it is now.
EDIT: Apparently not licensed, just completely unrelated.
Outer Wilds is exactly what came to mind for me, too. Made a jump...missed. Thrown into a decaying orbit around the black hole. Absolutely terrifying, and panicking didn't help in the least!
And getting close to the upper atmosphere of Giant's Deep for the first time, staring, thinking about the atmospheres of real-world gas giants, knowing that I need to take the plunge.
That game exposed some phobias that I'd only been vaguely aware of before.
Tangential, but this being a nearly word-for-word translation of “black hole fear” made me realize how odd it is that we insist on latinizing these things.
Helio- is actually "sun", not "hole", and it's Greek, not Latin, but I 100% agree with you: it's pointless technical vocabulary that only serves to obfuscate. I think in this particular case, it's just some internet neologism (which is a good word, since coinage can mean a couple different things), made based on analogies with older phobias. For those of us who know Latin and Greek, though, all we can really do is shrug at the eagerness to make the clumsiest words possible.
I've also wondered the same thing about healthcare and other fields. All the complex sounding phrases are child-like in simplicity in their "native" tongue, yet completely indecipherable to most people in modern times. Quite a weird and undesirable path we ended up going down through inertia.
I’ve long considered medical jargon to be Latin Buffyspeak[1] because it’s usually just describing the body part, often simplistically, but in Latin so it sounds fancy.
It’s arguable whether it’s weird or undesirable. There are benefits to using unusual words when they have precise scientific or other technical meaning. It helps identify them as terms of art, so that they’re not confused with their native tongue equivalent, which invariably has much looser meanings.
Sure, but I think there's some cause/effect to consider there. The same logic would have applied in Ancient Rome, but I expect that people would have likely been less casual with their usage of such terms when they also had specific technical meanings.
For example many food dishes we have retain basic naming conventions, yet have well understood meaning. In the US a customer ordering spaghetti is likely to be quite unhappy if they get a cream sauce, even though the order itself is literally just the name of the noodle.
"Spaghetti" is a great example - notice how you have specific expectations of food that happens to be named in a foreign (relative to where you live) language.
To be fair, is there anyone alive who wouldn't be afraid of a black hole? It's a celestial body so gargantuan its gravity bends the light passing around it like a lens. Anyone who gets too close to one will literally never be seen again, ever.
Supernova and asteroids were always scarier to me because they’re potentially planet-ending scenarios. Whereas a black hole is benign as long as you don’t move into its orbit at too acute an angle.
Someone correct me if I'm wrong, and maybe it depends on the type of the black hole, but if you were to fall directly into one, or even enter an orbit too close, you would still be seen - and seen for an extremely long time.
Yes, altho "very long time" doesnt do it justice - while your light would be fading and redshifting, mathematically you could detect photons comming off you the whole remaining age of the universe.
They don’t have to be gargantuan (except in terms of mass) - the low end of stellar mass black holes can have radii as small as 6 km.
Many black holes have a bright accretion disk outside their event horizon, so visibility for those is not an issue.
But it’s certainly possible to have maximally scary black holes that have no accretion disk and are small enough so as not to cause significant lensing. You could fly your spaceship straight into one of those without even realizing, until you start turning to spaghetti.
Thanks for sharing – as someone who studies black hole environments daily, I didn't even think of such a phobia existing!
I wonder if some tricks, adjustments are feasible, to minimize the effects of these phobias? I see these visualizations as a pathway to make understanding such a complicated, unintuitive object more accessible – and would be great to make it even more accessible, if it makes sense...
Happy to chat more, brainstorm some solutions.
Sorry but a word for fear of black holes is ridiculous. Black holes are scary period. Anyone not feeling a deep sense of fear during that VR experience is missing something.
I think it’s perfectly reasonable to have a word for this fear, but I agree that ‘phobia’ isn’t appropriate because (unless you’re worried about running into one on the way to the shops) it’s quite rational. ;)
Definitely one of the most malevolent possible objects. Infinitely black, so powerful it will kill you without noticing your presence, unknowable, impossible to get rid of, you will be well aware you can't escape as you fall in before it turns you into spaghetti Amigara Fault style. My understanding is from the outside you can even see the remains of previous victims being stretched and crushed in slow motion.
Okay, so this appears to be a neologism that may not be found outside of science fiction dialogue. But I can appreciate the humorous derivation here.
Wiktionary defines this as an "irrational fear" which is in-line with other irrational fears known as phobia. So, is it possible to have a rational or healthy fear of black holes? Is it rational to be unafraid of them?
I am unafraid of personally meeting the Flying Spaghetti Monster whilst not wearing a colander on my head, and I am not irrationally afraid that Azeroth will be invaded by Kardashians. I am not afraid that a dragon will bite my head off.
It seems rationally to be respectfully "fearful" of the capabilities and awesome astrophysical properties of black holes, but it would be irrational to be afraid that I could fall into one, or be personally harmed in any way by one. If someone begins "seeing" black holes at the end of their suburban cul-de-sac, then probably get some professional help.
If anyone's interested in the accuracy, this is very 'visualisation grade' software. Its a bit of a pet peeve of mine that people present these sims as being very physically accurate, when they contain major inaccuracies, some of which are very obvious and/or deliberate. This one has some serious physical limitations
I wouldn't mind at all if it didn't say that this was a *physically accurate* black hole specifically, but this now falls under misleading science communication in a way that often gets hand waved away as if it doesn't matter, so we've got to clear some things up!
1. The accretion disk shouldn't be red, people just expect it because it looks cool. Black hole accretion disks are near universally hot enough to be blue. Interstellar did this too, and tried to handwave it away very unconvincingly
2. This is a non/low (?) spin black hole, which isn't super duper realistic
3. It ignores the position of the camera (which affects the lorentz shifting)
4. The doppler shifting isn't terribly accurate
5. It doesn't model the accretion disk temperature distribution or colour with any kind of accuracy. Usually you model accretion disks as a blackbody radiator, shift it by the doppler, and to display this convolve this against the human eye response (LMS), go to XYZ, then RGB, do a physical tonemapping step, before an sRGB conversion. This instead does none of that - no step of this is done with any physical accuracy. Its not even illustratively correct as we'll get into
6. The actual radiative transfer is very simplified compared to what you'd use for realsies, and isn't based on any real numbers, with very simplified equations. The opacity and emissivity of the disk is arbitrary, as is the size, and it does not correctly incorporate brightness or extinction, eg here https://github.com/aplavin/blackhole.plav.in/blob/2f004bfeca... is super simplified
7. The wrong equation is used for the doppler calculation. They use the I^3 variant, whereas the data you get out of a disk sample is *radiant flux* which is actually F_obs = F_emit / (z+1)^4. This is a very common mistake in image processing, which means that the doppler shift and observer brightness isn't correct. Surface brightness over here https://github.com/aplavin/blackhole.plav.in/blob/2f004bfeca... is *not* a spectral radiance but instead a radiant flux
Stuff like the brightness -> colouring conversion is particularly inaccurate. Eg if you check out the source:
It maps the pseudo brightness completely arbitrarily to colour. The resulting colour/brightness here then doesn't correspond to anything remotely physical. It also performs a *linear* mapping of a linear quantity (brightness) to sRGB (which is a nonlinear process!!), which means that it doesn't even retain any of the underlying physical characteristics of the brightness simulation, which itself is quite inaccurate. Its vibes all the way down
This is all fine if you're doing visualisation, but this isn't an accurate simulation. I wish this was just called a visualisation of a black hole, but its being communicated as if this is super hard science with credentials and all
I clicked on this because I worked on the infra that simulated the famous blackhole sim in interstella.
I thought "oooh this is interesting I wonder how they are going to do physically accurate on an end device" Recalling how the original particle sim was something like 100TB, took 2 weeks to generate and seemed to write in a way that killed disks. but that was >10 years ago, so what clever stuff has been done to model it locally.
Its been a long time since I've looked at black holes, but what I'm not understanding is why the stars surrounding the black hole are just points, and more over why the lines are straight to the centre of the hole. from memory the way light enters the hole appears non-linear and changes on view point.
Some are fair – of course this is a simplified visualization!
Observationally, we don't really know how fast a given black hole is rotating, and here I indeed assumed a non-rotating one. It's not an inaccuracy per se, more like a missing feature. The camera mode has a (half-hidden) toggle to enable Kerr metric and set spin, but even there it's not a default.
I consider the colormap choice to be completely arbitrary though, without affecting accuracy. Basically, it represents intensity at a given frequency, the image like one would get from a telescope. It wasn't intended as a faithful optical color representation! And really, in my (admittedly biased) view of a radio astronomer, I tend to assume frequencies invisible to the human eye anyway.
Its titled a "physically accurate black hole"! Please don't do this, if its intentionally not physically accurate and heavily simplified! The general public on here don't know better, and it takes someone else with years of experience simulating black holes to dig through your code to show what you've simplified. There's like a few hundred people who have the right experience worldwide to know that you've got some of your equations incorrect
The issue is when you're communicating doppler, if you want to correctly show the change in doppler, you can't make the intensity or colour mapping arbitrary
There's two ways to communicate accurately an example linear change in emissive power:
1. Use a perceptual brightness system, so that a linear change in power represents a linear perceptual change in perceived brightness. This accurately communicates to a viewer the underlying shift in power emission, if you want to show off how a radio telescope perceives a black hole for example
2. Use an emitted power <-> sRGB mapping (with tonemapping), so that a linear change in power is perceived as if it were a physical light getting brighter. This is more "what would this look like to a person?"
At the moment the change in your image brightness doesn't correspond to anything, which means that its not really communicating any science, and it doesn't correspond to doppler. Which is fine if its just illustrative and that's clear, but again vanishingly few people will know this is a visualisation not a physically accurate render
> Its titled a "physically accurate black hole"! Please don't do this, if its intentionally not physically accurate and heavily simplified!
It also doesn't exert the gravity an actually accurate black hole should :)
And also, even on a phone with two cameras, they only cover a part of sphere – while a real black hole would bend light coming from all 4pi directions. Some simplification is generally required ("the map is not the territory") and I don't see "simplified" as being opposite to "accurate".
Colormap choice: it can be a useful mode to show proper linear power -> linear perceived brightness mapping – true! But that's only one of many possible choices, and scales like logarithmic are very common in scientific images.
>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 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:
“Physically accurate” indeed raises the bar significantly.
You’ve already done great work here. That said, the feedback seems to come from someone who spent considerable time analyzing your work. Even if only a few of the suggestions are ultimately valuable, that’s still a meaningful contribution and worth considering.
Great job. Please consider turning on rotation by default (for those who missed it, it's in the parameters). The overwhelming majority of astrophysical black holes are expected to be spinning (Ker) black holes.
Please correct me if I'm wrong, but it feels like the leading edge of the accretion disk (coming towards the viewer) should be significantly brighter than it is shown here, and the trailing edge (going away from) should be significantly dimmer?
Or could the brightness shown be a result of it being Kerr vs Schwarzschild?
Yeah the doppler in this picture is all wrong unfortunately, the underlying equation used isn't right here (they mixed up spectral radiance and radiant flux). The rendering is also done without taking into account sRGB, and its run through a function that messes with the brightness - so the brightness is really incorrect. Plus all the colours are wrong (it uses an amhot colouring function, they aren't based on anything), and the extinction and emissivity isn't correct either, and the camera basis is also set up wrong so it also has the wrong perspective too. Other than that its all good
One side of the accretion disk is indeed brighter than the other – in the default view in the app, the bottom part is brighter. The effect appears quite clearly visible to me, although the exact contrast depends on the colorscale mapping. Here, I tried to find a colorscale that works well for both the disk and the jet, which naturally means the leading/trailing edge contrast can be less than in the linear mapping.
Hope it explains the visual effect!
Kerr vs Schwarzschild (static vs rotating black holes) is a much smaller effect visually – that's why it is so hard for us to measure black hole spins (= how fast they are rotating) observationally, even with the Event Horizon Telescope.
I think the contrast between the two sides is typically greater with an optically thick disk, and it looks like you are rendering an optically thin disk. I think that's the main difference from what I was expecting when I saw it.
True, the disk is rendered optically (and geometrically) thin. This is done so that real-time performance is attained on devices like phones – volumetric GR rendering would be significantly more expensive. The jet (zoom out to see it) is rendered with full volumetric effects, because it's just special relativity there.
Fortran punchcard style to render black holes?! That's really going full circle to the origins, I really enjoyed reading about Luminet's work some time ago.
Oh nice, I had not zoomed out enough. I don't think I've seen the relativistic jets rendered before. The AR mode looks great on my phone.
Yep, I had fun learning a lot about punchcards, Fortran, and the math behind black holes. I suspect I'm doing something similar to you in my Fortran implementation, raymarching along the null geodesic to come up with my final image: https://imgur.com/a/czysDls
Also, I have to point out the "going full circle" pun, intended or not.
Actually, the jet was the first part of the app – I wanted to just see and "feel" relativistic beaming in practice, in physical space. And it was fun and instructive indeed!
Really puts into perspective how tight is the jet vs line-of-sight alignment for those bright jets we see across the universe. And how beaming is the dominant effect that determines the jet/quasar appearance.
Very cool, and very mind bending.
Very faithful to the Event Horizon Telescope rendering.
A decade ago I got really into black holes for like a few months, and I read Kip Thorne's book called "The Science of Interstellar", talking all about black hole simulations.
Have you read it? I wonder how the simulation tech has evolved, as 10 years is a lot.
I do wonder if you do like, size estimates of a black hole in my room. Suppose I have a black hole in my room, I'd be curious to know what the mass of that is, like a fun fact, tidbit somewhere.
The technology has come a long way indeed! The first simulations of how a black hole would look like are from 1979, by Jean-Pierre Luminet – take some time to find and look at them, it's super impressive what they achieved using that era tech!
Now, we can get much higher-resolution ones in real time on any smartphone.
I work in the Event Horizon Telescope, studying jets accelerated by black holes, and immediate black hole surroundings as well. I do ray tracing / radiative transfer simulations, and this app is an adaptation of those simulations – with the primary focus on being physically accurate under reasonable assumptions.
And totally, I enjoyed listening to Kip Thorne's lectures and talking to him, he gives them in a very approachable style while remaining honest!
In my experience, on Android, it definitely relies on camera: AR doesn't work in dark room, and barely works in slightly-lit room. So it must be fusing camera + accelerometer + ...
on iPhone 12 Pro Max and later (maybe only on Pros, I forget) they have a LiDAR sensor built in, allowing for impressively accurate 3D scans of objects with a free app like Scaniverse. But yeah I think AR was the intention there
Your phone has an accelerometer, which can be integrated twice to result in slightly accurate dead reckoning; just keep accumulating 3-vectors with every time-slice. That's a helluva lot easier than visual cues.
"slightly accurate" is the correct description, though -- dead reckoning on a cell-phone-class IMU accumulates drift too quickly to keep objects anchored in space for more than seconds at a time. You need something (visual odometry, SLAM) that provides long-term stability, even if it has short-term noise or poor availability, to fuse in.
When this topic comes up, I'm always happy to share this incredible lecture from many many years ago about sensor fusion and dead reckoning and how you _cannot_ integrate acceleration twice:
12 years ago I had to write the firmware for an IMU. It took me some real effort to convince my bosses that double integration was, for all practical purposes, impossible. I wish I had known about this video back then...
IMU are very useful to known your orientation though. Even an inaccurate IMU is useful to provide an initial estimate to feed vision-based algorithms.
Yes, linked in the readme! They simulate light bending, but ignore time delay effects.
I think the earliest of these black-hole-camera renderings is https://dominic-chang.com/bhi-filter/ though (also linked in readme) – a direct inspiration for the camera mode in my app!
If this app turns the entire screen black, this probably means WebGL is not supported :)
Black holes don't really "suck in" light. Whatever falls onto the black hole itself gets deleted, of course – but otherwise, it bends light rays towards its center. That's why the app shows distortion + black circle in the in middle in the camera mode.
The event horizon for even the smallest black hole is in the scale of kilometers. If the user is a meter away from the black hole light isn't going to move away from the center of it to your camera.
Now I think I see what you meant.
There actually are no upper/lower limits on the black hole size (in classical physics – ignoring quantum effects). Compressing the Earth to ~1 cm in size would give you a black hole, and its event horizon size would be ~1 cm, not kilometers.
And even black holes this small are stable, according to our physics knowledge.
I grew up with micro black holes being a possibility, with conjectures such as primordial black hole evaporating down to Planck dimension stability, etc.
I just get a flat floating image of a black hole. Am i holding it wrong?
Yeah, that was the day I learned I have a deep, crippling phobia of large objects. And Melanoheliophobia, which is fear of black holes. The only other time I've felt that way was snorkeling once near a giant 3 story tall bait ball of swirling fish, which was so disorienting and panic inducing that I vomited.
I was nervous beforehand, but once I was in (and had accepted the inevitability of my own death) it was surprisingly calm / calming floating around and having these frickin' aquatic alien species just going about their dailies around me. I went close to the massive grouper just to get the scale right (not that I can really remember, it was 26 years ago). I even looked through the perspex so I could see the non-human-safe sharks in the tank next door.
After the (awesome) experience, I went and looked at the grouper from the outside (one of those underground big perspex viewing rooms) and I was back to being awed / scared by its size, and somewhat refusing to believe that I'd been in there with it. The memory of it is scarier to me than what I remember feeling when actually doing it. It's weird.
EDIT: Apparently not licensed, just completely unrelated.
No Orcas, good rehab program, seal exhibit is good (no true seals), Polar bears are a bit sad though
I did the seal diving experience which was great - mostly disabled California sea lions and NZ Fur seals (which do well in captivity)
Strongly recommend Outer Wilds. Falling into the black hole the first time was one of my most scared moments in gaming. I was totally panicking lol
Side effects may include overwhelming hate for Walt Disney Productions.
And getting close to the upper atmosphere of Giant's Deep for the first time, staring, thinking about the atmospheres of real-world gas giants, knowing that I need to take the plunge.
That game exposed some phobias that I'd only been vaguely aware of before.
Tangential, but this being a nearly word-for-word translation of “black hole fear” made me realize how odd it is that we insist on latinizing these things.
[1] https://tvtropes.org/pmwiki/pmwiki.php/Main/BuffySpeak
For example many food dishes we have retain basic naming conventions, yet have well understood meaning. In the US a customer ordering spaghetti is likely to be quite unhappy if they get a cream sauce, even though the order itself is literally just the name of the noodle.
Supernova and asteroids were always scarier to me because they’re potentially planet-ending scenarios. Whereas a black hole is benign as long as you don’t move into its orbit at too acute an angle.
Many black holes have a bright accretion disk outside their event horizon, so visibility for those is not an issue.
But it’s certainly possible to have maximally scary black holes that have no accretion disk and are small enough so as not to cause significant lensing. You could fly your spaceship straight into one of those without even realizing, until you start turning to spaghetti.
> it’s certainly possible to have maximally scary black holes that have no accretion disk and are small enough so as not to cause significant lensing
Now that's a proper cosmic horror.
I wonder if some tricks, adjustments are feasible, to minimize the effects of these phobias? I see these visualizations as a pathway to make understanding such a complicated, unintuitive object more accessible – and would be great to make it even more accessible, if it makes sense... Happy to chat more, brainstorm some solutions.
Okay, so this appears to be a neologism that may not be found outside of science fiction dialogue. But I can appreciate the humorous derivation here.
Wiktionary defines this as an "irrational fear" which is in-line with other irrational fears known as phobia. So, is it possible to have a rational or healthy fear of black holes? Is it rational to be unafraid of them?
I am unafraid of personally meeting the Flying Spaghetti Monster whilst not wearing a colander on my head, and I am not irrationally afraid that Azeroth will be invaded by Kardashians. I am not afraid that a dragon will bite my head off.
It seems rationally to be respectfully "fearful" of the capabilities and awesome astrophysical properties of black holes, but it would be irrational to be afraid that I could fall into one, or be personally harmed in any way by one. If someone begins "seeing" black holes at the end of their suburban cul-de-sac, then probably get some professional help.
I wouldn't mind at all if it didn't say that this was a *physically accurate* black hole specifically, but this now falls under misleading science communication in a way that often gets hand waved away as if it doesn't matter, so we've got to clear some things up!
1. The accretion disk shouldn't be red, people just expect it because it looks cool. Black hole accretion disks are near universally hot enough to be blue. Interstellar did this too, and tried to handwave it away very unconvincingly
2. This is a non/low (?) spin black hole, which isn't super duper realistic
3. It ignores the position of the camera (which affects the lorentz shifting)
4. The doppler shifting isn't terribly accurate
5. It doesn't model the accretion disk temperature distribution or colour with any kind of accuracy. Usually you model accretion disks as a blackbody radiator, shift it by the doppler, and to display this convolve this against the human eye response (LMS), go to XYZ, then RGB, do a physical tonemapping step, before an sRGB conversion. This instead does none of that - no step of this is done with any physical accuracy. Its not even illustratively correct as we'll get into
6. The actual radiative transfer is very simplified compared to what you'd use for realsies, and isn't based on any real numbers, with very simplified equations. The opacity and emissivity of the disk is arbitrary, as is the size, and it does not correctly incorporate brightness or extinction, eg here https://github.com/aplavin/blackhole.plav.in/blob/2f004bfeca... is super simplified
7. The wrong equation is used for the doppler calculation. They use the I^3 variant, whereas the data you get out of a disk sample is *radiant flux* which is actually F_obs = F_emit / (z+1)^4. This is a very common mistake in image processing, which means that the doppler shift and observer brightness isn't correct. Surface brightness over here https://github.com/aplavin/blackhole.plav.in/blob/2f004bfeca... is *not* a spectral radiance but instead a radiant flux
Stuff like the brightness -> colouring conversion is particularly inaccurate. Eg if you check out the source:
https://github.com/aplavin/blackhole.plav.in/blob/2f004bfeca...
It maps the pseudo brightness completely arbitrarily to colour. The resulting colour/brightness here then doesn't correspond to anything remotely physical. It also performs a *linear* mapping of a linear quantity (brightness) to sRGB (which is a nonlinear process!!), which means that it doesn't even retain any of the underlying physical characteristics of the brightness simulation, which itself is quite inaccurate. Its vibes all the way down
This is all fine if you're doing visualisation, but this isn't an accurate simulation. I wish this was just called a visualisation of a black hole, but its being communicated as if this is super hard science with credentials and all
I thought "oooh this is interesting I wonder how they are going to do physically accurate on an end device" Recalling how the original particle sim was something like 100TB, took 2 weeks to generate and seemed to write in a way that killed disks. but that was >10 years ago, so what clever stuff has been done to model it locally.
Its been a long time since I've looked at black holes, but what I'm not understanding is why the stars surrounding the black hole are just points, and more over why the lines are straight to the centre of the hole. from memory the way light enters the hole appears non-linear and changes on view point.
I consider the colormap choice to be completely arbitrary though, without affecting accuracy. Basically, it represents intensity at a given frequency, the image like one would get from a telescope. It wasn't intended as a faithful optical color representation! And really, in my (admittedly biased) view of a radio astronomer, I tend to assume frequencies invisible to the human eye anyway.
Its titled a "physically accurate black hole"! Please don't do this, if its intentionally not physically accurate and heavily simplified! The general public on here don't know better, and it takes someone else with years of experience simulating black holes to dig through your code to show what you've simplified. There's like a few hundred people who have the right experience worldwide to know that you've got some of your equations incorrect
The issue is when you're communicating doppler, if you want to correctly show the change in doppler, you can't make the intensity or colour mapping arbitrary
There's two ways to communicate accurately an example linear change in emissive power:
1. Use a perceptual brightness system, so that a linear change in power represents a linear perceptual change in perceived brightness. This accurately communicates to a viewer the underlying shift in power emission, if you want to show off how a radio telescope perceives a black hole for example
2. Use an emitted power <-> sRGB mapping (with tonemapping), so that a linear change in power is perceived as if it were a physical light getting brighter. This is more "what would this look like to a person?"
At the moment the change in your image brightness doesn't correspond to anything, which means that its not really communicating any science, and it doesn't correspond to doppler. Which is fine if its just illustrative and that's clear, but again vanishingly few people will know this is a visualisation not a physically accurate render
It also doesn't exert the gravity an actually accurate black hole should :) And also, even on a phone with two cameras, they only cover a part of sphere – while a real black hole would bend light coming from all 4pi directions. Some simplification is generally required ("the map is not the territory") and I don't see "simplified" as being opposite to "accurate".
Colormap choice: it can be a useful mode to show proper linear power -> linear perceived brightness mapping – true! But that's only one of many possible choices, and scales like logarithmic are very common in scientific images.
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 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
You’ve already done great work here. That said, the feedback seems to come from someone who spent considerable time analyzing your work. Even if only a few of the suggestions are ultimately valuable, that’s still a meaningful contribution and worth considering.
Or could the brightness shown be a result of it being Kerr vs Schwarzschild?
Kerr vs Schwarzschild (static vs rotating black holes) is a much smaller effect visually – that's why it is so hard for us to measure black hole spins (= how fast they are rotating) observationally, even with the Event Horizon Telescope.
Very cool demo! Thanks for sharing!
(For reference, my experience rendering black holes is recreating Luminet's rendering from the late 70s: https://www.ioccc.org/2025/cesmoak/index.html )
Fortran punchcard style to render black holes?! That's really going full circle to the origins, I really enjoyed reading about Luminet's work some time ago.
Yep, I had fun learning a lot about punchcards, Fortran, and the math behind black holes. I suspect I'm doing something similar to you in my Fortran implementation, raymarching along the null geodesic to come up with my final image: https://imgur.com/a/czysDls
Also, I have to point out the "going full circle" pun, intended or not.
I work in the Event Horizon Telescope, studying jets accelerated by black holes, and immediate black hole surroundings as well. I do ray tracing / radiative transfer simulations, and this app is an adaptation of those simulations – with the primary focus on being physically accurate under reasonable assumptions.
And totally, I enjoyed listening to Kip Thorne's lectures and talking to him, he gives them in a very approachable style while remaining honest!
https://www.youtube.com/watch?v=C7JQ7Rpwn2k&t=1401s (the whole video is incredible, but this timestamp is the magical bit)
IMU are very useful to known your orientation though. Even an inaccurate IMU is useful to provide an initial estimate to feed vision-based algorithms.
Me: zooms in
I think the earliest of these black-hole-camera renderings is https://dominic-chang.com/bhi-filter/ though (also linked in readme) – a direct inspiration for the camera mode in my app!
Two black holes at once?!?!?? Yeah, I'm crazy like that.
Black holes don't really "suck in" light. Whatever falls onto the black hole itself gets deleted, of course – but otherwise, it bends light rays towards its center. That's why the app shows distortion + black circle in the in middle in the camera mode.
I grew up with micro black holes being a possibility, with conjectures such as primordial black hole evaporating down to Planck dimension stability, etc.