+1 888 340 6572
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
feature_request_small.png
Closed Feature request MC-1933

Get"Mid-point' data for FX from IB for Trade instead of Ask (currently)

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
icon_info.png This issue has been closed with status "Duplicated" and resolution "Not determined".
Description

For FX, since there is no official Trade data,  Ask is obtained from IB and reported as Trade.
However, when backtesting AND Trading, using only Ask or Bid-based bars is somewhat deceiving and requires workarounds
when trying to identify if a stop price was actually hit, when one would like
to use limit orders, or when monitoring order execution vs.target.
To make it more convenient, IB prvides bid-ask "mid-point" data  via API.
So, my suggestion is to change FX Trade data received from IB as Ask to Mid-point.

Steps to reproduce this issue

Try downloading historical FX Trade data from IB (say, 1min) and see that actually Ask is reported.

Comments (1)
#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jan 15, 2016 - 12:26

Same as: http://www.multicharts.com/pm/viewissue.php?issue_no=MC-194

History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
  • Posted by
    user-offline.png  Zheka (Zheka)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    0 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates