+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-1800

Problem with Session end classification

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

Whether one uses the default sessions or 24/7 session, or I suspoect any session, we are always forced to select 'session end' times for each day. For markets like FOREX and even many futures now, that trade almost around the clock, the concept of session ending times loses much of its meaning.
But the real problem is when it comes to plotting tick, range or volume bars. 
Imagine a scenario when your plotting a 2000 tick chart. The day is about to end, and it completes a 200 tick bar and plots it, then right afte the enext tick comes thorugh, the session end is reached. So it plots a bar with jusrt 1 tick. Clearly this is absurd. And for those of us who wish to plot a market 24/7, where we know every bar is 2000 ticks, even if it spans more than a day or over a weekend say, we ar left with a situation where all our indicators are innacurate. 
This can be corrected by allowing us the option to NOT tick the session end box when using any particular session classification. I'm sure this would be dead easy to correct.

Steps to reproduce this issue

To see this for yourself, plot a 2000 tick chart on one of the currencies. You will notice every so often a tiny bar (sometimes so tiny you won't even see it) that is very close to another bar, instead of being evenly spaced. 
I would much appreciate it this glaring error/anomaly could be corrected or at least allow the end user to have th echoice to leave 'session end' unchecked. 
Thank you.

Comments (0)
There are no comments
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Not Reviewed
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
  • Resolution
    Not determined
  • Severity
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