optipie / tradingview-optimizer-extension Goto Github PK

The Period is shown as 1m in every report regardless of the timeframe used in the optimization. A recent commit message suggests there was maybe an intent to fix this(?), but it still occurs at least at commit 0b49f6f.

I would like to kindly suggest the ability to run the optimizer with Deep Backtesting feature on TradingView.

This issue will be fixed soon, you can keep using app as usual it does not affect report creation process.

Hi, I stumbled across your project and this is exactly what I was thinking of doing.
I use Trading Pro scripts that have a ton of inputs but backtest on only a handful, 3-4.
IF you could enhance your project to allow me to pick which fields I want to be optimized, instead of the first 4 it finds (my assumption based on testing), this would be a game changer.
Let me know your thoughts, I could help with 'a few coffees' to get this going.
And honestly, I think you could turn this into a paid-for product.
Thanks Rob

Does this actually work for some people? For me it kind of follows the start and stop ranges sometimes, and it completely ignores the step size.

Why is it still running?
Maybe I did something wrong?
because close I cant choose , so I picked 1 - 8

But 4th Parameter is beyond the 25 now at 57 ????

it is running for 2 days now.
What happened if i close it? It will print results?
please advise

I have had problems with step size. When I have more than one parameter, for some reason I can only get the step size of the first parameter to work, but not the step size of the second parameter. Even in the first parameter it only works if I add number like "2.0", but without ".0" it doesn't work at all. However, this solution no longer applies to the second parameter, I've tried everything, but I can't get it to work in another parameter at all. It always counts every number that is between the "start" and "end". I have also tried with another browser, but it had no effect.

Input parameter # 1 is 1-3, step 1, but the optimizer seems to be going beyond what I set.
I've attached the pine script I am testing Opti with.

pine-script-example.txt

It would be useful to have a stop button (the Optimize button could turn into a stop button). And then when the process is manually stopped it should ask the user if they want to see the results of what was processed or discard them.

In version 1.0.3, when you try to optimize a floating point parameter value, for example start=1.5, end=2.0, step=0.1, the optimization will fail. To me it seems it's trying to step with integer steps even though 0.1 step is given, but that is just a guess. I think this worked in version 1.0.2 but I'm not sure.

Fixing the query selector for the strategySymbol, affected report creation process hence will be fixed very soon

I was able to successfully run the optimizer once. Ever since it seems like MutationObserver is not running on var element = document.querySelector("div[class*=backtesting-content-wrapper]") I have tried clearing my cache and even trying to observe on an element on level higher but the code does not seem to pickup any mutations on that or its children.

Always end up with Rejected Timeout exceed error even with a fresh install of the extension directly from chrome extensions.

I assume you build and save the report when optimization is done.
If there is a long opti, and for some reason it doesnt finish, I lost what was captured so far.
If you could save it during each loop, then if it stops, we'd have progress so far.

I'm using 1 param just to try it out but it's not engaging with Tradinview after the "Optimize" btn click.

Ability to test on Watchlist and timeframe