Skip to documentation
Screebits Docs
Flow Editor
Open Screebits
  • Screebits
  • Flow Editor documentation
  • Blueprints
  • Your first steps in Screebits
  • Workspace, strategies and account
  • Get started with the Flow Editor
  • Build an RSI Momentum Alert
  • Flow Editor concepts
  • How a strategy starts and continues
  • Control and data connections
  • Nodes, parameters, outcomes, and ports
  • Plans and feature availability
  • Saves, versions, and checkpoints
  • Tactical and Portfolio strategies
  • Validation and readiness
  • Flow Editor mode guides
  • Build Portfolio strategies
  • Build Tactical strategies
  • Flow Editor guides
  • Add a Quant Hub metric
  • Configure a node
  • Configure Settings and visual preferences
  • Connect nodes
  • Create a strategy
  • Create checkpoints and restore versions
  • Reset a Flow safely
  • Debug and replay a Backtest
  • Fix validation issues
  • Use keyboard shortcuts
  • Manage variables
  • Run a Backtest
  • Save and resolve conflicts
  • Work on tablet and mobile
  • Use Quick add
  • Use the Inspector
  • Add, move, duplicate, and remove nodes
  • Flow Editor examples
  • Portfolio rebalance with risk limits
  • Tactical order and position monitoring
  • Use Backtest Center
  • Read a Backtest result
  • Compare and export Backtests
  • Explore Quant Hub
  • Metric parameters, charts and overlays
  • Flow Editor node reference
  • Ranking
  • Flow Editor troubleshooting
  • Troubleshoot activation and validation
  • Troubleshoot Backtests and replay
  • Troubleshoot compact layouts
  • Troubleshoot connections and data types
  • Troubleshoot plans and locked features
  • Troubleshoot Quant Hub in the Flow Editor
  • Troubleshoot save, offline, and conflicts
  • Backtests and responsible use
  • Flow Editor glossary
  1. Screebits
  2. /Flow Editor documentation
  3. /Flow Editor node reference
  4. /Ranking
IntermediateLast verified Sep 30, 2026

Ranking

Orders scored assets and selects a subset of the connected universe.

On this page
  1. When to use
  2. Example
  3. Select from scored assets
  4. Common problems
  5. Next steps

Orders scored assets and selects a subset of the connected universe.

When to use

Use it when the Portfolio graph should choose candidates by a connected score.

Example

Rank the filtered universe by a momentum score and pass the selected assets to Weight Calculator.

Try it here

Explore Ranking

Inspect an intentionally incomplete Ranking example and its required Scores input.

Exercise steps
  1. Change the direction and compare Top N with percentage selection.
  2. Inspect the missing Scores input. It requires a metric output explicitly typed as Ranking.
Schedule TriggerUniverseRanking
Graph preview — a diagram of the example

Select from scored assets

Ranking needs both an Asset Universe and a compatible Scores ranking input; it does not calculate the scores itself. For example, imagine three candidate assets with scores 0.9, 0.6, and no score. Set Direction to Higher is better, Selection to Top N, Count to 2, and Null policy to Exclude. The two scored assets are selected, in score order, while the unscored asset is excluded. This is an illustrative input, not a promise that a specific metric emits those values.

Switching to Lower is better reverses the preferred score direction. A Bottom N or percentage selection asks a different question and may change the asset count. Inspect the Selected universe before Weight Calculator; if it is empty, a later target-weight or rebalance stage cannot act as though two assets were selected.

Common problems

Scores must correspond to the connected universe. Review ascending or descending direction and selection limits.

Next steps

Review the generated Parameters, Outcomes, and Data Ports on this page, then open the related guides for the complete workflow.

Node facts

These facts come from the current Flow Editor node catalog.

Node type
Ranking
Activation role
No activation role
Category
Portfolio
Availability
Portfolio only
Modes
Portfolio
Required plan
None
Behavior
Transforms a value
Control inputs
0
Output data types
ranking, asset Universe

Parameters

NameInput typeRequirementDefaultOptions and constraints
DirectionSelection listRequireddescendingOptions: Higher is better, Lower is better
SelectionSelection listRequiredtopNOptions: Top N, Bottom N, Top percent, Bottom percent, All
CountNumberOptional when shown20Minimum: 1; Shown when Selection is one of topN, bottomN
PercentNumberOptional when shown10Minimum: 1; Maximum: 100; Shown when Selection is one of topPercent, bottomPercent
Null policySelection listRequiredexcludeOptions: Exclude, Bottom

Primary parameters

  • Direction
  • Selection
  • Count
  • Percent

Outcomes

None

Data inputs

  • Universeasset Universe · Required
  • Scoresranking · Required

Data outputs

  • Rankedranking
  • Selectedasset Universe

Related documentation

  • Screen FilterFilters a Portfolio universe with supported liquidity or predicate rules.
  • Composite ScoreCombines several rankings into one composite ranking.
  • Weight CalculatorCalculates target weights for a connected asset universe.

On this page

1 / 5
  1. When to use
  2. Example
  3. Select from scored assets
  4. Common problems
  5. Next steps

Practical guidance for strategies, historical simulations and metric research in Screebits.

Responsible useGlossary