#riemannsolver
Live, measured metrics for the hashtag #riemannsolver from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #riemannsolver
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 23:11 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 23:11 UTCNo related tags with measured usage found for #riemannsolver.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 23:11 UTCEverything below is measured over the latest 2 public posts (spanning ~233 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 1
Top of the latest posts
I'm a week late 🎃 but do any #CFD folks want to see a ghost? One versatile technique for compressible flow is to implement "characteristic" boundary conditions by using a #RiemannSolver with a freestream solution outside. This nice paper d
@[email protected] Indeed, upgrading the #RiemannSolver to #HLLC (which includes a contact wave) from #HLL (which only estimates the acoustic waves) fixes this problem. Here's a pair of oblique bubble simulations to campare HLLC (lef
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/riemannsolver