This is pretty, but none of those visualisations look very... singular to me? Can anyone tell me where to look in those simulations to see the blowup? Does speed go infinite in some region (which one? the blue or orange part?), or just non-smooth?
“ This is not the smoothness problem solution, but rather the Burgers vortex, an exact solution of the Navier–Stokes equations published by J. M. Burgers in 1948, chosen because it has the same anatomy: fluid drawn inward in a plane, stretched along the axis and thrown out of both ends, spinning fastest in a core.”
I've my own particle visualizations, after editing the ThreeJS particle attractor example I've started building a collection of these with R3F ReactThreeFiber and Drei in westurner/particlewavefluid: https://github.com/westurner/particlewavefluid
ThreeJS can use WebGPU if available or fallback to WebGL.
I haven't yet implemented NS; I should prioritize building Fedi's SQG and DDF Dilatant Dark Fluid models of black holes with only just one vortex moisture with GOE Gross-Pitaevskii equation.
I did do (ai) review and try to find extensions from the new NS for Incompressible fluids solution. There are connections from Navier-Stokes to Lagrangian mechanics through the Madelung transformation; https://news.ycombinator.com/item?id=49637058
But SQS and DDF say that the Superfluid of space-time is a dilatant fluid that is both compressible and incompressible, and there's a 4th term. So far, I've used 4x4 normed tensor Gaussian splatters to quantize the fluid simulations and it seems advantageous because FWIU the normed tensors already naturally do conservation of energy in the sim.
Also working with sim optimizations on limited architectures;
A few weeks ago in the CircuitPython implementation of MU-AV (Mu Animation Video) codec and gaussian splatter scene rep, I
implemented loop unrolling for a 14X return (actually 100% to 5% utilization on 1 (one) core)) over nested lists in the CPython on x86-64 emulated version for the 156Mhz TI-84 ARM processor dedicated to running Python. But will it work on a really slow processor with no SIMD or GPU shaders?
This is pretty, but none of those visualisations look very... singular to me? Can anyone tell me where to look in those simulations to see the blowup? Does speed go infinite in some region (which one? the blue or orange part?), or just non-smooth?
It might be that the velocity at the spiraling axis is not infinity (i.e. there is no blow-up in finite time). Viscosity is a bitch.
“ This is not the smoothness problem solution, but rather the Burgers vortex, an exact solution of the Navier–Stokes equations published by J. M. Burgers in 1948, chosen because it has the same anatomy: fluid drawn inward in a plane, stretched along the axis and thrown out of both ends, spinning fastest in a core.”
Neat! Geisswerks has Navier-Stokes visualizations that run on Win98/2k IIRC.
Milkdrop3/projectM can vary visualization parameters according to audio attributes samples in real time.
Could be in an open source bowling alley: https://news.ycombinator.com/item?id=48971134
I've my own particle visualizations, after editing the ThreeJS particle attractor example I've started building a collection of these with R3F ReactThreeFiber and Drei in westurner/particlewavefluid: https://github.com/westurner/particlewavefluid
ThreeJS can use WebGPU if available or fallback to WebGL.
I haven't yet implemented NS; I should prioritize building Fedi's SQG and DDF Dilatant Dark Fluid models of black holes with only just one vortex moisture with GOE Gross-Pitaevskii equation.
I did do (ai) review and try to find extensions from the new NS for Incompressible fluids solution. There are connections from Navier-Stokes to Lagrangian mechanics through the Madelung transformation; https://news.ycombinator.com/item?id=49637058
But SQS and DDF say that the Superfluid of space-time is a dilatant fluid that is both compressible and incompressible, and there's a 4th term. So far, I've used 4x4 normed tensor Gaussian splatters to quantize the fluid simulations and it seems advantageous because FWIU the normed tensors already naturally do conservation of energy in the sim.
Also working with sim optimizations on limited architectures;
Re: the first version of MU-AV (in C++) on an ESP32-S3 with a 1Hz ePaper price tag screen; https://news.ycombinator.com/item?id=49060309
A few weeks ago in the CircuitPython implementation of MU-AV (Mu Animation Video) codec and gaussian splatter scene rep, I implemented loop unrolling for a 14X return (actually 100% to 5% utilization on 1 (one) core)) over nested lists in the CPython on x86-64 emulated version for the 156Mhz TI-84 ARM processor dedicated to running Python. But will it work on a really slow processor with no SIMD or GPU shaders?
Did i386 have SIMD? Re: "SIMD-accelerated computer vision on a $2 microcontroller": https://news.ycombinator.com/item?id=40784199
"Show HN: WebGPU Particles Simulation" https://news.ycombinator.com/item?id=38678703