PROF TOKEN IMBALANCE

Login or Register

Please login or register in order to view and post in the Forum.

24 posts / 0 new
Last post
Alex Savin
Last seen: 4 years 5 months ago
Joined: 08/31/2016 - 10:57
Figured that out and edited

Figured that out and edited my second post, but thanks anyways, outstanding customer service!

cpayne
Last seen: 1 year 7 months ago
Joined: 03/30/2009 - 00:00
Large Imbalance Shift

Chart below shows on a 1-min chart how the shifts in VPOC were accompanied by large imbalance shifts...

uri101
Last seen: 6 years 3 months ago
Joined: 05/14/2014 - 00:00
how to use it

did not find the way to use this information in real time,yet

WAYNE CHANDLER
Last seen: 3 years 4 months ago
Joined: 09/09/2015 - 04:25
Developing Imbalance on a Boundaries chart

Hi Chad I wonder if you could have a look at a chart which I am about to post. As illustrated in the charts which you have posted on this topic, I have used a custom indicator to plot the Developing Imbalance on the symbol BD#. I have also added the Boundaries RTX extension to the chart (which is an extension that I use extensively) and the "Time per Profile>Custom" drop down box is set to 'IsBoundaries' as it should be. However you will notice that the Imbalance% printed by the Profile does not match the Developing Imbalance % generated by the custom indicator. I am assuming that the Developing Imbalance calculation is based on VPOC at the profile.
https://www.linnsoft.com/charts/wayne-testing-imbalance-bd

cpayne
Last seen: 1 year 7 months ago
Joined: 03/30/2009 - 00:00
Developing Imbalance in PROF

Wayne, 

The TPO Indicator used in your custom indicator has no knowledge of the Boundaries indicator and now way to link to Boundaries.  The Profile Indicator will need to be enhanced with a "Developing Imbalance" result option when PROF is used in RTL.  With that in place, you can link your PROF to the Boundaries indicator and everything will all into place.  I will try to get to this during the 13.1 beta cycle.  I think it's probably time to add a more general purpose "Developing Data" result option, and then allow user to choose what developing data they want from another listbox (VPOC, Imblance, High, Low, Volume, Delta, etc).

cpayne
Last seen: 1 year 7 months ago
Joined: 03/30/2009 - 00:00
Developing Data - Coming in 13.1

Done for 13.1.

If you have other developing data you'd like to see in this list, let me know.

WAYNE CHANDLER
Last seen: 3 years 4 months ago
Joined: 09/09/2015 - 04:25
Preferences for RTL token PROF

Thanks for the feedback Chad..........I have been meaning to ask you about this topic for weeks! The developing data that interests me personally is Imbalance and Delta on the PROFILE and I see from the list above that both of these have been included in 13.1.

cpayne
Last seen: 1 year 7 months ago
Joined: 03/30/2009 - 00:00
Delta Above/Below POC

I have also added options for Delta Above/Below the POC.

WAYNE CHANDLER
Last seen: 3 years 4 months ago
Joined: 09/09/2015 - 04:25
Delta Above/Below POC

Amazing! I am always blown away by the degree and sophistication of the technical and programming support available with Linnsoft. Thanks Chad, your platform is the finest by far of all the platforms that I have ever used, especially for traders interested in Market Profile theory.

WAYNE CHANDLER
Last seen: 3 years 4 months ago
Joined: 09/09/2015 - 04:25
Calculating Delta & Imbalance using PROF

Hi Chad,
I am using 13.1 beta to calculate Delta & Imbalance using the updated PROF in RTL token. I have used the new "Developing Data" result in PROF to create two new RTL, Custom Indicators which I have called Delta_PROF and Imbalance_PROF. I have then used the RTX PaintIndicator to plot these two, new Custom Indicators on a 16min BD# chart, see https://www.linnsoft.com/charts/wayne-testing-delta-imbalance-bd. As you can see the chart has RTX Boundaries added, but the Delta & Imbalance readouts on the Custom Indicators do not agree with the corresponding readouts on the Profile indicators. What am I doing wrong..........I must be doing something wrong, but I can't work it out.

Pages