When the technical issue would be out of the way, I think it still can not work, but not sure. You started out in this topic with questions about the adding of parameters. I think that would be a necessity in your situation, so that idea seemed good. Thus, the parameters from the backtesting can be passed on to the Indicator code. I think as how you have it currently, they live on their own (with the same name).
But the technical issue must be solved first. And as said, possibly by following some (more special ?) guidelines.
What you want to do is perfectly normal for Backtesting and Live. But in the MarketPlace situation all is a bit different in PRT (so that would be their issue, not Nicolas).
For @Nicolas : I now recall the similar situation. This was from [now anonymous] who always provided a 100% profitable trades. But all what happened was that his StopLoss parameter was set to the same too high number and could not be influenced by BackTesting. The rest of his parameters were just in-code, so backtesting with *those* seemed to work nicely. But without active StopLoss all looks nice, until you see what causes it.
Buy your own trial, and try to run the backtest from there. Did you do that ? Can you even do that ? (I just don’t know)
To be sure : my broker is IG and it is through PRT-Sponsored (so I have an account with PRT-IB (which would be PRT-Direct) but can obviously only use IG for broker because IB can’t do Autotrading (yet). Notice that I could do backtesting with IB, though.
Does this make a difference somewhere ?
Very good find !
But it is still different. You show the execution of the Backtest of your original (the one which can not be adjusted). That indeed works.
But a copy like one of those in that tree (you have the copies too), still does not work. I suppose this is workable now, but we can’t adjust the parameters (current enumerating by 9800 iterations) and we also can’t adjust the code itself (because that requires a copy).
The backtest is running and optimising the strategy based on predefined range of values. This range of values cannot be modified. The code itself also cannot be modified.
Not from the Indicators. But from the main strategy, sure it can. E.g. change %LOSS to $LOSS. Everything.
Of course you need to do that in the copy you made (from the top of my head S1 or S2 on your screen).
But influencing the Backtest variables … no. So all we got is the iteration of all the combinations which *you* implied, working. Limit the range here and there so no 9800 iterations come from it, and it could be doable. But not really (not for me) because all what would come from it is an over-optimised strategy. Right ?
The information collected on this form is stored in a computer file by ProRealCode to create and access your ProRealCode profile. This data is kept in a secure database for the duration of the member's membership. They will be kept as long as you use our services and will be automatically deleted after 3 years of inactivity. Your personal data is used to create your private profile on ProRealCode. This data is maintained by SAS ProRealCode, 407 rue Freycinet, 59151 Arleux, France. If you subscribe to our newsletters, your email address is provided to our service provider "MailChimp" located in the United States, with whom we have signed a confidentiality agreement. This company is also compliant with the EU/Swiss Privacy Shield, and the GDPR.
For any request for correction or deletion concerning your data, you can directly contact the ProRealCode team by email at privacy@prorealcode.com
If you would like to lodge a complaint regarding the use of your personal data, you can contact your data protection supervisory authority.
Get Assistance
Assistance Type
Your Need
Proposed Solutions
Do you like cookies? 🍪 We use cookies to ensure you get the best experience on our website.
(Learn more)
