MBO Bundle addon
Posted: Mon Apr 06, 2020 1:05 pm
your blog has a description of this addon
1) "he S-I Tracker precisely displays the transactions of Stop Orders and Iceberg Orders with 100% accuracy."
2) "The SI Tracker also identifies Iceberg Order transactions. No more guesswork is required since CME MBO data assigns iceberg order transactions with unique OrderIDs. Note the Bookmap Global + version already includes iceberg detection, however this indicator is based on microstructural events and false positives can occur. The SI Tracker displays Iceberg transactions with 100% certainty due to MBO data. "
That is, you yourself confirm that the Iceberg algorithms built into the BOOKMAP are not always correct and are likely to mislead the user at any time?
this begs the following question:
why do you know that your algorithm works with errors, do not fix it in BOOKMAP itself?
The CME exchange delivers the same MBO data to all intermediaries
if some suppliers are unsuitable for analyzing iceberg due to the fact that they give the user a low-quality date, then there can be no conventions - if the market date is low-quality then any algorithm there will show not what it really is
there are not so many high-quality suppliers and it is enough to warn users not to mislead them
I don’t understand why you have 3 algorithms that are not clear what they show if there is an exchange algorithm (native) and there are synthetic icebergs CME exchange ?(dxFeed provider indicates the same)
I do not understand why you did not introduce the algorithm (native) patented by the CME exchange for all suppliers with a high-quality market date? default
do you use the algorithm(native) described by dxFeed? (dxFeed API) dxFeed API
And now you are selling an algorithm (native) for the Rithmic
This is some kind of nonsense.
-------------------------------------------------------------------------------------------------------
Squeeze (market or market stop orders) is more clearly visible where?
1) I see the size of the trade
2) I see the hidden part
3) I see how many glass levels the market went through
4) I can turn on the display of point 1 of the order and the last one where the squeeze ended
5) I can filter the sizes to avoid a bunch of junk on the chart
you need to separate the market orders so that there is no confusion (passive and squeeze) and make a different depth of color so that they do not overlap (for those who want to have this kind, this is like an alternative view, your standard spread with compression is an excellent type of chart)
there is another order in the picture (108)
this is not a squeeze, this is an ordinary passive order, passed per unit of time and at 1 price
I can also select such orders by size
this view is suitable for graphs of 1min and higher
no need to reinvent the bike with stripes and sell it as a separate 100% stopmarket-iceberg indicator
it has long been done by other developers
combining everything in an iceberg order is a very stupid approach,you plus those who know something and fools
Squeeze
all this is implemented by other developers. and if you will divide such things into pieces and sell as separate 100% indicators, I think that your users will simply leave
1) "he S-I Tracker precisely displays the transactions of Stop Orders and Iceberg Orders with 100% accuracy."
2) "The SI Tracker also identifies Iceberg Order transactions. No more guesswork is required since CME MBO data assigns iceberg order transactions with unique OrderIDs. Note the Bookmap Global + version already includes iceberg detection, however this indicator is based on microstructural events and false positives can occur. The SI Tracker displays Iceberg transactions with 100% certainty due to MBO data. "
That is, you yourself confirm that the Iceberg algorithms built into the BOOKMAP are not always correct and are likely to mislead the user at any time?
this begs the following question:
why do you know that your algorithm works with errors, do not fix it in BOOKMAP itself?
The CME exchange delivers the same MBO data to all intermediaries
if some suppliers are unsuitable for analyzing iceberg due to the fact that they give the user a low-quality date, then there can be no conventions - if the market date is low-quality then any algorithm there will show not what it really is
there are not so many high-quality suppliers and it is enough to warn users not to mislead them
I don’t understand why you have 3 algorithms that are not clear what they show if there is an exchange algorithm (native) and there are synthetic icebergs CME exchange ?(dxFeed provider indicates the same)
I do not understand why you did not introduce the algorithm (native) patented by the CME exchange for all suppliers with a high-quality market date? default
do you use the algorithm(native) described by dxFeed? (dxFeed API) dxFeed API
And now you are selling an algorithm (native) for the Rithmic
This is some kind of nonsense.
-------------------------------------------------------------------------------------------------------
Squeeze (market or market stop orders) is more clearly visible where?
1) I see the size of the trade
2) I see the hidden part
3) I see how many glass levels the market went through
4) I can turn on the display of point 1 of the order and the last one where the squeeze ended
5) I can filter the sizes to avoid a bunch of junk on the chart
you need to separate the market orders so that there is no confusion (passive and squeeze) and make a different depth of color so that they do not overlap (for those who want to have this kind, this is like an alternative view, your standard spread with compression is an excellent type of chart)
there is another order in the picture (108)
this is not a squeeze, this is an ordinary passive order, passed per unit of time and at 1 price
I can also select such orders by size
this view is suitable for graphs of 1min and higher
no need to reinvent the bike with stripes and sell it as a separate 100% stopmarket-iceberg indicator
it has long been done by other developers
combining everything in an iceberg order is a very stupid approach,you plus those who know something and fools
Squeeze
all this is implemented by other developers. and if you will divide such things into pieces and sell as separate 100% indicators, I think that your users will simply leave