- Joined
- 8 June 2008
- Posts
- 13,223
- Reactions
- 19,513
while still bringing in funds to start the system, today was opening day:
I purchased the following:
BRG : 324 @15.41
JIN 476 @ 10.53105
MWY 1388 @ 3.61
Is also added
IFM 2608 @ 1.495
to fill last week Buy signal.
last week was up to 1.45 but I find it ok to populate today at this price
As I see it, it is a race against time to have enough positive positions before the next crash
Another last purchase triggered last week might be processed this week if the price is decent
Thanks for the feedback Skate: Is it the strategy you actually run ?..I know you have an hybrid approach and so leverage multiple systems but, is the code you backtest above something you actually run?qldfrog, I'm sure there would be a great deal of differences between our CAM Strategy. I'll post my CAM strategy results & buy signals for comparison.
Thanks Skate, I will get back to the above soon;
Today I completed my entries to "initiate the system":
I purchase more shares to align the portfolio to a backtest started on the 8/02/2019
AMI 5681 @0.88 $5,009.28
CNU 990 @5.05 $5009.5
NHC 1204 @ 4.15 $5006.6
cost above reflecting $10 brokerage
The start of the system highlighted an interesting problem
When you start, and assuming you have an edge in your position score:
you can either:
1)just purchase the "new" buys only...discard last week ones just get new
or
2) fill your 20 positions allocation on day one including previous period buy recommendations.
But then you will probably buy at less than optimum time based on your system concept:
either buy too high, or buying codes which are already loosers
or would be so low with their position score that they would never be actually considered on an ongoing system with only a few free postions at a time
How to you solve this?
Whatever the method, I feel you end up a looser and with a less than optimum results until the effect of the initial positioning lessen.
I opted for a half baked solution:
purchase the recommendation of the last 3 bars, at today's price..
From the start, my real portfolio is already behind a backtest version by $1k..the extra profit ownership on the last 3 weeks would have gathered, but we have at least 34% of funds invested.And will only use new recommendation from now on
Thanks for the feedback Skate: Is it the strategy you actually run ?..I know you have an hybrid approach and so leverage multiple systems but, is the code you backtest above something you actually run?
Reason I ask is that your entry into BRG is quite "lucky": entry on a day where the share jump 21pc, want to make sure this is not some test code with maybe a future looking part or similar.
Indeed I expect much difference between your code and my current version as I have changed the initial base code you provided a LOT to suit my style (aka less DD ideally, etc)
I understand if you feel answering is providing too much information.
Thanks again
Well spotted, it took us a while to discover initially but we noticed this a while back and used the =Ref(xxx, -1) as a safe way ahead.Not sure if anyone is using a derivative of the code from the amibroker forum
https://forum.amibroker.com/t/s-c-magazine-jan-2018-traders-tips/3875/5
But their version of the cam indicator is future looking.
***************************
PositionScore = 100 * RSI(scoreLookBackPeriod);
**************************
It uses todays open prices, but then uses positionscore RSI calculated using todays close.
Having said that, when fixing it up, the indicator is one of the safest around.
Sell = Sell AND Status( "BarInRange" ) ;
I use "status(bar in range") to declutter my charts display,-> only show buy/sell on the range I do backtest (the range I specify) and so can zoom out and avoid having too many arrows displayed..more cosmetic and can also be a nuisance potentially: to each his ownwhat does the status("barinrange") do for you ?
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?