| Pages:
1
..
14
15
16
17
18
19 |
asobi
Junior Member
Posts: 12
Registered: 23-10-2019
Member Is Offline
|
|
Hello Peter,
after being updated to build 62.69, my gsb workers got lazy.
The manager initiated walk-forward at best worker, but the tasks just keep waiting in the queue and the workers staying idle.
Is such case a bug?
Thanks!
|
|
|
JozefSusko
Junior Member
Posts: 21
Registered: 24-6-2020
Member Is Offline
|
|
Quote: Originally posted by asobi  | Hello Peter,
after being updated to build 62.69, my gsb workers got lazy.
The manager initiated walk-forward at best worker, but the tasks just keep waiting in the queue and the workers staying idle.
Is such case a bug?
Thanks! |
Hello
I have the same problem with walk-forward at best worker.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
wf is fixed. Related to server reboot and one process did not restart. Apologies.
|
|
|
JozefSusko
Junior Member
Posts: 21
Registered: 24-6-2020
Member Is Offline
|
|
Hello Peter,
after upgrading to 62.88 my GSB workers didn't work properly under the WF as before when I was talking about speed and then they crashed. The manager
took a step forward for the best workers and then my workers failed. what should i do with it? any idea?
Thanks.
|
|
|
JozefSusko
Junior Member
Posts: 21
Registered: 24-6-2020
Member Is Offline
|
|
problem solved it was on my side, its all good already thanks ,sorry for bothering
|
|
|
REMO755
Member
Posts: 181
Registered: 11-4-2021
Member Is Offline
|
|
Hello,
TS calculation errors.
I show you examples, What's going on here? Is something wrong with the library? Can some indicators be wrong?
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
@remo, most likely volume on ts <> whats in GSB DATA Accumdist is one of the few that use volume
|
|
|
REMO755
Member
Posts: 181
Registered: 11-4-2021
Member Is Offline
|
|
| Quote: Originally posted by admin | | @remo, most likely volume on ts <> whats in GSB DATA Accumdist is one of the few that use volume |
GSB_AccumDistDR flag has problems.
Please, I suggest you check this indicator, whenever it appears in a system the errors of calcualo TS vs GSB appear.
It has taken me a few hours to identify this error. It is possible that there is some other volume indicator also with problems.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
| Quote: Originally posted by REMO755 | | Quote: Originally posted by admin | | @remo, most likely volume on ts <> whats in GSB DATA Accumdist is one of the few that use volume |
GSB_AccumDistDR flag has problems.
Please, I suggest you check this indicator, whenever it appears in a system the errors of calcualo TS vs GSB appear.
It has taken me a few hours to identify this error. It is possible that there is some other volume indicator also with problems.
|
shall do
Peter
|
|
|
OUrocketman
Junior Member
Posts: 18
Registered: 10-5-2018
Member Is Offline
Mood: No Mood
|
|
Potential Bug In EWFO
Peter,
I recently used the WF to EWFO option in GSB, and when I copied the WFO final parameters, the resulting system in TS did not match the final walk
forward curve remotely close.
Do you know if there is an issue with the parameter indexing when writing the WFO files from GSB? I've never had this issue before, and note this is
the first time I've used EWFO with a system that has a Take profit and a stop loss. Worth noting, I absolutely confirmed that TS matched GSB prior to
dropping in the final parameters. I also tried dropping the parameters in different orders to see if I could get things to match up that way, but
could not.
Thank you!
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Ive seen this once, many years ago. Spent a massive amount of time on it, and could not resolve it. However I have not seen this as an issue for some
years. Check slippage and commission values are the same.
There is a possibility of human error as you likely dont wf all parameters that the system has.
for example its likely the paramaters with red arrow are not optimized, but its easy to get the paramaters wrong in the chart.
(im not saying this is the case, but that it could be the case)
|
|
|
thowoc213
Junior Member
Posts: 39
Registered: 22-8-2021
Location: Poland
Member Is Offline
|
|
A BUG?
Hi,
I'm working on a GC strategy and quite a few strategies are getting an error : "Error:elsystem.FPInvalidException: Floating point invalid
calculation".
I happens when executing the lines below:
// Indicators
v1 = GSB_Lowest(Low, i1length) of Data(i1Data);
v2 = TrueRange of Data(i2Data);
v3 = GSB_BollingerBand(Close, i3length, i3numDevs) of Data(i3Data);
vn1 = GSB_Norm4(v1, 13, 100) of Data(i1Data);
vn2 = GSB_Norm4(v2, 13, 100) of Data(i2Data);
vn3 = GSB_Norm4(v3, 13, 100) of Data(i3Data);
vSF = GSB_CloseLessPrevCloseDBpv2(iSFbpv) of Data(iSFData);
vnSF = GSB_Norm4(vSF, 13, 100) of Data(iSFData);
// Result and decision
// Represents a value that is not a number(NaN) for real value types.
print("v1 = ",v1:0:4," v2 = ",v2:0:4," v3 = ",v3:0:4);
print("vn1 = ",vn1:0:4," vn2 = ",vn2:0:4," vn3= ",vn3:0:4);
print("vSF = ",vSF:0:4," vnSF= ",vnSF:0:4);
result = ((Sign(vn1) * Power(Absvalue(vn1), i1Weight)) * ((Sign(vn2) * Power(Absvalue(vn2), i2Weight)) * (Sign(vn3) * Power(Absvalue(vn3),
i3Weight))));
print("result = ",result);
The last 4 values of the involved variables are below:
v1 = 969.7000 v2 = 1.7000 v3 = 983.2989
vn1 = 67.8999 vn2 = -36.6248 vn3= 67.8999
vSF = -190.0000 vnSF= -54.9283
result = -189.95
v1 = 969.7000 v2 = 2.6000 v3 = 983.1911
vn1 = 67.8999 vn2 = -11.7632 vn3= 67.3368
vSF = 220.0000 vnSF= -11.0669
result = -25.76
v1 = 969.7000 v2 = 1.2000 v3 = 983.2940
vn1 = 67.8999 vn2 = -48.6761 vn3= 67.8745
vSF = 140.0000 vnSF= -20.6871
result = -312.34
v1 = 969.7000 v2 = 1.1000 v3 = 983.3776
vn1 = 0.0000 vn2 = -50.8980 vn3= 67.8999
vSF = 210.0000 vnSF= -12.2847
result = -nan(ind)
The error occurs when vn1 is ZERO.
The function GSB_Norm4(969.7000, 13,100) executes the case 13:
Case 13: // CenteringScaling2
hst = GSB_Highestffc(Price, Length); // Highestffc is just faster version of highesthigh
lwst = GSB_lowestffc(Price, Length); // Lowestffc is just faster version of lowest low
iq25 = lwst + 0.25 * (hst - lwst);
iq50 = 0.5 * (hst + lwst);
iq75 = lwst + 0.75 * (hst - lwst);
num = Price - iq50;
denom = iq75 - iq25;
IF AbsValue(denom) > zs THEN
result = 200 * GSB_CDF(num / denom) - 100
Else
result = 0;
IF AbsValue(result) > zs Then
GSB_Norm4 = result
ELSE
GSB_Norm4 = 0;
Apparently the value of "lwst + 0.75 * (hst - lwst) - lwst + 0.25 * (hst - lwst)" is ZERO, which happens only when HIGHEST equals LOWEST.
Any thoughts about that?
|
|
|
thowoc213
Junior Member
Posts: 39
Registered: 22-8-2021
Location: Poland
Member Is Offline
|
|
I did a simple check writing what's below. That is basically what GSB_Norm4 does when executing Case 13.
once Clearprintlog;
if Date = 1070418 Then
Begin
print("Time -->",time,"<--");
print (" Highest Low=", GSB_Highestffc(GSB_Lowest(Low, 71), 100));
print (" Lowest Low=", GSB_Lowestffc(GSB_Lowest(Low, 71), 100));
end;
The first 2 bars return different values for Highest Low and Lowest Low.
Then 4 consecutive bars return the same value. That cause the FPException.
After that everything goes to the normal.
Why is the 'impossible' happening?
New bar: Time -->400<--
Highest Low= 969.70
Lowest Low= 966.30
New bar: Time -->430<--
Highest Low= 969.70
Lowest Low= 969.40
New bar: Time -->500<--
Highest Low= 969.70
Lowest Low= 969.70
New bar: Time -->530<--
Highest Low= 969.70
Lowest Low= 969.70
New bar: Time -->600<--
Highest Low= 969.70
Lowest Low= 969.70
New bar: Time -->630<--
Highest Low= 969.70
Lowest Low= 969.70
New bar: Time -->700<--
Highest Low= 971.90
Lowest Low= 969.70
New bar: Time -->730<--
Highest Low= 971.90
Lowest Low= 969.70
New bar: Time -->800<--
Highest Low= 973.40
Lowest Low= 969.70
New bar: Time -->830<--
Highest Low= 973.40
Lowest Low= 969.70
New bar: Time -->900<--
Highest Low= 975.00
Lowest Low= 969.70
New bar: Time -->930<--
Highest Low= 975.00
Lowest Low= 969.70
New bar: Time -->1000<--
Highest Low= 975.00
Lowest Low= 969.70
New bar: Time -->1030<--
Highest Low= 975.00
Lowest Low= 969.70
New bar: Time -->1100<--
Highest Low= 975.00
Lowest Low= 969.70
New bar: Time -->1130<--
Highest Low= 975.90
Lowest Low= 969.70
New bar: Time -->1200<--
Highest Low= 976.30
Lowest Low= 969.70
New bar: Time -->1230<--
Highest Low= 976.40
Lowest Low= 969.70
New bar: Time -->1300<--
Highest Low= 976.60
Lowest Low= 969.70
New bar: Time -->1330<--
Highest Low= 976.60
Lowest Low= 969.70
|
|
|
BlackBox
Junior Member
Posts: 39
Registered: 24-4-2019
Member Is Offline
Mood: No Mood
|
|
GSB_SCRIPTS_2022_3_7
Function GSB_AverageSignHL2, where is this function used, and how is it called.
It gives an error, either the function name must be revised or the return indentifier.
GSB_AverageSignHL2 or GSB_AverageSignHL3
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
@blackbox,
thanks for finding that bug. Change the 3 to a 2.
I will fix in next build
|
|
|
BlackBox
Junior Member
Posts: 39
Registered: 24-4-2019
Member Is Offline
Mood: No Mood
|
|
Peter, another question
Do we still use "type 14" // Average , in function GSB_Norm4 ,because that one doesn't show up anymore in the last ELD
|
|
|
Carl
Member
Posts: 342
Registered: 10-5-2017
Member Is Offline
Mood: No Mood
|
|
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
@carl, your post is empty
|
|
|
BlackBox
Junior Member
Posts: 39
Registered: 24-4-2019
Member Is Offline
Mood: No Mood
|
|
GSB_SCRIPTS_2022_06_07+WITHUPDATEDGSBSYS1ES_V1.21
Peter, the bug still exist, will you fix in next build.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
@blackbox, thank you for chasing me on this. I fixed the code on my end, but did not export it.
Next build it will be have a B on the end of the 07
GSB_SCRIPTS_2022_06_07b+WITHUPDATEDGSBSYS1ES_V1.21
|
|
|
TheMetalDog
Junior Member
Posts: 8
Registered: 13-5-2022
Member Is Offline
|
|
I'm experiencing a lot of SQL network exceptions by the Worker app.
Also, the Manager and Works show that they are still running, but the Manager "Machines" list drops to an empty list, with the Stus. Sum. back to
Searching...
Thoughts?
System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: A network-related or
instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the
instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed
out.) ---> System.ComponentModel.Win32Exception: The wait operation timed out
--- End of inner exception stack trace ---
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate,
Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions
userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions
userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory,
TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation,
TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.b__0()
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
--- End of inner exception stack trace ---
at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection(Boolean shouldMonitorTransactions)
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean
startLocalTransaction, Boolean releaseConnectionOnSuccess)
at System.Data.Entity.Core.Objects.ObjectContext.<>c__DisplayClass47`1.b__45()
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteFunction[TElement](String functionName, ExecutionOptions executionOptions,
ObjectParameter[] parameters)
at n$FU1_MRbB2uE$UpAgQUzzm_TMncIhzMcvxkG1LdwucN.gbWfJRUFgYGR9EkHoFM9el2_kcI5Gmu$ArhORME_VGUa()
at n$FU1_MRbB2uE$UpAgQUzzm_TMncIhzMcvxkG1LdwucN.yRfDJkTYXboGpaonwG6w1hSDZ6XHb0ZOj9fHAs4ZcykgER1PxdEaVnl78Wbb1dAtRg()
Params:
Header Text:
Icon Text:
Icon Color: Color [Empty]
Workplace Mode: Worker
Instance ID: PqHkzId9QYuzxofcA
Workplace ID:
App Version: 1.0.65.01 / 2022-07-27
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
@THemetaldog
Happy to say those errors can be ignored, they are not visible in newer build (GSB purchasers)
if we cant connect to the data base, we just retry.
Thanks received (1):
+1 TheMetalDog at 2022-08-10 18:02:29
|
|
|
TheMetalDog
Junior Member
Posts: 8
Registered: 13-5-2022
Member Is Offline
|
|
Strange Recalculation
When clicking on systems, GSB appears to recalculate the row to better values.
Is this a bug? Hopefully this gif link works:
https://imgur.com/a/eepun64
|
|
|
Daniel UK1
Member
Posts: 470
Registered: 4-6-2019
Member Is Offline
|
|
Hi, Yes this is a known bug reported by several users including myself. Still present i believe.
|
|
|
admin
Super Administrator
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
@TheMetalDog, there can be legit reasons why this occurs. ie you change dates on left side, when you click on it then it changes to the new dates and
results all change.
However this is a known intermittent bug thats very hard to identify. Im happy to look at it via anydesk.com
The best setup would be run a manager with only one worker connected on your local pc.
Then build a few systems and see if the same system on the manager matches the same system on the worker
|
|
|
| Pages:
1
..
14
15
16
17
18
19 |
![[*]](images/davis/default_icon.gif){kind=icon}
