GSB Forums - Powered by XMB 1.9.11

I am getting no connection between my workers and managers, and all my workers, public and my own are used by others right now and i get no workers for my own development, my managers is searching for over an hour now for workers, been looking for the 55.84 update, but not seeing any 55.84 updates.. what to do?

I erased all sharekeys for my workers and then they seem to be connected, however do i need to do this on every new workers that starts up ?
i saved the app setting as default for the workers, every time i change i need to save it it seems

if you set the worker to use local network etc, and you an put in a share key(not needed if first step is done) then save the app settings. then kill all workers, and open them via rm
Regardless you should have picked up some free gcloud workers if you have the free cloud share key as well. Worst ccase we can do teamviewer to look at this.

Daniel UK1 - 1-11-2019 at 02:58 AM

Peter, When you say "set the worker to use local network" which setting control this?

If i pick one worker (started from RM or not ) and save the app setting as default with no keys used meaning key field empty, which as i understand shall be the used if i understand your post about this issue a few days ago... will this mean all started workers going ahead will use this app setting i just saved which i assume is correct? started from RM or not?

EDIT, SEEMS TO BE SOLVED WITH .84

admin - 5-11-2019 at 03:46 AM

coming in the next day or two, lots of bug fixes including some systems with indicator cross entry type not trading,
and improvement on miss-match issues.
I should be back in Australia < 24 hours, so will be given a bit higher service levels than the last week.

admin - 5-11-2019 at 01:22 PM

.87 released to a few beta testers.
Bug fixes for no trades in ts, and tc <> gsb.This build is worse for MC - hence no public release.
https://www.dropbox.com/s/k76qcecjbrmn5h9/GSBWorker.55.870.z...

I am flying back to au today, so no time for me to test.You need to update workers and manager
Other fixs and mc fixes are being working on.

Peter

admin - 7-11-2019 at 12:55 AM

50.87 released.

Daniel UK1 - 7-11-2019 at 06:19 AM

Not receiving 50.87, has it been pushed out trough RM? Thanks

admin - 8-11-2019 at 05:05 AM

Not receiving 50.87, has it been pushed out trough RM? Thanks

My mistake
released now

admin - 8-11-2019 at 05:07 AM

coming soon
55.90

release notes for .88 & .87

* 1.0.55.88 / 2019-11-07:

Fixed bars-ago reference of secondary-data indicators in GSB to match TS, ex. RSI[1] of Data2. Note: not tested with older bars or higher data (ex. RSI[3] of Data5).
Fixed the three new cross-based entries (AnyIndicatorCrossed, AllIndicatorsCrossed, and NoConflictsCross), as a result of the bars-ago reference fix. Note: AnyIndicatorCrossed only tested.
Fixed CrossAndCloseD entry type in GSB and TS.
Still to be done, Partially-implemented BarsAgo (applies to indicators in GSB only, not to TS, MC, or NT yet) in IndicatorsTester,

* 1.0.55.87 / 2019-11-05: Multiple fixes for the mismatch issues

Fixed TS/MC script to use inputs/vars in function calls. Note: this is a recent bug where GSB exported TS/MC script with hard-coded, static values (instead of inputs or vars).
Hiding ExitModesAll from trial users.
Writing MC debug files to a .mc.txt file to differentiate from TS files (of .ts.txt extension).
Hiding indicators vars in the TS script (that uses inline-calls) to avoid users’ confusion. Note: MC still used vars-calls of indicators/oscillators functions.
Moved the result and decision calculation outside the start-end date check in TS/MC script to match GSB’s HL2 and CS2 norm types. Note: HH3 and CS3 are currently Alpha user only and disabled by default with plans to remove altogether in later builds.
A minor improvement in debug script readability/editability for better diagnosis.
A minor updates to IndicatorsTester strategy script.
Fixed the mismatch caused by the built-in SEOC (when enabled), and renamed it from “BiSEoC” to “EL-SEoC”

admin - 8-11-2019 at 04:03 PM

55.90 released. Has one new ts function and implemented BarsAgo (applies to indicators in GSB only, not to TS, MC, or NT yet) in IndicatorsTester,

admin - 12-11-2019 at 10:43 PM

55.93 under testing. Has a few bug fixes and data folder trees are shrunk bu default. I may not release till more significant improvements made.
Current build 55.90 seems quite good.
Support ticket placed to MC about their bugs that cause mc <> gsb was done today.

The ticket was
"We have recently discovered two serious bugs in indicators calculation that return incorrect values for many, and sometimes all, bars.

