GSB AUTOMATION

indicator testing is built, but has one critical bug still
this saves the green_orange onto the app settings file name.

Quote: Originally posted by Daniel UK1

Hi, very interesting stuff, i also believe this will help a lot. Will you also include in GSB the possibility to by auto/macro, test each choice within a specific setting and then save this to excel, for example test all or some option in Entry mode seting? And will it compile it to one result in excel, or you need to save the result per single choice/test? Would be great with option to compile results to one excel table, for the people with not so much python skills. Cheers

Im working on this but dont yet know how it will be done.
Its easier to shuffle through a set of indicaots (ie sf) or entry types in sequence.

But to choose the sequence is harder to do. It all can be done though

We are 1 tweak away from 2 pass and build being 100% automated, though export of final stats to csv not done yet
see new command line autoexit feature

Quote: Originally posted by Carl

A lot of this kind of analysis can be done in Excel. Grouping per indicator can also be done by using a pivot table in Excel. Averages, median, standard deviation and so on. Anyone interested in this? I can post a video to show how to do this.

two pass method now works 100% via dos prompt, but export of stats to CSV file not done yet

/autoexit could be used on the pass1 and pass2 lines
this would close GSB
all this can be run from batch file using windows start feature.
(someone is welcome to show how this is done)
Macros will be in file repository in next day

Quote: Originally posted by admin

This is not the direction i'm going it, but seeing what UI path could do made me appreciate how much better GSB will be when much more is automated. Im going to have GSBAutomation, a front end batch processor for GSB. Likely UI path can do more, but user Randy has said UI path etc is sometimes a bit problematic for a variety of reasons. However even if you use UI path, more and more automation can be done inside of GSB Here is a video kindly made on how to use UI path

Quote: Originally posted by RandyT

Quote: Originally posted by admin   This is not the direction i'm going it, but seeing what UI path could do made me appreciate how much better GSB will be when much more is automated. Im going to have GSBAutomation, a front end batch processor for GSB. Likely UI path can do more, but user Randy has said UI path etc is sometimes a bit problematic for a variety of reasons. However even if you use UI path, more and more automation can be done inside of GSB Here is a video kindly made on how to use UI path Just to put my cards on the table in case someone wants to challenge my thinking regarding these UI automation tools... I see these tools like UIPath, pywinauto, etc. as stop gaps for situations where the application being driven by these tools is unable or unwilling to automate these tasks. The scripts created by these tools are somewhat fragile and very dependent on the application being driven to not change, and have well written UIs that properly define all windows elements. If any of those UI elements change, it will usually result in your hard work developing these automation scripts to be broken, requiring updates to match new UI element names and workflows. These tools have their place, but given Peter is willing to invest in developing these automations in GSB, IMO that is the best place to do this. Counterpoints welcome.

next build has export stats. Its working now but needs some tweaks

Show is my build+stats + export macro

build 46 under testing
it has stats

Quote: Originally posted by admin

build 46 under testing it has stats

Quote: Originally posted by Bruce

Quote: Originally posted by admin   build 46 under testing it has stats Hi Peter, I can't see 'ExportStats'' in the Macro list of actionable items, or am I missing something? Thx.

Quote: Originally posted by admin

Quote: Originally posted by Bruce   Quote: Originally posted by admin   build 46 under testing it has stats Hi Peter, I can't see 'ExportStats'' in the Macro list of actionable items, or am I missing something? Thx. It can only be seen on .46 build or above. DO you have this on any of your machines? If not I will send you a url to the exe.

Yes, I'm running .46 now, I just started a new test and I can see it now at the bottom of the list.

These macros will be in .47 build (not made yet)
and the batch file in c:\gsb\gsb_batch.bat
the batch file assumes that your app settings are CL_TEST1.gsboptset
Best edit the macros to see what they do

Quote: Originally posted by Bruce

Quote: Originally posted by admin   Quote: Originally posted by Bruce   Quote: Originally posted by admin   build 46 under testing it has stats Hi Peter, I can't see 'ExportStats'' in the Macro list of actionable items, or am I missing something? Thx. It can only be seen on .46 build or above. DO you have this on any of your machines? If not I will send you a url to the exe. Yes, I'm running .46 now, I just started a new test and I can see it now at the bottom of the list.

