Hi Nice result but myself in real account i'm always in loss.....Here are the results from this week with version 1.4, Vol=0.01
View attachment 172200
I hope this success continues next week.![]()
so please can you share your set ?
Hi Nice result but myself in real account i'm always in loss.....Here are the results from this week with version 1.4, Vol=0.01
View attachment 172200
I hope this success continues next week.![]()
please kindly share your set file here please. i want test it with your set fileHere are the results from this week with version 1.4, Vol=0.01
View attachment 172200
I hope this success continues next week.![]()
helloHello, colleagues!
Now our "golden" AI advisor has stopped being stubborn as a sheep and has learned to obey his master.
What was added:
• Two new fields in the settings: LLM_BuyThreshold and LLM_SellThreshold
(search in the "AI Settings (DeepSeek)" group).
Previously, the thresholds were tightly sewn in:
prediction >= 0.65 → BUY, prediction <= 0.35 → SELL.
Now you decide for yourself with what confidence the AI should open a deal.
If you want, tighten the nuts to 0.8 and 0.2 in order to trade only "reinforced concrete" signals.
If you want, loosen to 0.6 and 0.4 and catch more movements (but with popcorn, because it can be stormy).
Now, instead of "the robot thinks you're a sucker and ignores your wishes," we have a "henpecked robot" - turn the sensitivity knob and watch as it obediently runs to open positions.
Try it, experiment, and share the results. Version 1.4 is already in the topic header. Profit for everyone!
The HTTP 400 error is not a glitch, it's DeepSeek that has granted an "amnesty" to old models and retired deepseek—chat. The counselor knocks on her door out of habit, and she says, "There's no such model anymore, come back tomorrow."hello
i am facing "HTTP 400" error, removed EA from the chart and added again, but still same issue. please give me solution
I am also in favor of having the logic of signals and execution live in different "apartments" — this makes it easier to understand who is messing up: the predictor neural network or the crooked hands of a broker with an extended spread on the news.For gold robots, I usually separate the signal logic from the execution assumptions. The same idea can look solid in a backtest, but I would want to compare it across spread regimes, then check out-of-sample behavior and forward-test drift. Session timing matters too, especially when liquidity thins out or the broker widens spread around news. If the result changes a lot when those inputs move, the edge is probably too fragile.