The first issue appears whenever we call an indicator of another (for example, HighestFc(AverageFC)) of a secondary data (such as Data2, Data3, etc.). This issue is mainly related to filtered data (or in other words, missing bars in the secondary data), which is quite common.

Moreover, the second issue is that the vars-call (as in value1=AverageFc; value2 = HighestFc(Value1)

gives different values compared to inline-calls (as in HighestFC(AverageFC))

, which is very confusing. After multiple tests, we have found that the vars-call is specifically wrong for some bars after Data2 date-gap (missing-bar compared to Data1), but the inline-call is nearly wrong in most bars, and even in Data1, unfortunately.

In the attached workspace, we have used a test data (CL as Data1 and HO as Data2) and a small indicator (MC_Test_Data2) to plot both var-call and inline-call and log them to files for an easy compare. "

admin - 14-11-2019 at 01:44 AM

50.96 under testing. (its failed)
It will have worker than can do wf, and build systems - but not both at the same time.
I think thats the most efficient use of cpu and ram.
Other small tweaks too.

admin - 17-11-2019 at 10:50 PM

50.98 released
bug fixes, and some minor improvements

admin - 21-11-2019 at 07:29 PM

51.01 released shortly.
bug fixes

Carl - 22-11-2019 at 01:22 AM

Peter, i think it is 56.01?

admin - 22-11-2019 at 01:52 AM

Quote: Originally posted by Carl

Peter, i think it is 56.01?

Your correct. Next we are finishing off Ninja Trader.

Daniel UK1 - 22-11-2019 at 03:05 AM

55.93 under testing. Has a few bug fixes and data folder trees are shrunk bu default. I may not release till more significant improvements made.
Current build 55.90 seems quite good.
Support ticket placed to MC about their bugs that cause mc <> gsb was done today.

gives different values compared to inline-calls (as in HighestFC(AverageFC))

Peter, have you heard back from MC support in regards to the bug? i propose that someone also post it on their forum, i would be happy to do it, however i am not sure i can argue my case for the bug since i am not a developer with proper knowledge of EL.

admin - 22-11-2019 at 05:25 AM

There has been zero response from mc. I will confirm when I hear anything. Yes, im open to numerous people complaining - as that might help.

admin - 26-11-2019 at 11:48 PM

Next build of GSB has all but two indicators matching Ninja Trader.

Newest video is just uploaded. This is critical for all user to see.
Significant changes in methodology, plus what works and doesn't work.
the video. Please hit like
https://www.youtube.com/watch?v=6bPAvyMXIwA&feature=youtu.be

admin - 28-11-2019 at 04:46 AM

under testing

1.0.56.04 / 2019-11-28:
Implemented LoadExtraPriceFiles(), ex. "Price Data.xyz.txt". This is so we can add price files (use in video demo) without over writing users price files)
Expiry extended to Mar 2020.
Updated Show Favorite C and D to be visible to all users.
defaults changed..
Disabled defaults of all SF indicators except Close/CloseD and CloseBpv.
Updated EntryLevelMode default from Exact to SignedPower.
Updated EntryLevelValue default from null to be 4.
Added VolumeLessPrevAverageFc, VolumeOverPrevAverageFc, and FractalDimension to all except trail users, enabled and SF disabled by default.
Removed CrossOrCloseD entry mode from trial users access.
Enabled CrossDualLevels (visible to all except trial users) by default.
Removed/Hided OptimizePriceData from trial users.
Updated "Entry Params." and "Entry Params. 2" defaults from 0:200:5 to -10:10:1 (and for WF params. as well).

admin - 29-11-2019 at 03:33 PM

56.04 released. 30 nov 2019

admin - 2-12-2019 at 01:00 AM

Next build has fix for MC issues when data2 has holes in the data

admin - 3-12-2019 at 07:19 PM

56.08 released. Dec 4 2019
The long awaited for GSB<>MC where there are holes in data2. Happy to say MC had a fix for the issue, without needed a new build of MC
Other bug fixes

admin - 9-12-2019 at 05:19 AM

56.12 under testing
Fixed SMTP in support ticket.
Added "Select Cloned" in PriceDataForm
dded "d-MMM-yy" date format. Note: MC export uses local machine format.
Fixed DataN in TS/MC scripts' variables. Note: Data(i1Data) is not supported in TS/MC, either Data(1) or Data1 allowed.

admin - 11-12-2019 at 09:54 PM