Likely we need to alphabeticaly sort the list.
When you loose something and its found, you find it in the last place you look.
You should go to the last place you look first
disclaimer, some pearls of wisdom may only be clear after the event and not useful for forward testing / living

It does 1 run in 1 manager
pass1. ie green orange or green

then pass2 normaly green

then build 50k, and do stats.
I did this 4 times to get stats on 4 different but identical tests
Here are results as an example

Avg. A Avg. B Avg. C Avg. D
28817 940 2013 3790
Avg. A Avg. B Avg. C Avg. D
28522 783 2144 4312
Avg. A Avg. B Avg. C Avg. D
28931 868 2012 3649
Avg. A Avg. B Avg. C Avg. D
29115 746 2106 4970

you can edit the macros supplied to see the function

Peter, i tried quickly the macro "indicator testing" and used green only, and save app setting to true ( i initially read t quickly and thougth it was OPT setting)
So my observation is like this... stats for params. look different compared to when done manually and when done by macro, a bug or feature ?

I ran the macro 3 times after each other after manually resetting the params ... the file name is saved by adding a "green" wording aafter each file saved, feature or bug ? i assume its somehow a feature to differentiate from multiple runs...

I am confused by the option "save app setting" in the macro, since it would be logical if it was OPT setting, but app setting ?
I can see the OPT setting getting saved, after running the macro, but i cant see any APP setting getting saved despite my was set to true by mistake..

Anyway, i understand we are just in the beginning of these features and i think it will save lots of time going ahead, after a proper understanding of how to incorporate them into the workflow process.

Cheers

Quote: Originally posted by Daniel UK1

Peter, i tried quickly the macro "indicator testing" and used green only, and save app setting to true ( i initially read t quickly and thougth it was OPT setting) So my observation is like this... stats for params. look different compared to when done manually and when done by macro, a bug or feature ? I ran the macro 3 times after each other after manually resetting the params ... the file name is saved by adding a "green" wording aafter each file saved, feature or bug ? i assume its somehow a feature to differentiate from multiple runs... I am confused by the option "save app setting" in the macro, since it would be logical if it was OPT setting, but app setting ? I can see the OPT setting getting saved, after running the macro, but i cant see any APP setting getting saved despite my was set to true by mistake.. Anyway, i understand we are just in the beginning of these features and i think it will save lots of time going ahead, after a proper understanding of how to incorporate them into the workflow process. Cheers

.48 build has this in export now
Avg. A Avg. B Avg. C Avg. D
27717 649 1867 2771
PRIMARY
AverageFc
BollingerUpperBand
CloseOverPrevCloseD
Dmi
FastK
ForwardReverseEMA
LowestFc
MyRSI
MyStochastic
XAverage
SECONDARY
CloseLessPrevHighD
ENTRYMODES
Compare2

Quote: Originally posted by admin

Hi Nick & Daniel The option of manager staying open, but batch continuing has been planed from the beginning. I know its needed. Not a lot of work to do and it will be done. Correct that save settings should be called saved opt sttings, not app settings. This will be renamed. Export to stats (not custom export ) can be done a little down the track Daniel,is whats in stats what you want? If not change the m3-macro dates etc Or is the problem whats in stats doesnt export correctly. A dont use just AB but ABCD cHECK ARE YOU ON 58.47 AND do you have export stats at the end of the macro

Hi Peter,

What i want exported is what i have in my included picture, what i have now is as you can see something else.. but i think it is as intended from you, but not what i wanted exported

Quote: Originally posted by Carl

Hi Randy, I agree. have worked with Blue Prism RPA (robotic process automation) in the past (not on GSB). Every little change in the underlying software you are trying to automate by using RPA can cause the RPA script to fail. I think GSB's development is too fast to be controlled by RPA. Better solution is to automate the steps within GSB. Setting up GSB could be improved by using a more process driven approach instead of data driven. The analysis part should be a combination of process and data driven aproach I think. What does the maker of the video think? I think I saw the name Lorenzo in the video?

Quote: Originally posted by Daniel UK1

Peter, sounds great, where do i find GSB automation software? btw this time updates with new managers and standalone worked, so thats also great.

Quote: Originally posted by Daniel UK1

