+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-526

Data series updated out of sequence for signals on multiple series

Go to the next issue (open or closed)
Go to the next open issue

When running a signal on multiple data series, the updates come out of order. Meaning if you had say 7 second, 12 second, 33 second data series on a chart, and a signal that required using the last value of an indicator calculated on all 3 series, sometimes it will run the say 00:00:12 bar then the 00:00:07 bar thereby causing the comparison of the next bar's indicator.

Steps to reproduce this issue

Create a chart with multiple data series (it may require series that don't divide evenly, haven't checked). Run the attached signal with PowerLanguage Editor opened so that you can view the printed output.

Comments (3)
user-offline.png  ecastroy1 (Id2)
Sep 12, 2011 - 15:19

Under what circumstances is it proper to execute bars out of temporal order??? Why would the user expect this, and far more importantly, how can one determine what sequence the bars will execute so as to be able to code indicator and signals relying on the proper sequencing of the bars?

user-offline.png  MultiCharts Support (MultiCharts)
Sep 12, 2011 - 15:20

Aliquant resolutions. Expected bahavior. The same as in TradeStation. It is not a bug, it is feature request.

user-offline.png  ecastroy1 (Id2)
Sep 12, 2011 - 15:24

Then is there any way whatsoever to force execution order to be in sequence? I just don't see how one is supposed to code a signal based on multiple time frames when there doesn't appear to be a way to read the latest data from each involved timeframe.

Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates