Stop-Loss Research on Equity Timing and Momentum Crashes
Summary
This review summarizes three studies on stop-loss rules. The first applies a 10% loss threshold to broad U.S. equity exposure, shifting proceeds into long-term government bonds until the market recovers. The second compares fixed and trailing stops with buy-and-hold for the OMX Stockholm 30 over a historical sample, reporting better results for several tested stop levels. The third applies daily stops to a monthly long-short momentum portfolio formed from recent winners and losers, moving closed positions into Treasury bills until month-end. The review reports that this approach reduced severe momentum losses and improved average return, volatility, and Sharpe ratio in the cited sample.
These findings are historical and specific to the markets, periods, portfolio rules, and stop thresholds tested. They do not establish that stop losses will improve every strategy. Stop orders can exit positions during temporary price reversals, and actual results may depend on execution and transaction costs. The article emphasizes repeated, disciplined use, but choosing a threshold and handling re-entry remain important design decisions.
Key ideas
- The review describes a rule that shifts equity exposure to government bonds after a loss threshold and re-enters after recovery.
- It compares fixed and trailing stop rules with buy-and-hold on a Swedish equity index sample.
- A cited momentum study uses daily stops on a monthly long-short portfolio and holds Treasury bills after exits.
- The reported improvements are historical results tied to specific samples and portfolio construction choices.
- Stops may exit during temporary reversals, and execution costs and re-entry rules affect practical outcomes.
Tags
Full text
# Bayesian performance analysis example in pyfolio
# Bayesian performance analysis example in pyfolio
There are a few advanced analysis methods in pyfolio based on Bayesian statistics.
The main benefit of these methods is **uncertainty quantification**. All the traditional measures of performance, like the Sharpe ratio, are just single numbers. These estimates are noisy because they have been computed over a limited number of data points. So how much can you trust these numbers? You don't know because there is no sense of uncertainty. That is where Bayesian statistics helps as instead of single values, we are dealing with probability distributions that assign degrees of belief to all possible parameter values.
Lets create the Bayesian tear sheet. Under the hood this is running MCMC sampling in [PyMC3](http://pymc-devs.github.io/pymc3/) to estimate the posteriors which can take quite a while (that's the reason why we don't generate this by default in `create_full_tear_sheet`).
## Import pyfolio
```python
%matplotlib inline
import pyfolio as pf
```
## Fetch the daily returns for a stock
```python
stock_rets = pf.utils.get_symbol_rets('FB')
```
## Create Bayesian tear sheet
```python
out_of_sample = stock_rets.index[-40]
```
```python
pf.create_bayesian_tear_sheet(stock_rets, live_start_date=out_of_sample)
```
Lets go through these row by row:
* The first one is the Bayesian cone plot that is the result of a summer internship project of Sepideh Sadeghi here at Quantopian. It's similar to the cone plot you already saw in the tear sheet above but has two critical additions: (i) it takes uncertainty into account (i.e. a short backtest length will result in a wider cone), and (ii) it does not assume normality of returns but instead uses a [Student-T distribution](https://en.wikipedia.org/wiki/Student%27s_t-distribution) with heavier tails.
* The next row compares mean returns of the in-sample (backest) and out-of-sample or OOS (forward) period. As you can see, mean returns are not a single number but a (posterior) distribution that gives us an indication of how certain we can be in our estimates. The green distribution on the left side is much wider, representing our increased uncertainty due to having less OOS data. We can then calculate the difference between these two distributions as shown on the right side. The grey lines denote the 2.5% and 97.5% percentiles. Intuitively, if the right grey line is lower than 0 you can say that with probability > 97.5% the OOS mean returns are below what is suggested by the backtest. The model used here is called [BEST](http://www.indiana.edu/~kruschke/BEST/BEST.pdf) and was developed by John Kruschke.
* The next couple of rows follow the same pattern but are an estimate of annual volatility, Sharpe ratio and their respective differences.
* The 5th row shows the effect size or the difference of means normalized by the standard deviation and gives you a general sense how far apart the two distributions are. Intuitively, even if the means are significantly different, it may not be very meaningful if the standard deviation is huge amounting to a tiny difference of the two returns distributions.
* The 6th row shows predicted returns (based on the backtest) for tomorrow, and 5 days from now. The blue line indicates the probability of losing more than 5% of your portfolio value and can be interpeted as a Bayesian VaR estimate.
* The 7th row shows a Bayesian estimate of annual alpha and beta. In addition to uncertainty estimates, this model, like all above ones, assumes returns to be T-distributed which leads to more robust estimates than a standard linear regression would. The default benchmark is the S&P500. Alternatively, users may use the Fama-French model as a bunchmark by setting benchmark_rets="Fama-French".
* By default, stoch_vol=False because running the stochastic volatility model is computationally expensive.
* Only the most recent 400 days of returns are used when computing the stochastic volatility model. This is to minimize computational time.
## Running models directly
You can also run individual models. All models can be found in `pyfolio.bayesian` and run via the `run_model` function.
```python
help(pf.bayesian.run_model)
```
For example, to run a model that assumes returns to be normally distributed, you can call:
```python
# Run model that assumes returns to be T-distributed
trace = pf.bayesian.run_model('t', stock_rets)
```
The returned trace object can be directly inquired. For example might we ask what the probability of the Sharpe ratio being larger than 0 is by checking what percentage of posterior samples of the Sharpe ratio are > 0:
```python
# Check what frequency of samples from the sharpe posterior are above 0.
print('Probability of Sharpe ratio > 0 = {:3}%'.format((trace['sharpe'] > 0).mean() * 100))
```
But we can also interact with it like with any other `pymc3` trace:
```python
import pymc3 as pm
pm.traceplot(trace);
```
## Further reading
For more information on Bayesian statistics, check out these resources:
* [A blog post about the Bayesian models with Sepideh Sadeghi](http://blog.quantopian.com/bayesian-cone/)
* [My personal blog on Bayesian modeling](http://twiecki.github.io/)
* A talk I gave in Singapore on [Probabilistic Programming in Quantitative Finance]( https://www.youtube.com/watch?v=MeKucat_gw8)
* A series of IPython notebooks on [Bayesian Methods for Hackers](https://github.com/CamDavidsonPilon/Probabilistic-Programming-and-Bayesian-Methods-for-Hackers).

Shown in full with attribution under the source's licence. Licence: Apache-2.0
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.