andi21 Forum Activity | cTrader Community

andi21 said:

Or more easy: just remember the incoming index parameter in the calculate method and if this index changed then it is a new bar (it is late so this easier solution came a little later than my previous answer ;) ).

How we can save old index and comparing with new one? because as result of each tick both parameters in Calculate would be update and reffer to same index

You could do something like this:

public int lastCalculatedIdx = -1;  

public override void Calculate(int index)
        {
            bool gotANewIdxSoANewBar = index > lastCalculatedIdx;
            if (gotANewIdxSoANewBar)
            {
                  lastCalculatedIdx = index;
                  // Do some calculations
            }
        }

@andi21

andi21
06 Nov 2017, 18:11

Hi Panagiotis,

ah ok, thank you.

I am happy to see that this problem is now known and will be fixed in the future.

Best Regards,

andi21

@andi21

andi21
06 Nov 2017, 17:57

Hi Panagiotis,

thank you for the answer.

MarketSeries for the selected symbol are updated on scrolling on the chart while other MarketSeries for other symbols are not

But in my example i am using only one symbol for all marketseries and the chart-symbol is also the same. So only one symbol is used over all.

Best Regards,

andi21

@andi21

andi21
06 Nov 2017, 10:52

Dear Spotware,

could you look after the problem, please?

Best regards,

andi21

@andi21

andi21
31 Oct 2017, 13:48

I forgot to mention that if i am just showing / displaying a chart with the chart-timeframe set to m15, then there IS past data before 25.06.2017 21:00:00, so there IS past data available, but not loaded enough through .GetSeries().

@andi21

andi21
11 Aug 2017, 11:34

Hi,

i just thought, that i could also answer the question by myself and made a simple test-bot.

The answer to my quote (see above) is:

Yes, that is correct.

So the pips passed to ExecuteMarketOrder (slPips and tpPips) are calculated with the Symbol.Ask if a buy-Order is done and Symbol.Bid if a sell-Order is done (so "Default-Trade-Side" is used).

Best Regards,

andi21

@andi21

andi21
11 Aug 2017, 11:08

Hi Spotware,

thank you for the answers - now it is clear how it is working.

Can you also answer the question in the second point, please?

at the moment the sl set by ExecuteMarketOrder() would be currently triggered at "default trade side" so at Ask with a buy-position and at Bid with a sell-position and the same with tp - is that correct?

Best Regards,

andi21

@andi21

andi21
25 Jul 2017, 15:52

Dear Spotware,

have you reviewed this bug-case?

Thanks in advance.

Best regards,

andi21

@andi21

andi21
21 Jul 2017, 15:36

Hi Spotware,

thank you for your answer.

Yes i can and will do that.

But if this happens again, probably i will have lost money because of that problem, because my bots are not connected and thus cannot handle positions. Currently that is not that bad, because i am "only" forward-testing (although the statistics could be falsified which is not good, too). But the key is, that if disconnections occur in my opinion cAlgo should not stop trying to reconnect automatically, although if it takes some time, and not show the login dialog, because it thinks something changed etc. and the credentials has to be filled in again.

Best regards,

andi21

@andi21

andi21
18 Jul 2017, 19:29

Dear Spotware,

thank you for your answer.

With the new(est) version(s) of cAlgo that problem seems to be fixed now.

But if it should occur nonetheless, i will get back to you with further details.

Best Regards,

andi21

@andi21

andi21
13 Jul 2017, 15:29

Dear cTrader Team,

thank you for your reply.

I am not writing an email, because of the following reason and that others can see, that if such problems occur somebody could see what the source of the problem probably might be:

At the moment there is no need to further spend time for this subject, because i had also contact to my broker.

And after a few emails they sent me a reply in which they stated, that they asked you about that and they forwarded the answer to me. I do not have this answer anymore, but there were some points / possibilites like:

- marketRange exeeded

- connection issues / too slow tick-consumption, so that price on my vps from onTick was not in sync with the real current price

- same point as the one before, but regarding cpu consumptions (ticks are processed to slow and were not in sync anymore)

Because that sounded valid and possible to me i was ok with that.

Best Regards,

andi21

@andi21

andi21
07 Jun 2017, 16:34

Dear Spotware,

thank you for the investigation of the crashing problem. It is a pity that you could not reproduce the problem.

Regarding your question about my cBot: it happened with two completely different bots - also like you have seen in the error logs from event log - not always from same method origin / stack. These methods are really really simple - i looked after them after i found the event log entries, but there could not been an error because of simplicity and also because the crashes did not always came from same method, so it is non determinist.

But what i can say / found out so far is that during the last few days there were no crashes anymore. But i am also not running 6 cAlgo instances anymore, i tried to run only 4 instances and cpu usage is - for my needs - completely acceptable at about 80%.

I have also quitted some tasks in task scheduler like defrag, autochk and many more of tasks like these, because i wanted to narrow the problem and i saw that many tasks in task scheduler ran at the same time, so i thought it could be a problem.

The end of the story is that 4 instances are - currently - running fine in parallel and i don't know neither if the crashes are solved now nor if they are solved because of the cancelling of the tasks in task scheduler or because of running not 6 but "only" 4 instances.

It could be a problem of cAlgo if there are running too much instances, but it could also be a problem of the operating system, if that was the problem. But there is no need to investigate this further because of the satisfactorily solution with "only" running 4 instances in combination with disabling multiple task scheduler tasks.

So this is fine so far and i hope the problems do not occur anymore.

But what a problem is farther, is that the optimization does stop prematurely many times although there would be enough parameter combinations also for generic algorithm-mode.

That problem existed since i started to use cAlgo last year, so it is present since a long time and costs much time.

It would be a pleasure if you could take care of that problem, so that optimization can always run to the end (2500 runs) and we can be sure, that the generic algorithm has tried the most parameter combinations possible in this mode.

Thanks a lot in advance.

Best Regards,

andi21

@andi21

andi21
03 Jun 2017, 08:34

RE: RE: RE: RE:

andi21 said:

andi21 said:

andi21 said:

andi21 said:

Hi Spotware,

i have just send you two troubleshooting info. It also happened at two cAlgo.exe instances ironically at 1715 runs at both instances. But another cAlgo.exe instance is still running (the only one left from six instances which does not crash or stop prematurely...).

I really really hope that you can fix this, because this destroys so much time...

By the way: what is send when i used strg + alt + shift + t ?

Thanks in advance - i hope i can help you with this.

Best regards,

andi21

And just now the last one stopped prematurely at 2285 runs... It is so frustrating.

And one more info which could be helpful: this problem is NOT pc-specific - it happened on various VPS-PCs and on my other pcs also.

And one more info: at the time of writing my post here the last cAlgo.exe instance stopped like i said. Before this happened the remaining clock showed about 1d and x hours. And after i wrote my post and turned back to my pc the last run stopped. So the clock said / ensured that there WAS definitely more runs to do, but it broke / stopped suddenly.

Started another one - also stopped prematurely at only 1430 Runs... (i also sent the troubleshooting info).

@andi21

andi21
02 Jun 2017, 23:46

RE: RE: RE:

andi21 said:

andi21 said:

andi21 said:

Hi Spotware,

i have just send you two troubleshooting info. It also happened at two cAlgo.exe instances ironically at 1715 runs at both instances. But another cAlgo.exe instance is still running (the only one left from six instances which does not crash or stop prematurely...).

I really really hope that you can fix this, because this destroys so much time...

By the way: what is send when i used strg + alt + shift + t ?

Thanks in advance - i hope i can help you with this.

Best regards,

andi21

And just now the last one stopped prematurely at 2285 runs... It is so frustrating.

And one more info which could be helpful: this problem is NOT pc-specific - it happened on various VPS-PCs and on my other pcs also.

And one more info: at the time of writing my post here the last cAlgo.exe instance stopped like i said. Before this happened the remaining clock showed about 1d and x hours. And after i wrote my post and turned back to my pc the last run stopped. So the clock said / ensured that there WAS definitely more runs to do, but it broke / stopped suddenly.

@andi21

andi21
02 Jun 2017, 23:43

RE: RE:

andi21 said:

andi21 said:

Hi Spotware,

i have just send you two troubleshooting info. It also happened at two cAlgo.exe instances ironically at 1715 runs at both instances. But another cAlgo.exe instance is still running (the only one left from six instances which does not crash or stop prematurely...).

I really really hope that you can fix this, because this destroys so much time...

By the way: what is send when i used strg + alt + shift + t ?

Thanks in advance - i hope i can help you with this.

Best regards,

andi21

And just now the last one stopped prematurely at 2285 runs... It is so frustrating.

And one more info which could be helpful: this problem is NOT pc-specific - it happened on various VPS-PCs and on my other pcs also.

@andi21

andi21
02 Jun 2017, 22:50

RE:

andi21 said:

Hi Spotware,

i have just send you two troubleshooting info. It also happened at two cAlgo.exe instances ironically at 1715 runs at both instances. But another cAlgo.exe instance is still running (the only one left from six instances which does not crash or stop prematurely...).

I really really hope that you can fix this, because this destroys so much time...

By the way: what is send when i used strg + alt + shift + t ?

Thanks in advance - i hope i can help you with this.

Best regards,

andi21

And just now the last one stopped prematurely at 2285 runs... It is so frustrating.

@andi21

andi21
02 Jun 2017, 22:45

Hi Spotware,

i have just send you two troubleshooting info. It also happened at two cAlgo.exe instances ironically at 1715 runs at both instances. But another cAlgo.exe instance is still running (the only one left from six instances which does not crash or stop prematurely...).

I really really hope that you can fix this, because this destroys so much time...

By the way: what is send when i used strg + alt + shift + t ?

Thanks in advance - i hope i can help you with this.

Best regards,

andi21

@andi21

andi21
01 Jun 2017, 17:38

Hi Spotware,

ok, great - i will definitely do that the next time it happens.

@andi21

andi21
01 Jun 2017, 17:27

RE:

Spotware said:

Hi andi21,

Regarding the following case

"1. Why does cAlgo optimization stop too early sometimes (see also /forum/calgo-support/11573?page=2#12)? THIS should NOT happen, because it is nearly the same effect like if cAlgo crashes!"

Can you please send us troubleshooting information as soon as the optimizations stops? You can do this by pressing Ctrl+Shift+Alt+T in cTrader or cAlgo. This will send us the logs from your PC and we will be able to investigate further.

Hi Spotware,

thanks for your answer.

Yes, of course i will do that the next time it happens (shouldn't take too much time, because i have this problem since a long time and again and again).

Is it possible to leave an email-address, so that you can contact me after i send the logs or is it "only" a "public" send log?

Thanks in advance.

@andi21

Showing 21 to 40 of 97 results

cTrader Ltd offers through its group of companies the cTrader platform. The information on this website is for general informational purposes only and does not constitute financial or investment advice. cTrader does not solicit retail investors. Reliance on this information is at your own risk.