Dark Theme
Light Theme
Trading Articles
Article Categories
Article Tools
Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to
register in order to view the content of the threads and start contributing to our community.
It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Buying/Selling Pressure...
Updated February 17, 2018
trending_up
12,748 views
thumb_up
6 thanks given
group
7 followers
forum
24 posts
attach_file
0 attachments
Buying/Selling Pressure...
December 27th, 2017, 06:20 PM
NY, NY
Posts: 68 since Dec 2011
Thanks Given: 27
Thanks Received: 19
wldman
are elite.
No, that is not what I am saying. I am saying that the code snippet that you posted does not make any sense to me. The
context that I have from you is still unclear. The tiny little pic does not describe what you are trying to look at.
I digress when I assume that your ideas about volume are consistent with mine...or even valid at all. Buy when volume is taking offers in other words buy when buying is the way and the opposite are not things that require an indicator.
Yes that is a typo, the + sign in the bottom statement is correct. The equals is a typo.
The mystery is why in the element you ask about that the calc is different for + and -. You can use a derivative for the calc depending on what you want to view specifically, but to use different calc methods in the same statement does not work.
I was asking about that in case you knew the reason (I do not) or to prompt you to do the math/code work, rather than me to divide the day to figure out the why of that snippet of code.
I'm still unsure of what you are looking at or for and I'm not sure anymore that you know. When I ask you to describe it or show it, you seem reluctant. Is this a secret or are you not sure? Either is fine. I'm just looking for the info that I would need to help or to point you to someone on
FIO that might know and care.
Go through the code snippet and determine what that equation is showing. Is that what you want to show? Why? Or, if not, what is it that you want to show? Why? This is how to diagram a view that can be specified to someone (not named Dan) that knows how to code.
I do not mean to go wldman on you but I won't use my understanding of what you are looking for, because I think mine is better. So I'm asking you to take a look and then say wait...mine does this calc and it is important because it shows this. If I do that work I might solve a problem with how something displays but I dont help you. Its a right path wrong mountain kind of thing.
Take a look at the full chart that I shared and the brief notes. Those explain and invite questions. Those tiny little buttons in the fractional chart that you showed dont do anything for the viewer because they still have to guess at context and method. I don't mean to be terse, but I keep asking what this is and how you consider it and you
bid me back rather than answer. My time is extremely valuable. I'm trying to help/share because others have done so with me. Past that I would perfect my application of a volume/price indicator based on accumulated knowledge of others. Peace man.
Dan
Hi Dan,
Sorry for the delay with this reply. Below is the updated code for the indicator reflecting the changes you suggested...
Code
input period = AggregationPeriod.DAY;
def O = open(period = period);
def H = high(period = period);
def C = close(period = period);
def L = low(period = period);
def V = volume(period = period);
def O1 = open(period = period);
def H1 = high(period = period);
def C1 = close(period = period);
def L1 = low(period = period);
def V1 = volume(period = period);
#def SV = -V * (H - C) / (H - L);
#def BV = V1 * (C1 - L1) / (H1 - L1);
def BV = H+L+C > H1+L1+C1; # accumulation
def SV = H+L+C < H1+L1+C1; # distribution
AddLabel(yes, "Buy ", if BV > SV then Color.GREEN else color.GRAY);
AddLabel(yes, "Sell", if BV < SV then Color.RED else color.GRAY);
Whereas I was getting 1 Green "Buy" light before the changes for all tickers, I now get 2 Gray lights for all tickers checked See attached pic...
Here's the macro-view:
Thanks for the link to your Journal. I'm looking forward to taking a look...
I am also a big believer in "paying it forward ". If I've been difficult to work with, please accept my apologies...
Thanks again for your insights, efforts and willingness to expend your valuable time to this ongoing endeavor. I really do appreciate it!
Matt
Can you help answer these questions from other members on NexusFi?
Best Threads (Most Thanked) in the last 7 days on NexusFi
December 28th, 2017, 09:05 AM
Chicago Illinois USA
Legendary Market Wizard
Experience: Advanced
Broker: IB, ToS
Trading: /ES, US Equities/Options
Frequency: Several times daily
Duration: Hours
Posts: 3,507 since Aug 2011
Thanks Given: 2,046
Thanks Received: 9,491
and appreciate the expanded comm. I will try my best to describe my understanding and see if we can figure it out when Im clear after the open. D
December 28th, 2017, 09:15 AM
Chicago Illinois USA
Legendary Market Wizard
Experience: Advanced
Broker: IB, ToS
Trading: /ES, US Equities/Options
Frequency: Several times daily
Duration: Hours
Posts: 3,507 since Aug 2011
Thanks Given: 2,046
Thanks Received: 9,491
December 28th, 2017, 09:42 AM
Chicago Illinois USA
Legendary Market Wizard
Experience: Advanced
Broker: IB, ToS
Trading: /ES, US Equities/Options
Frequency: Several times daily
Duration: Hours
Posts: 3,507 since Aug 2011
Thanks Given: 2,046
Thanks Received: 9,491
On the code changes. I was not suggesting that you switch code, rather I was asking why the code you displayed was using a non uniform method and an alternative calculation for VForce...which is an element defined by Klinger as what I posted.
That code is using one calc for buy volume and another calc for sell volume. Even if by design, that is not generally accepted or reliable.
I thought maybe someone was jacking with you, but now it seems that you are jacking with me.
The ToS forum will snap that off for you, yet you have not asked in there?
I have to move on from this.
Dan
December 28th, 2017, 11:59 AM
NY, NY
Posts: 68 since Dec 2011
Thanks Given: 27
Thanks Received: 19
wldman
and appreciate the expanded comm. I will try my best to describe my understanding and see if we can figure it out when Im clear after the open. D
Quoting
On the code changes. I was not suggesting that you switch code, rather I was asking why the code you displayed was using a non uniform method and an alternative calculation for VForce...which is an element defined by Klinger as what I posted.
That code is using one calc for buy volume and another calc for sell volume. Even if by design, that is not generally accepted or reliable.
I thought maybe someone was jacking with you, but now it seems that you are jacking with me.
The
ToS forum will snap that off for you, yet you have not asked in there?
I have to move on from this.
Dan
Hi Dan,
First and foremost, I am definitely NOT jacking with you. When I say that I really appreciate your time and attention to this, I really mean it...
Communication in this manner is very difficult with the lack of auditory and visual cues. As a result, misunderstandings are bound to happen...
The difference between what we're looking at is the option to view extended hours data in TOS Chart Settings...
As a result, we are looking at different KVOs. Couple that with the fact that whenever I create a derivative of an original TOS study, I give it a different name. Therefore, VForce2 = KVO...
I apologize for my not properly adhering to standards/uniformity, especially since you were trying to establish common ground...
I understand that you have to move on. I just want to thank you again for expending the time, effort and energy to try and help me. Per your suggestion, I will check out the TOS forum and see if there is an answer there...
Wishing you and yours a very Healthy, Happy and Prosperous New Year
Best Regards,
Matt
December 28th, 2017, 12:11 PM
Chicago Illinois USA
Legendary Market Wizard
Experience: Advanced
Broker: IB, ToS
Trading: /ES, US Equities/Options
Frequency: Several times daily
Duration: Hours
Posts: 3,507 since Aug 2011
Thanks Given: 2,046
Thanks Received: 9,491
Ive got a hundred plates spinning. I appreciate your sincerity and I'll be back to help you with this when the plates are in the cupboard or on the floor.
BTW volume from after hours session on equities HAS TO be eliminated from consideration. It's a quagmire man.
Dan
December 28th, 2017, 01:46 PM
NY, NY
Posts: 68 since Dec 2011
Thanks Given: 27
Thanks Received: 19
wldman
Ive got a hundred plates spinning. I appreciate your sincerity and I'll be back to help you with this when the plates are in the cupboard or on the floor.
BTW volume from after hours session on equities HAS TO be eliminated from consideration. It's a quagmire man.
Dan
Hi Dan,
Thanks for getting back to me. I certainly understand the need to attend to more pressing matters. No problem...at your convenience...
As far as the after hours session volume, I will adjust things on this end. Thanks for the tip
Matt
January 14th, 2018, 12:10 PM
NY, NY
Posts: 68 since Dec 2011
Thanks Given: 27
Thanks Received: 19
January 20th, 2018, 04:42 PM
NY, NY
Posts: 68 since Dec 2011
Thanks Given: 27
Thanks Received: 19
For those whom might be interested, thanks to a generous Thinkscripter, here is the final code:
Code
input vPeriod = AggregationPeriod.HOUR;
def O = open(period = vPeriod);
def H = high(period = vPeriod);
def C = close(period = vPeriod);
def L = low(period = vPeriod);
def V = volume(period = vPeriod);
def SV = V * (H - C) / (H - L);
def BV = V * (C - L) / (H - L);
AddLabel(yes, "Buy ", if BV > SV then Color.GREEN else color.GRAY);
AddLabel(yes, "Sell", if SV > BV then Color.RED else color.GRAY);
January 20th, 2018, 04:58 PM
Chicago Illinois USA
Legendary Market Wizard
Experience: Advanced
Broker: IB, ToS
Trading: /ES, US Equities/Options
Frequency: Several times daily
Duration: Hours
Posts: 3,507 since Aug 2011
Thanks Given: 2,046
Thanks Received: 9,491
Happy this is working out for you.
Is the thing you are working on the KVO? I thought it might be but I'm not a code guy. Post a pic of what you have working, love to see it.
Dan
Last Updated on February 17, 2018