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)
@Rui S - Thanks for the reply. So far today's tests with V15 - I haven't found issues and would be curious to know the results from your side tomorrow.
@Rui S - Related to this - If you notice this issue with V15 ( just in case ) - Please post the following information(all of the 4 points are important). Crosshair is likely to show the timestamp of the bar:
- T&S record
- Timestamp of the bar where it is marked incorrectly
- Timestamp of the a bar prior & a bar after the incorrectly marked bar.
- Timestamp of the bar where it should have been actually marked.
It is official now: there are no repetitions of plotting anymore, even with fast chart printing. This is great.
However we still have the issue of the "misplaced" plotted trades. It is happening exactly the same way with versions 14, 15 and 16. They are running side by side and I can't see any difference between them.
The good news is this seems to be the only issue left now. All the rest seems to be working very well.
If you allow me to express my humble opinion, it gives me the idea that upon price thrusts conditions the bar that should be painted "slides" to the next bar, leaving the number of contracts at the correct price level but vertically aligned with the wrong painted bar.
Maybe my computer has too much oil...
And again, the difference of time tags seems to be 1 millisecond...
I am attaching some edited screenshots in two posts, to try to transmit you an idea on what I am seeing here.
I am not sure exactly what you mean with "T&S record"; I suppose it is the T&S window I am attaching. If not, please let me know.
Please let me know if I can help any further somehow.
@Rui S - Thanks for the update. Please use the version 15 as a baseline going forward until we have a new version.
To me it appears like an inherent nature of the way Sierra handles the range charts and nothing to do with speed of the market(have to analyze further to confirm). Please see if you notice similar issue with any other type of charts ( Tick charts for example ).
As you can see the timestamp on the crosshair shows the timestamp rounded to second for the first tick bar ( where milliseconds are being truncated ). Coming up with a solution to this specific open issue might be a bit tricky (doable but would be expensive from CPU point of view - I would imagine).
I was testing with a Tick chart and the issue shows the same way. It seems it's not exclusive of the Range charts. Please take a look at the attached screenshots with examples, the same trades misplaced in both Tick and Range charts.
Regarding the speed of the market, I don't know if it causes the problem or not but I am sure that it happens much more when the price is moving with thrusts. Many times the price have sudden thrusts even when the market is slow. This happens very often with CL.
So I will be using version 15 as a baseline as you suggest until further instructions.
@Rui S - Thanks for the update. So only open issue at present is few of the trades are being marked to a bar next to it ( offset by 1 millisecond ). Would review and see if I can take care of this issue by other means. Please continue to use v15 until then.
@RuiS - taking v15 as baseline - Would you please check the following 2 versions(v17 & v18) and let me know your observations? These versions are meant to address the one pending bar shift issue ( now that all the other issues are sorted out).