Subject: Short term progress reports on GSB features
admin posted at Jun 08 2018 04:00:10
This list isn't concrete, but is the intend short term road map forward.
1) Currently we are 80% complete the alpha build of multi time frame & data support.
This means you can build systems on 29, 30,31 minute bars and the system that works with the best parameters on all the times will have the highest metrics.
This should lead to more robust systems.
Also you could use ES,NQ,emd,er,ym etc
or
es data1, $spx data2
emd data1, $idx data2
nq data1, $ndx data2 etc

Later we will use 1 minute input data, so you can optimize bar interval
and just select say 5,15,30,60 min bars that are derived from the 1 minute.

2) csv export of trade lists, not just Portfolio analyst format.

3) Then ability to save averages of all system metrics, to variable storageA
You can then do inverse nth, or invert dates etc, then send to variable storageB
You then get to see the ratios of A vs B. This is for market validation
refer to the youtube video on market validation.
https://www.youtube.com/watch?v=NFC7ego_Y70

4) Smarter stops, exits etc
5) Additional secondary filters.

A lot of work also going into portfolio analysts cloud. Just trialing auto upload of TS trades so results appear on your web site.
admin posted at Jun 09 2018 05:16:04
Multi market validation beta build for GSB purchasers out Monday I hope.
It means you can build on es, $spx and validate on emd$idx, nq $ndx , ym,$dow
I have the build, but no time to test and document it.
admin posted at Jun 11 2018 02:06:08
Out soon 1.0.45.02 / 2018-06-11:
Verification data implemented (as a right click).
Price Data implemented in Tools menu (similar to Contracts).
PerformanceSummary.VerificationScore implemented.
Trades' Export to CSV implemented.
PriceFileInfo implemented to replace PriceFileName.
PriceFileInfos implemented.
Allowed null in DB's ExceptionLog.WorkplaceId.
Minor UI fixes in Admin window, Contracts window, and performance grid.
Minor UI fixes in AdminForm.
ReformatAndRelocateOldFiles() function removed.
OptimizationSettings.ConvertPrimaryAndSecondaryDataToOptimizationData() implemented (to replace primary/secondary data with PriceFileInfos).
Multiple logic updates to the main GSB window.
OverrideOriginalData set to hidden and UpdatePriceData() function deleted.

Cant release this build till the new features are documented. The new features just to hard to use without documentation. Working on this now


Shown is a system built on es data1, with $spx data2.
It's verified on emd $idx, nq $idx, ym $comp, rty $rut etc
Other screen shot is verified on es, $spx 27,28,29,31,32 min bars




COLOURS.png - 253kB



5-symbols.png - 236kB







export.png - 60kB

admin posted at Jun 11 2018 04:52:12
Here is the docs on the verification data. GSB.exe is in beta section (GSB paid users only)



Attachment: verificationData45.02.docx (775kB)
This file has been downloaded 25 times

rws posted at Jun 11 2018 16:20:08
Thank you so much for implementing this usefull feature!!

It would be good if there would be a way of operation where
you can set the additional tickers to have at least xx% profit
of the main ticker in order to have it automatically searching for robust systems.

Quote: Originally posted by admin  
Out soon 1.0.45.02 / 2018-06-11:
Verification data implemented (as a right click).
Price Data implemented in Tools menu (similar to Contracts).
PerformanceSummary.VerificationScore implemented.
Trades' Export to CSV implemented.
PriceFileInfo implemented to replace PriceFileName.
PriceFileInfos implemented.
Allowed null in DB's ExceptionLog.WorkplaceId.
Minor UI fixes in Admin window, Contracts window, and performance grid.
Minor UI fixes in AdminForm.
ReformatAndRelocateOldFiles() function removed.
OptimizationSettings.ConvertPrimaryAndSecondaryDataToOptimizationData() implemented (to replace primary/secondary data with PriceFileInfos).
Multiple logic updates to the main GSB window.
OverrideOriginalData set to hidden and UpdatePriceData() function deleted.

Cant release this build till the new features are documented. The new features just to hard to use without documentation. Working on this now


Shown is a system built on es data1, with $spx data2.
It's verified on emd $idx, nq $idx, ym $comp, rty $rut etc
Other screen shot is verified on es, $spx 27,28,29,31,32 min bars




cotila1 posted at Jun 11 2018 18:34:38
Thanks Peter, its a great job. I think the multiple market and 29,30,31 min bars verification is a great step for GSB.
once you release a consolidate build version, would be great you make a new video on this 29,30,31 min bars, and es,emd,ym,nq,rty validation.