settings partial is in the next build. I did this due to my own human error in following the methodology.
The defaults are correct for building the 50k systems with all indicators. This assumes that other settings are at the updated defaults. ie signpower etc

This macro can then be programed to change the settings to find the best indicators too.

admin - 13-12-2019 at 12:08 AM

Next build will have price data trees shrunk as one user requested. I cant find his post but strongly agreed with his need for the feature. Happy to let the user try the feature as pee-release if they email me. Likely i get the build in 24 hours or so

admin - 17-12-2019 at 08:08 PM

under testing
56.18
Fixed/Updated PriceFiles.Initialize() to fix mismatches in multi-timeframe date (reported by Wong),
Fixed duplicates systems bug introduced before V56.09

admin - 18-12-2019 at 11:37 PM

56.18 released December 19 2019

Daniel UK1 - 19-12-2019 at 05:49 AM

Hmm my RM and GSB folder contains only latest 56.120
RM also starts new workers with 56.120, you sure its released ?

RandyT - 19-12-2019 at 04:18 PM

Could someone share with me what is required to get the beta version? Not seeing any way to enable that through RM and have not found a link for download.

tks

admin - 19-12-2019 at 06:42 PM

Quote: Originally posted by RandyT

Could someone share with me what is required to get the beta version? Not seeing any way to enable that through RM and have not found a link for download.

tks

should be fixed now. Rebooted the server, hadnt been done for months.

cipher - 19-12-2019 at 07:48 PM

settings partial is in the next build. I did this due to my own human error in following the methodology.
The defaults are correct for building the 50k systems with all indicators. This assumes that other settings are at the updated defaults. ie signpower etc

This macro can then be programed to change the settings to find the best indicators too.

is the settings partial file supposed to be in the Macros folder for 56.18? i dont see any new macro files after updating to the latest build

admin - 19-12-2019 at 08:09 PM

Quote: Originally posted by cipher

is the settings partial file supposed to be in the Macros folder for 56.18? i dont see any new macro files after updating to the latest build

There is no macro's included in any rm updates.The macro is (when you create a new macro). But the defaults for settings partial macro are what I used in my build process for ES. We are also working on settings full. It means we can publish our settings, but dont need to included the data files. Data files are too problematical. MC users have different symbols, people use different paths, and random data all has different names

admin - 19-12-2019 at 11:50 PM

If you dont have the feature already, there is export of the stats summary so you can cut and paste into excel. Should be in next build.

17584 23132 3993 3722 3319 2791 13825

admin - 27-12-2019 at 12:44 AM

Here is whats new in the next build. Out in the next week.
Export code with dates stripped for live trading version. (current version has a bug)

support ticket upload now includes your macros, and gsb admin mode file (if used)

settingsfull macro.
This allows us to have a set of macros, that all users can have to change settings. Every thing can be done (except changing data used - deliberately not done)

admin - 5-1-2020 at 08:46 PM

54.32 released. Jan 6 2020
This includes ts / mc / nt code for future release 56.34 and
portfolio analysts file that allows export of trades via a strategy, not xml file
See https://trademaid.info/gsbhelp/GettingdatafromTradestationto...

You dont need to load the new code for this release.

Daniel UK1 - 6-1-2020 at 04:09 AM

Hi Peter, can you please clarify what you mean with the below

"You dont need to load the new code for this release."

Regards

admin - 6-1-2020 at 04:25 AM

Hi Peter, can you please clarify what you mean with the below

"You dont need to load the new code for this release."

Regards

there is new eld & NT files included in the update files. Needed for the next build, not current one

admin - 7-1-2020 at 09:00 PM

under testing 56.35. Fix for multicharts bug where Closed(1) gives wrong values in some parts of the day.
It only affects some MC users. Mainly those who have sessions than span 2 days. IE time zones gmt10 Australia
All users will need to update ts/mc code to 20200107 version. It will be supplied in RM in c:\gsb\

Bruce - 8-1-2020 at 02:36 PM

under testing 56.35. Fix for multicharts bug where Closed(1) gives wrong values in some parts of the day.
It only affects some MC users. Mainly those who have sessions than span 2 days. IE time zones gmt10 Australia
All users will need to update ts/mc code to 20200107 version. It will be supplied in RM in c:\gsb\

Has this version been distributed out as it's not in my c:\gsb\

Thx.

admin - 8-1-2020 at 04:59 PM

Quote: Originally posted by Bruce

Has this version been distributed out as it's not in my c:\gsb\

Thx.

