The next week I'll rewrite it on the terminal and then I can put it to the tests. I will rewrite it for the terminal next week and it will be possible to put it for tests.
I added new predictors (all sorts of returns according to my technology, volatility, regression channel for the day), I think it turned out okay - not perfect - plausible.
But even with the old ones I'm on the plus side, 30 models (100%) in the green zone - nice, I don't know, maybe the CatBoost training settings have also had an effect.
The next week I'll rewrite it on the terminal and then I can put it to the tests. I will rewrite it for my terminal next week and I will be able to use it for tests.
By the way, this is a bug in the packet analyzer. I fixed it this way:
The standard there is jedi in the settings. I installed Pylance and changed 'jedi' at the bottom to Pylance in the studio settings through the search. Now it sees all the fields of the package and doesn't give out errors.
It is based on a forest, but can easily be replaced by a neural network. There is loading from file, renders, history depth setting (input size), importance of inputs, error on tray and validation, simple tester.
The plan is to add a zigzag, ma, to finalize the tester.
It is based on a forest, but can easily be replaced by a neural network. There is loading from file, renders, history depth setting (input size), importance of inputs, error on tray and validation, simple tester.
The plan is to add a zigzag, ma, to finalize the tester.
Your critique is welcome.
This "system" is designed for 1 DTs with positive slippages.
And where is the system itself, what is it compared to?
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
The next week I'll rewrite it on the terminal and then I can put it to the tests. I will rewrite it for the terminal next week and it will be possible to put it for tests.
Do you have a chart with spread?
I added new predictors (all sorts of returns according to my technology, volatility, regression channel for the day), I think it turned out okay - not perfect - plausible.
But even with the old ones I'm on the plus side, 30 models (100%) in the green zone - nice, I don't know, maybe the CatBoost training settings have also had an effect.
The next week I'll rewrite it on the terminal and then I can put it to the tests. I will rewrite it for my terminal next week and I will be able to use it for tests.
Maybe I should use watch watch?
By the way, this is a bug in the packet analyzer. I fixed it this way:
The standard there is jedi in the settings. I installed Pylance and changed 'jedi' at the bottom to Pylance in the studio settings through the search. Now it sees all the fields of the package and doesn't give out errors.
It worked )
14. Quick R Assemblies
15. The JIT Compiler
Why do you need all this?
You have a working algorithm, but it lacks speed?
you have a super-duper idea but it lacks processing power?
Why do you need all that? Concentrate on the TS, everything else is just bollocks.
Hear me, I've got the ECLIPS and you can do it. Wipe your drooling weakling and keep working :-)
You understand R-ka already? Prof.)
How about watchdogs?
I made a magic button that reduces/increases the number of trades
get into python, you'll test it... I'm already sick of so much coding)
I made a magic button that reduces/increases the number of trades
get to know python, you'll test it... I'm already sick of so much coding )
i don't know if i could do that, but if i wanted to, i could become a programmer in a day)
My Pipeline. The initial goal is to create a base for further research, the final goal is to beatthe "classic" system.
It is based on a forest, but can easily be replaced by a neural network. There is loading from file, renders, history depth setting (input size), importance of inputs, error on tray and validation, simple tester.
The plan is to add a zigzag, ma, to finalize the tester.
Criticism is welcome.
Why do you need all this?
Do you have a working algorithm, but it lacks speed?
You have a super-duper idea but it lacks computing power?
Why do you need all that? Concentrate on the TS, all the rest is rubbish.
I have a system, but not enough speed.
My Pipeline. The initial goal is to create a base for further research, the final goal is to beatthe "classic" system.
It is based on a forest, but can easily be replaced by a neural network. There is loading from file, renders, history depth setting (input size), importance of inputs, error on tray and validation, simple tester.
The plan is to add a zigzag, ma, to finalize the tester.
Your critique is welcome.
This "system" is designed for 1 DTs with positive slippages.
And where is the system itself, what is it compared to?