- Topics: 13
- Replies: 25
- Posts: 38
I’d also like to congratulate Optuma for what they have produced. Do not to underestimate the raw power of the Optuma script environment.
I’ve been heavy-duty scripting for several years now, and may have used the scripting environment in ways that were never intended. For example, my latest creation consists of about 5000 lines of code, across over 100 inter-dependent scripts operating on two workbooks.
It uses functions like IF(), SCRIPT(), TIMESINCESIGNAL() and all the OHLCs hundreds of times, VALUEWHEN(), SWITCH(), SIGNALAFTER() scores of times and other functions like ACC(), ACCSINCESIGNAL(), MOD(), MIN(), MAX(), IsUp, IsDown, NOREPEAT(), CANDLESTICKPATTERN(), LOWESTLOW(), HIGHESTHIGH(), etc. Some scripts have dependencies on 10 or more other scripts and there’s funky stuff like deep-nested SIGNALAFTER() functions to get specific outcomes.
Maybe the guys at Optuma would shudder when reading that, but, pleasingly, I can say Optuma works like a charm even under these conditions – although the workbooks do take half a minute or so to open 🙂
So, in my experience, what can be done with Optuma scripting is quite astonishing.
About the only area that I haven’t been able to achieve with Optuma scripting is really nasty recursive compounding calculations, but there has been a way with Optuma scripting to solve every other harebrained idea I’ve had. 🙂
The guys at Optuma are super helpful and have given insightful answers to my scripting questions in this forum over the journey, which has really helped improve my skills and understanding of the Optuma scripting environment. They really know their stuff.
So hooray and three cheers for Optuma scripting from me too. I’ll say it again, don’t underestimate how sophisticated and powerful Optuma scripting is and the awesome things you can do with it.