Would you be so kind as to answer my question exactly? I am not interested in your opinion on the necessity of a counsellor.
Integration with Python is made in such a way that it can only see and interact with the terminal. To interact with MQL you need R or many other less successful solutions IMHO
Vladimir Perervenko #: Integration with Python is made in such a way that it can only see and interact with the terminal. To interact with MQL you need R or many other less successful IMHO solutions
How does R interact with MQL? I don't understand the difference in what globally.
How does R interact with MQL? I don't understand the difference in what globally.
Using the long-standing proven mt-R library. Globally, it makes it possible to use MQL/R/Python together both in combat application and in testing, with a small change. When testing quotes and commands through MQL and when working through Python.
Vladimir Perervenko #: Using the mt-R library, which has been tested for many years. Globally, this makes it possible to use MQL/R/Python together both in combat and testing, with a small change. When testing quotes and commands through MQL and when working through Python.
As I understand it, the difference is that you can run code from MQL for execution in R.
in one fellswoop, if the quotes are loaded in the terminal
I'd rather have a figure, however approximate.
I'd rather have a figure, however approximate.
I don't have a computer at hand
Advisor is unnecessary. All queries from python, including trade queries.
Here, you can read the documentation on the language.
Would you be so kind as to answer my question? I am not interested in your opinion about the necessity of an advisor.
Would you be so kind as to answer my question exactly? I am not interested in your opinion on the need for a counsellor.
Please read the documentation at the link, and formulate questions after reading - substantively.
Well, one week, for example, on 20 instruments, all TFs.
How much +-? Half a second, a minute?
After starting the terminal, 21 seconds.
Repeated request for data 13 seconds.
And again - here it's almost instantaneous 0.5 seconds.
In general, experiment - the code from the terminal will work.
Would you be so kind as to answer my question exactly? I am not interested in your opinion on the necessity of a counsellor.
Integration with Python is made in such a way that it can only see and interact with the terminal. To interact with MQL you need R or many other less successful IMHO solutions
How does R interact with MQL? I don't understand the difference in what globally.
How does R interact with MQL? I don't understand the difference in what globally.
Using the mt-R library, which has been tested for many years. Globally, this makes it possible to use MQL/R/Python together both in combat and testing, with a small change. When testing quotes and commands through MQL and when working through Python.
As I understand it, the difference is that you can run code from MQL for execution in R.
After starting the terminal, 21 seconds
Repeated data request 13 seconds
And again - almost instantaneous 0.5 seconds.
In general, experiment - the code from the terminal will work
like