thanks
admin posted at Jun 13 2018 01:53:41
Quote: Originally posted by cotila1  
Thanks Peter, its a great job. I think the multiple market and 29,30,31 min bars verification is a great step for GSB.
once you release a consolidate build version, would be great you make a new video on this 29,30,31 min bars, and es,emd,ym,nq,rty validation.

thanks

I will do, but there is a lot of features coming in short period, so will wait till the dust settles.
admin posted at Jun 13 2018 01:54:58
Verification score. We now have a count of the number of verification systems that pass the verifcation metrics in app settings.
This should be released in a few days




verification2.png - 313kB

admin posted at Jun 13 2018 01:59:53
Override original settings. If something on the left opt settings is changed, after systems are built - Then the system results will change when you click on them.
This is wrongly perceived as a bug. To fix this highlight the system(s) and click override original settings.



override.png - 38kB

admin posted at Jun 13 2018 06:26:23
In Build 45.31
We now can do nth ratio calculations fully automated. averageAllSystems(fitness*netprofit*averatetrade*profitfactor)/{nth trade}
averageAllSystems(fitness*netprofit*averatetrade*profitfactor) {Nth dont trade}
run GSB with say nth 1.
If you run the manager (not standalone) wait till new systems top coming through. This can take some time to stop.
Select all system
Right click and change nth day mode from donotTrade to Trade.
Wait till all systems have changed. (popup in windows taskbar will tell you, or scroll through all the systems in GSB to check)
right click and do update statistics.
Ave/previous average. Note in last videos the higher above 1 the ratio is, the worse.
Not we have done the reciprocal of this number. So if our threshold of a market failure was 2, its now 0.5. 1 or above would be perfect score meaning
out of sample performance > in sample performance
This is described in detail in the market validation video https://www.youtube.com/watch?v=NFC7ego_Y70





stats-gsb.png - 79kB

admin posted at Jun 13 2018 11:28:28
bug, to fix next build
System average should be (fitness*at*np*pf) not fitness+at+np+pf)
Petzy posted at Jun 13 2018 11:41:41
Quote: Originally posted by admin  
Override original settings. If something on the left opt settings is changed, after systems are built - Then the system results will change when you click on them.
This is wrongly perceived as a bug. To fix this highlight the system(s) and click override original settings.


I'm not sure I understand this. This is a new behaviour as far as I can remember.
Also I can't see that Overriding the original settings will make any difference. The values still changes
admin posted at Jun 13 2018 22:08:39
Quote: Originally posted by Petzy  
Quote: Originally posted by admin  
Override original settings. If something on the left opt settings is changed, after systems are built - Then the system results will change when you click on them.
This is wrongly perceived as a bug. To fix this highlight the system(s) and click override original settings.


I'm not sure I understand this. This is a new behaviour as far as I can remember.
Also I can't see that Overriding the original settings will make any difference. The values still changes

It might change but thats the settings the system was calculated on. My assumption is settings changed after system building began. I havnt yet seen this issue with the new build, so happy to look via teamviewer when it happens.
rws posted at Jun 13 2018 23:37:30
Good progress
admin posted at Jun 19 2018 07:15:49
Update to documentation for new features of the last week or two.




Attachment: verificationData45.32.docx (1.2MB)
This file has been downloaded 19 times



admin posted at Jun 25 2018 06:20:25
GSB 46.13 should be out later this week. It is very significant in improvements in out of sample results.
If we leave every 2nd day out of sample on ES.30 minutes bars, my tests show a 25% drop in out of sample results.
All systems no matter how bad are included in these results.

Ive got that down to 5.4% drop in out of sample results (best case) compared to in sample.
However my favorite method - that gave the highest fitness (Net profit* average trade) gave 9.4 % drop in out of sample results
but average net profit of $38900 compared to $28,300 out of sample of 30 min bars.
This is research you can objectively test your self, with minutes of human time, and an hour or so CPU time per market.

admin posted at Jun 27 2018 09:46:13
Hoping to upload in a few hours, but have a problem with last part of the video....
Here is a video on some of the features of GSB 47.03
It shows a comparison of a system built on ES, but verified on Dow, Nasdaq, Russell, MidCap S&P400.
It also shows the much faster method to see how much a large group ES30 min system degrades, and then the same test repeated with ES29,30,31 min bars.
Video uploaded but not finished. Hope to have done in the next day or so

video obsolete, see MarketValidation_video2_rev2o.2.mp4 below


Attachment: MarketValidation_video2c.mp4 (102.3MB)
This file has been downloaded 23 times

admin posted at Jun 28 2018 09:23:33
I started the video from scratch again. One of the many smart GSB users comment that the point value needed for closeD-close offset varies massively for the dow compared to ES, EMD etc, and this might be why so many systems didn't pass on multi market validation. Turns out this was strongly the case. However I got a surprise in results with CloseD(1) /Close compared to closeD(1)-close. The next video shows this.
Video not complete, and about 12 minutes long.
GSB 47.07 is being tested now by some experienced GSB users. It has the features shown in this video.

video obsolete, see https://youtu.be/2R4t9uYzfD4



admin posted at Jun 29 2018 08:44:59
Finished video


It is critical to have good out of sample results, to make money in trading.
Today we are going to have solid evidence showing how much better building systems with multiple time frames is with the same parameter values, and multiple indices with the same parameter values. This data is no derived from the results of one system, but of thousands of systems.
We also cover better alternatives to leaving certain dates for out of sample testing.
The implications to this are far reaching. You can tell what time frame, secondary data source is going to work best on all systems, not just the one you try it on.
Sound logic on 1000's of systems leads to sound logic on one system. Font reverse this concept!

Video now on youtube
https://youtu.be/2R4t9uYzfD4

alvestjo posted at Jul 01 2018 10:12:17
About using closeD(1)-close as a filter. Does this make sense at all if you are using many years of data since the market has traded at very different levels 5-10 years ago. I find it very strange you get better results with this filter. Any ideas why?

Jonas
admin posted at Jul 01 2018 23:01:31
Quote: Originally posted by alvestjo  
About using closeD(1)-close as a filter. Does this make sense at all if you are using many years of data since the market has traded at very different levels 5-10 years ago. I find it very strange you get better results with this filter. Any ideas why?

Jonas

I'm not sure why and in once sense I dont care why. I just want the to know what works best, and what doesn't. The first thing I would do is graph range in points of the Dailyclose absvalue(closed(1)-closed(0)) over the years to see the results
One comment is there are some other markets that closeD(1)/close is going to
work better than closeD(1)/close but i have forgotton what ones. I found this by accident. I think for the indices Closed(1)- is best
Run this code on daily bars.
you cloud change
hl = Averagefc(h-l, ATRLength ) ;
to
Averagefc(absvalue(close/open)*100, ATRLength )





range-pz.png - 11kB

admin posted at Jul 02 2018 08:59:59
Coming soon is GUI tweaks, better formatting of the market metrics, and ability to turn of and on sections of the gui you dont need.
I got market degradation down to -1.2%! today on ES.
I will write about in tomorrow in the private form for GSB purchasers





1.2pc.png - 100kB

admin posted at Jul 03 2018 07:25:16
The market validation video is now on youtube. Only a few tweaks since the post of MarketValidation_video2_rev2o.2.mp4
Here it is on youtube. https://youtu.be/2R4t9uYzfD4
Crude oil so far out of sample compared to in sample is degradation -35.2%
admin posted at Jul 17 2018 07:42:33
In build 47.41 we can now build systes on say 29,30,31 min bars. Then test the out of sample nth (every second day)
to see the degradation out of sample on 29,30,31 and the individual time frames too.
In the big picture is means we build systems on say 29,30,31 min bars, same parameters for all time frames, but just trade the 30 minute bars. This build will be out soon to in the beta section for paid GSB users, and in a about a week for trial users.





30+35+25.PNG - 11kB



es25.PNG - 13kB



es35.PNG - 15kB



es30.PNG - 12kB

admin posted at Jul 18 2018 11:02:04
For market validation, in build 47.41 we now have long short stats for all time intervals / markets traded.
Useful to tell if a market has a strong long or short bias.





longshort.png - 98kB

Carl posted at Jul 18 2018 13:50:41
Great! Thanks
admin posted at Aug 24 2018 03:50:22
In build 48.24 Being tested now.
Ability to walk forward multi time frame/market systems to the cloud

Next in the job pipeline, in not exact order
Custom dates for Training, test, validation.
Ability to make larger time frames from small bars. ie make 29,30,31 min bars from 1 minute
Secondary filter. Ability to genetic use Close-Closed,close/CloseD,close-closeBPV (Big point value) in a normalized and non normalized mode.
Custom made metrics in GUI, and additional fitness types. ie sqn and the additional ones in EWFO (Enhanced walk forward optimizer)

