- This topic has 257 replies, 18 voices, and was last updated 8 years, 5 months ago by
.
- Posts
Hi, This is my testing code of calling Gadi_NormalizeVolume blue & red histogram …
This is newer one, adding alert & changing in logic of blue/red/white histogram comparison.
Hi smallcat if can add alert to sc_gTactic2_02 when the arrow appear,give a pop alert. Regards.
Will try today mate, because my niece will marry tomorrow, so tomorrow to Sunday will be busy days for me.
Hi smallcat if can add alert to sc_gTactic2_02 when the arrow appear,give a pop alert. Regards.
Will try today mate, because my niece will marry tomorrow, so tomorrow to Sunday will be busy days for me.
Hi smallcat
Got it,I wish your niece Happy Wedding.
Best Regards.
Hi smallcat if can add alert to sc_gTactic2_02 when the arrow appear,give a pop alert. Regards.
Will try today mate, because my niece will marry tomorrow, so tomorrow to Sunday will be busy days for me.
So, here it is, quick and dirty version. I added other feature too beside alert. I will look at it next week if there is bugs. Please try it.
And many thanks for your congratulations @blueface.Hi G, do you mean to call the red & blue histogram, compare it to avg, then plot on chart? I think using iCustom will possible, will try it soon.
Hi, This is my testing code of calling Gadi_NormalizeVolume blue & red histogram …
Although you got some bugs, you can surely see the very high winning rate of the single Volume strategy.
You can even increase that high winning rate by putting the dot at the exact price, inside the bar, even before the bar closes, when Volume>= its avg.
Good job !!
G.
You can even increase the winning rate if you use SESSION AVERAGE instead of the naive one used in current indicator (i.e. London, London+NY, NY, Asian Sessions).
That was suggested long time ago, again with no productive feedback or contribution, as usual…
G.
Hi G, do you mean to call the red & blue histogram, compare it to avg, then plot on chart? I think using iCustom will possible, will try it soon.
Hi, This is my testing code of calling Gadi_NormalizeVolume blue & red histogram …
hi smallcat
I looked at your code and noticed you take only ‘pure’ blue/red volume bars. Don’t know if it was your intention or not, but a blue/red bar can appear even if white volume is > 0. In that case, the last green dot would have appeared one bar earlier.
V.
You can even increase the winning rate if you use SESSION AVERAGE instead of the naive one used in current indicator (i.e. London, London+NY, NY, Asian Sessions). That was suggested long time ago, again with no productive feedback or contribution, as usual… G.
I’ll try to code it and share it here. The problem with me is I can’t devote as much time to this forum as I would like to. Hopefully I’ll find some time tomorrow.
V.
Vlan:
I’ll try to code it and share it here. The problem with me is I can’t devote as much time to this forum as I would like to. Hopefully I’ll find some time tomorrow.
Look here for my newest blueprint – might save you some time to manage that session averaging.
It’s still a prototype! If you find bugs I’d appreciate if you notified me.
Have fun!
s.
A good trader is a realist who wants to grab a chunk from the body of a trend, leaving top- and bottom-fishing to people on an ego trip. (Dr. Alexander Elder)
Although you got some bugs, you can surely see the very high winning rate of the single Volume strategy. You can even increase that high winning rate by putting the dot at the exact price, inside the bar, even before the bar closes, when Volume>= its avg. Good job !! G.
Thanks G, will try it next week, and will see simplex’s idea on how to code based on session. Thanks @simplex too.
hi smallcat I looked at your code and noticed you take only ‘pure’ blue/red volume bars. Don’t know if it was your intention or not, but a blue/red bar can appear even if white volume is > 0. In that case, the last green dot would have appeared one bar earlier. V.
Thanks for the feedback bro. You are right about this. I was wrong in getting the buffer data from Gadi_NormalizedVolume indicator. At new codes (version 03), i am using the snippet code from yours, comparing all blue, red, and white histogram, and get the biggest. Thanks for that.
a session vol indy i tried to mess with a long time ago. i don’t think it can help anyone but i will upload it just in case.
“I believe the very best money is made at the market turns. Everyone says you get killed trying to pick tops and bottoms and you make all
your money by playing the trend in the middle. Well for twelve years I have been missing the meat in the middle but I have made a lot of
money at tops and bottoms.”
– Paul Tudor JonesAlthough you got some bugs, you can surely see the very high winning rate of the single Volume strategy. You can even increase that high winning rate by putting the dot at the exact price, inside the bar, even before the bar closes, when Volume>= its avg. Good job !! G.
Thanks G. This is the new version, trying to put “dot” at the time Volume(blue/red) >= average (realtime). Still have problem for previous bars (still need to create an MTF version of Gadi_NormalizeVolume / sx_VolumePerSession ), to call the “approximately” price the blue/red volume >= its average on TF M1.
a session vol indy i tried to mess with a long time ago. i don’t think it can help anyone but i will upload it just in case.
Thanks Lowphat, will look inside it.
Thanks G. This is the new version, trying to put “dot” at the time Volume(blue/red) >= average (realtime). Still have problem for previous bars (still need to create an MTF version of Gadi_NormalizeVolume / sx_VolumePerSession ), to call the “approximately” price the blue/red volume >= its average on TF M1.
The problem of drawing “dot” at the time blue/red volume >= average, is to draw the “dot” in the past candles of current bigger TF (ex. at M30). If we have MT4 that connected to internet 24/7 and we do not need to restart our MT4, i think it is not a problem. But, some times we need to restart our MT4, and the indicator must draw the “dot” again at the exact price where blue/red >= average. But, now we just have OHLC data of past bars, so the “dot” can only be drawn at ex. High/Low/Close of past M30 candles.
An idea is to go to small TF (like M1), and try to calculate the same thing (as we do on M30) on that M1 TF. I know if the blue/red >= average in M1, it is not exactly represent the exact time or price that happened in M30. But i think it is better than we just take the HLC of M30 to draw the past candles “dot”.Lets say we are at M30, and the we have “dot” because the volume of blue/red >= average on M30 at price 1,xxxx and time yyyy-mm-dd hh:MM:ss , but after we restart our MT4, we do not get this information again. we just know the past M30 bar Begin on Time1 and End on Time2, with its OHLC information. So, i am trying to “recover” the “dot” , to get that price 1,xxxx and time yyyy-mm-dd hh:MM:ss of M30 bar on M1 TF.
We have the volume average (and blue,red,white volume) value of M30, and we can passed it to M1 TF. But, the we can not compare it with the volume average of M1 as it is (the average on M1 must be smaller). So, i try just to get the biggest average value in M1 during that M30 candle time, and if the blue/red of M1 >= biggest average of M1 volume, i get the price and time, and send back to M30.Do not know this is a good idea or not. Any comment is welcome, thanks …
Edit: although we have the MTF version of Gadi_NormalizeVolume or MTF version of sx_volumePerSession, this problem is still exists.
Thanks G. This is the new version, trying to put “dot” at the time Volume(blue/red) >= average (realtime). Still have problem for previous bars (still need to create an MTF version of Gadi_NormalizeVolume / sx_VolumePerSession ), to call the “approximately” price the blue/red volume >= its average on TF M1.
The problem of drawing “dot” at the time blue/red volume >= average, is to draw the “dot” in the past candles of current bigger TF (ex. at M30). If we have MT4 that connected to internet 24/7 and we do not need to restart our MT4, i think it is not a problem. But, some times we need to restart our MT4, and the indicator must draw the “dot” again at the exact price where blue/red >= average. But, now we just have OHLC data of past bars, so the “dot” can only be drawn at ex. High/Low/Close of past M30 candles. An idea is to go to small TF (like M1), and try to calculate the same thing (as we do on M30) on that M1 TF. I know if the blue/red >= average in M1, it is not exactly represent the exact time or price that happened in M30. But i think it is better than we just take the HLC of M30 to draw the past candles “dot”. Lets say we are at M30, and the we have “dot” because the volume of blue/red >= average on M30 at price 1,xxxx and time yyyy-mm-dd hh:MM:ss , but after we restart our MT4, we do not get this information again. we just know the past M30 bar Begin on Time1 and End on Time2, with its OHLC information. So, i am trying to “recover” the “dot” , to get that price 1,xxxx and time yyyy-mm-dd hh:MM:ss of M30 bar on M1 TF. We have the volume average (and blue,red,white volume) value of M30, and we can passed it to M1 TF. But, the we can not compare it with the volume average of M1 as it is (the average on M1 must be smaller). So, i try just to get the biggest average value in M1 during that M30 candle time, and if the blue/red of M1 >= biggest average of M1 volume, i get the price and time, and send back to M30. Do not know this is a good idea or not. Any comment is welcome, thanks … Edit: although we have the MTF version of Gadi_NormalizeVolume or MTF version of sx_volumePerSession, this problem is still exists.
When in M30, start summing up volumes of M1 candles (from oldest to newest) of that given M30 candle until the sum exceeds the value of M30 average. Paint the dot at the close price of the last summed M1 candle.
V.
Volume per Session:
Accumulate all Volume Histogram bars per Start/End of each session (London, London+NY, NY, Asian) for the last 5 days.
Divide by number of bars per the relevant session*5, making it weekly average per session.
That’s the avg. when Volume >= should generate a dot or alert or both. No need to wait for bar Close.
G.
Yes:
Accumulate all Volume Histogram bars per Start/End of each session (London, London+NY, NY, Asian) for the last 5 days. Divide by number of bars per the relevant session*5, making it weekly average per session.
That’s what my 1st volume per session prototype does. I also chose 5 days as a lookback period.
s.
A good trader is a realist who wants to grab a chunk from the body of a trend, leaving top- and bottom-fishing to people on an ego trip. (Dr. Alexander Elder)
Yes:
Accumulate all Volume Histogram bars per Start/End of each session (London, London+NY, NY, Asian) for the last 5 days. Divide by number of bars per the relevant session*5, making it weekly average per session.
That’s what my 1st volume per session prototype does. I also chose 5 days as a lookback period. s.
I know, I tried to answer VlanFx & smallcat.
G.
Thanks G. This is the new version, trying to put “dot” at the time Volume(blue/red) >= average (realtime). Still have problem for previous bars (still need to create an MTF version of Gadi_NormalizeVolume / sx_VolumePerSession ), to call the “approximately” price the blue/red volume >= its average on TF M1.
The problem of drawing “dot” at the time blue/red volume >= average, is to draw the “dot” in the past candles of current bigger TF (ex. at M30). If we have MT4 that connected to internet 24/7 and we do not need to restart our MT4, i think it is not a problem. But, some times we need to restart our MT4, and the indicator must draw the “dot” again at the exact price where blue/red >= average. But, now we just have OHLC data of past bars, so the “dot” can only be drawn at ex. High/Low/Close of past M30 candles. An idea is to go to small TF (like M1), and try to calculate the same thing (as we do on M30) on that M1 TF. I know if the blue/red >= average in M1, it is not exactly represent the exact time or price that happened in M30. But i think it is better than we just take the HLC of M30 to draw the past candles “dot”. Lets say we are at M30, and the we have “dot” because the volume of blue/red >= average on M30 at price 1,xxxx and time yyyy-mm-dd hh:MM:ss , but after we restart our MT4, we do not get this information again. we just know the past M30 bar Begin on Time1 and End on Time2, with its OHLC information. So, i am trying to “recover” the “dot” , to get that price 1,xxxx and time yyyy-mm-dd hh:MM:ss of M30 bar on M1 TF. We have the volume average (and blue,red,white volume) value of M30, and we can passed it to M1 TF. But, the we can not compare it with the volume average of M1 as it is (the average on M1 must be smaller). So, i try just to get the biggest average value in M1 during that M30 candle time, and if the blue/red of M1 >= biggest average of M1 volume, i get the price and time, and send back to M30. Do not know this is a good idea or not. Any comment is welcome, thanks … Edit: although we have the MTF version of Gadi_NormalizeVolume or MTF version of sx_volumePerSession, this problem is still exists.
When in M30, start summing up volumes of M1 candles (from oldest to newest) of that given M30 candle until the sum exceeds the value of M30 average. Paint the dot at the close price of the last summed M1 candle. V.
Wow, thanks a lot Vlan. Really great idea
And thanks for bugs reporting on calling blue/red/white histogram. I have changed it in all of my new versions …
Volume per Session: Accumulate all Volume Histogram bars per Start/End of each session (London, London+NY, NY, Asian) for the last 5 days. Divide by number of bars per the relevant session*5, making it weekly average per session. That’s the avg. when Volume >= should generate a dot or alert or both. No need to wait for bar Close. G.
This is really really great G, thanks a lot.
I know, I tried to answer VlanFx & smallcat.
That’s what I assumed. Just pointed to my indicator because it might save them some work.
s.
A good trader is a realist who wants to grab a chunk from the body of a trend, leaving top- and bottom-fishing to people on an ego trip. (Dr. Alexander Elder)
@gg53: Yesterday I read again over this thread and a questions arose: Let’s assume we want to trade in the M1 chart and we have five channels regarding your rules – one M1, one M5, one M15, one M30, and one H1. How would you interprete the situation if the M1 sticks out of the M5 channel (on its upper site) but the M5 channel itself is at the bottom of the M15, M30, and H1 channels. As we trade the M1, would you actually look at all higher TF channels or would you focus your analyses only on the current TF (M1 in our case) and the next higher one?
Thanks in advance for clarification!
- You must be logged in to reply to this topic.