- Joined
- 28 December 2013
- Posts
- 6,392
- Reactions
- 24,319
Let's talk about opportunities
Value investing is a timing-related issue. What looks good one week can be a "terrible buy" the next. Remembering, this statement works both ways.
There is never a good time to start trading
Luck & timing plays a significant role in the performance of any portfolio
Opportunities
The COVID-19 flash crash gave me the perfect opportunity to take advantage of what was being offered. Opportunities like these don't come around all that often
There are plenty of opportunities
At any given time, there are plenty of opportunities in the share market as there are some excellent quality companies that are growing and out performing their competitors right now & the trick is finding them.
On another line of thought.
Has anyone converted a system from daily to weekly and what was the impact on CAR/MDD? I they would go down and up respectively but keen to hear anyone's experiences with that.
Is there a way to highlight , bold and underline that post.i remember reading about this way of testing systems consistency from @Lone Wolf months and months ago,and could not find it back and here it pops up again.Credit to the wolf and also @othmana86 .Hey man
Are you using position score as part of your code if you are or planning to then that isn't the best method.
i used a different method which was posted by @LoneWolf which works really well. Have it as part of your buy method. Just be very careful, make sure you take it out of your production code. made the mistake many times and had a few WTF is going on moments.
step = Optimize( "step", 1, 1, 1000, 1 );
Buy = cond1 AND Random() >= 0.20
I found the best way to differentiate between strategies is to plot CAR v MDD as below. CAR is X and MDD is Y. Green strategy 1 blue strategy 2.View attachment 121441
On this topic, it's worth repeating the advice @MovingAverage threw in:Is there a way to highlight , bold and underline that post.i remember reading about this way of testing systems consistency from @Lone Wolf months and months ago,and could not find it back and here it pops up again.Credit to the wolf and also @othmana86 .
This is a gem of a code snippet ??
That is my prefered way of doing monte in AB. Simply export the optimization results into Excel and you can do some great visual/charting analysis of your systems performance. This is much better than doing a single run. Although I'd suggest you push the 1000 value to much higher to get a better perspective. Only thing I'd add is that you're better to use mtRandom() over the regular Random() function. Be very careful about selecting the random comparison value (you use 0.2), choose the wrong value and the number of trades you take will have an adverse impact on your system.
peter2 said:
The large caps (LC) move the index and it's going to be very important to buy these at the earliest opportunity. I will start the large cap portfolio (5 positions) soon. It'll be a low activity portfolio and I'll post actions and progress in this thread. The main aim for the large cap portfolio is to earn more than a term deposit (TD) + tax. This is not a very high standard but I don't want to leave the money at the bank earning next to nothing when I have the skill to earn a little more.
Be very wary of some of these sites as apart from professionals like Radge they will send you broke.
Look up @Skate, @peter2, @tech/a in no particular order, actually just about anyone on here. You will learn a lot more but it may not be as pretty or appealing and you will have to do the hard yards but it will save losing money and confidence.
If I may
instead of trying a period 1992 to present, work on a recent year;
In 1992, was there many qant around?, fast trading? were Central bank covering your asses?
what I mean is you try to compare the performance of a ferrari in 2020 against the speed of a roman charriot in a mud track in 10BC..
totally irrelevant IMHO;
I would dare saying testing anything before 2006 and expecting a relevance in 2021 is a folly;
Anyway:
then try to run and compare with 2011 as per Monsieur Skate; the 2019 crash?
how does your system behave and handle the crash then the recovery ?
what about the yoyo period we have had since nov 2020 to now basically?
We are REALLY lucky to have many types of markets within the last 2 y..use these to your advantage
PS I noticed you have a 42% exposure during some of the longest bull market in history,
if not during that given period, when would your system get in ? A bad sign IMHO
also: std error: 1986636?????
what does the MC show?
I fundamentally disagree. The more data you have to run a back test, the more statistically significant the results will be.This post seemingly was overlooked. It really should not have been. It is central to the issue of backtesting mechanical based systems.
The basic premise that seems to be predominating is; the more information I have as a trader and use in my backtest, the more (statistically) certain I can be of my proposed system.
The (statistical) confidence level increases (however) in a non-linear proportion to the number of observations (n) and which results in an improved confidence level, as the square root of (n).
The issue that Monsieur Frog has identified is (and why this is the case) that the 'market's' distributions are non-symmetric, particularly in the ones that we are primarily interested in: market dislocations (lower) or (black swan) events. Looking at 1987, 2019, 2020 will provide you with far more relevant information than 1992 - 2021 inclusive.
I mean no disrespect when I say this, but I don't agree with the generalized proposition that old data (pre 1992 as suggested by frog) or that '87, '19 and '20 will be more relevant that 1992 - 2021. What is important first and foremost is that you have a statistically relevant number of trades in your backtest--in other words your sample size in statistics parlance. To suggest that you need to test over a certain time period without regard to the system characteristics (e.g., hold time, trade frequency etc) is naïve at best. For example, for a short hold time system such as a swing system you may get a statistically relevant number of trades within a six month period, but in contrast a long hold system may require a backtest period of 5 years to get a statistically relevant number of trades. What specific period you backtest over is irrelevant to a degree--what is critical is that post backtesting (optimization) the systems performance on out of sample data is carefully reviewed. So by all means backtest your system on pre '92 data but make sure you forward test (not optimizing) on data post '92 to see if it consistently performs to your requirements. This should of course include forward testing on out of sample data that represents a range of market conditions, pullback, sideways and heading north. Also, (and I'm probably misunderstanding your point) but the z-score / t-score is the common measure of statistical confidence and there is nothing non-linear about them.This post seemingly was overlooked. It really should not have been. It is central to the issue of backtesting mechanical based systems.
The basic premise that seems to be predominating is; the more information I have as a trader and use in my backtest, the more (statistically) certain I can be of my proposed system.
The (statistical) confidence level increases (however) in a non-linear proportion to the number of observations (n) and which results in an improved confidence level, as the square root of (n).
The issue that Monsieur Frog has identified is (and why this is the case) that the 'market's' distributions are non-symmetric, particularly in the ones that we are primarily interested in: market dislocations (lower) or (black swan) events. Looking at 1987, 2019, 2020 will provide you with far more relevant information than 1992 - 2021 inclusive.
jog on
duc
With my english as a foreign language, i might have been misunderstood, but i preach the opposite: in clear words:I mean no disrespect when I say this, but I don't agree with the generalized proposition that old data (pre 1992 as suggested by frog) or that '87, '19 and '20 will be more relevant that 1992 - 2021. What is important first and foremost is that you have a statistically relevant number of trades in your backtest--in other words your sample size in statistics parlance. To suggest that you need to test over a certain time period without regard to the system characteristics (e.g., hold time, trade frequency etc) is naïve at best. For example, for a short hold time system such as a swing system you may get a statistically relevant number of trades within a six month period, but in contrast a long hold system may require a backtest period of 5 years to get a statistically relevant number of trades. What specific period you backtest over is irrelevant to a degree--what is critical is that post backtesting (optimization) the systems performance on out of sample data is carefully reviewed. So by all means backtest your system on pre '92 data but make sure you forward test (not optimizing) on data post '92 to see if it consistently performs to your requirements. This should of course include forward testing on out of sample data that represents a range of market conditions, pullback, sideways and heading north. Also, (and I'm probably misunderstanding your point) but the z-score / t-score is the common measure of statistical confidence and there is nothing non-linear about them.
1. I fundamentally disagree. The more data you have to run a back test, the more statistically significant the results will be.
2. The less parameters a system has and the longer the historical data set, the bigger the trade sample size will be and therefore the more confidence you can have that your system will perform within the backtested results, over time.
3. I never understood the idea that people would try and backtest a system over a small historical data set of say, 1 year, to try and either reduce drawdown or get a positive return over a black swan or economic crisis event.
4. If your system trades all the markets the same and the longs and shorts the same, the bigger the trade sample size, the more statistically significant the results and the more certainty you have regarding the range of expected outcomes the system could face over time.
1. I mean no disrespect when I say this, but I don't agree with the generalized proposition that old data (pre 1992 as suggested by frog) or that '87, '19 and '20 will be more relevant that 1992 - 2021.
2. What is important first and foremost is that you have a statistically relevant number of trades in your backtest--in other words your sample size in statistics parlance.
3. To suggest that you need to test over a certain time period without regard to the system characteristics (e.g., hold time, trade frequency etc) is naïve at best.
4. For example, for a short hold time system such as a swing system you may get a statistically relevant number of trades within a six month period, but in contrast a long hold system may require a backtest period of 5 years to get a statistically relevant number of trades.
5. What specific period you backtest over is irrelevant to a degree--what is critical is that post backtesting (optimization) the systems performance on out of sample data is carefully reviewed. So by all means backtest your system on pre '92 data but make sure you forward test (not optimizing) on data post '92 to see if it consistently performs to your requirements.
6. This should of course include forward testing on out of sample data that represents a range of market conditions, pullback, sideways and heading north. Also, (and I'm probably misunderstanding your point) but the z-score / t-score is the common measure of statistical confidence and there is nothing non-linear about them.
I'm not suggesting more data is better--I'm suggesting that a statistically relevant amount of data be used. If you used more data than is statistically relevant then no adverse influence will result other than allowing you to have a higher level of confidence in your results--there is no down side to using more data than is statistically relevant. However, use a sample size that is not statistically relevant then you must would apply a low level of confidence in your results. Your reference to monthly systems is very apt here--I said on this forum before that I abandoned my monthly system because I just simply could not have any faith in the backtesting results--could not get a statistically relevant result even over 20 years so very low confidence. The key is understanding the statistical confidence you have in your sample size and then applying the appropriate level of error to your results. I appreciate the real world analogies, but system trading is nothing more than applied statistics. Stock market price data is nothing more than discrete time series data and statistical analysis is a well established form analysis for such data. Anyway, each to their own and whatever works for everyone is good--just sharing my thoughts.With my english as a foreign language, i might have been misunderstood, but i preach the opposite: in clear words:
Testing on old data, and by old i mean anything pre GFC is irrelevant.
I disagree with your idea of the more data the better: this would be true in a static environment, but the market is not static, forever changing and i am talking here about the mechanics, the mental response of traders and qants.
Would you be happy to analyse the average speed of a butterfly and take into account its chrysalis and caterpillar stage to have more data?
I want to follow mr Skate animal analogies?
If you use a monthly system, you have no better choice i agree than spanning years and years..good luck for it to be relevant.
Hope it clarifies my point of view..which is just that, and never pretented to be a truth
The only constant in the market is the change
Opinions & differing points of view
The recent exchanges (between differing points of view) in this thread demonstrate why the "Dump it here" thread is different to most other threads as it allows every member the right to express their views on a subject or topic respectfully.
Opinions are welcomed in the 'Dump it here' thread
It's a perfect segue to remind others that we all enjoy reading differing points of view because that's how we learn. "Refrain" is sometimes advisable because we're all "wordsmiths to a point" & challenging poster serves no purpose, it's much like masturbating in public, it may feel good to you, but it looks disgusting to everyone else.
Express your views
Whether your view is right or wrong isn't important, what's more important, this thread gives you the ability to express your views without being ridiculed or challenged. Every member enjoys a different level of experience & expertise. Posting an alternative view is the "heart & soul" of this thread as displayed in the last series of posts. I'm just saying, without self-moderation, the tone can quickly escalate.
Skate.
2. I disagree. What is important is that your system can hold up to the infrequent dislocations that blow you up. Now some of that risk will be in how you actually trade (Futures, Options, Stocks, CFDs, etc.) and the leverage you have in the system. That is not a function of the number of observations in total that you h
Hang on a minute--I was referring about a statistically relevant sample size. What you are talking about is something very different, unrelated and not relevant to my point. In fact your response is confirming one of my very points in which I said it is important to do out of sample testing across a range of market conditions--which as you point out MUST include infrequent dislocations that blow you up.
No my general point is not that more data is relevant--like I said, a statistically relevant amount of data is what is need. They are two very different things and should not be confused. It may seem like one and the same, but trust me in the world of statistics they are chalk and cheese.Your general point is that more data is better than less data. I am saying that that is simply not the case. We agree that specific samples of data are required.
jog on
duc
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?