That huge drop could well be today.
What with news today that Portugal requires a second bail out .... it looks like there may be some activity today.
Doing what you like is Freedom. Liking what you do is Happiness.
- #4,721
- Jan 27, 2012 3:13am Jan 27, 2012 3:13am
- Joined Feb 2009 | Status: Hasta la victoria siempre - El Che | 19,542 Posts
- #4,722
- Jan 27, 2012 3:13am Jan 27, 2012 3:13am
- Joined Jan 2011 | Status: ,,,,, ....,,,,,, | 6,008 Posts
.... laughing all the way to the bank
- #4,725
- Jan 27, 2012 4:40am Jan 27, 2012 4:40am
- Joined Feb 2009 | Status: Hasta la victoria siempre - El Che | 19,542 Posts
Doing what you like is Freedom. Liking what you do is Happiness.
- #4,727
- Jan 27, 2012 6:20am Jan 27, 2012 6:20am
- Joined Feb 2009 | Status: Hasta la victoria siempre - El Che | 19,542 Posts
Doing what you like is Freedom. Liking what you do is Happiness.
- #4,728
- Jan 27, 2012 7:30am Jan 27, 2012 7:30am
- Joined Jan 2011 | Status: ,,,,, ....,,,,,, | 6,008 Posts
lhDT,
Your signals indicator 1.8 is a dream
I'm trying out a few settings . Is it possible to use Current Extreme rather than HTF Extreme as one of my trigger requirements? So, I normally trade form the 5 Min timeframe and would like to use it .
I also would like to exclude Emotions and Sentiments from my trigger trade conditions .
Can I do this?
Thanx
Your signals indicator 1.8 is a dream
I'm trying out a few settings . Is it possible to use Current Extreme rather than HTF Extreme as one of my trigger requirements? So, I normally trade form the 5 Min timeframe and would like to use it .
I also would like to exclude Emotions and Sentiments from my trigger trade conditions .
Can I do this?
Thanx
.... laughing all the way to the bank
Hi all,
my first version of the new MTF HA is available and ready for testing. Please consider it experimental, there may be still some bugs inside
Changes/features:
1. no external HA indi needed, it is coded inside
2. normal mode: as you know it, but with consistent repainting. It should always show the same, if you refresh or not.
3. static mode (option StaticView=true): this is basically a non-repainting mode for those who want to see later what the indi had shown live.
4. Alert generation (option AlarmOn=true): it will give an alert if all TFs show the same on the most recent closed candle (bar 1), only one time for each pattern occurance and only one time per candle.
5. Meter: shows the HA close right to the bars
One comment on the static mode:
To calculate the static values, I basically took the open price from the higher timeframes and the other prices from the chart timeframe. I still observe that sometimes there is a shift of one bar compared with what the indi had shown live. this need some analysis, but it should be 99% correct.
In the screenshot, there is one example. H4 was DOWN from 16:00 to 17:20. Then it turned to UP. Of course, in normal mode the complete H4 candle turned UP and caused a repaint back to 16:00. In static mode you can still observe at any time later was happened live.
I welcome your feedback and recommend to run it in parallel to the original MTF HA as a reference.
have fun and a nice weekend
candletiger
my first version of the new MTF HA is available and ready for testing. Please consider it experimental, there may be still some bugs inside
Changes/features:
1. no external HA indi needed, it is coded inside
2. normal mode: as you know it, but with consistent repainting. It should always show the same, if you refresh or not.
3. static mode (option StaticView=true): this is basically a non-repainting mode for those who want to see later what the indi had shown live.
4. Alert generation (option AlarmOn=true): it will give an alert if all TFs show the same on the most recent closed candle (bar 1), only one time for each pattern occurance and only one time per candle.
5. Meter: shows the HA close right to the bars
One comment on the static mode:
To calculate the static values, I basically took the open price from the higher timeframes and the other prices from the chart timeframe. I still observe that sometimes there is a shift of one bar compared with what the indi had shown live. this need some analysis, but it should be 99% correct.
In the screenshot, there is one example. H4 was DOWN from 16:00 to 17:20. Then it turned to UP. Of course, in normal mode the complete H4 candle turned UP and caused a repaint back to 16:00. In static mode you can still observe at any time later was happened live.
I welcome your feedback and recommend to run it in parallel to the original MTF HA as a reference.
have fun and a nice weekend
candletiger
- #4,737
- Edited 11:23am Jan 27, 2012 11:00am | Edited 11:23am
Hope you jumped into the E/U ride based on greek's rumours !
Signal sent by ... Symphonie
Edit : +65pips, nice for the end of the week ...
Signal sent by ... Symphonie
Edit : +65pips, nice for the end of the week ...
#### Follow me at @LioH_ on Twitter ... ####
I also want to share my findings while working on the MTF HA indi. I may be wrong in some aspects. If you have a different opinion, please share it.
Repainting (you cannot hear it anymore?
)
I think the word repainting is widely used in this thread but different people have a different understanding what this is.
1. Any indi that does calculation on more than the open price is repainting the current bar (until closed). This is not really repainting, this is just work in progress.
2. Some indies re-calculate values of previous closed bars while moving on. That depends in the indi. Cycle does it, HA does it not! Here it could make sense to have a so-called non-repainting version of the indi to keep in memory what happend.
3. Indies repaint on TF change, or reload button or scrolling or number of bars in history. I don't know if there are really indies where this is intended behaviour, I rather see this as bugs. But I don't want to start a heated discussion on this.
findings on the MTF HA indi:
Why is the known MTF HA indi repainting?
Because the rightmost squares you see from TFs above are from a still-not-closed bar (current bar 0 in above TF). So this is perfectly ok.
Why does the known MTF HA not repaint *all* sqares from the current bar while watching the chart but it does after a TF change?
To save processing power, the indies usually only calculate new bar values and consider it done for the existing ones (see IndicatorCounted() in mql).
This works fine for a normal indi but not for a MTF version as indi values from higher TFs are not yet complete while in your chart the bars are already closed.
For coders: One could simply remove the IndicatorCounted() but this would waste processing power, especially if your chart history grows to thousands of bars. So it is better to do a smart calculation how much is really needed.
happy weekend
candletiger
Repainting (you cannot hear it anymore?
)I think the word repainting is widely used in this thread but different people have a different understanding what this is.
1. Any indi that does calculation on more than the open price is repainting the current bar (until closed). This is not really repainting, this is just work in progress.
2. Some indies re-calculate values of previous closed bars while moving on. That depends in the indi. Cycle does it, HA does it not! Here it could make sense to have a so-called non-repainting version of the indi to keep in memory what happend.
3. Indies repaint on TF change, or reload button or scrolling or number of bars in history. I don't know if there are really indies where this is intended behaviour, I rather see this as bugs. But I don't want to start a heated discussion on this.
findings on the MTF HA indi:
Why is the known MTF HA indi repainting?
Because the rightmost squares you see from TFs above are from a still-not-closed bar (current bar 0 in above TF). So this is perfectly ok.
Why does the known MTF HA not repaint *all* sqares from the current bar while watching the chart but it does after a TF change?
To save processing power, the indies usually only calculate new bar values and consider it done for the existing ones (see IndicatorCounted() in mql).
This works fine for a normal indi but not for a MTF version as indi values from higher TFs are not yet complete while in your chart the bars are already closed.
For coders: One could simply remove the IndicatorCounted() but this would waste processing power, especially if your chart history grows to thousands of bars. So it is better to do a smart calculation how much is really needed.
happy weekend
candletiger
- #4,739
- Jan 27, 2012 11:24am Jan 27, 2012 11:24am
I have to agree with RJ on this one, it is definitely a bullish hidden divergence, should enter long instead of short.
Check this out.
EDIT: The key to divergence is whenever you draw a line above price or the oscillator, it will always be a short (bearish divergence) and whenever you draw a line below price or the oscillator, it will always signal a long (bullish divergence), no matter if its regular, hidden, or exaggarated.
