bayesline.api.equity.XSR_COLUMN_SETTINGS_MENU#
- bayesline.api.equity.XSR_COLUMN_SETTINGS_MENU = ReportColumnSettingsMenu(metrics={'exposure': 'book', 'beta': 'book', 'nav': 'book', 'contribution': 'contribution', 'relative_contribution': 'contribution', 'volatility': 'per_unit', 'correlation': 'per_unit', 'exposure_raw': 'per_unit', 'relative_exposure': 'per_unit'}, choices={'leg': ['portfolio', 'benchmark', 'active'], 'reference': ['own', 'root'], 'denominator': ['none', 'net', 'gross'], 'name_contribution_basis': ['Grinold-Kahn', 'Menchero-Davis']}, defaults={'book': {'leg': 'portfolio', 'reference': 'root', 'denominator': 'net'}, 'contribution': {'leg': 'portfolio', 'reference': 'root', 'denominator': 'net', 'name_contribution_basis': 'Menchero-Davis'}, 'per_unit': {'leg': 'portfolio', 'reference': 'root'}}, presets={})#
What a report’s columns may be: metrics, choices, defaults and presets.
A column is validated against the menu of the report it is asked of, and
resolve()fills itsNonechoices from the menu’s defaults. The precedence a column resolves by is its explicit field, then a preset, then the defaults a deployment lays over the report’s, then the report’s, then the variant’s. A bare name invalue_colsis a preset where the menu has one of that name, and a metric otherwise: a preset wins over a metric of the same name, which stays reachable as a pair, and nothing stops a preset taking a metric’s name. A menu with no metrics offers no column.