It will be on your gsb5 server, but not your local machine.
Only one other users has it yet

saycem - 8-1-2020 at 07:04 PM

Hi Peter
I read a few posts ago about settings full macro. Has this been released?
(My manager is on 56.18 and workers are on 56.32. I don't have a later manager version in any folder.)

admin - 8-1-2020 at 07:17 PM

Quote: Originally posted by saycem

Hi Peter
I read a few posts ago about settings full macro. Has this been released?
(My manager is on 56.18 and workers are on 56.32. I don't have a later manager version in any folder.)

no, i got busy on other things, the the defaults are correct I think if oyu make a new macro.

Will try to get to it monday.

you can always copy a worker to manger folder, and the rename it to the correct name. The worker file is identical to manager. Its just the name that determines the function

admin - 14-1-2020 at 12:37 AM

56.41 out
Fixed TrailingStop and AtrTrailingStop TS/MC script.
Minor GUI changes.
Fixed CounterTrend and CounterTrend2 indicators in GSB and NT.
Fixed GSB_CloseD in TS and MC to cover up MC closeD bug
Fixed macros run on manager's pause
New ts scripts should be on c:\gsb

admin - 16-1-2020 at 10:33 PM

Coming in 2-3 builds
Option of ticks (up&down volume) instead of volume (up only)
Note the current default will stay the same, but users should change to ticks.

Verification of systems can be done via macro as well as right click verify.

Option to save appsettings with machinename . ie myoptsettings.myDualXeon.gspopt (for user Randy)
This will give unique settings for each computer if its saved in a network/dropbox drive

All these features are being tested.

Data export including up & down volume

Gregorian - 16-1-2020 at 10:47 PM

That's great, Peter. Now in order for GSB to have access to the up and down ticks, users will need a consistent file export format. The attached indicator does precisely that, including the up and down ticks after the OHLC.

Attachment: Login to view the details

admin - 16-1-2020 at 11:08 PM

Quote: Originally posted by Gregorian

That's great, Peter. Now in order for GSB to have access to the up and down ticks, users will need a consistent file export format. The attached indicator does precisely that, including the up and down ticks after the OHLC.

Hi Alex,
all a user should need to do is to be consistent with the two modes of volume that are on ts/mc chart.

Please also reply to my comment on your indicator request with volume

admin - 16-1-2020 at 11:11 PM

in 56.49 average of custom field (in app settings gui) is now in stats. (for user Marco)
Build is under testing

admin - 22-1-2020 at 07:34 PM

In 1 to 3 builds.
fix for minor bug where default settings dont reload when you export params

Bug in new macro verify fix.

Working on whole new use of indicators.

ie if long use highest and if short use lowest.
Currently we use only highest for long and short

or lowest for long and short. etc
A few more indicators added

admin - 27-1-2020 at 12:45 AM

56.62 under testing.
Has option to turn all new features off. What will be turned on is only whats in your config files.

Ignore the 58 indicators. Some tests concepts that were tried, and some other indicators didnt work well, so need to try some alternatives.
These current new indicators wont be released.

admin - 28-1-2020 at 05:53 PM

Jan 29 2020 56.70 released
New ELD included.
For the few Alpha users who are using the total of 66/68 indicators - beware. The new indicators are experimental. Many I feel are not going to prove being good.
So many will get revoked, and or parameter used will change causing save systems to not match.

admin - 30-1-2020 at 06:22 PM

56.72 released.
Bug fix for error of no secondary filters used if manager is in beta tester mode, and worker is not.

admin - 31-1-2020 at 07:25 PM

coming in 2 builds, secondary filter stats. Its in my current build Im testing, but is very faulty

admin - 10-2-2020 at 12:10 AM

coming in a few builds
delayed start. It means you can in effect que multiple managers to work in sequence. When one has nearly finished, the other starts up

RandyT - 10-2-2020 at 08:29 AM

coming in a few builds
delayed start. It means you can in effect que multiple managers to work in sequence. When one has nearly finished, the other starts up

Very cool

admin - 14-2-2020 at 03:12 AM

20200214 56.95 released. Has new accumdistrubtion code in the eld, SF STATS and fixes, some of the new indicators moved so admin (not beta) users can use them

admin - 16-2-2020 at 06:48 PM

Coming in the next build is 10 more indicators. They will be on alpha mode only for some time. Not match to see if they = TS has been done yet

and a few builds latter wf efficiency (i hope)

admin - 18-2-2020 at 09:21 PM

in 57.05 under testing
walk forward efficiency

admin - 27-2-2020 at 07:13 PM

57.21 under testing.
has optional alt path to save systems, can be saved as default, and the symbol name is optional prefix on the file name.

We are upto 86 indicators in beta tester mode only

admin - 2-3-2020 at 03:50 PM

57.23 released. March 3 2020
has bug fixes for the last few builds that were not released plus features above

admin - 5-3-2020 at 02:49 PM

Very sorry, all users will get message gsb code is too old. Will get fix shortly

admin - 5-3-2020 at 03:48 PM

52.70 released via resource monitor. fix for expiry date + other features bug fixes and tweaks. WIll add later exactly what.

admin - 25-3-2020 at 09:48 PM

57.46 out soon.
fix for loading systems that give different results to when they were saved.
families coulomb moved further to the left.
All users have favorites c,d
fixes to default settings.
a few macro bugs fixed, inc nth " " now allowed
macro simple settings added
fix Fixed Volatility Indicator <> TS/MC/NT
MOC friday afternoon feature in settings, but not working yet.
Fix for TS dates in EWO out a little due to bug in TS
Fixed defaults in SettingsFull.
moving speed section to top right
fix for Save system opens system directory folder even though set to false

m15_CL_findBestIndicators

Next build after this, macros files in a sub folder allowed

admin - 26-3-2020 at 12:09 AM

march 26 2020. 57.46 released.
There still is a tiny bug in nth post build simple settings.

admin - 26-3-2020 at 03:25 AM

There is a bug in 57.46. Will be fixed in next release.
fav c&d may not appear. Reset app settings back to default.
Before you do this, remember your share key(s) if you are running your own workers that are not on your own lan/ip address

Attachment: Login to view the details

Attachment: Login to view the details

admin - 26-3-2020 at 11:22 PM

57.49 has fix for favorites issue.
sorry but above files were not in png format. Anyway reset is not needed now.
Forgot to mention a reset of app settings will also reset cache settings.

admin - 31-3-2020 at 12:51 AM

57.52 under testing.
Fix for NT error,
fix for no trades if Secondary filter turned off (for daily bars)

admin - 31-3-2020 at 10:16 PM

57.52 released

admin - 4-4-2020 at 12:27 AM

coming up is a macro to put current settings into macros. This will tend to give portability between users, but wont touch data files used.

admin - 6-4-2020 at 04:46 AM

in 57.57 under testing, the option to pull the current settings into macros.

admin - 15-4-2020 at 09:42 PM

Under testing 57.67

added ChaikinVolatility, CounterTrendHL working ok
Skew and Kurtosis, CounterTrendHL2 improved but not matching properly
Added QQQ, SPY, and NFLX to default/initial contracts
GSB recovers after prolonged no Internet connection
Fixed QQQ price file format issue
GSBsys1.2x in the included ELD's. (note private forum has improved 1.3)

Note also data center outage for 1 hour tomorrow

admin - 17-4-2020 at 06:27 PM

April 28 2020 57.67 released
New ELD, NT files included

Ninjatrader

kiwibird - 18-4-2020 at 02:29 PM

Is the current build still pretty much a beta for Ninjatrader?

admin - 22-4-2020 at 05:15 AM

Quote: Originally posted by kiwibird

Is the current build still pretty much a beta for Ninjatrader?

Sorry I missed this post.
Most users have NT working well, but at least two have a compile error. I think its a simple fix and hope to have it fixed shortly

admin - 22-4-2020 at 05:16 AM

April 22 2020
Fix for AvgDeviation indicator causing exceptions and slowing GSB down.
Its currently only in the beta users build. Now up to 92 indicators

admin - 22-4-2020 at 09:52 PM

57.73 released April 23 2020
1.0.57.73 / 2020-04-23 (TS/MC and NT script version 2020_04_22):
Renamed HighD1LowD1 to CloseOverPrevHighDLowD and HighD1LowD1CloseD1 to CloseOverPrevHighDLowDCloseD.
Minor update to CloseOverPrevHighDLowD and CloseOverPrevHighDLowDCloseD to use 2 * Close and 3 * Close, respectively.
Implemented GSB_DecisionCloseD in NT
Fixed ROC by renaming script name from "GSB_RateOfChange" to "RateOfChange"
Fixed AccumDist (Ticks) in NT

for beta users.
We are now uptp 90/92 indicators

EaseOfMovement Does not match - Partially fixed (next build)
ParabolicSAR Does not match GSB o/p is always zeros - Still to be fixed
TrendBiasIndex Does not match - Still to be fixed
TrendBiasExp Does not match - Still to be fixed
AccumDistClose Matches
AccumDistNoVolume Matches
AverageDnMove Matches
AverageUpMove Matches
AvgDeviation Matches
Detrend Matches
MACD Matches
TRIX Does not match - Still to be fixed
Volatility Matches
Fisher Couldn't test because GSB o/p is always -999 - Still to be fixed
FisherInv Couldn't test because GSB o/p is always NaN - Still to be fixed
DevSqrd Matches
CounterTrendHL Does not match - Still to be fixed
CounterTrendHL2 Does not match - Still to be fixed
HighLowC Matches
HighLowD Matches
HighLowHL Matches
HighLowLvl Matches

admin - 22-4-2020 at 10:12 PM

2 builds away, Fixed TrendBias and TrendBiasExp, partially fixed EaseOfMovement.

Daniel UK1 - 23-4-2020 at 02:33 AM

Perhaps in the wrong thread, but... i think it would be good if there was a library and in GSB, a short, easy to understand explanation of the indicator (Main and SF). Not just the math formula but a explanation in words what it actually does.. i think it would be very good for new people coming into GSB but also for myself i have to admit.. sometimes its not really easy to understand certain indicators and its application.. Regards

Bruce - 23-4-2020 at 02:39 AM

Perhaps in the wrong thread, but... i think it would be good if there was a library and in GSB, a short, easy to understand explanation of the indicator (Main and SF). Not just the math formula but a explanation in words what it actually does.. i think it would be very good for new people coming into GSB but also for myself i have to admit.. sometimes its not really easy to understand certain indicators and its application.. Regards

RandyT - 23-4-2020 at 06:48 AM

admin - 23-4-2020 at 05:00 PM

Hi Randy, not sure if you mean description for each indicator or just primary vs sf indicator
Think i need a section in the docs called understanding gsb architecture.
its in the videos, but not sure what ones and where.

admin - 27-4-2020 at 08:15 PM

57.79 under testing. This build may take some time as I suspect bugs that cause workers to stop. If there is a bug its not easy to find.
Fixed SwingIndex, AccumSwingIndex, Kurtosis, Skew, NormalDensity, LWAccDis and modified StdDev
Fixed ChaikinVolatility, partially fixed TimeCyclies, MoonSin, MoonSaw
Implemented CloseLessPrevHighDPrevCloseD, CloseLessPrevLowDPrevCloseD,
CloseOverPrevLowDPrevCloseD and fixed Trix indicators
Fixed TrendBias and TrendBiasExp, partially fixed EaseOfMovement.

We are up to 99/101 indicators in beta tester mode.
Updates / fixed to NT code, inc missing code for some functions

Daniel UK1 - 28-4-2020 at 01:01 AM

Hi Randy, not sure if you mean description for each indicator or just primary vs sf indicator
Think i need a section in the docs called understanding gsb architecture.
its in the videos, but not sure what ones and where.

Hi Peter, i meant for both SF and Main indicators, thanks

Yes understanding architecture section for GSB would be awesome.

Daniel

admin - 28-4-2020 at 01:02 AM

Hi Peter, i meant for both SF and Main indicators, thanks

Yes understanding architecture section for GSB would be awesome.

Daniel

I will add that in the docs in time.

admin - 6-5-2020 at 05:34 AM

being worked on now
Italian and German.
All the GSB docs are now auto translate via google

admin - 8-5-2020 at 05:21 AM

Just some updates
Its much more work to convert GSB to other languages. At least a weeks programing time for the first languge, then much less.
We are having Italian and German translated by a human, the other languages translated by google.
The docs are now all translated by google too.

Have spent about 6 months on CL. Ive done 70% of the content of part 1 of 2 today, but havnt started recording.
Part 2 will for GSB purchasers only, and has got lots on secondary filters that work with CL. (quite a number in the beta build)
and significant tweaks that improve things.

Tertiary filters are running in the programmers build, but still a bit rough and missing things like stats. (vip to me)

For GSB users, Im possibly going to launch VPS dedicated for trading, and some tools that reduce execution errors, and monitor your trading server.
Ive heard a few horror stories of execution issues of late. Keep in mind I trade a lot of contracts and Im always asleep when doing so. Hence why I need tight execution.

Daniel UK1 - 8-5-2020 at 05:47 AM

Just some updates
Its much more work to convert GSB to other languages. At least a weeks programing time for the first languge, then much less.
We are having Italian and German translated by a human, the other languages translated by google.
The docs are now all translated by google too.

Have spent about 6 months on CL. Ive done 70% of the content of part 1 of 2 today, but havnt started recording.
Part 2 will for GSB purchasers only, and has got lots on secondary filters that work with CL. (quite a number in the beta build)
and significant tweaks that improve things.

Tertiary filters are running in the programmers build, but still a bit rough and missing things like stats. (vip to me)

For GSB users, Im possibly going to launch VPS dedicated for trading, and some tools that reduce execution errors, and monitor your trading server.
Ive heard a few horror stories of execution issues of late. Keep in mind I trade a lot of contracts and Im always asleep when doing so. Hence why I need tight execution.

Sounds very good Peter, and yes CL has kept me also occupied almost full time since december.

I provided a CL system results comparison to show how much better Peters newly shared CL system is using latest methodology compared to my own developed CL systems using a much older version of GSB.
My systems was developed using very similar to previous methodology, but new features in GSB together with a better process has for sure provided better end systems as Peters system is showing.
One pic is showing all data, and one is showing previous 12 months.

I like very very very much the part about
"and some tools that reduce execution errors, and monitor your trading server."
This is really missing from both TS and MC.

Regards
Daniel

admin - 8-5-2020 at 06:07 AM

Hi Daniel, and others.
can you please email me execution issues you have experienced.
ie this week I had no trades on chart at all, until strategy turned off and on. It was an over night system but fortunately it failed just after the exit.
I want to see what the most common errors are.

Daniel UK1 - 8-5-2020 at 06:26 AM

Hi Daniel, and others.
can you please email me execution issues you have experienced.
ie this week I had no trades on chart at all, until strategy turned off and on. It was an over night system but fortunately it failed just after the exit.
I want to see what the most common errors are.

Hi Peter,

I dont have any issues at all..
However i think its a good idea you have in terms of prevention, since something like this does not exist, preferably that could alert you on mobile etc.. would be great.. tons of things could go wrong though with auto trading.. data loss, server down, software down/hangs, not closing positions end of day etc etc.. and lots lots of other stuff..

Regards

RandyT - 8-5-2020 at 07:01 AM

FWIW, I don't have these mysterious issues with trades not appearing on chart until start and stop and other resets of Tradestation either. Multicharts solved those issues for me.

Daniel UK1 - 8-5-2020 at 07:12 AM

A good topic about failure alerts

https://www.multicharts.com/discussion/viewtopic.php?t=47391

zazzi - 9-5-2020 at 08:44 AM

Hi - sorry if this is the wrong place to post but I don't think I have permission to make a new post.

I already have BuildAlpha and am keener on swing trades rather than intra day for now. My question is I wanted to understand the advantages of buying GSB. I have seen a number of posts here that GSB is superior to Adaptrade.

1) How is it vs Strategyquant?

2) I understand that all of these strategy generators are essentially tools to generate strategies and it is the user and not the software that makes the strategy such as to minimize the probability of it being fitted to the noise and not the signal. Accordingly, I can totally understand that "strategies created in X software" did not survive on unseen data may not be a fair criticism.

