Support Board
Date/Time: Wed, 27 Nov 2024 15:37:59 +0000
Post From: Drawn VbP
| [2023-08-11 15:53:09] |
| JohnR - User831573 - Posts: 306 |
|
In what I am in the process of creating / implementing, Using Vol by Price study will break the current architecture. I am looking to have on avg 15 locations on a chart each RTH day where I would a need VAH, VAL, POC from a 1 - 4 bar Vol Profile. I would run out of studies @ 255. In doing the math, that only gets me approx 17 days before I can no longer add a new one. Additionally, the load on calculating a study, that has that much capability/overhead, would be tremendous every update on the chart, vs calling the sc.newVolProfile_Func_ only once to create the drawing objects from my script. Possible solutions - I use drawing tools, and create my own 'stuff' on the chart. I can and am willing to do this. I've done it before. But currently SC at the ACSIL function level, only provides this info for a single bar. from docs... The sc.GetPointOfControlAndValueAreaPricesForBar() function gets the price values for the Point of Control, Value Area High, and Value Area Low into their respective variables, for the given BarIndex and ValueAreaPercentage. I am requesting you, SC either enhance the current function to have either # of bars or start-end bar # as additional input and calculate the Vol profile function return the POC/VAH/VAL from the multiple bars. The logic for this is already being done within the current Volume Profile study/tool. Also, I have read the docs on calculating a vol profile, I could do this, but since you already have this working as a study, it should be fairly easy to grab the additional logic for multiple days. Hope you consider this, as I think this would be useful to others as they work with orderflow concepts. Code snippets from anyone would be appreciated around the logic for POC/VAH/VAL. I already have code working that accesses the price levels, staring with SC example. JohnR Date Time Of Last Edit: 2023-08-11 15:58:37
|