For auto software..I struggle to understand logic of how i can control when a macro is started within same manager, for example i want to have the auto software to launch a manager and then run 3 separate macros in the same manager after another... and how i control instead to have 3 separate managers after each another, running one macro per manager... is the logic that if Start to build, is in the macro a new manager is started, and when not a macro is just run in same manager after another ?

Quote: Originally posted by admin

Daniel, In ideal world, the front end for Automation needs a lot more work, though its functional. Not sure if you realize but its a modification of GSB Benchmark program more from me later

Quote: Originally posted by Daniel UK1

Quote: Originally posted by Daniel UK1   For auto software..I struggle to understand logic of how i can control when a macro is started within same manager, for example i want to have the auto software to launch a manager and then run 3 separate macros in the same manager after another... and how i control instead to have 3 separate managers after each another, running one macro per manager... is the logic that if Start to build, is in the macro a new manager is started, and when not a macro is just run in same manager after another ? Is it possible to setup from one instance to run 3 separate managers started after each other with a chain of macros in each manager. Or is it only possible to run one macro per manager started ? I think i just struggle to understand the full logic so i can control it as i want.

you can run as many managers s you want in sequence.
Whats not done is the ability to change things while AU is running. Im really keen to have this.

There has been a change in todays build.
It was way too complex having macros and having to choose opt settings for each line.
Now we choose opt settings, and have a choice of macro
green , greenorange, or build
I had way too much human error due to this.
What I still need to do is have Custom macro as well as these three
setup now really simple
show here is two pass using green each time
of course you could add one line and make it 3 pass etc

Quote: Originally posted by admin

Quote: Originally posted by Daniel UK1   Quote: Originally posted by Daniel UK1   For auto software..I struggle to understand logic of how i can control when a macro is started within same manager, for example i want to have the auto software to launch a manager and then run 3 separate macros in the same manager after another... and how i control instead to have 3 separate managers after each another, running one macro per manager... is the logic that if Start to build, is in the macro a new manager is started, and when not a macro is just run in same manager after another ? Is it possible to setup from one instance to run 3 separate managers started after each other with a chain of macros in each manager. Or is it only possible to run one macro per manager started ? I think i just struggle to understand the full logic so i can control it as i want. you can run as many managers s you want in sequence. Whats not done is the ability to change things while AU is running. Im really keen to have this. There has been a change in todays build. It was way too complex having macros and having to choose opt settings for each line. Now we choose opt settings, and have a choice of macro green , greenorange, or build I had way too much human error due to this. What I still need to do is have Custom macro as well as these three setup now really simple show here is two pass using green each time of course you could add one line and make it 3 pass etc

Here is a preview of the next build. The SF option doesnt yet work in this build, but if gives you an idea if it.

Automation is now fully working going through the secondary filters.
I want to finish all cl work in the next few days. If anyone has spare cpu time, please email me your share keys. I will then share the entire results file.

Quote: Originally posted by Daniel UK1

Hi Peter, does this mean that one cant anymore use different macros per opt setting used as i do now? I kind of sense that the macro table is used for all opt settings in your frontend pic ? Looking forward to test the toggle trough settings feature, it means though that one needs to be able to export output stats as one can see it now in gui.

Quote: Originally posted by admin

Quote: Originally posted by Daniel UK1   Hi Peter, does this mean that one cant anymore use different macros per opt setting used as i do now? I kind of sense that the macro table is used for all opt settings in your frontend pic ? Looking forward to test the toggle trough settings feature, it means though that one needs to be able to export output stats as one can see it now in gui. there is now two custom macro fields, The version you tested did not yet have this feature I will get you a copy in < 24 hours. The exit manger option is buggy and managers stay open when you say they should close. Apart from that the build works fine

Quote: Originally posted by Daniel UK1

Sorry, i used the wrong word should have been Auto Software GUI "macro table" on the left side, i am not unclear of any specific macro. I mean that today, in auto software, in the GUI on the left side, i use settings group, to add an opt setting and then macros i want to use on that opt setting. If i want to use another opt setting i just click on add in GSBSettingsGroup2Collection Editor, and add another opt setting and macros i want to use.. so this is what i do today. However in the new GUI you showed a picture of, on the left side you seem to add macros before you even chose opt setting.. so my question what is the logic of that, is that macro table used for ALL opt settings you add in settings? or can you still use specific macros per opt setting as i can now ? I hope this clears out the misunderstanding. If not, perhaps you can just explain the logic of the gui where you seem to add macros before deciding which opt setting that its for ? Many thanks