However, it is critical that, since the strategies are being generated through mining, it is very, very rigorous in cross-validation (or that generates a "lower number" of strategies that *would* certainly fail, whether through its built-in search optimization functions or the cross-validation tools).

3) Also, how is it in dealing with other types of instruments e.g. ETF's, futures from say, non US markets - i.e. not just the futures for which people primary use it for (ES, CL, Soybeans etc. as I may not be interested in trading these?) Can I very easily just load up, for example, OHLC data on say the Dhaka Stock index, if I want to trade this index? My sense is SQ may be more geared for example towards FX/Metatrader 4. From what I have seen and read, FX can be quite tricky for non-retail (primarily due to non-being on exchanges etc, broker manipulation). Also, what about not using TS and instead using Multicharts with IBKR?

Some of the comments in other forums seem to be that GSB is mainly best for ES systems.

4) To be frank, even if GSB is superior in all the other respects on the backend which is great, on a quick glance, its UI definitely seems to not be too intuitive vs SQ/Adaptrade - now, this may not be a problem for people who are very experienced with using the software but one would not want to spend too much time on trying to manually doing things?

Any thoughts appreciated.

Gregorian - 9-5-2020 at 02:25 PM

I already have BuildAlpha and am keener on swing trades rather than intra day for now. My question is I wanted to understand the advantages of buying GSB. I have seen a number of posts here that GSB is superior to Adaptrade.

