Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Active GeoKing - Triple Auto Swing Indicator for NT8
I have done a fair amount of testing on resource use. All the resource use is coming from DailyCals at moment because it is written improperly, needs a rewrite. This is the function that calculates the Daily Pivots, 3DB and Open price.
Additionally, in the indicator properties you will notice the (1.b) Refresh rate setting. This is set to one second. It means it will never refresh more than once per second even with multiple ticks. This avoids stacking up in fast paced markets.
Testing shows that the rest of the indi is very resource efficient. At the moment, every function reports 0ms apart from DailyCals which reports 127ms. Once fixed, I imagine that you will notice very efficient resource use apart from during the first load.
Cheers.
Can you help answer these questions from other members on NexusFi?
Just an observation, but since running V1006 resource usage is much reduced.
With resource usage currently around 40,000 it's well below the benchmark Chart Style usage of around 180,000 (running as of the V1006 download about 2 - 3 hours ago). So this is running very efficiently as you say.
Ps: the image in my post 28 of 1,375,800 resource usage was for previous v1005. I'd forgotten to reload the Output Window after installing the latest v1006.
Yes, I'm seeing a LOT less (ms) used for 'GeoKing' as well..(after installing V1006)
My values have dropped from 12 to 14 X Candlestick () value to 5 X Candlestick () value.
Um, I'm not getting anything close to the adjustment you get in the video when I hit the
Swing (pink + -) adjustment buttons (that's a great feature and one I think we'd
all agree is necessary)
I've tried to use them while the AutoSw is toggled on and off and its the same non-action..
Any suggestions..?
Hey @Chof , swing adjustment is limited by the SW3. Meaning that if SW3 (the largest one) can't adjust higher, then the others will not either as they are governed by their relationship with each other. Therefore, GK needs a fair amount of data loaded for full functionality.
Work on the basis of 300 days for a 60 min chart, said in bar terms... (300 * 24) = 7,200 bars.
Yes, you HAD explained that earlier in the thread, but the SW3 dependancy hadn't sunk in..
You've been REALLY patient and I appreciate it..(Good on ya !)
I'm going to post a really simple Bollinger code that is working very well with this.. I'm using it
for targets and Overbought/Oversold zones..
Take care...
Chof
Thanks for posting your indicator.
I went to your youtube channel and saw there was only the one video.
I would be interested in seeing you post more videos.
(Perhaps, live trading, or a journal of your trading on NexusFI?)
Rejoice in the Thunderstorms of Life . . .
Knowing it's not about Clouds or Wind. . .
But Learning to Dance in the Rain ! ! !
This looked interesting so I installed it. But today I opened Market Analyzer and tried to open my link to Jigsaw and the only option I get when I click Indicators in market Analyzer is ActiveGeoking.
I tried removing/deleting ActiveGeoking but it is buried deep and I can't get rid of it. Any ideas here...?
Conceptzx
Posts: 111 since May 2022
Thanks Given: 25
Thanks Received: 74
open the script editor and right click the open area where code is displayed, go to resources and delete it from the list
(that's a great feature and one I think we'd 
