GSB Forums

Not logged in [Login - Register]

Futures and forex trading contains substantial risk and is not for every investor. An investor could
potentially lose all or more than the initial investment. Risk capital is money that can be lost without
jeopardizing ones’ financial security or life style. Only risk capital should be used for trading and only
those with sufficient risk capital should consider trading. Past performance is not necessarily indicative of
future results
Go To Bottom

Printable Version  
 Pages:  1  ..  10    12    14  ..  19
Author: Subject: Report bugs here
avatartrader
Junior Member
**




Posts: 60
Registered: 1-10-2018
Member Is Offline

Mood: No Mood

[*] posted on 3-2-2019 at 06:39 PM


Not necessarily a correctable bug, but here is an issue that I experienced yesterday (which I was eventually able to resolve) that may have to do with how GSB managers/workers clear (or don't) cached or other in-memory system/price data between builds:

I was beginning to do some initial research and prototyping on the 6E to assess the viability of using some GSB to create some currency futures systems to add to my portfolio. As I just mentioned in the previous post, I discovered that I made an error in the contract specs, and so obviously, the first run of systems I created were invalid.

I stopped the build process, corrected the problem, updated the optimization settings, and started some new iterations. Even after the change, I was getting dramatically different results in TS/MC than GSB - even after restarting the manager.

Finally, I ended up clearing the price data cache on the manager, updating it with the most recent data, and starting a new iteration. This time, as I was clicking on the systems to review, many of the generated systems were recalculating as I was clicking on them, resulting in significant changes to the original stats as I went along.

However, this time both the recalculated systems and ones that didn't recalculate did match up when tested in TS/MC.

So, as best as I can tell, even though I had stopped the previous builds, there was something cached either on the manager or in the workers that was causing a significant number of systems to be generated and/or sent over that were generated based on bad data, probably associated with the original erroneous contract settings.

This was on 51.05 and all workers were being managed by RM. I didn't kill them between builds, so they definitely still had systems from prior builds.

At any rate, I am not having any issues now, but I thought I would mention it in case you think it is worth looking further into or anyone else has experienced similar behavior.





View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 3-2-2019 at 07:13 PM


Quote: Originally posted by avatartrader  
Not necessarily a correctable bug, but here is an issue that I experienced yesterday (which I was eventually able to resolve) that may have to do with how GSB managers/workers clear (or don't) cached or other in-memory system/price data between builds:

I was beginning to do some initial research and prototyping on the 6E to assess the viability of using some GSB to create some currency futures systems to add to my portfolio. As I just mentioned in the previous post, I discovered that I made an error in the contract specs, and so obviously, the first run of systems I created were invalid.

I stopped the build process, corrected the problem, updated the optimization settings, and started some new iterations. Even after the change, I was getting dramatically different results in TS/MC than GSB - even after restarting the manager.

Finally, I ended up clearing the price data cache on the manager, updating it with the most recent data, and starting a new iteration. This time, as I was clicking on the systems to review, many of the generated systems were recalculating as I was clicking on them, resulting in significant changes to the original stats as I went along.

However, this time both the recalculated systems and ones that didn't recalculate did match up when tested in TS/MC.

So, as best as I can tell, even though I had stopped the previous builds, there was something cached either on the manager or in the workers that was causing a significant number of systems to be generated and/or sent over that were generated based on bad data, probably associated with the original erroneous contract settings.

This was on 51.05 and all workers were being managed by RM. I didn't kill them between builds, so they definitely still had systems from prior builds.

At any rate, I am not having any issues now, but I thought I would mention it in case you think it is worth looking further into or anyone else has experienced similar behavior.

Lets keep an eye on this. Something to look at on the far right of the systems is the contract used. Check its the correct one, also not from another GSB user.
As far as I know this issue was fixed.
Also check if changes to nth / dates will make the stats = what they were before you clicked on them


View user's profile View All Posts By User
engtraderfx
Junior Member
**




Posts: 98
Registered: 15-10-2018
Member Is Offline

Mood: No Mood

[*] posted on 18-4-2019 at 04:45 AM


Minor issue noted testing AD (Aus dollar futures), the trade list only shows results in 2 decimal places so can't see actual trade value, should be to at least same decimals as contract being used (4 or 5 for currency in this case). Chrs, Dave

GSB AUD trade list.JPG - 114kB


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 18-4-2019 at 05:12 AM


Quote: Originally posted by engtraderfx  
Minor issue noted testing AD (Aus dollar futures), the trade list only shows results in 2 decimal places so can't see actual trade value, should be to at least same decimals as contract being used (4 or 5 for currency in this case). Chrs, Dave


Agreed, thanks for that. Will fix before too long


View user's profile View All Posts By User
appengineer
Junior Member
**




Posts: 61
Registered: 8-4-2019
Member Is Offline

Mood: No Mood

[*] posted on 24-5-2019 at 06:16 AM


Hi Peter,

I observed that when I run the wf-stats macro, the Global date and date range gets modified after the macros is complete

I started with End Global date of 2015-06-30 and date range of 1900-01-01 to 2015-06-30. This got updated to End Global date 2018-02-28 and range 1900-01-01 to 2018-02-28.

How does this change the result if I am rerunning wf-stats for Astab >=40, should I set it back to the original dates before rerunning macros or it doesn't impact the result?

Thank you


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 24-5-2019 at 06:19 AM


Quote: Originally posted by appengineer  
Hi Peter,

I observed that when I run the wf-stats macro, the Global date and date range gets modified after the macros is complete

I started with End Global date of 2015-06-30 and date range of 1900-01-01 to 2015-06-30. This got updated to End Global date 2018-02-28 and range 1900-01-01 to 2018-02-28.

How does this change the result if I am rerunning wf-stats for Astab >=40, should I set it back to the original dates before rerunning macros or it doesn't impact the result?

Thank you


yes
global and the other dates back to 20150630
nth to all
oos off
wf param off.
I can send a macro tomorrow
off to sleep now


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 24-5-2019 at 05:17 PM


Quote: Originally posted by appengineer  
Hi Peter,

I observed that when I run the wf-stats macro, the Global date and date range gets modified after the macros is complete

I started with End Global date of 2015-06-30 and date range of 1900-01-01 to 2015-06-30. This got updated to End Global date 2018-02-28 and range 1900-01-01 to 2018-02-28.

How does this change the result if I am rerunning wf-stats for Astab >=40, should I set it back to the original dates before rerunning macros or it doesn't impact the result?

Thank you

Here are my macros.
Check them before use.
We now have neat mouse-overs that show us the content.
But we also have some sort of issue where numbers sneaked in. My guess is there might be a macro version compatibility issue



macros-mouseover.png - 69kB

Attachment: Login to view the details



View user's profile View All Posts By User
appengineer
Junior Member
**




Posts: 61
Registered: 8-4-2019
Member Is Offline

Mood: No Mood

[*] posted on 26-5-2019 at 01:17 PM
How to name price data file


Is this a real bug, see attached

My price data file is named as
NG1330.1.MINUTE.900-1430_CentralUsaTime_cl_ho_ng_rb_09-2006-to-date.txt

Capture.PNG - 21kB


View user's profile View All Posts By User
Carl
Member
***




Posts: 342
Registered: 10-5-2017
Member Is Offline

Mood: No Mood

[*] posted on 26-5-2019 at 02:36 PM


I think you have to use Minute, not MINUTE

View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 26-5-2019 at 05:46 PM


appenginer,
I think the issue is in the format of the data. Tools app settings data.
most MC/ts/quote.com formats are auto detect


View user's profile View All Posts By User
appengineer
Junior Member
**




Posts: 61
Registered: 8-4-2019
Member Is Offline

Mood: No Mood

[*] posted on 27-5-2019 at 12:41 PM


Quote: Originally posted by admin  
appenginer,
I think the issue is in the format of the data. Tools app settings data.
most MC/ts/quote.com formats are auto detect


I exported the data from TS
Here is a sample
02/28/2008,14:24,18.553,18.553,18.532,18.532,29,91

And the settings
M/d/y,
yyyyMMdd,
d/m/y,
M/d/yyyy,
d/M/yyyy

H:m,
HHmm,
H:m:s,
HHmmss,
HHmmss fffffff

I will also try to change the file name from MINUTE to Minute when the build is done.

Thanks


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 27-5-2019 at 05:07 PM


appengineer
d/m/y is incorrect
its d/M/y //M is month., m is minute

see the last part of this in the docs
https://trademaid.info/gsbhelp/Data1.html
I asked the programmer, whats case sensitive in gsb.
Nothing except share keys, date time file formats under app settings , workplaceid, instantID, sharekeys
symbol.MINUTES.30 IS FINE IN UPPER and lower case


View user's profile View All Posts By User
boothy
Junior Member
**




Posts: 54
Registered: 21-5-2018
Member Is Offline

Mood: No Mood

[*] posted on 29-5-2019 at 07:40 PM


Hi Peter,

I have just started up 52.45 to do some testing and GSB is stuck on status initializing and is not picking up any workers and is not starting to build systems. Its been initializing now for 15min.


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 29-5-2019 at 07:51 PM


Quote: Originally posted by boothy  
Hi Peter,

I have just started up 52.45 to do some testing and GSB is stuck on status initializing and is not picking up any workers and is not starting to build systems. Its been initializing now for 15min.

Is that the wf status?
send me a screen shot and or teamviewer details


View user's profile View All Posts By User
boothy
Junior Member
**




Posts: 54
Registered: 21-5-2018
Member Is Offline

Mood: No Mood

[*] posted on 29-5-2019 at 08:34 PM


Quote: Originally posted by admin  
Quote: Originally posted by boothy  
Hi Peter,

I have just started up 52.45 to do some testing and GSB is stuck on status initializing and is not picking up any workers and is not starting to build systems. Its been initializing now for 15min.

Is that the wf status?
send me a screen shot and or teamviewer details


No it was status under workplace R/H GUI. It finally did start building systems but none had any system metrics.
I think its related to price files again. I updated my ES 1 min file but when I add it in and put multiplier of 30, as soon as I click OK it changes the time frame from 1 to 30.




Pricedataissue.PNG - 167kB


View user's profile View All Posts By User
appengineer
Junior Member
**




Posts: 61
Registered: 8-4-2019
Member Is Offline

Mood: No Mood

[*] posted on 30-5-2019 at 06:05 AM
GSB Worker - Guard page Error


Hi Peter,

See attached, is it because of running too many workers, running 10 workers on e5 2680, 256GB RAM

Thank you

Untitled.png - 6kB


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 30-5-2019 at 06:07 AM


Increase your virtual mem size and reboot.
Likely rm not configured correctly


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 30-5-2019 at 08:02 AM


Hi Boothy
that looks correct. your c/us figure is good. (lower is good)
1min * 30 is supposed to give 30
Im not sure if your stuck or resolved.


View user's profile View All Posts By User
boothy
Junior Member
**




Posts: 54
Registered: 21-5-2018
Member Is Offline

Mood: No Mood

[*] posted on 30-5-2019 at 04:55 PM


Quote: Originally posted by admin  
Hi Boothy
that looks correct. your c/us figure is good. (lower is good)
1min * 30 is supposed to give 30
Im not sure if your stuck or resolved.


All the metrics of the systems, np, fitness,A/T etc were all 0.

I've just shut down GSB and tried again and seems to be working now.


View user's profile View All Posts By User
Gregorian
Junior Member
**




Posts: 97
Registered: 23-5-2017
Member Is Offline

Mood: No Mood

[*] posted on 26-9-2019 at 02:26 PM


In 55.38, the top half of the results screen (the Performance-Graphs-Trades part) does not populate. When you click on any of the line items below for a generated strategy, the graph etc. do not appear.

View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 26-9-2019 at 03:57 PM


Quote: Originally posted by Gregorian  
In 55.38, the top half of the results screen (the Performance-Graphs-Trades part) does not populate. When you click on any of the line items below for a generated strategy, the graph etc. do not appear.

Hi Gregorian, good to hear form you again. Can you show a screen shot?
Teamviewer.com also may be a good idea. Ive used .38 a lot and not had issues, but I cant tell more without looking at it.


View user's profile View All Posts By User
Daniel UK1
Member
***




Posts: 470
Registered: 4-6-2019
Member Is Offline


[*] posted on 27-10-2019 at 11:18 AM
Systems deleted and dates showing is 1899 after clicked


Error, systems being developed on CL, systems being generated and then when i click on then, the graph is deleted and i just see 0... i have tested different version of GSB, i have removed and loaded price files again, i have changed dates... the strange thing is that dates on the graph thats deleted, shows 1899 12 30 .... i am using US date formats and you can see price file in the screenshot... i dont know what to do... can not develop any systems until hat is causing this is fixed, kindly help// Thanks

Captureclerror1.JPG - 296kB Captureclerror.JPG - 394kB


View user's profile View All Posts By User
OUrocketman
Junior Member
**




Posts: 18
Registered: 10-5-2018
Member Is Offline

Mood: No Mood

[*] posted on 27-10-2019 at 01:24 PM


Peter,

Hope you and your family are well, and thank you for all the work you put into your products!

I have noticed what could be a bug. Whenever I run the manager 55.60 with Nth mode set to no trade some of the systems come back with results shown as having nth mode set to all and some come back as having nth mode set to no trade. Important to mention here that I have the macros run on opt complete flag set to false.

Can you confirm if there is programming in GSB that's not transparent to the user that makes results in the manager show up as nth mode set to all even though they may be being built with nth mode set to no trade, or does something seem to be going awry somewhere?

Also, not really a bug, but trying to keep posts to a minimum, is it a known thing that NQ is not as easy to build systems for as ES? Starting to do some systematic work on improving NQ, but first would like to verify I'm not inventing the wheel in this regard.

Thank you for your time! :)


View user's profile View All Posts By User
admin
Super Administrator
*********




Posts: 5060
Registered: 7-4-2017
Member Is Offline

Mood: No Mood

[*] posted on 27-10-2019 at 03:08 PM


Quote: Originally posted by OUrocketman  
Peter,

Hope you and your family are well, and thank you for all the work you put into your products!

I have noticed what could be a bug. Whenever I run the manager 55.60 with Nth mode set to no trade some of the systems come back with results shown as having nth mode set to all and some come back as having nth mode set to no trade. Important to mention here that I have the macros run on opt complete flag set to false.

Can you confirm if there is programming in GSB that's not transparent to the user that makes results in the manager show up as nth mode set to all even though they may be being built with nth mode set to no trade, or does something seem to be going awry somewhere?

Also, not really a bug, but trying to keep posts to a minimum, is it a known thing that NQ is not as easy to build systems for as ES? Starting to do some systematic work on improving NQ, but first would like to verify I'm not inventing the wheel in this regard.

Thank you for your time! :)

