| stevehopwoodforex.com https://www.stevehopwoodforex.com/phpBB3/ Print view |
|
| Peaky on Steroids https://www.stevehopwoodforex.com/phpBB3/viewtopic.php?t=5204 |
Page 10 of 97 |
| Author: | SteveHopwood [ Sat Jul 01, 2017 10:03 pm ] |
| Post subject: | Peaky on Steroids |
Completely spot on. That is why there is only one MarketDistancePips inputs instead of one per time frame. By the by folks, my code for calculating the number of pairs with open trades is correct, but the call to it is in the wrong place. I shall post a fix in time for the markets opening after the weekend. |
|
| Author: | TraderJoeForex [ Sat Jul 01, 2017 10:22 pm ] |
| Post subject: | Peaky on Steroids |
Doh! Ok that's my free pass used up for this year. For some reason I thought it was one per time frame. Of course you thought of this first! Thanks Steve |
|
| Author: | SteveHopwood [ Sun Jul 02, 2017 9:58 am ] |
| Post subject: | Peaky on Steroids |
V 1g is in post 1. I have moved the maximum pairs allowed filter to where it will do some good. Also, Gary just pm'd me with suggestions to help cut out the 'unknown ticket' errors that crop up. For those of you who like to go under the bonnet, do a search for "Note to coders about hedging." This will take you to the explanatory comment about hedging. Underneath that and before the two blocks of code that set up the trade, insert this: Code: Select all The other changes are in four code blocks, two each in these two functions:
Code: Select all The block will look like this: Code: Select all |
|
| Author: | SteveHopwood [ Sun Jul 02, 2017 10:16 am ] |
| Post subject: | Peaky on Steroids |
I just realised that those four cc++; instructions in the trade closure blocks are the cause of the 'unknown ticket' errors. They are necessary when iterating through all the trades on the platform because otherwise the next trade in the list would become the current one, and so be missed when cc is decremented. This is not the case with FifoTickets[] which is an array of ticket numbers that are not deleted at the time the trade is closed - this happens at the start of CountOpenTrades(). It does no harm to leave Gary's extra code in but cc++ definitely has to go. The block will look like this: Code: Select all if (!BetterOrderSelect(FifoTicket[cc], SELECT_BY_TICKET, MODE_TRADES) ) continue; It will fail if the order closure return receipt has not arrived back on the platform and so order is still in the platform's memory even though it is closed. There is a time delay in between something that we see happen on the platform and this change being reflected in its memory - the reason for so many of the safety features in my single-pair EA's. |
|
| Author: | SteveHopwood [ Sun Jul 02, 2017 2:18 pm ] |
| Post subject: | Peaky on Steroids |
Here is a clever spot by odrisb, sent to me in a PM: Here is the code as it stands: Code: Select all Code: Select all ----------------------------------------------------------- I have moved all Peaky threads to their own forum in the Automation section. |
|
| Author: | Zool [ Sun Jul 02, 2017 5:50 pm ] |
| Post subject: | Peaky on Steroids |
Well last week on M1 was not a certain % of the losers was closed out at loss, but all of them, since the price haven't retraced for such a long time that the bottom sixths line was crawled upward constantly, and closed them out at a minor retracement while there were multiple recovery stop orders in place. I agree that M1 can make the biggest gains in account balance, but this time all the profit was eaten with those closed out losers. Steve: when the close trade on opposite signal is triggered and the trade is closed, PoS will not remove the recovery stop orders placed on that timeframe. Can you make it to delete the pending orders too, when the opposite signal close happens? EDIT: attached a screenshot of one of my closed-on-opposite-signal M1 trades. It's on M5 because on M1 tf you cannot see the whole trade on 1 screen. The second sell was the glitch happened, when the recovery order placement was not working, and when finally it was fixed somehow PoS moved that order following the trade line as it was a normal order and later haven't placed additional recovery orders. The sell stops marked with pink rectangles are the remaining M1 recovery trades, after the original trade was closed. |
|
| Author: | SteveHopwood [ Sun Jul 02, 2017 6:50 pm ] |
| Post subject: | Peaky on Steroids |
Will do. It is what I intended, so something got lost in translation. |
|
| Author: | SteveHopwood [ Sun Jul 02, 2017 8:28 pm ] |
| Post subject: | Peaky on Steroids |
I have uploaded 1g again to post 1, with the change that Zool highlighted. Go to line 1290 and you will see this snippet: Code: Select all |
|
| Author: | TraderJoeForex [ Mon Jul 03, 2017 11:36 am ] |
| Post subject: | Peaky on Steroids |
I didn't have any M1 losers last week but this morning my pairs have caught up! The 4 in recovery have now closed for loss with an opposite M1 signal. This is going to be an issue for the lower timeframes. Steve would it be possible to have an option for PoS to ignore opposite signals for any pairs that are in recovery? Then once in recovery it will either be a basket close or up to the user to pull the plug on those trades. Using USDCAD as an example. Price is at the bottom of every chart from M5 up to H4 (in fact H4 looks like it's forming level 3 right now). This should mean there will be a decent bounce up very soon and if my M1 long trade stayed in recovery it would most likely come good this week. PoS is entering long on M5, M15, M30 so it may not make sense for M1 long recovery to be cut short by close on opposite? |
|
| Author: | SteveHopwood [ Mon Jul 03, 2017 12:12 pm ] |
| Post subject: | Peaky on Steroids |
This is a problem of bad program logic that I foresaw when I planned the code - then forgot. |
|
| All times are UTC | Page 10 of 97 |
|
Powered by phpBB® Forum Software © phpBB Limited |
|