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)
As a little exercise this morning I thought I'd plot the values of Major Cycle Buy, Major Cycle Sell and The Line. The idea being to see the relationship of each of the values plotted out visually. Turns out they all plot identically. They are all the exact same thing.
For those of you tearing into the code you surely know this already, but thought it would be interesting for others who are following this topic.
Can you help answer these questions from other members on NexusFi?
So it's basically plotting a single line, then looking back "n" bars to see if it's at a new high or new low for the "n" period. The image below shows 2 points of the line.
Low 1 = looks back 20 bars to see if it's at the lowest point. Since it was a new low, it painted a Minor Cycle Buy bar.
Low 2 = also looks back 20 bars and discovers it is a new low. So it erases the first Minor Cycle Buy bar and draws a new one.
I'm guessing on the look back period of 20 bars, but it's something like that. For a Major Cycle it simply looks back a larger number of bars.
To compliment this indicator I whipped up one of my own. The idea being to verify "real" signals and avoid the false signals.
It's basically a combination of 3 indicators into one oscillator. You can easily edit the oscillator to include the indicators of your choosing, but these seem to work pretty well. I would like to tweak it some and add "thresholds", but need to do some testing first. The "threshold" idea is to better identify chop.
Right now it works pretty well at identifying most of the tops and bottoms. I look for a change in color of the oscillator bar to coincide with the Cycle Indicator (within a few bars).
An expert coder could probably improve on this a great deal.
I could't import this one first it said duplicate linregsfx, so I wiped out lingregsfx, vpa_beta, vpavolumeanalyzer then I re-imported it but it said duplicated DTWopen method or something like that and I couldn't find that method to delete.
Uh oh. I really don't know too much about the import process except a few basics.
When I did the export I selected the option to include any scripts used by this indicator. Since it uses 3 other indicators it should have only included those 3 along with the oscillatory name JimmyJoe. Those 3 are:
LinRegSlopeSFX
CCI
KrauseSlope
From your message it sounds like it included every indicator I have. That's odd because it gives you a list of the files exported together in the zip file. Anyway, I re-exported the zip file, double checked the list of files included, and I think the import should work better now. Crossing my fingers.
I've been using the StepMAv71 for some time and like it very much. In fact, I've just added the relationship of the 2 lines to the oscillator I built. It seems to run just fine but the darn thing won't export the file now. I'll attach the .cs file anyway.
So the oscillator simply adds together the values of the 3 indicators mentioned earlier and this new version adds the StepMA lines as well. The purple line is subtracted from the yellow line to arrive at a value. That value is then multiplied by 10, then added to the value of the group of 3.
