vapora
Guides

Rerank saved observations

  1. Open a completed run's Ranking tab.
  2. Set the weights and baseline controls.
  3. Select Save ranking to regenerate reports and CSVs offline.

Ranking tab with fixture data

Controls

ControlDefault
Incoming-mutual count weight1; the only enabled score component
Friend, group and game Jaccard weights0
Top N5
Count baseline50
Location aggregationProduct
Location baseline100
  • Reranking uses saved observations and needs no API key or provider calls.
  • Missing games, groups or friendships remain missing, with availability visible.
  • All-zero weights produce no combined index and sort observed incoming counts.
  • Attached history indices are recalculated; collection settings and observations stay intact.
  • Incomplete runs and concurrent Steam/analysis operations reject reranking.

Recover exports

Use Exports → Rebuild exports on a completed run when you need to regenerate files from current saved observations. It preserves checkpoint bytes and attached history.

npm start -- analyze RUN_ID --root ./research

The CLI rebuilds reports; it does not provide a command to change a saved run's ranking weights. Use Save ranking in the UI for that.

Read scoring reference for formulas and settings for allowed values.

Edit this page on GitHub ↗

On this page