Login Page - Create Account

Support Board

Date/Time: Thu, 29 Oct 2020 07:16:36 +0000

Market Depth Historical - Bug with new logic when scrolling

[2020-09-21 18:02:05]
nosast - Posts: 191 | Ending Date: 2020-10-31
The new percentage options for coloring liq are great and work well when set to all bars. Setting it to only visible bars and then srcolling to an area with no liq will mess up the coloring and even changes the set min threshold value. This is not only happening for me but also with other guys using Sierra in our trading group.

For now we are working with all bars but it would be even better to have only visible bars for the logic.

Would be nice if you find some time to look into it.

[2020-09-21 18:51:00]
John - SC Support - Posts: 3016 | Ending Date: 2020-10-31
What you are stating is correct functioning. If you have the Value Type for Lowest Quantity for Coloring set to Actual Value then if you get to a region where the Maximum value is smaller than what is set for the Lowest Quantity for Coloring, then it will set that Lowest Quantity for Coloring to be the Maximum minus 1. This ensures that the Lowest Quantity for Coloring is never greater than the Highest Quantity for Coloring / Maximum Market Depth.

In this case we recommend that you use the Percentage of Maximum Depth for the Value Type instead. The Lowest Quantity for Coloring will then stay as a constant relative value as you scroll through the chart.

Refer to the information here:

[2020-09-21 18:56:46]
nosast - Posts: 191 | Ending Date: 2020-10-31
Hi John,

thanks for your quick reply. I found that out already and I know that when scrolling back to an area with no liq the thresholds will change. But shouldn't they then revert back when scrolling to the end of the chart again?
[2020-09-21 18:59:40]
nosast - Posts: 191 | Ending Date: 2020-10-31
Another thought: Instead of using the max depth wouldn't it make sense to use some sort of average for the depth? Maybe the average of the top 10 levels just to smooth out such levels with a very outstanding bid/offer like we currently see in the ES at 3212.
[2020-09-21 19:14:22]
User267701 - Posts: 63 | Ending Date: 2020-09-30 [Expired]
i always asked myself, why sc doesnt do it like bookmap, which has a flawless algo regarding autostacking of liquidity.
[2020-09-21 19:17:31]
User590236 - Posts: 12 | Ending Date: 2020-10-25 [Expired]
Having the same issue here the scaling is awesome and thank you guys for implementing this but it seems to need a little work with the scaling. Have been testing it out all day and the only complaint is when a larger offer/bid comes in that is larger than average it throws off the whole calculation. Perhaps a max % for orders larger than X would solve it?

Thanks a bunch for implementing this!
[2020-09-21 20:24:19]
John - SC Support - Posts: 3016 | Ending Date: 2020-10-31
We have been wanting to implement some kind of factor to apply to determine the Maximum Depth by removing outliers for some time. We will see if we can get to this soon.
[2020-09-21 20:56:29]
User590236 - Posts: 12 | Ending Date: 2020-10-25 [Expired]
Awesome , Thanks John!
[2020-09-23 13:26:47]
nosast - Posts: 191 | Ending Date: 2020-10-31
I'm using actual values for now. But still when scrolling to an area with no liquidity (SC is off overnight) the actual min number changes and messes up the logic.

How can I prevent that to just keep them fixed for now?
[2020-09-23 13:53:58]
John - SC Support - Posts: 3016 | Ending Date: 2020-10-31
This occurs because the Maximum value in the area in which you are looking (you must be using Visible Bars) has become smaller than the value that you have set for the Lowest Quantity for Coloring and/or Highest Quantity for Coloring. Therefore, we are updating these values to show you what is actually being used. Refer to the information on this here:

We will have to think about what we need to do to change this around.
[2020-09-23 16:29:50]
John - SC Support - Posts: 3016 | Ending Date: 2020-10-31
We have updated the software so that the Highest and Lowest Quantity for Coloring Inputs will not change based on the actual values that are being used. This will allow values to be set that do not change, so you can scroll back and forth through the chart and get back to the same state you were in previously.

This change will be in the next Pre-Release (v 2173).

We do want to add some additional information so the actual Minimum and Maximum values that are being used can be reviewed. We will work on this, but it may be a week or more as there are some other items we need to finish up first.
[2020-09-23 22:36:10]
nosast - Posts: 191 | Ending Date: 2020-10-31
Thanks John. Sounds great and I will test v2173 once available.

To post a message in this thread, you need to login with your Sierra Chart account:


Login Page - Create Account