+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
feature_request_small.png
Open Feature request MC-2730

Make possible Backtesting of Renko Charts Tick by Tick (BarMagnifier/IOG mode)

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

Please make possible the backtesting of Renko Charts Tick by Tick (Bar Magnifier/IOG Mode). Renko Charts are very popular charts all over the world. In stock terminology, noise refers to random or short-term market fluctuations that distort the picture of underlying trends, making it difficult to forecast the market's direction, and thus causing losses for traders.
Renko charts solve this problem by filtering out the noise/fluctuations/volatility, producing equal price-based renko boxes, that make analyzing charts much simpler and easier, and making easier to make a profit.
That is why it is needed to backtest these Renko charts Tick by Tick to obtain the results. Currently the only way to see the result of a Renko chart (tick by tick) is to do papertrading; but in order to see the results of these Renko charts longterm, it is needed to do papertrading for at least a year (in order to see meaningful results) which is a very long time.

Comments (0)
There are no comments
History
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 (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
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