Topics
Replies
Elogos
01 Nov 2014, 20:36
RE:
Elogos said:
Might be do with the thread the form was created in.
I'll have a look when I get a bit of time.
Yep, it is created in the cTrader main thread and Show() isn't returning.
I have some developers notes somewhere from a Spotware developer on creating a new WPF Window. I'll see if I can dig them up somewhere.
@Elogos
Elogos
11 Oct 2014, 15:42
RE:
breakermind said:
Hello support
Is it possible to connect to the Servers without cTrader / cAlgo platform only with login and password to account
from C# (Visual Studio) and API?
Bye...
A few people have asked this already, a shell library of sorts, however they specifically said this would not happen some time ago.
It would be nice, however most brokers do have FIX offerings and there are plenty of c# libraries bought and free that can give you the connectivity for these FIX offerings.
@Elogos
Elogos
25 Sep 2014, 10:52
RE:
emeeder said:
I have seen places on the internet that sell price data. Does anyone know a good source?
It looks like we can use our own data now to backtest in Calgo using a .csv file.
Does anyone know if it works good and if it is fast? Is there tick data available anywhere? or is it just 1 minute data?
It would be nice to back test for more years than calgo currently allows. So maybe getting my own data, that i know is reliable, is the way to go.
PS: i just refreshed my chart and it looks like data is back to normal for the time frames that were missing. I have been in touch with Spotware as well since last week and they were working on it. I'm pretty sure that it is a Spotware issue, not an IC Markets problem. Can anyone confirm that?
Dukascopy's data is regarded to be decent enough.
@Elogos
Elogos
25 Sep 2014, 10:51
Thank you Roman.
It would be nice to have greater declared transparency in support also. I am sure a lot of these issues could be resolved by better broker training and stricter service level agreements from all parties down to the user. Just better understanding of the fault at the broker level would be a start, then perhaps they could relay to the software vendor what is going on.
@Elogos
Elogos
24 Sep 2014, 23:01
It is aweful isn't it?
How are we supposed to trade under these conditions?
IC Markets say that they are powerless to do anything because they are at the mercy of Spotware. In reality I think it is a mix of both of them not presenting and diagnosing, either give wrong information back to me or give answers unrelated to anything I was explaining. To be honest, I think it is hard to impress upon anyone who doesn't do the stuff we do how important it is for data to be 100% accurate. It is the only thing we work by. I thought the days had gone where I'd get a skipped data feed because the sat link cut out midstream for a few seconds, but at least I could re sync that stuff, this I can't even fix myself.
I will have a think about a cut out for you, we might be able to detect bad data based on candle times on static timeframes, but on ticks it would have to be something based on ticks per minute average or something similar.
The main problem is the timeframes for the fixes are given in weeks not hours, which for any high frequency algo or intraday system is killer because this missing data/corrupt data means the end to a correct algo/indicator signal set.
@Elogos
Elogos
24 Sep 2014, 17:53
I refer you to this issue as well emeeder that you should probably be aware of when refreshing data or restarting the client.
/forum/ctrader-support/3481
There have also today been issues with the data going missing on the Demo server as well.
Night shift at IC Markets have limited power to do anything and are next to useless, which is silly since their night-shift is when most of the symbols have their highest volume and movement.
@Elogos
Elogos
24 Sep 2014, 17:39
Today the demo servers went down for IC Markets.
When they came back data for the 23rd was missing.
Now I have been told that it won't be fixed until first week in October.
Live data is unaffected.
For the algo runners this means data corruption causing missed entries and for cTrader users the problem comes into play for every indicator.
The outage was unacceptable alone, since IC Markets didn't seem to even know about it until I contacted them.
I have linked demo accounts to logging profile sites that show missed entries and fudged data will cause suspicion and possible suspension that I can't have and a zero tolerance policy is applied to most.
I find this an unacceptable way of operating since data is what we run on, and data should be the #1 priority to get right.
A whole day missing is totally unacceptable.
This needs to be fixed now.
@Elogos
Elogos
10 Sep 2014, 13:00
I just received a reply back from the enquiry that my broker made with you.
Why would you generate TIck charts in reverse?
That makes them relationally useless and will give different results each time you test historically to recent.
I know it is a crude comparison but if the Daily Chart history changed even minutely each time you would have people asking why it changed.
The fix for the chart change if Dynamically generated from the most recent Tick is to pick a point in time in the past and snapshot the tick data daily, that way there is a constant reference without dynamic generation from recent, but the last tick on the previous day it works on the roll-over even if it is in the middle of a grouped T34 range.
@Elogos
Elogos
02 Apr 2014, 22:30
RE:
rkokerti said:
Thanks for your answer Elogos!
I would have liked read the opinion of developers as well, but I think I will follow your train of thought.
Thanks again!
No problem, the thing about using OpenTime is it also makes it inherently easier code for any MarketSeries for MTF indicators.
@Elogos
Elogos
29 Mar 2014, 16:52
RE:
rkokerti said:
Dear Support,
I would like to ask you that, sometimes you change the index number of candles ? If yes, what is the technical reason of this? Because I use a custom indicator that refers to indexes, and I have to reset it in this cases, and that's a lot of work for me.
Thanks in advance!
It is preferable to refer to candles by open time with this platform.
The index of any given candle can change if refresh is called (history is trimmed) or you are on some sort of composite chart like Tick Charts.
The index of a given candle is useful when referring to the collection when in a snapshot state, say for example the Calculate() event, any locally stored references should be fine.
But input parameters or if you store data outside of the indicator and use indexes for reference then it won't have any referential integrity. Indicators call Initialise() when the chart refreshes so data held within the scope of the indicator or any instances it makes should be fine.
I am sorry if this hasn't helped you, I have tried my best to understand the issue you have, and unless there is a bug, the chart indexes should not change without calling an Initialise() after, which allows short-term referential integrity.
@Elogos
Elogos
24 Mar 2014, 00:24
When markets are closed MarketSeries load about 1-2 seconds per symbol/timeframe combo.
When markets open MarketSeries load about 1-2 minutes per symbol/timeframe combo.
When you are looking at 420 combinations you can be there for 7 hours.
A week on and the data services are still not fixed.
IC Markets live/demo and Spotware's direct demo are having the same issues on both my local machine here and on my server in data centre.
@Elogos
Elogos
02 Nov 2014, 00:11
RE: RE:
Elogos said:
I have looked for the notes, but it seems to be hidden somewhere in an old Archive.
I'll keep searching, but Perhaps I hope that the same person will repost here.
@Elogos