I have sent out notifications to previous downloaders.
Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.
Need help? 1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first. 2) Start a journal and post to it daily with the trades you made to show your strengths and weaknesses. 3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make. 4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance. 5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers. 6) Help using the forum? Watch this video to learn general tips on using the site.
If you want to support our community, become an Elite Member.
The following user says Thank You to Big Mike for this post:
I created this because I was interested in determining the hours in an extended trading session for which liquidity is adequate to trade. I've also noticed, but not tested, that turning points in price seem to be highly correlated with spikes in tickspeed.
The following 5 users say Thank You to fluxsmith for this post:
I've also discovered a method of supporting multiple MA types without having a compile time dependency on those you don't wish to use.
Today I'm reposting jhlTSI and jhlTSIv2. If anyone has problems importing the new versions, you'll need to copy the .cs files from the .zip manually, compile, and let me know your error (it'll be a conflict with some other source file not from those two archives). I'll respond with a fix promptly.
The following 2 users say Thank You to fluxsmith for this post:
Updated jhlEMA to use new version of JHL.Utility.MA and use JHL.Utility.MAType vs JHL.Utility.MA.Type. Also further reduces memory footprint and increases CPU efficiency (trivially). Changed CalculateOnBarClose default to true, as I intend to set the default according to the refresh efficiency of the indicators.
Not my doing: NT support has recommended not having any COBC entry in indicators that are used for strategies. I am not sure of the reason, though I do know it makes a small difference in backtesting. All the NT supplied indicators in their distribution (as far as I have checked) do not have any COBC line in their code.
Just my 2 CDN cents worth,
Writing to you from the wonderful province of Ontario, Canada. Home to the world's biggest natural negative ion generator, the Niagara Falls, and to those that dare to know how to go over it in a barrel. SALUTE!
Maybe I'll do some testing, but as far as I know if you set the strategy itself to COBC = true all indicators within it will be run at COBC = true regardless of their defaults.
I like to have an indicator default to COBC = false if it is efficiently calculated, and COBC = true if it cannot be, especially if it has to iterate bars in order to update. I can always change it from the default if I want.
The following user says Thank You to fluxsmith for this post:
Updated jhlWMA to use new version of JHL.Utility.MA and use JHL.Utility.MAType vs JHL.Utility.MA.Type. Also increases CPU efficiency (trivially). Changed CalculateOnBarClose default to true, as I intend to set the default according to the calculation efficiency of the indicators.