fundamental-ratios

name

fundamental-ratios

description

Use to look up the exact path or spelling of any Morningstar RATIO field on a QuantConnect/LEAN `Fundamental` object — everything under py`f.operation_ratios.*`cs`f.OperationRatios.*` (ROA, ROE, margins, turnover, growth), py`f.valuation_ratios.*`cs`f.ValuationRatios.*` (PE, PB, PS, EV multiples, yields), and py`f.earning_ratios.*`cs`f.EarningRatios.*` (EPS/DPS growth). Triggers — "path to PE ratio / book value per share / ROE / operating margin / dividend yield / revenue growth". For other field families start at the equity-fundamental-data skill.

Ratio fields — Fundamental data points

Full path from the snapshot f with the field's description — copy the path rather than guessing from English names; a wrong path wastes a backtest run. The path-reading rules and the index of all field-family skills are in the equity-fundamental-data skill.

Reading the paths

• A path ending in .[value 1M 2M 3M 6M 9M 12M] is a MultiPeriodField — append one period accessor to read the number. py.valuecs.Value is the most recent reported period; the 1M–12M tokens are py.one_month .two_months .three_months .six_months .nine_months .twelve_monthscs.OneMonth .TwoMonths .ThreeMonths .SixMonths .NineMonths .TwelveMonths respectively (trailing-twelve-month at 12M). e.g. pyf.financial_statements.income_statement.net_income.twelve_monthscsf.FinancialStatements.IncomeStatement.NetIncome.TwelveMonths. Forgetting the accessor is silent — the wrapper compares as truthy and numeric inequalities give nonsense.
• A path with no bracket is read directly. e.g. pyf.valuation_ratios.pe_ratiocsf.ValuationRatios.PERatio.
• The integer *_code fields under asset_classification compare against the named constants in the fundamental-classification skill.

Data points