General support questions.

Hello
I'm building on crude and I get this trading chart.
The start is very strange, a straight line
I would like to know why this straight line comes out.
Is it a bug?
I think that line increases metrics, and that affects strategy performance, falsifying it

Quote: Originally posted by portfolioquanttrader2020

Hello I'm building on crude and I get this trading chart. The start is very strange, a straight line I would like to know why this straight line comes out. Is it a bug? I think that line increases metrics, and that affects strategy performance, falsifying it

I think it's a future leak.
I don't know if it's a builder bug or if it's a data problem.
it's quite strange
I put a photo

Hola
You can see D favorites, just above out-of-sample periods, after build 50.000 systems. That's why I consider the choice to be after the sample period.

https://trademaid.info/gsbhelp/RunningStatsonBuiltSystems.ht...

In the raw process, macros are only used to set and choose stats and not to build. The construction is done by pressing play, but after building 50,000 systems we must do a rebacktest to place the out-of-sample period and choose the favorites there. That is not well set up in oil and so the experiment is null.

I am also seeing an error in the nasdaq macro
Favorites A are also chosen within the sample.
I think that is not correct either.

@portfolioquanttrader2020
I have reviewed the current nq macro. (not the CL)
fav A are out of sample.
Im not going to look at CL,as these macros should not be used.

Quote: Originally posted by portfolioquanttrader2020

I am also seeing an error in the nasdaq macro Favorites A are also chosen within the sample. I think that is not correct either.

Quote: Originally posted by tialt

i've not been able to log onto my trading server since Thursday, anyone else having a problem? Radmin is working, I can log onto a remote computer I have set up.

Using Macros To Automate My Workflow

Hi guys,

Here is how you can do this in a few different ways:

The recalculating consists of two steps.
1. change the settings (like change Dts from Trd to NoTrd)
2. recalculate all strategies based on the new settings

Option 1:
By hand (steps 1 and 2)
Left click the first strategy
Hold shift down and left click the bottom strategy
Then right click and change the setting in the dropdown menu (for example change Dts from NoTrd to All)
Choose "Yes" to start the recalculating process

Option 2:
By hand (what is described here only performs step 2)
Left click the first strategy
Hold shift down and left click the bottom strategy
Then right click and choose "Overright Original Settings (OOS)".
Now the recalculating process starts (this might take a while)

Option 3:
By macro (what is shown only performs step 2):


Hope this helps

EWFO issue

Two questions relating to workers

Quote: Originally posted by TraderGeorge

I hope that one of you can help me. I have two pressing issues to do with "workers". 1. Why is it that some times workers won't start (or connect) to the manager. After 20 minutes or so, I kill them and restart them. I may have to do that 3 times before they finally take off. 2. Is there a way to NOT use certain (or any) cloud workers? I need to have my own local workers, but I don't want to use any cloud workers. Why, you might ask? Some kind person (or two people) have made workers available to other users. For some reason, those workers aren't finding any viable strategies. They do generate thousands of strategies per minute, but none meet my minimum requirements. This means that my manager is spinning its wheels sending off strategy requests that won't be satisfied. Local workers find hundreds of strategies for me, so I know that my manager is sending requests properly.

Quote: Originally posted by TraderGeorge

I hope that one of you can help me. I have two pressing issues to do with "workers". 1. Why is it that some times workers won't start (or connect) to the manager. After 20 minutes or so, I kill them and restart them. I may have to do that 3 times before they finally take off. 2. Is there a way to NOT use certain (or any) cloud workers? I need to have my own local workers, but I don't want to use any cloud workers. Why, you might ask? Some kind person (or two people) have made workers available to other users. For some reason, those workers aren't finding any viable strategies. They do generate thousands of strategies per minute, but none meet my minimum requirements. This means that my manager is spinning its wheels sending off strategy requests that won't be satisfied. Local workers find hundreds of strategies for me, so I know that my manager is sending requests properly.

I have problems with version 65.55
Doesn't build systems, but 65.46 does build systems

Hello,

Does anyone know what this means? should exist?

Dts = NoTrd
Nth = Trd

What does it mean?

Thank you.

Quote: Originally posted by REMO755

Hello, Does anyone know what this means? should exist? Dts = NoTrd Nth = Trd What does it mean? Thank you.

systems change when selected

Quote: Originally posted by brk

