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)
Earlier I've proposed to add the option of making the dot as a ring. And the heavier the "clash" the thicker the ring.
As I'm mainly looking for areas of collisions the current design (be it gradient, solid or pie) would hog up too much areas of display. I find myself having to keep adjusting transparency and dot size when I zoom in and out.
by having a ring setting with variable thickness I could set the dot size smaller and still see size of the collisions, adding clarity to the chart. The ring can still work in the form of gradient or pie, but it would appear as outline rather than fill.
One other suggestion, it would be great if the price column can be adjusted for size with option to not display xx digit (say in the case of euro or yen it gets long)
If other users have other ideas please chime in.
Thanks for always listening.
Can you help answer these questions from other members on NexusFi?
Please could you make the close tab " X "show on right click as it takes up 1/3 of tab ,I am continually losing the data with an inaccurate click and have to reopen
I have copied an instance where i would consider an iceberg is in action on the offer at 3389 in the Estoxx.
But my understanding is that the quick release up of the offer to 90 and then straight back down will kill the cumulative count.
I think consideration could be given to having the the option to continue the iceberg count if say the offer is pulled within x milliseconds, I see this type of action frequently.
Trading: Emini ES, Currency Futures & US Treasuries
Posts: 12 since Nov 2016
Thanks Given: 6
Thanks Received: 5
Hello, I have couple questions:
1. What's the difference between Bookmap and S5 Bookmap other than the fact that S5 Bookmap is associated with Stage 5? Is there any additional features to S5 Bookmap that the standard Bookmap doesn't have? Can S5 Bookmap be obtained by anyone that doesn't have account with S5 as well?
2. I have heard from many that because Interactive Brokers provide only snapshot data (4 times per second) and not Tick Data, there is a widespread belief that IB Data is not suitable for Volume related studies. If so, how come Bookmap considers IB Data suitable for Bookmap? Doesn't the DOM, the Volume Dots, Heat Map, CVD require Tick Data?
This thread is intended to attend to the needs and questions of our community of traders. The thread will cover various issue related to the operation and use of Bookmap such as:
1. Use of …
Answer to #1(from previous response, just so others have it here as well)
There is no functional difference between S5 Bookmap and Bookmap. The S5 Bookmap is a white label for Stage Five Trading brokerage. However, now due to Bookmap's new API, it is now possible for anyone to write proprietary Trading Strategies and Indicators within Bookmap. S5 has developed their own features and offer it for their S5 Bookmap clients. It is a beta offering. The Bookmap API will be available to all shortly, in Q1 of 2017.
Answer to #2
Bookmap supports 10 different data feed providers that are different from each other; it's up to the user to decide which data he/she wants to use. Interactive Brokers updates data 4 times per second. However, the data packet still contains all the data -- it's just that it has been aggregated into 250 millisecond packets. It doesn't mean that the feed doesn't contain reliable data, but details in the data will be lost due to the aggregation.