@tdschulz, to get access to the naked swing values you have to make the "nakedSwingHighsList" and nakedSwingLowsList" public in the PAS indicator and access the lists within your strategy. The first value/key pairs of the lists contain the closest naked swings.
@madLyfe, the PasOsc/Volume isn't that well tested, it was more a quick and dirty implementation. I'll check into it soon and see whether I can reproduce your problem.
@DarrenH, this is possible but would require some work to re-write the PAS calculation for swings to work with the bar close values instead of the bar high/low. I'll keep this in mind but in the moment I have no time to implement this.
@rickr, you're right. There is a difference between Ensigns description of the Gann swing rules regarding outside bars and my implementation.
In the PAS indicator outside bars don't count as a consecutive higher bar (for an up swing) because they also make a new low. But to change the swing direction consecutive bars with higher highs AND higher lows are needed.
I can't say for sure which implementation is correct. If you find the original source in Ganns literature for this particular case with outside bars let me know. I have access to a lot of Ganns books/articles and can check it if you point me in the right direction.
E.g. we're in an up swing. The PASOsc/Volume will show the cumulative volume from the last low to the current bar with the green histogram. The red line represent the down volume and if the swing direction will change to the down side the red line will become a red histogram. The VLowCurrent/VHighCurrent plots basically represent the values to which the indicator will repaint if the swing direction changed.
@jpstyles2002, download the PAS indicator from the download section, download the latest template (#1 post of the thread) and save it under C:\Users\Username\Documents\NinjaTrader 7\templates\MarketAnalyzer and then open a new Market Analyzer and load the template.
The following 10 users say Thank You to dorschden for this post:
It`s way too lagging to me,instead of a leading as it should be with volume.Is there a way to get the change signal a bit earlier(sound alert,maybe)?In a short time frame,by the time you get the signal from the volhisto,the price is already away.How to catch the moment,where the low volume line becomes another color histo?Is proportion aplicable to that logic in this sense?
Last edited by tst1; October 25th, 2012 at 10:13 AM.
Reason: additional text
Thanks @dorschden for this great contribution!
Hi @cal1152 i just downloaded installed the current PriceActionSwing pro that puts the 3 indis(PriceActionSwing, PriceActionSwingOscillator, and PriceActionSwingPro) into NT7 and downloaded your templates. I got your templates from posts #507 (ABC60.xml,ABC Daily.xml) and #508(Div daily 15.xml)
When I open a new MarketAnalyzer and apply a template. I do not get the same results as seen in your posts (attached pic of mine).
Wanted to see if you, or anyone have any ideas on what could be wrong? All three templates when applied to a Market Analyzer window result in showing only the columns seen in attached pic.
Thanks in advance for any suggestions
Please register on futures.io to view futures trading content such as post attachment(s), image(s), and screenshot(s).
The following user says Thank You to learning0101 for this post:
@learning101 ....It may be because dorschden has released new version of the PAS and the MarketAnalyzer template since I posted those templates and my old templates are not compatible. I haven't updated to the new versions yet. You can save my old templates to check out the configuration and just download the new MA template and apply the configuration. That may work.
Hope it helps....Cal
The following user says Thank You to cal1152 for this post:
Apologies if this is a fundament coding question, but how do you access or change the additional parameters or variables of the PriceActionSwingPro for use in a strategy? The indicator appears to only have DtbStrength, SwingSize, and SwingType as parameters. For example, the DivergenceMode is initially set to “false”, so how do you change that to MACD (without saving it that way within the code)? Or more importantly, how would you access/change Param1, Param2, Param3, AbcMaxRetracement, and AbcMinRetracement in order to test or optimize various settings while backtesting? Thanks in advance for any possible suggestions; and thanks again to dorschden for such an amazing indicator.