I have BA, SQ, AT, and also TSL, as well as GSB. BA is much faster at generating strategies than GSB - minutes versus hours to get the best results - but OOS performance is relatively poor, and equity curves are not as flat. You also only get rare updates, versus GSB's very frequent updates.

1) How is it vs Strategyquant?

SQ has a superior user interface, but it generates orders using next bar at open rather than GSB's this bar at close, which makes it less reliable with special bar types such as Renko and Kase. Of all the competitors, SQ is the most likely to provide serious competition to GSB, though most of its users do not seem to be as sophisticated as GSB users.

3) Also, how is it in dealing with other types of instruments e.g. ETF's, futures from say, non US markets - i.e. not just the futures for which people primary use it for (ES, CL, Soybeans etc. as I may not be interested in trading these?) Can I very easily just load up, for example, OHLC data on say the Dhaka Stock index, if I want to trade this index? My sense is SQ may be more geared for example towards FX/Metatrader 4. From what I have seen and read, FX can be quite tricky for non-retail (primarily due to non-being on exchanges etc, broker manipulation). Also, what about not using TS and instead using Multicharts with IBKR?

I have used GSB with HSI and DAX futures, and GSB has not been able to generate strategies of comparable quality to those it can for the U.S. index futures. It may be because of the larger slippage associated with those foreign instruments.