GSB 1.0.65.56 I'm trying to setup/run a new build. I'm running a Manager and 3 workers. When systems come up in the manager, I sort them by NP/DD-F, putting the largest on top. When I select it, many times (not every time) it will change the values. Whenever I find a system that looks good with a NP/DD-F of 27 or more, I like it, click it and it drops to 12. It's not just the top one, it's almost any of them that have been sitting there for a few minutes. This happens to most of the results in the list. I've even tried looking/selecting in the workers and the same thing happens there. I did notice that on some if I right-click and start a WFO on it before left-clicking, I can get the WFO to work and save it. Or if I save it and grab the easy language script before it changes, I can save the strategy. But something happens to them eventually, like they're getting overwritten or something. What can I be doing wrong?

Quote: Originally posted by brk

Thx. Yes, the manager & workers all match. This is a new setup, so there's nothing to go back to that "works". I'm thinking since I'm still new at this so I bet I have settings in a way that exploits the bug/issue. I'm going through the docs completely (all 710 pages) before I commit that I'm not doing something stupid. On another note I'd like to find for the WF on the chart, is it possible to change the colors? I'm not exactly color blind, but I am color deficient. So I see a yellow line and two dark lines. I would like to have 3 very different and identifiable colors (light, dark and medium). If I could change one of the dark ones to either blue or red, that would help dramatically.

Recent Performance June 2022 - March 2023

Just curious if anyone out there has been able to build systems in US stock indices using GSB which have delivered out-of-sample performance in the past few months. It's been a challenging market, but I've put together a group of systems that seems to have no lost money, but hasn't really made any either.

I'm just getting back into the swing of GSB (last used it in 2017). And just ordered a new computer to make better use of it. Looking forward to getting some real work done!

See attached...

Not able to match trades

Quote: Originally posted by admin

Hi Daniel Im not aware of any such issues. If ts has multiple stops running, i believe the tightest applies. I assume mc is the same If you have this issue, i see it as an execution error, not a easy language error I believe the stops are all in the docs, and I have little faith in them helping in any way on a day trading system. Long term system much more likely to work how to use them is also in the docs or videos, cant remember as its years ago. if you optimize the exit levels on an existing system you will see many stop methods do nothing, others give much less dd at great expense to NP, some might help but affect very few trades

Quote: Originally posted by ChuckNZ

just for completeness.... i have tried standalone and manager/worker combinations. i have tried 4 different futures contracts. i have not tried an older version.... will do that now. rquote=9051&tid=229&author=ChuckNZ]When doing some beta testing, I only saw strategies that had perfect matches between gsb and tradestion trade listings. But something has happened on my system. I'm running GSB 1.0.65.56 and TS 10.0. I'm getting some matches, some trades in GSB not in TS and some trades in TS not in GSB. I just made the data files in TS and copied them over.... no help. I've run out of ideas and could really use some help. I think it's only on my end, but perhaps you might want to run some match checks on your end. Thanks for any suggestions.[/rquote]

Quote: Originally posted by admin

@daniel I will update this https://trademaid.info/gsbhelp/Exitmodes.html Its simple IflatRevAANDSFFlatRev = exit if Indicator flat (IE for long gone from positive to zero or negative) and SF gone from positive to zero or reverse)

Thanks, that is kind of you.
We have about 18 of them as of now i think, and many is just a letter combination, so "simple" is a strong word perhaps

Running multiple systems on the same ticker

Quote: Originally posted by Daniel UK1

Quote: Originally posted by admin   Hi Daniel Im not aware of any such issues. If ts has multiple stops running, i believe the tightest applies. I assume mc is the same If you have this issue, i see it as an execution error, not a easy language error I believe the stops are all in the docs, and I have little faith in them helping in any way on a day trading system. Long term system much more likely to work how to use them is also in the docs or videos, cant remember as its years ago. if you optimize the exit levels on an existing system you will see many stop methods do nothing, others give much less dd at great expense to NP, some might help but affect very few trades Hi Peter, yes its true that tightest applies, but that a less good way in terms of risk management of the trade, 2 contracts to sell, and one contracts in position, if all goes well, yet tightest applies. Anyway, this is not the main point. Main point is, we need an explanation of what each exit type actually does with human words. Since the name itself does not lend the user to understand what it is or what it does. There is no guide for this that makes it possible to read or understand as of this moment.

Quote: Originally posted by REMO755

Quote: Originally posted by Daniel UK1   Quote: Originally posted by admin   Hi Daniel Im not aware of any such issues. If ts has multiple stops running, i believe the tightest applies. I assume mc is the same If you have this issue, i see it as an execution error, not a easy language error I believe the stops are all in the docs, and I have little faith in them helping in any way on a day trading system. Long term system much more likely to work how to use them is also in the docs or videos, cant remember as its years ago. if you optimize the exit levels on an existing system you will see many stop methods do nothing, others give much less dd at great expense to NP, some might help but affect very few trades Hi Peter, yes its true that tightest applies, but that a less good way in terms of risk management of the trade, 2 contracts to sell, and one contracts in position, if all goes well, yet tightest applies. Anyway, this is not the main point. Main point is, we need an explanation of what each exit type actually does with human words. Since the name itself does not lend the user to understand what it is or what it does. There is no guide for this that makes it possible to read or understand as of this moment. @Daniel UK1 Hello, Please, what are the flags that do not match? These flags must be removed. Does it seem foolhardy to swap systems where the flags don't match? Are we then playing the lottery? What is the point of using buggy indicators?

