Corn closed with a loss and then opened a new position according to the autoroll thing.
Palladium closed with a profit and then did the same thing.
Best regards, David
Edit: I can add that neither shows in PRT, only in IG.
Soybeans just opened a further long position (the third in total) @ 1,023. This execution is confirmed in both Live and Demo IG Spreadbet.
Hi Guys,
I didn’t get a further signal for Soybean but the algo has bought 2 Euro Stoxx contracts at 3319.
In my opinion the Soybean position is a little bit to high for the default 10K account size. You have now a risk of 60 Euro per point. I have to admit that all grains are to aggressiv if further positions were accumulated.
I will reduce the default algos to the half of the position size and please keep an eye on Soybeans.
Best, Reiner
@Manel No Soyabeans trade executed for me again today. We need to bottom this out between us as to what is the difference between yours and mine as we are both Spreadbetting?
You mentioned you were trading Soyabeans DFB Index? How you know its an Index? Might you be trading Soy bean (no A) Index?
Anyway seeing is believing so here’s my System and proof of no Rejection of Soyabeans DFB.
Cheers
GraHal
update Pathfinder swing positions, grains recover, indices are trendles
Currently Corn and Wheat have no algo monitoring because of the future rollover. I have closed both positions manually. The algo would have closed both positions tonight.
ArnoParticipant
Average
I confirm in live (CFD IG account) & demo (CFD PRT account), Soybeans 60 contracts long :
– Feb 22 at 2am > 20 contracts long @1035
– Feb 24 at 2am > 20 contracts long @1021
– Feb 28 at 2am > 20 contracts long @1023
Guys,
as mentioned I have reduced the position size for Corn and Wheat and have started the attached robots with the related May futures.
Best, Reiner
@Arno:
as I mentioned before the position is to high for an 10k account and I’ll also reduce the size to half for the next round. You have a nice profit – keep an eye on it :-).
Hi Grahal – sorry, I didn’t mean index, the Soyabeans DFB I have run the strategy on is exactly the same as yours shown above in the chart. I can’t see an obvious reason as to what would cause the difference as we’re both on exactly the same live platform, it’s really strange. The obvious q’s like cancellations/rejections, min/max position in the code is set correctly, max orders per day etc seem to have been addressed. I’ve had a look at the code again as well but can’t spot anything there either – assuming you have the positionsize set to 15 (minimum) and maxpositionsizelong = max (15,….) and Once February2=1
The mystery continues…..
Reiner – quick question. Does the maxcandleslongwithprofit count take into account the candle of the day the position is taken ? This means in the above trade of the first Soyabean position taken on Feb 22, it would close it on Wed night/Thurs morning @ 1/2am (6 full candles) if still in profit ?
Also I presume it counts the Sunday daily candle (if there is one for the instrument, even if it’s usually only an hour long) ?
Many thanks.
@manel
Max candle check refers always to the opening of the last position, you can check easily when you GRAPH numberCandles
@Manel here’s the code (you mention above) that I’m using …
positionSize = 20
maxPositionSizeLong = MAX(60, abs(round(maxRisk / (close * stopLossLong / 100) / PointValue) * pipsize))
ONCE January2 = 1
ONCE February1 = 1
ONCE February2 = 1
ONCE March1 = 0
I have my Platform timezone set to GMT (see attached) … I assume you do also?
Are you direct with IG (not via PRT?)
Thanks
GraHal
@ GraHal – I have exactly the same settings and code as you. Yes, I have a direct account with IG. Running out of ideas here…..really bizarre.
I think it may be time to hand this over to the support desk and they have to investigate what’s going on. It makes no sense as the code execution should be a binary outcome – it should work for all or no one. It could be because not all accounts are run on the same servers (which I know is the case) and somehow something didn’t work on one of them that yours was on. We’re just speculating now though.
We should keep an eye on occurrences of this though and people should highlight on here when this happens again as the more frequent the issue the more serious they are likely to take it.
