Software Used to Trade Jack Hershey Methods

Quote from ljyoung:

Thanks palinuro for the update and the well taken point re 'time synchronization'. What DP (other than another broker) have you used for the index data? I know you can get it from IB but have tried to find some NT-friendly outfit and have not yet been successful.

I've only used IB, but you can use any of the NT compatible data providers. If you use one that also provides futures data there wouldn't be a synch issue.

- palinuro
 
Quote from palinuro:

It can't be done properly as an Indicator until NT7 comes out.

Also, if you're using ZenFire for futures data you would need some other feed for the DJ Index data, and that can lead to questions about update timing from the data providers....

I've done it as a Strategy, but it was fiddly to set it up each day and I never found it very useful, so it has been gathering dust for a long time.

- palinuro

Thanks for the insights!
 
I have improved the BarPaint2 indicator for NinjaTrader

-1 tick ibgs has lighter color
-lateral formation will be killed by an IBGS that pierces its boundary
-lateral formation must end by 2 consicutive closes outside, and as such will will continue when price closes outside followed by close inside

I believe it does laterals much more accurate now.

HTH

--
innersky
 

Attachments

Quote from innersky:

I have improved the BarPaint2 indicator for NinjaTrader

-1 tick ibgs has lighter color
-lateral formation will be killed by an IBGS that pierces its boundary
-lateral formation must end by 2 consecutive closes outside, and as such will will continue when price closes outside followed by close inside

I believe it does laterals much more accurately now.

HTH

--
innersky

Thank you very much innersky for the 'lateral tuneup'. Indeed it is more accurate however as you will see in the attachment, it appears that there is no volume constraint on the 'ability' of a 'piercing' IBGS to terminate a lateral. Do you think you could address this?

TIA

attachment.php
 

Attachments

Quote from charts:

... Sorry guys ... I'm pretty sure you're on the wrong track with this kind of emphasis on laterals ... :)

It will do until something better comes along.
 
Quote from charts:

... I suggest learning to better draw tapes :)

Hmmm. Let's see if I remember the lateral protocol. Yes I do. As I said, come up with something better. As an aside, a lateral very frequently reflects the overnight price action, especially on a 60 min timeframe.

Memo to innersky. Booleans deal with perceived absolutes, for want of a better term and as yet I have to find a violation of your proclamation voiced elsewhere. Interestingly, lateral movements do violate the condition and perhaps that's one of the reasons why they have been left behind.
 
Quote from ljyoung:

Thank you very much innersky for the 'lateral tuneup'. Indeed it is more accurate however as you will see in the attachment, it appears that there is no volume constraint on the 'ability' of a 'piercing' IBGS to terminate a lateral. Do you think you could address this?

TIA


While I don't think volume is of any importance here, here is the code you asked. (this code will only end the lateral when an IBGS pierces the lateral on increasing volume)
Just add the bold part in the code.


// if ibgs that pierces a lateral then it must end this lateral
if (FirstTickOfBar
&& lat
&& Volume[1] > Volume[2]
&& ((High[1] > High[CurrentBar - latBar])
&& ( High[1]>High[2] )
&& ( Close[1]<Open[1] ))
|| ((Low[1] < Low[CurrentBar - latBar])
&& ( Low[1]<Low[2] )
&& ( Close[1]>Open[1] )))
{
lat = false;
}
 
Quote from innersky:

While I don't think volume is of any importance here, here is the code you asked. (this code will only end the lateral when an IBGS pierces the lateral on increasing volume)
Just add the bold part in the code.


// if ibgs that pierces a lateral then it must end this lateral
if (FirstTickOfBar
&& lat
&& Volume[1] > Volume[2]
&& ((High[1] > High[CurrentBar - latBar])
&& ( High[1]>High[2] )
&& ( Close[1]<Open[1] ))
|| ((Low[1] < Low[CurrentBar - latBar])
&& ( Low[1]<Low[2] )
&& ( Close[1]>Open[1] )))
{
lat = false;
}

Thank you innersky.
 
Back
Top