You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Generator repaired. Replace your exe with this.
The generator sets sometimes Indicator Period + Shift > Bar Count;
I'm already confused. :)
New version.
But having reduced bar count to 300, the generator works and can be stopped with Stop button
'
Old version (quickly downloaded from site)
But, if amount of bars < 1000, then generator hangs.
'
IMHO it's better to get used to the 1000 bar limit requirement for the tester, but the convenience of selecting the interval.
'
I'm already confused. :)
'
Old version (downloaded quickly from website)
But, if number of bars < 1000, generator hangs.
'
Happy thoughts about 'old version' turned out to be mistaken.
I.e. picture is the same as with new version. (I.e. number of bars has higher priority than date DO!!!!)
'
'
Oops
Is it correct that the loop goes to iTempBars - MINIMUMBARS, i.e. to the maximum number of bars iTempBars = iMaxBars; from the beginning of the history ?
In my history files a lot more than 50 000 lines and in this interval from iTempStartBar = iBars - iMaxBars to iMaxBars- MINIMUMBARS can simply not be ordered date?!
Logically the End date and the start date should be searched to the end of the whole story, i.e. to iBars ???
But the ending bar is found correctly.
About your screen shots:
1. "Remove data older than September 1st 1st 2008" is ignored since there are less than 300 bars till January 1st 2009
2. "Remove data newer than January 1st 2009" - it seams there is no data for January 1st FSB cuts out all bars from 01.01.08 including . That why FSB limits the bars till 31.12.08.
(I.e. number of bars has higher priority than date BEFORE!!!!)
Exactly.
1. "Remove data older than September 1st 2008" is ignored since there are less than 300 bars till January 1st 2009.
2. "Remove data newer than January 1st 2009" - it seams there is no data for January 1st. That why FSB limits the bars till 31.12.08.
Not anymore.
I am now showing the clock.
In file 63291(iBars) the lines from 1999-01-04 to 2009-03-18
Date 2008-09-01 is line 59 973
The date 2009-01-02 is line 62 021.
I.e. when the program searches for the start date, the cycle "runs" from bar 63 291 - 50 000 = 13 291(iTempStartBar = iBars - iMaxBars; ) to bar 50 000 - 300 = 49 700(iTempBars - MINIMUMBARS) and not finding my "before" date (bar 59 973), leaves(iTempStartBar = iBars - iMaxBars;) start bar = 63 290 - 50 000 = 13 290.
In my file it is 2001-02-21 12:00 (+/- 300, which corresponds to the figure)
File attached.
iBars<= 50,000
FSB imports the newest 50,000 bars from the data file.
So:
Date 2008-09-01 is line 59 973
Date 2009-01-02 is line 62 021
are outside of the loaded data. Data Horizon does not take them into account.
Ops. I'm wrong.
iBars <= 50,000
FSB imports the newest 50,000 bars from the data file.
So:
Date 2008-09-01 is line 59 973
2009-01-02 is line 62 021
are outside of the loaded data. Data Horizont does not take them into account.
newest !!!!, i.e. from 13,291 to 63 291!!!!! and now searches from 0 to 50,000 (rounded ;) )
No agreement. :( Pity :(
Although it seems to me that it would be more correct toreplace iTempStartBar ;iBar < iTempBars - MINIMUMBARS; iBar++) with iTempEndBar inplace of iTempBars - MINIMUMBARS. And the whole block "// Set the maximum nuber of bars" is redundant if AND bUseStartDate=True AND bUseEndDate=True
'
But again, I don't insist. :( (I'll cut the file, though for minutiae it may well want to optimize the strategy on the previous 50 000 bars and check it on the next 10 000 bars.
:(
SZY. There is still an error in the code and it does not correspond to the scheme!!!!! (my interval is on the right and not on the left) :(
Let's think about it.
Give me the code you want. I'll put it in the program and we'll test it.
Let's think about it.
Give me the code you want. I'll put it in the program and we'll test it.
A snippet of your code from the previous pages.
add
But for start date reset iTempStartBar must be!!!!if dtStartingDate is earlier than iMaxBars you should ignore dtStartingDate and limit by iMaxBars
And I think there should be iMaxBars from dtStartingDate "to the right", so that you can move the window size of iMaxBars throughout the file!
But if to the right dtStartingDate bars are smaller than iMaxBars. then it should be dtStartingDate that has priority, as dates are more intuitive than bars. IMHO.
And in general, a user puts a 'tick' deliberately, and bars - by default, the more so it's written in the system (iMaxBars)
'
ZS. The funny thing is that I probably will not use the program :)