I've gone through most of the bar types and there are extremely obvious errors in all of the unique bar types.
Video of a couple bars: http://screencast.com/t/6p0lkr19z
*note the wick
*note the open and closes
(these settings are turned on)
very good ! good suggestion...
-Add a tick by tick back-test option for ALL charts
-Fix Renko with resolution
-Add a similar resolution addition to Point bars
-Add a Point measurement setting to Line Break bars
-Add a Point measurement setting to Heikin-Ashi bars
-Remove back-test execution within the part of Heikin-Ashi bars that have no price
Hello MAtricks and Smoky,You're right, MC needs to work on ALL unique bar types since they need updates/upgrades.
Smoky, please elaborate what particular issue do you have with backtesting.I do not understand why MC don't have a tick by tick backtest for renko:(
StefanoSF and me want to have same feature on renko charts than regular bar !
Discussion forum is not the best tool to ask for improvements or new features. We have a dedicated tool for that: Project Management.Multicharts team: Please look at these unique bar types! They're sold in the platform and most are NOT usable. A few suggestions would be:
http://screencast.com/t/6p0lkr19zTo sum up - there are no outstanding confirmed issues with Renko or any other chart type at the moment, according to the current design of these chart types. If you have found any behavior that you consider to be incorrect - please provide a detailed description of it and it will be forwarded to our engineers for further analysis.
there is noSmoky, please elaborate what particular issue do you have with backtesting.
So you have an issue or no?there is noSmoky, please elaborate what particular issue do you have with backtesting.
Taking only a realtime bar into consideration:From all of this I think we need to think of solutions for:
-Show Wicks option to show the entire wick for the time based renko so these are more realistic. It seems like this is feasible if we're using minute data..
Only with non time based resolution. For example Renko box size 10pts and 1 tick resolution will do this job. Almost the same thing will be done by regular chart type with 10 point resolution.Question (and this may be another topic completely):
Is there any way for the a 10pt/1minute renko box to close at 10pts/1.5 minutes? Or 10pts/3 minutes 42 seconds? In other words, can we get away from waiting for a whole other minute just because the bar wasn't more than 10pts at 59seconds?
I use last MC beta but this issue is on every MC (Easylangage not tested in .net)So you have an issue or no?there is noSmoky, please elaborate what particular issue do you have with backtesting.
If you have an issue with the current implementation of Renko bars and you want it to be adressed - please provide us the following information for analysis:
0) Create a sample code without excessive logic that will replicate this behavior;
1) What exact version and build number of MultiCharts are you running? (in MultiCharts go to Help tab-> About);
2) attach the workspace you are using;
3) in QuoteManager select the symbol you are using, make a right click on it->Export data->Export instrument (with data). Send me the Qmd export file for analysis;
4) in PowerLanguage editor->File->Export->export with dependent functions the studies you are using for replicating the case. Send me the study export file.
Right now Renko charts in MultiCharts are implemented based on the user requests (similar to Better Renko).
If you consider the current implementation to be incorrect – please describe what exactly does not work as you expect and provide a distinct algorithm on how to improve the Renko chart type.
All feature requests are forwarded to the management of the company and are evaluated in a timely manner. Please note that even though we value your opinion not all requests can be implemented due to the fact that some features do not fit into our current roadmap.
Code: Select all
[IntrabarOrderGeneration = true]
vars: intrabarpersist tick(0), intrabarpersist nobar(0);
tick = tick + 1;
if nobar <> (currentbar+MaxBarsBack) then
begin
tick=0;
nobar=currentbar+MaxBarsBack;
end;
if tick= 1 then buy 1 share next bar at market;
if tick= 3 then sell all shares next bar at market; // OK ON BACKTEST
//if tick= 6 then sell all shares next bar at market; // NOT WORK ON BACKTEST
// ONLY 4 TICKS IN BACKTEST !!!
messagelog(numtostr(nobar,0), " Tick number= ",numtostr(tick,0));
That is correct. As the Wiki page that you have already quoted above says:I use last MC beta but this issue is on every MC (Easylangage not tested in .net)
remember i works on ticks by ticks ! IOG
On Your WIKI :
"" Intra-Bar Order Generation in Backtesting
Intra-Bar Order Generation mode allows generating orders within a bar. In backtesting Intra-Bar Order Generation is limited by four calculations per bar: Open, High, Low, Close. Historical Intra-Bar calculation of the strategy is divided into 4 segments:
(Open),
(Open-High),
(High-Low),
(Low-Close).
""
no need workspace use this code !Code: Select all
[IntrabarOrderGeneration = true]
vars: intrabarpersist tick(0), intrabarpersist nobar(0);
tick = tick + 1;
if nobar <> (currentbar+MaxBarsBack) then
begin
tick=0;
nobar=currentbar+MaxBarsBack;
end;
if tick= 1 then buy 1 share next bar at market;
if tick= 3 then sell all shares next bar at market; // OK ON BACKTEST
//if tick= 6 then sell all shares next bar at market; // NOT WORK ON BACKTEST
// ONLY 4 TICKS IN BACKTEST !!!
messagelog(numtostr(nobar,0), " Tick number= ",numtostr(tick,0));
This is exactly the same case as described above.ANOTHER THING: in tick/tick next bar at market must be next tick
run this code and you'll see sell order is on NEXT BAR !
if you use sell if tick=6 you never see this order in backtest !
buy tick=1 sell tick=3 works in backtest
buy tick=1 sell tick=6 NEVER works in backtest you lose realy trades in backtest
as you ask me this is a realy simple code, but 10 lines of code to prouve that i'm right !
In realtime all works fine you buy and sell at number of ticks you want ...
look at messalog text :
in bactest you'll see only four tick 1,2,3,4 on each barnumber
in realtime in 60tick/bar you'll see 60 lines/bar 1 line by tick