Add data collection pipeline for DCF analysis #18
+339
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
New src/dcf_inputs.py collects and derives the inputs a future DCF (discounted cash flow) model will need, from the same cached raw data metrics_engine.py already uses — no new network calls. This is intentionally data collection only, not the DCF calculation itself (projection, terminal value, present value), which stays out of scope for a separate future issue. - compute_dcf_inputs(): capital structure (total debt, net debt, cost of debt), beta, effective tax rate (prefers yfinance's own "Tax Rate For Calcs" when present, falls back to tax provision / pretax income), and latest free cash flow (uses yfinance's own "Free Cash Flow" row when present, falls back to operating cash flow + capital expenditure) - build_dcf_inputs_table(): one row per company for a whole industry - build_fcf_trend(): chronological (oldest-first) multi-year free cash flow table per company, for future FCF projection config.py: new FIELD_ALIASES entries for cash flow statement fields, verified against real cached yfinance payloads rather than guessed. Also added DCF_MARKET_ASSUMPTIONS documenting the two inputs yfinance can't provide at all (risk-free rate, equity risk premium) and that need to be set manually. Verified compute_dcf_inputs() and build_fcf_trend() manually against real cached data (Mowi ASA) before writing tests, to confirm the numbers were sensible, not just that the code runs. Full suite: 50 passed, 89% coverage on src/. Closes #1
bendikto
added
Enhancement
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New src/dcf_inputs.py collects and derives the inputs a future DCF (discounted cash flow) model will need, from the same cached raw data metrics_engine.py already uses — no new network calls. This is intentionally data collection only, not the DCF calculation itself (projection, terminal value, present value), which stays out of scope for a separate future issue.
config.py: new FIELD_ALIASES entries for cash flow statement fields, verified against real cached yfinance payloads rather than guessed. Also added DCF_MARKET_ASSUMPTIONS documenting the two inputs yfinance can't provide at all (risk-free rate, equity risk premium) and that need to be set manually.
Verified compute_dcf_inputs() and build_fcf_trend() manually against real cached data (Mowi ASA) before writing tests, to confirm the numbers were sensible, not just that the code runs.
Full suite: 50 passed, 89% coverage on src/.
Closes #1