this library can draw typical liquidation lines, which can be called e.g. by indicator signals You can see the default implementation in the lower part of the code, starting with RUNTIME Don't forget to increase max lines to 500 in your script. It can look like this screenshot here, with only minor changes to your executing script. The base is the same
릴리즈 노트
⋅
v2 Runtime Demo update, no function changes
릴리즈 노트
⋅
This update mainly does 2 things:
Deleting lines which are just wasting free lines (selectable min length, -1 to disable (standard value in the function)
Speeding up the runtime by filtering doublegets inside the liqline_update by a additional if branche for preselection gets are slow, so why calculate when not needed.
small fixes: typo on bollinger block always requesting BB Nr. 1 instead of 1 2 3
v3
Added: f_getbartime() this does give you the average time per bar from a sample of 100 bars
Updated: f_liqline_update(_Liqui_Line, _killonlowhigh, _minlength, _timeperbar) Parameters: _Liqui_Line (Liquidationline[]) _killonlowhigh (bool) _minlength (int) _timeperbar (float) minlength and timeperbar is added but not needed to function correctly. aware this adds some repainting behavior as it deletes lines after detecting
Hey bro, Do you know if there's a way to merge the near lines, to make a little cleanest the view of the chart?
djmad
⋅
@RenzoTrader, there is sure a way when i decide to code it, little bit lacking of time for the moment... may in a future update i accumulate the data and make the line 1 point thicker each time there is a hit on the same level
RenzoTrader
⋅
@djmad, Can you give a little example of how to make it? thank you man
RenzoTrader
⋅
@djmad,Do you have an idea about how to get the most important ones, and only render that lines on the chart, based on the posibilities of getting the most exact liquidation lines? I appreciate your time
djmad
⋅
@RenzoTrader, yes i have ideas, you need to slice the pricebase doing a decissiontree to sort and averaging with currently living liquidations. Estimate: codelines of the library times 3 to times 4
RenzoTrader
⋅
@djmad, Hey there! I'm a bit puzzled about this part, and I was wondering if you might have a guide or something that could make it a bit clearer? Your help has been amazing with this library, and I really appreciate it!
you see, i use that completly different, 8 leverages multiple different indicators creating this picture.
liquidation lines will never show an exact turning point, more a range as you dont know what x5 x10 x2 x3 the marketmakers want to kill this time to get liquidity. so it gives estimates, why you want an exact estimate which may is not true...
count as example elliot waves, when fir retrace/extensions comes dear such a liquidity-zone its interesting to trade there
Marco189
⋅
Hi, thanks for the great indicator. I entered it in the editor and changed the library line as you mentioned but am getting the following error message: Only libraries can contain exported functions What would need to be done in this case? Thank you!