Quote: Originally posted by admin

Quote: Originally posted by Daniel UK1   Sorry, i used the wrong word should have been Auto Software GUI "macro table" on the left side, i am not unclear of any specific macro. I mean that today, in auto software, in the GUI on the left side, i use settings group, to add an opt setting and then macros i want to use on that opt setting. If i want to use another opt setting i just click on add in GSBSettingsGroup2Collection Editor, and add another opt setting and macros i want to use.. so this is what i do today. However in the new GUI you showed a picture of, on the left side you seem to add macros before you even chose opt setting.. so my question what is the logic of that, is that macro table used for ALL opt settings you add in settings? or can you still use specific macros per opt setting as i can now ? I hope this clears out the misunderstanding. If not, perhaps you can just explain the logic of the gui where you seem to add macros before deciding which opt setting that its for ? Many thanks On the left there is green, green/orange, build and 2 customs These are the only choices you have for pre-defined macros. You can of course change them at any time. The obn the right you can chose your pre-defined, green,greenorange, build,custom1,custom2 Hope this helps A video should be done before long. AU needs many tiny changes, but its working 100% ok

Quote: Originally posted by Daniel UK1

Out of curiosity, are you or Nick and Randy using Python to compile all excel files when done to one table for comparison ? Thanks

Quote: Originally posted by NickW

Daniel, I'm also still waiting for the stats export to be complete before automating that part. Right now I manually copy and paste the results into a Google Sheet for further analysis. My eventual goal is to store all these results in a database for analysis and record keeping. Will probably be using python to do all that. Nick

Quote: Originally posted by Daniel UK1

Just to point out, i dont have a complete failure for the actual export.... its just that what is exported i can not use, i can not control what is exported and format is strange.. What i want is what i can see in the GUI frame, that i now by hand export by copy paste.. Also i woke up to having a few crashes with exception error, of new released auto software... i saw that new workers and managers was released... i think this has something to do with it, because before that update new release was working all good. I had a crash with new release yesterday but this was after i pasted a very long sentence to the header input, after that it crashed also. with crash i mean exception error. But tonights several crashes i believe has to do with update.

best email me the exception report.
Ive had not issues yet 58.55, but found one Italian user than has Italian number formats in windows, which caused lots of bugs and mismatchs.
The short term fix was windows to standard usa number formats.
Im running about 250workers and all ok that I can see

Quote: Originally posted by Daniel UK1

Auto tool is using path to manager version before updated one.. and i just correlated the crashes overnight of auto tool to the update that happened ... before that all was good... so its not manager that crashed... it was auto software.. It also crashed one time before the update, but that happened after i populated the header text Cheers

New feature in GSB.
we tell automation that we are finished as soon as systems made. This means we can start building the next lot of systems before stats is done.
This saves a number of minutes each loop as we dont need to wait for stats

Somehow, AU somehow is not providing data for elapse and cumulative time, very strange...

Edit, just got numbers after first one was finished, so i assume time numbers dont get populated while running, Never thought about it before.

Quote: Originally posted by getty002

I've been attempting to get automation to work, but I get a timeout every 2 minutes for each step in the automation list. I'm not receiving feedback as to the error, but no instance of GSB Manager opens, yet it says "done" after 2 minutes. Any feedback on where I may be setting up the tool incorrectly? Path is pointed to the correct location for GSB manager, the option settings, and app settings. Both settings files work fine directly in the GSB Manager. Thanks.

Quote: Originally posted by admin

Likely cause is you are running the tool without a matching macro Copy the macros in the macro subfolder of AU \MacrosToAddIntoGSBMacroFolder and put into GSB macro folder Then select the macros in AU There is no error messeage in GSB for running invalid macro file, but it gives an exception in the exception folder

Quote: Originally posted by getty002

Quote: Originally posted by admin   Likely cause is you are running the tool without a matching macro Copy the macros in the macro subfolder of AU \MacrosToAddIntoGSBMacroFolder and put into GSB macro folder Then select the macros in AU There is no error messeage in GSB for running invalid macro file, but it gives an exception in the exception folder OK, now I'm past that step. Thank you. I pointed the macro file location to the original folder, but it requires being in the GSB macro folder? I regularly have file pointing problems withing GSB, not sure if this is just me, due to Google Drive perhaps. Next question - for members 0 and 1, can I use the same Opt Settings file? Will the macro make the necessary changes to switching from 2 to 3 indicators, etc? How do I know what fields the macros change? The time zone of my data is not market time, so I've had some troubles with the macros changing the trading time to something incorrect for my data. Thanks.

