#hierarchicalportioning
Live, measured metrics for the hashtag #hierarchicalportioning from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #hierarchicalportioning
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 · mastodon.online (Mastodon public tags API) · fetched 2026-10-04 12:23 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-10-04 12:23 UTCNo related tags with measured usage found for #hierarchicalportioning.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-04 12:23 UTCEverything below is measured over the latest 3 public posts (spanning ~3911 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0
Top of the latest posts
The ‘spatialreg.hp’ #RPackage extended the concept of #AverageSharedVariance (ASV) to #SpatialAutoregressiveModels (SARs), quantified spatial and environmental effects in SARs. #HierarchicalPortioning | #VariationPartitioning https://doi.or
Jiangshan Lai et al. developed an #RPackage "spatialreg.hp", which extended the concept of #AverageSharedVariance to #SpatialAutoregressive models, enabling the decomposition of total model R2 into unique and shared contributions of spatial
【🎉Latest accepted article】 Quantifying Spatial and Environmental Effects in Spatial Autoregressive Model with the spatialreg.hp #RPackage #AverageSharedVariance | #HierarchicalPortioning | #SpatialAutocorrelation | #VariationPartitioning h
#hierarchicalportioning across platforms
every network with a public tag surfaceFollow #hierarchicalportioning straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/hierarchicalportioning