cyrus68 posted at Aug 24 2018 08:02:26
GSB has made enormous progress over the past year. The pace of development outshines anything achieved in similar software. Inevitably, there are bugs and annoyances along the way.

The great strength of GSB is the emphasis on good methodology.
zdenekt posted at Aug 24 2018 14:54:05
I still can not see EXITs in the job pipeline :-(
I'm sorry to have to write it, but I'm a little disappointed with the direction of GSB's development over the past few months.
Everything is still spinning around the entering to trade.
We are constantly looking for an ideal entry to trade for a few markets.

In GSB we have thousands of settings for everything that some of us do not even understand, but we have no option to set the type of EXIT ... donīt you think it's a little weird?

I donīt know if there is any major edge in your multitimeframe testing method when the exit from the trade is always at CloseD price. I understand that the results will improve a few percent but it is quite logical when EXIT is on the same price on every timeframe...and programmers still work over and over on one and the same ... better entry on just a three markets.

Yes I can ignore your way of multitimeframe testing, but iīm still waiting for implementation of any different exits.
I believe the implementation of only a few other reasonable EXITs than closeD would not be as problematic as multitimeframe testing and would open a new space of strategies on many more markets than only ES, CL, NG.

Anyway, GSB is a great tool, although it is now going through a more complicated way than it might have been.
admin posted at Aug 24 2018 22:36:49
Quote: Originally posted by zdenekt  
I still can not see EXITs in the job pipeline :-(
I'm sorry to have to write it, but I'm a little disappointed with the direction of GSB's development over the past few months.
Everything is still spinning around the entering to trade.
We are constantly looking for an ideal entry to trade for a few markets.

In GSB we have thousands of settings for everything that some of us do not even understand, but we have no option to set the type of EXIT ... donīt you think it's a little weird?

I donīt know if there is any major edge in your multitimeframe testing method when the exit from the trade is always at CloseD price. I understand that the results will improve a few percent but it is quite logical when EXIT is on the same price on every timeframe...and programmers still work over and over on one and the same ... better entry on just a three markets.

Yes I can ignore your way of multitimeframe testing, but iīm still waiting for implementation of any different exits.
I believe the implementation of only a few other reasonable EXITs than closeD would not be as problematic as multitimeframe testing and would open a new space of strategies on many more markets than only ES, CL, NG.

Anyway, GSB is a great tool, although it is now going through a more complicated way than it might have been.

The pipeline is what I hope to get done in the next week or two.
Exits and additional secondary filters are a high priority, but they are both are a big job that must be done at the same time. So I am trying to get most of the small features that lots of users have request - finished before we start exits. If exits and additional SF filters were a small job, it would be done now. Much time was spend on multi time frame systems, and this is something that has massive significance to nearly (all?) users. The improvement is massive on multi time frame. On crude oil out of sample degradation went from -42 to - 12 %. There are not 1000's of settings, and if whats on the bottom GUI & limited docs are not enough, you can ask. Improved documentation is being working on as well. Regardless Im sorry for your frustration and you will get what your after. If you follow GSB growth in the last year, it has taken massive and consistent leap forward. Many users are asking for lots of things, and I am hoping that most features user ask for get implemented.
zdenekt posted at Aug 24 2018 23:59:09
It's not frustration (I have no problem setting up and using GSB) ... it's just a disillusion that after more than a year of GSB existency and so many different updates we still donīt care about such an important thing as the exits.

I must say again that GSB is a great tool and I really respect your work.
I will try to be patient.
JasonT posted at Aug 26 2018 06:33:20
Quote: Originally posted by zdenekt  
... we have no option to set the type of EXIT ...


zdenekt, have you explored the Minute, Stop Loss, Profit Target, Time of Day exits that are available in addition to the close at end of session exists?





Exits.JPG - 88kB

zdenekt posted at Aug 26 2018 15:50:43
I'm working mainly on swing strategies so now I can only use stop loss and profit target. The problem is the varying volatility across history.

For intraday trading there are only a few suitable markets and their reactions to different events are very closely correlated.

For swing trading I can use markets from all sectors and I can set up a portfolio as I need.
admin posted at Aug 26 2018 22:25:15
Quote: Originally posted by zdenekt  
I'm working mainly on swing strategies so now I can only use stop loss and profit target. The problem is the varying volatility across history.

For intraday trading there are only a few suitable markets and their reactions to different events are very closely correlated.

For swing trading I can use markets from all sectors and I can set up a portfolio as I need.

From memory, GSB as is - can reverse a position, so this is an exit too.
Its not what you want but for now better than just stop and profit target exit
zdenekt posted at Aug 28 2018 19:46:48
Peter,
Based on my research I can not confirm your thesis that reverse position is for now better than stop and profit target.

I tested a lot of markets with just a reverse position exit but I could not find the only strategy that would profitable/tradeable on OOS period. If someone had some succes with it, please show us the results.

While I set up stop and profit target (coexist together with reverse exits) it is possible to find strategy that is profitable on OOS period.

You can see some of my swing strategies on the picture.
All these strategies also passed the Cluster Analysis in Tradestation WFO.



GSB-swing samples.jpg - 339kB

admin posted at Aug 28 2018 22:13:37
Quote: Originally posted by zdenekt  
Peter,
Based on my research I can not confirm your thesis that reverse position is for now better than stop and profit target.

I tested a lot of markets with just a reverse position exit but I could not find the only strategy that would profitable/tradeable on OOS period. If someone had some succes with it, please show us the results.

While I set up stop and profit target (coexist together with reverse exits) it is possible to find strategy that is profitable on OOS period.

You can see some of my swing strategies on the picture.
All these strategies also passed the Cluster Analysis in Tradestation WFO.

I'm not saying reverse is better, but its an option as well as stop and PT. The first thing I would check is what secondary filter you have. This is typically one of the most important settings. So try closed-close, and ga with closed-close and ga with close/CloseD
Note the ga S.F. are normalized, while the SF others are not
Can you let me know how this goes. Worked fine on Apple but I didnt do market validation tests on it. Focusing all time on Crude oil right now
zdenekt posted at Aug 28 2018 23:15:14
I have to go sleep so very shortly for now.
Yes, filter is most important element in GSB strategies.

I think that none of my swing strategies use CloseD in any form.
I found that CloseD in swing strategies only works on In-sample period but OOS period always failed. This applies to both the indicator and the filter.
So I often uncheck CloseD and do not using it at all.

For now, I only work with futures markets.
Stocks or ETFs donīt tried yet.
admin posted at Aug 28 2018 23:18:11
Quote: Originally posted by zdenekt  
I have to go sleep so very shortly for now.
Yes, filter is most important element in GSB strategies.

I think that none of my swing strategies use CloseD in any form.
I found that CloseD in swing strategies only works on In-sample period but OOS period always failed. This applies to both the indicator and the filter.
So I often uncheck CloseD and do not using it at all.

For now, I only work with futures markets.
Stocks or ETFs donīt tried yet.

Stocks and eft should be fine overall. I have never seen closed filters not work on any market, but I havnt looked at all of your markets before. When you do a support ticket upload, I can look further
Carl posted at Aug 29 2018 10:01:11
Quote: Originally posted by zdenekt  
Peter,
Based on my research I can not confirm your thesis that reverse position is for now better than stop and profit target.

I tested a lot of markets with just a reverse position exit but I could not find the only strategy that would profitable/tradeable on OOS period. If someone had some succes with it, please show us the results.

While I set up stop and profit target (coexist together with reverse exits) it is possible to find strategy that is profitable on OOS period.

You can see some of my swing strategies on the picture.
All these strategies also passed the Cluster Analysis in Tradestation WFO.


Hi Zedenekt,

The four equity lines on wheat, corn, sugar, cotton and belong to swing strategies that were developed by GSB?

Thanks.
zdenekt posted at Aug 29 2018 10:02:15
Sorry for my english.
I found that swing strategies with CloseD indicator or filter can have positive results on In-sample period but OOS period has always had negative results.
admin posted at Aug 29 2018 12:02:01
Quote: Originally posted by zdenekt  
Sorry for my english.
I found that swing strategies with CloseD indicator or filter can have positive results on In-sample period but OOS period has always had negative results.

Under help, do a support ticket and I will look into this
zdenekt posted at Aug 29 2018 13:05:28
I'm talking about robustness of CloseD filter in swing strategies. I did not said it's bug in GSB.
admin posted at Aug 29 2018 20:47:00
Quote: Originally posted by zdenekt  
I'm talking about robustness of CloseD filter in swing strategies. I did not said it's bug in GSB.

Agreed, but I want to look into this issue regardless
cotila1 posted at Sep 02 2018 07:00:33
zdenekt, sorry not sure if understood this: your equity lines in pics (corn etc.) are from systems built by GSB?
thanks

Quote: Originally posted by zdenekt  
Peter,
Based on my research I can not confirm your thesis that reverse position is for now better than stop and profit target.

I tested a lot of markets with just a reverse position exit but I could not find the only strategy that would profitable/tradeable on OOS period. If someone had some succes with it, please show us the results.

While I set up stop and profit target (coexist together with reverse exits) it is possible to find strategy that is profitable on OOS period.

You can see some of my swing strategies on the picture.
All these strategies also passed the Cluster Analysis in Tradestation WFO.
zdenekt posted at Sep 02 2018 08:38:50
Yes, these equity lines are from systems built in GSB.

On the picture you can see one of my potential portfolio of 11 strategies (9 of them are built in GSB).



Portfolio sample - 11 strategies.jpg - 146kB

cotila1 posted at Sep 02 2018 18:10:50
Oh sounds great!
If you dont mind could u mention the 9 symbols you built in GSB?

When does the OoS start from? Is that OoS the so-called test period or is it an unseen period by the software?

thank you so much

Quote: Originally posted by zdenekt  
Yes, these equity lines are from systems built in GSB.

On the picture you can see one of my potential portfolio of 11 strategies (9 of them are built in GSB).
admin posted at Sep 06 2018 21:46:30
I ended up with 900 CL systems, which all passed verifcation profit factor 1.8, pearsons 0.95 on the 11 bar intervals 25 to 35 min. A hard job to narrow this down to get fewer systems.
I then added 24 and 26 minute bars, and added 20 and 40 minute bars to verification.
This dropped things down to 300 systems.
I then though, would be good for portfolio analysist pro to sort out the best combination of say 10 systems.
However GSB couldnt do bulk export of all systems to PA.
This feature has now been added.
Sorry for the delay in new releases this week. Interval multiplier has been added. So you can now just use 1 minute bars and multiple by 30 etc
You can also clone bar setups. ie if you have CL,NG,HG,RB 30 minute bar, you can clone and change the interval to 29 minute.
This feature however has at least one bug, and a danger that TS <>GSB in some circumstances. Hence I didnt release it.
If anyone is desperate for the above feature, send me a email & I will supply


pa_export.png - 41kB






26minbars.png - 28kB

admin posted at Sep 12 2018 02:58:02
Most of us have made a great GSB system and put it into TS. We do however loose the GSB format of the system if we are not careful.
Why we might want this is to apply new GSB features to an older system, or to walk forward.
There is some binary info at the end of the TS/MC code of GSB, that can be converted back to a GSB format system
This feature will be in 49.07 release onwards.




hash.png - 150kB

admin posted at Sep 12 2018 03:03:15
Another useful feature, is the stats function a&b can be applied to only the systems that are stored on favorites tab.
It means you can test the stats of say systems that have verified on all markets, without having to delete all the non verified markets.
Useful as you might delete some systems with metrics, and turn out to regret that.




fav.png - 15kB

admin posted at Sep 19 2018 02:34:18
A new release will be out for trial users by the end of the month. Old code will have expired too.
We now have CLoseDBPV (Big point value) which makes closeD-Close redundant. Much better for when we you compare multiple markets that have very different point values. Lots of small tweaks and features have been added. Much better use of ram when nth / dates tests are used.
There now is a job que on the right side gui for NTH, dates and market verification. (49.09 onwards)
A help file. (not complete) has been added under help. (top menu)
cotila1 posted at Sep 19 2018 05:48:01
I like this new CloseD (CLoseDBPV) . That means that if I use the close-closeD(1) as SF for ES and I want to verify on nq, then i should not have big difference/issue by using this new CLoseDBPV?
So the old ''CloseLessPrevCLoseD'' will have new name in SF dropdown menu?

Quote: Originally posted by admin  
A new release will be out for trial users by the end of the month. Old code will have expired too.
We now have CLoseDBPV (Big point value) which makes closeD-Close redundant. Much better for when we you compare multiple markets that have very different point values. Lots of small tweaks and features have been added. Much better use of ram when nth / dates tests are used.
There now is a job que on the right side gui for NTH, dates and market verification. (49.09 onwards)
A help file. (not complete) has been added under help. (top menu)
admin posted at Sep 19 2018 05:51:13
Quote: Originally posted by cotila1  
I like this new CloseD (CLoseDBPV) . That means that if I use the close-closeD(1) as SF for ES and I want to verify on nq, then i should not have big difference/issue by using this new CLoseDBPV?
So the old ''CloseLessPrevCLoseD'' will have new name in SF dropdown menu?

Quote: Originally posted by admin  
A new release will be out for trial users by the end of the month. Old code will have expired too.
We now have CLoseDBPV (Big point value) which makes closeD-Close redundant. Much better for when we you compare multiple markets that have very different point values. Lots of small tweaks and features have been added. Much better use of ram when nth / dates tests are used.
There now is a job que on the right side gui for NTH, dates and market verification. (49.09 onwards)
A help file. (not complete) has been added under help. (top menu)

correct on all points but dropdown box will have closed and closedBPV
cotila1 posted at Sep 19 2018 05:54:59
Quote: Originally posted by admin  
Quote: Originally posted by cotila1  
I like this new CloseD (CLoseDBPV) . That means that if I use the close-closeD(1) as SF for ES and I want to verify on nq, then i should not have big difference/issue by using this new CLoseDBPV?
So the old ''CloseLessPrevCLoseD'' will have new name in SF dropdown menu?

Quote: Originally posted by admin  
A new release will be out for trial users by the end of the month. Old code will have expired too.
We now have CLoseDBPV (Big point value) which makes closeD-Close redundant. Much better for when we you compare multiple markets that have very different point values. Lots of small tweaks and features have been added. Much better use of ram when nth / dates tests are used.
There now is a job que on the right side gui for NTH, dates and market verification. (49.09 onwards)
A help file. (not complete) has been added under help. (top menu)

correct on all points but dropdown box will have closed and closedBPV


So If i want to use close-closeD(1) as SF for ES building and I want to verify on nq and avoid the BPV issue between es and nq, should I choose closed or closedBPV for building?
admin posted at Sep 19 2018 07:28:37
Quote: Originally posted by cotila1  
Quote: Originally posted by admin  
Quote: Originally posted by cotila1  
I like this new CloseD (CLoseDBPV) . That means that if I use the close-closeD(1) as SF for ES and I want to verify on nq, then i should not have big difference/issue by using this new CLoseDBPV?
So the old ''CloseLessPrevCLoseD'' will have new name in SF dropdown menu?

Quote: Originally posted by admin  
A new release will be out for trial users by the end of the month. Old code will have expired too.
We now have CLoseDBPV (Big point value) which makes closeD-Close redundant. Much better for when we you compare multiple markets that have very different point values. Lots of small tweaks and features have been added. Much better use of ram when nth / dates tests are used.
There now is a job que on the right side gui for NTH, dates and market verification. (49.09 onwards)
A help file. (not complete) has been added under help. (top menu)

correct on all points but dropdown box will have closed and closedBPV


So If i want to use close-closeD(1) as SF for ES building and I want to verify on nq and avoid the BPV issue between es and nq, should I choose closed or closedBPV for building?

Use bpv, there is no need to use close-CloseD any more. Beta 49.09 uploaded in private forum shortly
admin posted at Sep 22 2018 00:02:00
49.12 has comments in data table. They are only for the user, not gsb.
There always is lots of confusion over session times.
Your TS should run local time. This is because if you have a data 2 with different time zone to data1, TS&MC wont allow it.
The session time on your chart is exchange time, but the exported data is in your local time.
Moc time should = local time last bar of day, not exchange time.
Note also cash indices have changed point value to what is on the futures contract. This is needed for closeDBPV (big point value) to work best




data.png - 16kB

admin posted at Oct 01 2018 19:11:32
In the beta section (GSB paid members) 49.20 was released today. Lots of long awaited features.
One of the best things in GSB is the ability to build 1000's of systems. Then tweak things to see what improves the out of sample results. We were using every second day as un seen to get a out of sample picture. Then we look at how much out of sample degrades compared to in sample. Well now we can choose say 3 days to trade, 1 day to not trade. This means greater in sample period - so we get more trades to form a more valid opinion. We can then get just as many trades out of sample by twice the amount of trades. (Before we traded 1 day, then 1 day out of sample) So now the statistics are normalized to take into account that you have less trading days.
We can also have unlimited custom dates for training, test and validation.
There is now a job que to submit changes in the dates or nth so changes in dates and nth can be done in one pass, not two.
kelsotrader posted at Oct 02 2018 20:25:45
Quote: Originally posted by admin  
49.12 has comments in data table. They are only for the user, not gsb.
There always is lots of confusion over session times.
Your TS should run local time. This is because if you have a data 2 with different time zone to data1, TS&MC wont allow it.
The session time on your chart is exchange time, but the exported data is in your local time.
Moc time should = local time last bar of day, not exchange time.
Note also cash indices have changed point value to what is on the futures contract. This is needed for closeDBPV (big point value) to work best


Excellent Explanation: I always add the exchange session time onto the file name when exported so that the GSB code will record the time in its code so as to keep a permanent record on the strategy.
admin posted at Oct 19 2018 00:45:41
Soon we will have market degradation score per system.
So lets say you build 5000 CL systems on 29,30,31 min bars.
You can then verify on 20,24...36,40 min bars. (12 different bar intervals)
You would expect the 20,24...36,40 min bars to give a bit worse performance than the 29,30,31.
Then those systems that get verification score of say 10 up, or even 12.
You can then choose the system where the verification degradation is the highest.
Shown here the verified bars had higher performance than the 29,30,31 that the system was build on.
The out of sample (alternate nth day) also had higher results than in sample.
I would say this would be very unusual.
800 systems were tested to get this result.





vs_IS.png - 198kB



vs_OS.png - 173kB

admin posted at Oct 19 2018 22:47:31
We can now turn off and on specific groups of curves, and the legend. This stops the graphs being too cluttered.
In build 49.44 onwards





gui.png - 130kB

cyrus68 posted at Oct 20 2018 07:37:43
I agree entirely. I think the information on the graph can be revised to reduce clutter and be more relevant. Instead of all the line items showing the metrics for each verification dataset (whether it can be turned on or off), we could have a single one showing the average metrics for all the verification datasets. This will allow us to make a direct comparison with the average result of the datasets that were used in the build. Is this what the VSS score is showing?

Having reduced the clutter, it is important to include line items for the metrics of EACH of the datasets that were used in the build – in this case, 29 30 31 min. I would like to see both the IS and OOS results. This is essential information when we want to run WF. I don’t automatically run WF on the central bar size and, even if I do, I want to see its metrics – not just the average IS and OOS for all of them.
admin posted at Oct 21 2018 21:12:22
Quote: Originally posted by cyrus68  
I agree entirely. I think the information on the graph can be revised to reduce clutter and be more relevant. Instead of all the line items showing the metrics for each verification dataset (whether it can be turned on or off), we could have a single one showing the average metrics for all the verification datasets. This will allow us to make a direct comparison with the average result of the datasets that were used in the build. Is this what the VSS score is showing?

Having reduced the clutter, it is important to include line items for the metrics of EACH of the datasets that were used in the build – in this case, 29 30 31 min. I would like to see both the IS and OOS results. This is essential information when we want to run WF. I don’t automatically run WF on the central bar size and, even if I do, I want to see its metrics – not just the average IS and OOS for all of them.

VSS is showing the metric for the individual time frame . market -not the average. I will look into "see both the IS and OOS results". This will be even more info in the GUI.
admin posted at Nov 01 2018 04:32:05
Additional work on exits has started about 2 weeks ago. Hence the lack of other updates the last few weeks.
I'm nearly finished the next video on CL, with significant refinement of methodology.
The next release will appear in the beta forum for paid users.






gsbstops.png - 30kB

admin posted at Nov 26 2018 23:39:20
In the beta forum, we now have trailing stops, atr stops, exits after x bars (we has exits after x minutes some time ago)
Additional exits are being debugged now.
The new video is out. https://www.youtube.com/watch?v=HDeJpONE090
verification of systems done in the workers, instead of only in GSB managers.
Soon we should have counter trend oscillators which should result in counter trend systems
admin posted at Nov 30 2018 07:00:51
GSB counter trend oscillator released in the private forum today.
Subject: Very Impressed
JasonT posted at Dec 10 2018 07:10:47
Hi Peter,

I just wanted to say how impressed I am with the 50.25 beta version of GSB. I'm finding it much easier to use than the 49.xx series, especially the way you've incorporated the IS/OOS degradation statistics - fantastic.

I've gone through the last 3 you tube videos a few times over the weekend and have got a much better idea of how to perform degradation testing. It took me a while to piece it all together. Now that I understand what you are doing and why, it is straight forward. Good work.

Videos here:
a) Genetic System Builder Market testing / validation 22 May 2018
b) GSB Market Validation video2 2 Jul 2018
c) Genetic system builder, new features to get better out of sample results 1 Nov 2018




JasonT posted at Dec 10 2018 07:20:11
Quote: Originally posted by JasonT  
I just wanted to say how impressed I am with the 50.25 beta version of GSB.


I'm also a fan of the User Tasks section in the resource monitor panel on the right. It's great to see progress against a change of Nth day mode or Verification calculation.




Status.JPG - 12kB