Quote: Originally posted by Daniel UK1

Quote: Originally posted by REMO755   Quote: Originally posted by Daniel UK1   Quote: Originally posted by admin   Hi Daniel Im not aware of any such issues. If ts has multiple stops running, i believe the tightest applies. I assume mc is the same If you have this issue, i see it as an execution error, not a easy language error I believe the stops are all in the docs, and I have little faith in them helping in any way on a day trading system. Long term system much more likely to work how to use them is also in the docs or videos, cant remember as its years ago. if you optimize the exit levels on an existing system you will see many stop methods do nothing, others give much less dd at great expense to NP, some might help but affect very few trades Hi Peter, yes its true that tightest applies, but that a less good way in terms of risk management of the trade, 2 contracts to sell, and one contracts in position, if all goes well, yet tightest applies. Anyway, this is not the main point. Main point is, we need an explanation of what each exit type actually does with human words. Since the name itself does not lend the user to understand what it is or what it does. There is no guide for this that makes it possible to read or understand as of this moment. @Daniel UK1 Hello, Please, what are the flags that do not match? These flags must be removed. Does it seem foolhardy to swap systems where the flags don't match? Are we then playing the lottery? What is the point of using buggy indicators? Hi, What you mean with "flags" you mean indicators right ? There is absolutly no point in using indicators that does not Match, I know@Peter is working extremely hard to fix all indicators in GSB that does not match. I know @Nick has a list of all indicators that has errors and does not match.. Perhaps its a good idea @Nick to share that list if you have it available?

Quote: Originally posted by admin

@remo its very hard to get indicators to match. Many years ago pre gsb most apps that made ts code were terrible match's The reason is , its just so complex to get right. Most platforms like ts mc and nt have various bugs that have to be coded around. the most common Nt data feed is lacking up/down volume and some indicators require this. You cant get a perfect match in this case. In recent years CL and a few others for the first time ever had negative prices. For example TS trix when price is < zero gives divide by zero. All results after that is wrong. CloseD, HIghD , Lowd functions before the first 500 bars gives -1, and if the first price is wrong, all other prices are wrong for some inidicators, or they are wrong for some time and then match after time Often there is rounding issues. ie 0.12345678 vs 0.12345679 Thats due to numbers being stored in binary format. The rounding errors can give from near perfect to significant errors. Othertimes match check was done on the first 10,000 bars and its perfect. After more years a missmatch occurrs. Roughly 2 months programing time has gone into this of late, and progress is now very rapid as one fix can fix multiple indicators, or the same concept applied fixes multiple indicators So in summary you always need to check gsb matches your platform results. You want a > 99% match. There is also a high amount of human error that causes match problems, or changes in data. GSB has extensive diagnostic tools to check these issues too. Once ts / mc is done, then we go to NT. That I hope will be fast as 1/2 the fixes were in GSB, not ts code. thanks all for patience

Manager does not agree with workers

Quote: Originally posted by admin

@chuck, we can do anydesk.com tomorrow. Thanks for all your efforts, but its time for me to look at it. As a test, you can also copy your manager settings to the standalone.

Quote: Originally posted by admin

@chuck, we can do anydesk.com tomorrow. Thanks for all your efforts, but its time for me to look at it. As a test, you can also copy your manager settings to the standalone.

Quote: Originally posted by NickW

Quote: Originally posted by admin   @chuck, we can do anydesk.com tomorrow. Thanks for all your efforts, but its time for me to look at it. As a test, you can also copy your manager settings to the standalone. @Chuck, it might also be a problem with your macro. Make sure after making settings changes to dates, etc, that there is at least a backtest being run as a last step (before exporting stats etc). Although i sometimes get this aswell, but extremely hard to reproduce on my side. I try not to touch the UI while the run is going on until the macro is completely finished. Nick

Quote: Originally posted by ChuckNZ

We can do an anydesk session, if you like. I tried the standalone, but the standalone won't disagree with itself. Quote: Originally posted by admin   @chuck, we can do anydesk.com tomorrow. Thanks for all your efforts, but its time for me to look at it. As a test, you can also copy your manager settings to the standalone.