I use MC. TS would bog down with fewer charts open and did not support multiple paper trading accounts, so was more restrictive with testing. Can't comment on IBKR; I use CQG and Rithmic. CQG is great; Rithmic is only good for execution, as they recently started cutting off users who downloaded significant historic data.

4) To be frank, even if GSB is superior in all the other respects on the backend which is great, on a quick glance, its UI definitely seems to not be too intuitive vs SQ/Adaptrade - now, this may not be a problem for people who are very experienced with using the software but one would not want to spend too much time on trying to manually doing things?

True, SQ and especially AT have superlative UIs, however that does not make up for their relatively lesser ability to generate flatter OOS curves.

GSB is your best bet of all of these products. Great support, sophisticated user community, and the fastest pace of advancement.

zazzi - 10-5-2020 at 02:43 AM

Thank you, that's very helpful - it seems like you've tried most of the mainstream available solutions on the market - TSL, which I understand is for $20k a year! - so its a very well reasoned view. Michael Harris (Price Action Lab) writes some great articles but I have heard its mostly marketing as the product is quite antiquated.

Do you also as a primary mode of trading - program strategies manually or do you principally use GSB etc. to generate the strategies (and perhaps, only as a secondary matter, tinker with them as you need). I guess, what I'm getting at is "if used properly/competently, could these tools substitute for a lack of programming expertise"?

