| / | Forum |
|
ququr
2006.05.30 20:47
This sounds like a server issue, but there's enough inconsistencies, I wonder if
anyone else has seen something like this. |
|
Terminal Service Client. How to Make Pocket PC a Big Brother's Friend The article describes the way of connecting to the remote PC with installed MT4 Client Terminal via a PDA. |
2824 |
Tatyana
2006.06.01 13:11
Please provide us with codes of these wrong EAs.
|
|
ququr
2006.06.01 20:23
First, I'd like to know how such an error is even possible. Pick any EA design.
Mine aren't that important. Can you design an EA that would place 20 orders in
4 minutes immediately closing them without designing them to do that on purpose?
What data is allowed to come off a server that is not refelected in the history?
Can the ask price be allowed to fluctuate so wildely that it would cause an EA
to fire, but the bid-line wouldn't reflect a price change? Or is ask ever allowed
to define the Close[0] for an open bar? Or how would those be closed? You can't
even get a 1-trade-per-bar EA to close that fast, or any crossover always in method
for that matter, as the closing should be accompanied by a sell. The point is there
is a lump of bad data, and I'm trying to understand if anyone else saw it, what
sort of bad data is possible, how to possibly trap for such errors, in general,
independant of the specific EAs that happened to detect the bad data this time.
There's at least one other report at sbfx of such a frenzy associated with data stream. ibfx has not responded to queries on their data during that period, which is typical. Demos don't count for much with them it seems. |
2824 |
Tatyana
2006.06.02 15:46
The matter is that we haven't ever faced such a problem by now. To reconstruct your situation, we would like to have the log (the "Journal" tab in the "Terminal" window) and the codes of those wrong EAs. Could you provide us with this? |