+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
bug_report_small.png
Open Bug report MC-2297

Playback: entire bars move backandforth sometimes
action_vote_minus_faded.png
2
Votes
 action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

When replaying two tick data series chart in Tick by Tick resolution,
entire candles move backandforth, which causes eye fatigue and hard to focus on finished candles.

I attached a screen recording and two tick data files to import.

Steps to reproduce this issue
  1. create two symbols "backandforth1", "backandforth2" with Data Source as ASCII Mapping.
  2. For each symbol, after selection, left mouse click, Import Data --> ASCII, select attached tick data file.
  3. create chart with these two symbols, 60 tick chart.
  4. Playback jump to around 2015-08-13 09:30:00
  5. Select playback resolution to "Tick by Tick", update speed about 5 / sec.
  6. Replay

You can see entire candles move backandforth sometimes.
last unfinished bars can move backandforth depending on the ticks they receive.
But bars already finished, and the order between data1 and data2 determined need not to move backandforth.

Comments (9)
icon-mono-settings.png
#1
user-offline.png Khitan (chi jeongki)
Aug 09, 2017 - 12:18
A file was uploaded. backandforth.wmvicon_open_new.png
#2
user-offline.png Khitan (chi jeongki)
Aug 09, 2017 - 12:19
A file was uploaded. backandforth.aviicon_open_new.png
#3
user-offline.png Khitan (chi jeongki)
Aug 09, 2017 - 12:20
A file was uploaded. backandforth1.txticon_open_new.png
#4
user-offline.png Khitan (chi jeongki)
Aug 09, 2017 - 12:20
A file was uploaded. backandforth2.txticon_open_new.png
#5
user-offline.png MultiCharts Support (MultiCharts)
Aug 14, 2017 - 11:19
Tick bars have their own indexes. The index is the bar close time. It is not possible to calculate close time of tick bars in advance, that is why the bar time is updated with each new tick. Ticks from different data series are coming asynchronously, as the result, the tick was received on one series and was not on another.
#6
user-offline.png Khitan (chi jeongki)
icon_reply.pngAug 17, 01:30, in reply to comment #5
What you are explaining is right end part of the chart. Look at only left end part of the chart, Bars already passed left end boundary and disappeared show up itself again later. I have never seen chart behaving like this.

#7
user-offline.png MultiCharts Support (MultiCharts)
Aug 17, 2017 - 07:53
That is the consequence of the behavior described above. As the chart is set automatically to scroll the bars when the new bar appears, once the new bar appears/disappears, the data series is moving forward and backward.
#8
user-offline.png Khitan (chi jeongki)
icon_reply.pngAug 17, 09:11, in reply to comment #7
Let the current Bar of data1 be A, and current Bar of data2 be B. A and B can move backward and forward depending on the ticks arrived. Their relative location is not determined until they complete(finish) their bar.

But finishd Bar should not move backward and forward. In the chart, for example, the left most Bar should be a finished Bar. The strange symptom is that finished bar moves backward and forward.

I am not talking about current bar which is not finished yet. I am talking about finished bar which has no more ticks to add. Common sense is that finished bar should not move backward and forward.

#9
user-offline.png Khitan (chi jeongki)
icon_reply.pngAug 17, 15:42, in reply to comment #7 
   On the relative location of BarsOfData(1).Time[m] and
   BarsOfData(2).Time[n] on time-axis
   The following statements are true.



   1. For all m >= 1 and for all n >= 1, relative location of
   BarsOfData(1).Time[m] and BarsOfData(2).Time[n] are fixed and never change.



   2. For  all n >= 0, relative locationof BarsOfData(1).Time[0] and
   BarsOfData(2).Time[n] are not fixed, until both BarsOfData(1).Time[0] and
   BarsOfData(2).Time[0] complete their bar.



   3. For  all m >= 0, relative locationof BarsOfData(1).Time[m] and
   BarsOfData(2).Time[0] are not fixed, until both BarsOfData(1).Time[0] and
   BarsOfData(2).Time[0] complete their bar.


Rules to move A and B would be,

If A is ahead of B, 
   If thre are bars between A and B
       If A gets tick, no move.
       If B gets tick, move B ahead of A
   If there is no bars between A and B
      If A gets tick, no move
      If B gets tick, exchange location of A and B
If B is ahead of A, 
   ......


Thus only current bar need moving, while they are being made.

History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Investigating
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
Attachments (4)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates