MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+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-2131

Day and GTC TIF selection in fill assumptions is incorrect

action_vote_minus_faded.png
1
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

The "DAY" fill assumption in MC10 is correct for all fills.
The "GTC" assumption is wrong and redundant.
Please remove this TIF option from the backtesting options and default behaviour to "DAY".
The INTRADAY changes to fill assumptions are all correct, which is great. But fills when the open of a new session gaps through a limit order are now only correct when "DAY" is selected.
There shouldn't be an option for TIF on fill assumptions as its effect on fills is beyond the scope of MCs backtesting engine (theoretically, GTCs will slightly increase fill priority in correlation with order book prevalence).
As it currently stands the GTC assumption will potentially cause large outlier losses (that are incorrect) on certain strategies. As it is the default fill assumption in porftolio trader, it has rendered it completely unreliable.

Steps to reproduce this issue

Please see attached the incorrect behaviour. If we have a buy limt order @49. Then market closes at 50. Then opens (new session) and 48. The fill is ALWAYS at 48. Never at 49.

Comments (1)
#0
user-offline.png  MultiCharts Support (MultiCharts)
Nov 07, 2016 - 18:59

This functionality is optional.

History
Issue basics
  • Type of issue
    Bug report
  • Category
    Usability
  • Targeted for
    MultiCharts 10.0 (RELEASED)
  • Status
    Released
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Critical
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates