Topics
Replies
Spotware
24 Nov 2015, 01:59
Dear Trader,
The data in backtesting mode are broker specific historical values of the Symbols. Tick data is accurate.
Currently, we don't provide provide users the ability to see bars based on the ask price. We will consider providing it in the future.
Additionally, you can post your ideas/suggestions to http://vote.spotware.com/
@Spotware
Spotware
24 Nov 2015, 00:09
Dear Trader,
The data in backtesting mode are broker specific historical values of the Symbols.
For your information m1 trendbars do not contain ask prices. In order to emulate ask prices cAlgo requires you to specify the spread.
The tick data contains ask prices, therefore, spread is already included in the data.
@Spotware
Spotware
23 Nov 2015, 23:14
Dear Trader,
Please have a look at the Referencing Custom Indicators section of our API Programmers Guides.
Please note that we don't provide coding assistance services. We more than glad to assist you with specific questions about cAlgo.API. You can contact one of our Partners or post a job in Development Jobs section for any coding assistance.
@Spotware
Spotware
23 Nov 2015, 02:56
Dear Traders,
Thank you all for your suggestion. We will consider it. Additionally, you can vote for it in: http://vote.spotware.com/forums/229166-ideas-and-suggestions-for-ctrader-and-calgo/suggestions/5498070-ability-to-stop-other-cbots-from-the-main-cbot
@Spotware
Spotware
23 Nov 2015, 02:49
Dear Trader,
Thank you for your suggestion. We will consider it. Additionally, you can post your ideas/suggestions to http://vote.spotware.com/
@Spotware
Spotware
23 Nov 2015, 02:48
Dear Trader,
Thank you for your suggestion. We will consider it. Additionally, you can post your ideas/suggestions to http://vote.spotware.com/
@Spotware
Spotware
23 Nov 2015, 02:42
Dear Trader,
We do not provide coding assistance services. We more than glad to assist you with specific questions about cAlgo.API. You can contact one of our Partners or post a job in Development Jobs section for further coding assistance.
@Spotware
Spotware
23 Nov 2015, 02:41
Dear Trader,
We do not provide coding assistance services. We more than glad to assist you with specific questions about cAlgo.API. You can contact one of our Partners or post a job in Development Jobs section for further coding assistance.
@Spotware
Spotware
23 Nov 2015, 02:40
Dear Trader,
We do not provide coding assistance services. We more than glad to assist you with specific questions about cAlgo.API. You can contact one of our Partners or post a job in Development Jobs section for further coding assistance.
@Spotware
Spotware
23 Nov 2015, 02:36
Dear Trader,
Thank you for your suggestion. We will consider it. Additionally, you can post your ideas/suggestions to http://vote.spotware.com/
@Spotware
Spotware
19 Nov 2015, 12:41
Dear Trader,
The formula for calculating ROI is balance based:
CurrentROI = (1 + PreviousROI) * (1 + CurrentRealizedPnL / OpeningDealBalance) - 1
where
CurrentRealizedPnL is the realized profit/loss of the current closing deal.
OpeningDealBalance is the balance at the moment of opening deal, which is offset by current closing deal.
We will add commissions adjusted ROI in the next cMirror update, which will be released in the near future.
Your suggestion regarding replacing the "Mirroring Funds" field with the "Mirrored Volume" field will be taken into consideration.
Additionally, you can post your ideas/suggestions to http://vote.spotware.com/
@Spotware
Spotware
19 Nov 2015, 09:38
Dear Trader,
1) In your experience what could cause the proxy latency to stay the same but server latency to differ between 2 ctrader applications running on the same machine.
There could be various reasons why the proxy latency may differ on two cTrader instances running on the same machine. For example, they might be connected to different proxies. Could you please send us as much information as possible regarding your issue so that we can try to reproduce it? (Connection speed, OS version, etc.)
Could you please press Ctrl+Alt+Shift+T while you experience a huge latency? It will submit troubleshooting information to our support team.
In addition, could you send us an email at troubleshooting@spotware.com with the exact time, Timezone, Broker’s name, account number right after you submit the troubleshooting information.
2) What could cause one instance of ctrader to login via Amsterdam -2 and the other by London-7.
Note - I am now running 2 instances of ctrader. One instance each on a different VPS (2 vps in total, both in France), hosted from the same server though.
When you open cTrader, it checks the connection with various proxies and it connects to a random proxy with good latency. Sometimes you have a cTrader instance connected with proxy X and when you open the second instance of cTrader it connects with proxy Y because it has good latency too or because proxy X has bad latency.
@Spotware
Spotware
18 Nov 2015, 09:10
Dear Trader,
cTrader disconnects when it detects that your that your internet connection is lost or failed (1) or it is slow (2). In both cases you will be unsubscribed from all depth of market information for all currency pairs. cTrader will automatically re-subscribe to depth of the market for all currency pairs when your connection is back and/or returns to normal speeds.
@Spotware
Spotware
18 Nov 2015, 08:28
Dear Trader,
We tried to reproduce your issue without success.
Could you please send us a video at troubleshooting@spotware.com showing it?
In addition, could you please tell us your Brokername and which cTrader platform you are using? ( If it's not shown in the video)
@Spotware
Spotware
17 Nov 2015, 07:50
Dear Trader,
We tried to reproduce your issue without success. We kindly ask you to clear your cache and Backtesting cache and try again. The cache and Backtesting cache are located in:
C:\Users\%USERNAME%\AppData\Roaming\%BROKER%-cAlgo\Cache C:\Users\%USERNAME%\AppData\Roaming\%BROKER%-cAlgo\BacktestingCache
@Spotware
Spotware
25 Nov 2015, 23:26
Dear Trader,
Please have a look at the Optimization Criteria section of cAlgo support site.
@Spotware