Problem with changing metrics (cont'd)

Update on metric discrepancy between original and final

Quote: Originally posted by ChuckNZ

I have devoted several more hours to this project and, perhaps, came up with something of interest. If I remove these two indicators (CloseOverLowestLow and CloseLessLowestLow) the problem goes away. Here's what I have done to prove this to be true: 1. Removed the two indicators 2. Run GSB and generate 600 strategies. 3. Highlight them all and send them to statistics A 4. Scroll through the strategies (3 times) 5. Highlight them all again and send them to statistics B 6. Statistics A and B agreed. Please let me know if my test sounds valid. I will now run the same test on a couple thousand strategies.

Quote: Originally posted by admin

Awesome work Chuck. While i dont dispute the facts, I have no idea how 2 indicators can change values once the systems used are clicked on. Hopefully the programmer will sort out whats going on. Its also surprising that the highestHigh variants dont have the same issue.

Quote: Originally posted by ChuckNZ

Hi Peter... I will be looking forward to a solution to the problem because those two are excellent performers. Of course, they might not be so good once they are "fixed". As to why the HighestHigh variants aren't performing incorrectly, I'm not using them because they weren't in my preferred indicator list for any instrument. Over the next week, I will undertake to do the tedious task of checking every indicator, one at a time. It's simple enough, just time consuming. It's the kind of thing that I do well and we all want precise indicators. Quote: Originally posted by admin   Awesome work Chuck. While i dont dispute the facts, I have no idea how 2 indicators can change values once the systems used are clicked on. Hopefully the programmer will sort out whats going on. Its also surprising that the highestHigh variants dont have the same issue.

Quote: Originally posted by admin

@chuck, well thats interesting. thank you for all your efforts you could try setting indicators to only1, with metrics that will allow any system of say a 100 trades through regardless of other performance metrics this would make the job of checking faster. If you dont get all indicators in that list, change indicators to 2.

Im grateful for your help. While i can do all this testing, if thats the case it will take me a while to get to it with lots of other time pressures.

I have added percentR of 4 ranges of length as a test, to test your custom inidcator range ideas
I choose percentR as it was the most popular NQ indicator

Quote: Originally posted by ChuckNZ

I'm essentially doing what you suggest. I am testing one indicator at a time, forced, with low minimum performance requirements. Unfortunately, I can't devote all of my time to it, as I'm doing about 30 trades each day that require a bit of monitoring. I'm checking them in order of how often I use them. By the way, I am getting good results with the VWAP indicators, albeit with a low number of trades. 100% win rate, but not enough trades to call it statistically meaningful. Happy you are getting good results with vwap, will start to do some testing with this myself soon, which markets are you testing it on, and what type of setup... like using targets stops, dynamic, timeframe ? Quote: Originally posted by admin   @chuck, well thats interesting. thank you for all your efforts you could try setting indicators to only1, with metrics that will allow any system of say a 100 trades through regardless of other performance metrics this would make the job of checking faster. If you dont get all indicators in that list, change indicators to 2.

@Peter. a question, I was going to test targets on GC markets, normally i am not using that, but, i cant understand the logic of the trailing" part, (if it trails it can never be hit ?) can you please explain the working logic please of the two trailing targets here with words.

Also, where is the value set for the targets ? target field further below in gui is normally a dollar value, so when you chose atr trailing what value is used ? and "trailing target" what decides the "trailing parameters" ..

Imho this is very confusing.

Getting Exceptions since upgrade to 65.56

Quote: Originally posted by brk

This past week I've been getting exceptions during the build. It started when I would click on a system in the list while building, but then I figured not to disturb it and let it run again (from start), but I still get the exceptions. I get a System.NullReferenceException and a System.IndexOutOfRangeException. I get it pretty much every time I do a run now. I've restarted, rebooted, no help. It still seems to operate after the exceptions, but suspicious of the results.

Junior Member?

Exceptions (again)

Quote: Originally posted by Daniel UK1

@Peter. a question, I was going to test targets on GC markets, normally i am not using that, but, i cant understand the logic of the trailing" part, (if it trails it can never be hit ?) can you please explain the working logic please of the two trailing targets here with words. Also, where is the value set for the targets ? target field further below in gui is normally a dollar value, so when you chose atr trailing what value is used ? and "trailing target" what decides the "trailing parameters" .. Imho this is very confusing.

Quote: Originally posted by admin

@daniel, sorry missed your question are you talking intra day trading, or long term. trailing is not good intra day, but long term trading might help. Ive never used the trailing logic, but assume its atr based. I would edit the ts code and view it. Sorry not more helpful, but I know nothing about it. if stuck chase me again

VWAP and grains

Restore a system with hash

How / Where can I restore a system back in GSB with a generated hash