This bug has been reported buy one other user. I have a few options to fix it.
1 fix this bug in 55.74
2 give all users 55.74
3 only allow 55.60 managers to talk to 55.60 workers

So I hope to have a fix for it, and are close to releasing 55.74 but I have a few bugs reported in 55.74. I can send you 55.74 too.
auto Nth has changed from app settings to opt settings, and this has a bug for compatibility with older workers.

User Bruce has done a lot on NQ, and hes going to post some stuff in time. Hes building up some OOS results in real time- which needs a decent amount of time to be significant.




Thanks received (1):

+1 OUrocketman at 2019-10-27 16:48:28
View user's profile View All Posts By User
Daniel UK1
Member
***




Posts: 470
Registered: 4-6-2019
Member Is Offline


[*] posted on 27-10-2019 at 04:21 PM


Quote: Originally posted by Daniel UK1  
Error, systems being developed on CL, systems being generated and then when i click on then, the graph is deleted and i just see 0... i have tested different version of GSB, i have removed and loaded price files again, i have changed dates... the strange thing is that dates on the graph thats deleted, shows 1899 12 30 .... i am using US date formats and you can see price file in the screenshot... i dont know what to do... can not develop any systems until hat is causing this is fixed, kindly help// Thanks


Btw its not only on CL where it has happened


View user's profile View All Posts By User
 Pages:  1  ..  10    12    14  ..  19

  Go To Top

Trademaid forum. Software tools for TradeStation, MultiCharts & NinjaTrader
[Queries: 67] [PHP: 32.5% - SQL: 67.5%]