Quote: Originally posted by getty002

After waiting for 3 hours for step 1 to complete, step 2 looked for the same exact option file from step 1 and crashed with the error "***.gsboptset does not exist". Why would it find the file in step 1, but not in step 2? Is there a way for the AU to check all files up front rather than crashing hours into the job? Thank you.

Quote: Originally posted by Daniel UK1

Thanks Peter for header lenght. Btw now when AU is up and running, do you use command line for any purpose in your process?

here else is whats planned.
custom#2 to give full stats export. See whats in cyan.

Data streams used will only export when au index=1 (default option will be true)

Quote: Originally posted by zordan

Peter, do you mind sharing in the paid forum the results (e.g. best indicators and secondary filters) from your latest automation work?

Im still working on it. Got interesting results but im redoing a fair bit of it.
Later tests used a total of 12 SF, but earlier tests did not.
So I want to do all tests on 12 sf to make valid comparison.
This is another 2 days work.
I will put results in private forum before too long, but the users who generously donated there cloud power are going to get all the full output files, and get them before everyone else. I think its fair to reward them for their contribution.
Collectivly its awesome what the GSB community can do together.
23 computers peaking 293 workers right now

Quote: Originally posted by zordan

Hi Peter, how can I give you cloud power? I agree the working as a community is more efficient. You are the GSB expert so it's probably better you drive this work. I would be interested in seeing your results on indicators+SF on all major tradables... it will take time but if we all give you cloud power it could be quicker...

Select minimum # indicators

Peter, sometimes when after pass2 you might not have a lot of green indicators to select only the green ones for final build.
Maybe we need a minimum num indicators in the IndicatorTesting macro so that if will select at minimum lets say 5 indicators, whether they are green or not.
If there's more than 5 that is green it will select ALL the green ones, otherwise it should start picking orange ones from the top down until reached...

Quote: Originally posted by NickW

Peter, sometimes when after pass2 you might not have a lot of green indicators to select only the green ones for final build. Maybe we need a minimum num indicators in the IndicatorTesting macro so that if will select at minimum lets say 5 indicators, whether they are green or not. If there's more than 5 that is green it will select ALL the green ones, otherwise it should start picking orange ones from the top down until reached...

Quote: Originally posted by Bruce

Hi Peter, Now that we can #move SF, is there plans to perform the same process for 'Entry Mode'?

Quote: Originally posted by admin

there is a new build of AU via auto update. It will only update if all au are closed on the machine. It also requires 58.62 manager or later. Hope to release that soon.

Quote: Originally posted by Daniel UK1

Hi Peter, as i understand header text in AU shall auto populate to manager, as it is now.... it kind of works, but not fully.. if i put the text 14 15 16 in header in AU, it populates only "14" I assume conclusion is that on the first word/letter populates but not anything after a spacing.. Apart from this it seems to work great, stats has not been tested yet though. Cheers

likely space is used as seperate command. I will see if we can fix that.

coming I hope next build is the ability to pic x indicators, if there are less than x.
Nick requested this and its good idea for a few reasons.
1 to slow to build 50,000 systems with few indicators. Not enough choice.
2 Range of systems is very low

Quote: Originally posted by Daniel UK1

Hi Peter, Thanks for that. About indicators, I like Nicks idea very much, makes sense, still have not encountered below 4 though when doing green green method. Below 4/5 is not really great i think, on my end i find best results around 4/5 for NG, and in CL a bit higher around 6-9. Have you experienced the same behaviour ? and how do you define "few" indicators? 3-4? Regards

Quote: Originally posted by admin

20200729.3 build released via auto update 1 bug fix 2 allows multiple au to be run at the same time

Interesting, i been running multiple AU since day 1 , was there a bug in regards to this ?

Quote: Originally posted by Daniel UK1

Quote: Originally posted by admin   20200729.3 build released via auto update 1 bug fix 2 allows multiple au to be run at the same time Interesting, i been running multiple AU since day 1 , was there a bug in regards to this ?