thanks interesting point.obviously make sense but imagine me suggesting this on AB forumI have recently switched from Amibroker to Realtest, partly because of the problem you have pointed out.
Realtest allows you to specify the maximum number of setups that can be considered for entry on any one day so if one packet is above the entry limit it will not be replaced by another with a lower position rank.
The switch is relatively easy, RT is well documented and there is a helpful user forum. The developer is very receptive to suggested amendments, a contrast to AB where the developer is openly hostile.thanks interesting point.obviously make sense but imagine me suggesting this on AB forum
This realtest gets more and more interesting; how hard was it to switch AB to RT, and how easy was it to do the equivalent of AB Explore? If I may ask @elbee ?
Hey Frog,AB help required:
In real life, some shooting start buys are missed as my:
last close+3% (for example) buy values at open are overshot;
I would like to model that in backtests to ensure backtests are as near real results as possible:
so a Buy if O<ref(C,-1)*1.03
I can do that but in cases like that we want to ensure this buy is missed not just replaced by the next one based on the positionscore
so need to reduce on that day the total number of buys by one
And obviously this should not interfere with explore results;
If someone has already coded this , I would be grateful, otherwise i will do the yard yakka...
And share with you on demand
yes exactly what I have in mind, but this is virgin territory as I have never done dynamic check of open positions, etc and not sure of backtest engine behaviourHey Frog,
Not sure if you're chasing the exact AFL code or general approach. Think you have a level of familiarity with AFL so I will describe a general approach you might find helpful. If you want some AFL let me know and will be happy to post up some general code for you to mess with. But here is how I'd do it.
Assuming your system using a fixed number of positions (e.g., 20) the first step is to determine the current number of open positions you have. There's a few ways to do this in AB but personally I do that with the custom backtest. Once you pull the number of open positions I'd define a variable POS_TO_TAKE as initially being your max open position - number of open positions. At this point I would reduce POS_TO_TAKE by 1 when you encounter the condition Open > ref(c,-1)*1.03. I'd use the POS_TO_TAKE in a loop to control the number of buys you take. When POS_TO_TAKE is reduced by 1 it would essentially simulate a missed trade, which what I think you're trying to do. You'll have to run this as an overall loop so POS_TO_TAKE is reset for each day (bar).
Hope this makes sense. Good luck
just need to be able to focus, between sorting some components for arduino, testing AB, checing RealTest and doing the daily explore and system homework/Tax return...yes exactly what I have in mind, but this is virgin territory as I have never done dynamic check of open positions, etc and not sure of backtest engine behaviour
It’s pretty straightforward—dynamically determining the number of open positions is a very commonly asked question so search the AB forum (plenty of posts about it there) or just google it.yes exactly what I have in mind, but this is virgin territory as I have never done dynamic check of open positions, etc and not sure of backtest engine behaviour
was actually brilliant indeed for the systems but today was a step back:lost today, VERY good previous 2 sessions I am doing the tally@qldfrog I'm expecting to see a good week from your systems. Your fingers should be flying across the abacus tonight.
Forget "the Reset", the conspiracies and allow yourself to revel in the satisfaction that market success brings. We have to take every opportunity to revel because the market doesn't give us too many. Don't disappoint me.
was actually brilliant indeed for the systems but today was a step back:lost today, VERY good previous 2 sessions I am doing the tally
Jigsaw results:@qldfrog I'm expecting to see a good week from your systems. Your fingers should be flying across the abacus tonight.
Forget "the Reset", the conspiracies and allow yourself to revel in the satisfaction that market success brings. We have to take every opportunity to revel because the market doesn't give us too many. Don't disappoint me.
I hope I did not disappoint you @peter2 , not stellar results@qldfrog I'm expecting to see a good week from your systems. Your fingers should be flying across the abacus tonight.
Forget "the Reset", the conspiracies and allow yourself to revel in the satisfaction that market success brings. We have to take every opportunity to revel because the market doesn't give us too many. Don't disappoint me.
Thanks PeterArgh. Yes, I'm disappointed to read the latest update. I fully support your trading efforts and because their yours, you. I respect all investors and traders who work diligently in this business. It tough emotionally. We learn so much about ourselves as we hit our personal boundaries and fall victim to our personal biases.
I suspect that there's a few details that have escaped your notice or that you don't understand when back-testing and then implementing your systems. I can't give you an example because I don't know your systems. It's just an impression I get when reading your updates. It's like hearing a 8 cylinder engine running on 6. Something needs a tune up.
A theoretical example, it could be that your entries are late into the current price swing. This will be disastrous when trading micro cap price rallies in daily charts. I've thought that many of @Skate's entries were a little late into the trend but the weekly charts seem to offer more protection. Daily charts don't provide the same protection. eg AJX an entry higher than 0.073 is too late. With the close at 0.079 your trade should still be profitable. Sure, it's lost some open profit but your system back test should give you the confidence that this is OK and across a larger batch of trades your trade mgt earns more with the current settings.
Your last post indicates that you've got much larger concerns than your trading business. They may be having a negative impact on the discretionary aspect of your systems. eg turning them on/off, increasing/decreasing position sizes.
I guess you would know but this is handy to see those sneaky signals Tools>Bar Replay.I found one issue this week: some of my buys disappear on the next day explore..usually a sign of look forward code issue
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?