When you say BA relatively poor on "OOS" do you mean "OOS" within the BA search engine or unseen data beyond the original OOS period (i.e. live/simulated)?

Also, have you used GSB systems for a "live" period longer than 2 years?

That is an issue I am now facing with TS - can't even login in 2 places at the same time or have a few simulator accounts running - very limiting and certainly not a long term solution. However, as I'm just building up the "business", I want to conserve cash and not fork out $1500 for MC just yet - perhaps in a year or so.

Also, would you say these tools are more "reliable" when generating swing ideas rather than intra-day?

Thank you again.

Gregorian - 10-5-2020 at 10:51 AM

Do you also as a primary mode of trading - program strategies manually or do you principally use GSB etc. to generate the strategies (and perhaps, only as a secondary matter, tinker with them as you need). I guess, what I'm getting at is "if used properly/competently, could these tools substitute for a lack of programming expertise"?

I trade with strategies produced by GSB, almost always unmodified. I don't write strategies manually any more.

While a lack of programming or indeed general IT experience does not preclude one from using these sorts of tools, it is certainly beneficial. I have over 40 years of programming and IT background, and it has been valuable.

When you say BA relatively poor on "OOS" do you mean "OOS" within the BA search engine or unseen data beyond the original OOS period (i.e. live/simulated)?

I mean within the curves BA generates. BA just seems incapable of producing very flat curves on strategies where the Average Trade is reasonable, i.e. two ticks or greater. Any of these tools will produce flat curves when you have an Average Trade of less than one tick, but that will never work in real life because the spread alone is at least one tick.

Also, have you used GSB systems for a "live" period longer than 2 years?

No. I keep learning ways to produce better strategies every few months.