YuClusters
325 USD
Demo heruntergeladen:
11 283
Veröffentlicht:
7 Februar 2014
Aktuelle Version:
7.27
Keinen passenden Roboter gefunden?
Geben Sie Ihren Eigenen in Auftrag
auf Freelance!
Gehen Sie zu Freelance
Geben Sie Ihren Eigenen in Auftrag
auf Freelance!
Wie man einen Roboter oder Indikator kaufen kann
Starte Deinen EA im
Virtual Hosting
Virtual Hosting
Teste einen Indikator/Roboter vor dem Kauf
Möchtest Du Geld im Market verdienen?
Wie man Produkte richtig präsentiert
Sie verpassen Handelsmöglichkeiten:
- Freie Handelsapplikationen
- Über 8.000 Signale zum Kopieren
- Wirtschaftsnachrichten für die Lage an den Finanzmärkte
Registrierung
Einloggen
Sie stimmen der Website-Richtlinie und den Nutzungsbedingungen zu.
Wenn Sie kein Benutzerkonto haben, registrieren Sie sich

Добавлена возможность изменять произвольные профили.
Added the ability to modify custom profiles.
Thanks for the message, I’ll fix it today.
Thanks for the message, I’ll fix it today.
Ok, thanks Yuri
Show what you did so I could repeat your situation.
Perhaps you started another indicator/program that deleted YuClusters objects from the chart.
Hi Yury,
Is it possible to access the net volume delta at each price level from within an EA? (maybe using the new alerts or consuming a buffer)?
Thanks!
Is it possible to access the net volume delta at each price level from within an EA? (maybe using the new alerts or consuming a buffer)?
Values in the profile cannot be obtained in alerts and in external EA's.
The YuClusters does not use indicator buffers, as cluster data cannot be described by indicator buffers and this data is not tied to the chart timeframe.
Values in the profile cannot be obtained in alerts and in external EA's.
The YuClusters does not use indicator buffers, as cluster data cannot be described by indicator buffers and this data is not tied to the chart timeframe.
Would it be possible to add an alert condition for this?
Something like "If delta@price > -10 then trigger alert"
I can then watch this alert and build an updating delta history in a hashmap.
Thanks!
Would it be possible to add an alert condition for this?
Something like "If delta@price > -10 then trigger alert"
I can then watch this alert and build an updating delta history in a hashmap.
I will add new conditions to the alerts, such as:
volume ---> left (or right) profile ---> delta (or sum, ask, bid) >/< value.
I will add new conditions to the alerts, such as:
volume ---> left (or right) profile ---> delta (or sum, ask, bid) >/< value.
That would be amazing. Please also add alert for cluster delta divergence - so its visible on native chart
Thats's also a very handy tool to find trapped traders
Also, if you could add : Moving average on volume sub window : so it's easy to visually identify above average volume in yuclusters window.
Please see example screenshot from another indicator
That would be amazing. Please also add alert for cluster delta divergence - so its visible on native chart
Thats's also a very handy tool to find trapped traders
Also, if you could add : Moving average on volume sub window : so it's easy to visually identify above average volume in yuclusters window.
Please see example screenshot from another indicator
This can be added in a future version.
This can be added in a future version.
Thank you Yury!
If you are considering features for a new update...
Thanks!
Добавлена возможность изменять произвольные профили.
Added the ability to modify custom profiles.
Hi Yury, what is the simplest way to activate custom profile. What do I click to consistently make custom profiles?
1) The closing time of the current cluster can be known only for a cluster of type timeslots.
And I really do not see much sense in this information. Why do you need to know the closing time for example for M1 or M21.
2) I will add an alternative way for building custom profile, for example, pressing the key "P" button and drawing with the left mouse button.
Hi Yury, what is the simplest way to activate custom profile. What do I click to consistently make custom profiles?
Press right button and move, then click "OK."
1) The closing time of the current cluster can be known only for a cluster of type timeslots.
And I really do not see much sense in this information. Why do you need to know the closing time for example for M1 or M21.
2) I will add an alternative way for building custom profile, for example, pressing the key "P" button and drawing with the left mouse button.
Thank you Yury!
Добавлена возможность изменять произвольные профили.
Added the ability to modify custom profiles.
1) The closing time of the current cluster can be known only for a cluster of type timeslots.
And I really do not see much sense in this information. Why do you need to know the closing time for example for M1 or M21.
2) I will add an alternative way for building custom profile, for example, pressing the key "P" button and drawing with the left mouse button.
Using P will make great usage. Thanks for considering that.
Wrt cluster closing time - many strategies are dependent on it. Example : cluster closes with high volume and high delta divergence could signals a reversal. So if it's known how many ticks/range/time is left in closing of cluster, it'll be very helpful.
This will also make a great event to consume programatically. An event for cluster open and an event for cluster close, with relevant information : like what was it's volume, delta, open, close, high, low etc.
I hope it helps :)
Cheers!
Hi Yury,
The imbalance levels is a bit unclear to me - how it works. Can you please share more about the following questions
For example in this screenshot, there are 2 sell imbalances marked
As you can see, my volume imbalance % is 400% and for plotting the imbalance level, it's 500%
Sell imbalance 1 : The tick above 50x80 is 0x7, hence there's a sell imbalance of >500% (50 > 7*500%). But the sell imbalance drawn is shown blue because 80 is bigger in 50x80 level. I was expecting a red level to show up here.
Sell imbalance 2 : The tick above 458x251 is 253x108. There is a sell imbalance (of 400%), but not enough to plot a sell imbalance level of 500% - hence the level should not appear.
Thanks