| Pages:
1
..
17
18
19
20
21
..
54 |
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by avatartrader  | I just upgraded to 51.59 and it looks there is a bug in the Price Data editor. I tried renaming the original PriceData.txt file and letting it
recreate it fresh, but when I open the window, GSB reports a NullReferenceException and I get the Windows Forms/GDI Red X of Death and can't edit
price data settings.
I still have 51.410 that I upgraded from, so I can launch that and edit price data. However, I am not sure what differences there are between 51.41
and 51.59 in terms of price data and how that may impact operation. |
This was fixed today in 52.00.
The issue occurs when you use the tools contract, rather than click on contracts on the left side of GSB.
I will upload via RM in a minute. Thanks for your other comments to Candymachine. I would like the forum to be a bit more active, so its appreciated.
Much of the communication that goes on is via email
|
|
|
eurtrader
Junior Member

Posts: 3
Registered: 6-4-2019
Member Is Offline
Mood: No Mood
|
|
Here are the macro settings used in video
https://www.youtube.com/watch?v=81jYQhN8-HA
Attachment: Login to view the details
Attachment: Login to view the details
|
|
|
eurtrader
Junior Member

Posts: 3
Registered: 6-4-2019
Member Is Offline
Mood: No Mood
|
|
Something went wrong with the upload of the document with macro settings.
Please change the file extention from "tmp" to "docx".
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
coming in a few days, 52.02
Change of session times to be closer to how TS & MC function. Bug fixes. Once this build is proven & tested, all users should upgrade.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
There is a simple bug that bit me today. The top indicators in indicator stats gets applied to primary AND secondary filters.
This should not be applied to secondary filters. It should be fixed in the next build.
I ended up running with 15 secondary filters instead of one. If you had SF closeD... instead of GA, then this wont affect you
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
52.05 build has not passed testing, though will be ok for most users.
The bug from the above post is fixed, and marketonclose issues, and issues with bar types that the last bar of the day is not going to natural fit.
ie 29 min bars , the last bar isnt 29 minutes if moc = 1500
Hope to release some time next week
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
April 15 2019 52.06 build released.
The bug from the above post is fixed, and marketonclose issues, and issues with bar types that the last bar of the day is not going to natural fit.
ie 29 min bars , the last bar isnt 29 minutes if moc = 1500
Session times updated under tools to be similar to TS / MC
|
|
|
avatartrader
Junior Member

Posts: 60
Registered: 1-10-2018
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by admin  | April 15 2019 52.06 build released.
The bug from the above post is fixed, and marketonclose issues, and issues with bar types that the last bar of the day is not going to natural fit.
ie 29 min bars , the last bar isnt 29 minutes if moc = 1500
Session times updated under tools to be similar to TS / MC
|
Hi Peter - quick question: as of this update, does this mean that the MOC function is now governed by the session settings, and not the contract
property (meaning that I no longer need multiple contracts, and hence multiple data files) just for the different session end times?
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by avatartrader  | Quote: Originally posted by admin  | April 15 2019 52.06 build released.
The bug from the above post is fixed, and marketonclose issues, and issues with bar types that the last bar of the day is not going to natural fit.
ie 29 min bars , the last bar isnt 29 minutes if moc = 1500
Session times updated under tools to be similar to TS / MC
|
Hi Peter - quick question: as of this update, does this mean that the MOC function is now governed by the session settings, and not the contract
property (meaning that I no longer need multiple contracts, and hence multiple data files) just for the different session end times?
|
I believe that is the case, though Im not yet very familiar with the new updates.
All my old settings worked transparently, so I didnt need to do anything different. I was more aware of the bugs that are fixed by these changes.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
52.08. under testing
Bug fixes, new addition using brackets that wont do silly things like
indicator1 * indicator2 + indicator3
It will do indicator1 * ( indicator2 + indicator3)
The top example, indicator3 value is so small compared to indicator1*indicator2 - thats its just noise.
Make sure you use weights if * and + both used
ie -100 to 100 step 20
You should no longer use the legacy add. Note the order of these how they appear may change in the next build
|
|
|
jptann
Member
 
Posts: 101
Registered: 13-6-2017
Member Is Offline
Mood: No Mood
|
|
Peter:
A few ideas to consider:
1. You should make clear where these new updates can be downloaded? Will they automatically be available when we start a RM?
2. The default op settings in both workers and managers should be available to change. Changing all the op settings each time is a pain.
3. There should be a global price file (this may be available now) and if available where for workers and managers. Nice to place in default
4. Sometimes workers open in RM that don't pick up the manager op settings. Is that suppose to happen?
5. I have the new worker, but will that use the old manager, or do I have to change the file name of the manager. As an example, I have worker 52.06
but the manager is 52.00. Can I just rename the manager file????
Thanks
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by jptann  | Peter:
A few ideas to consider:
1. You should make clear where these new updates can be downloaded? Will they automatically be available when we start a RM?
2. The default op settings in both workers and managers should be available to change. Changing all the op settings each time is a pain.
3. There should be a global price file (this may be available now) and if available where for workers and managers. Nice to place in default
4. Sometimes workers open in RM that don't pick up the manager op settings. Is that suppose to happen?
5. I have the new worker, but will that use the old manager, or do I have to change the file name of the manager. As an example, I have worker 52.06
but the manager is 52.00. Can I just rename the manager file????
Thanks |
1) RM will download them. Most users should have RM running all the time.
RM docs are here. https://trademaid.info/gsbhelp/GSBResourceManager.html
2) Opt settings are always available. You can save and load them with the name of your choice.
You should never touch worker opt settings. The manager will update them each time it starts the worker. I can understand if you didnt know that, its
a pain.
3) same as above. worker gets price file from manager.
4) That should never happen. It its an issue send me teamviewer details.
5) Never rename the manager file. It will do nothing at best.
RM should download the new manager file. Typically for most but not all users, its set to c:\gsb\gsbmanager...exe
In most cases, new workers run on all older managers. In some cases new managers run on old workers.(depends on version compatabilty)
Its best to run new manager and new worker.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
march 18 2019
52.08 released. See post above for details
|
|
|
Bruce
Member
 
Posts: 115
Registered: 22-7-2018
Location: Auckland - New Zealand
Member Is Offline
Mood: No Mood
|
|
I'm unable to locate a 52.08 manager anywhere, do I download this from somewhere else?
I've got the worker.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Quote: Originally posted by Bruce  |
I'm unable to locate a 52.08 manager anywhere, do I download this from somewhere else?
I've got the worker.
|
Under update on RM, look at gsbmanager folder
You can rename a worker to a manger. They are the identical file.
The name determines the function
|
|
|
appengineer
Junior Member

Posts: 61
Registered: 8-4-2019
Member Is Offline
Mood: No Mood
|
|
Macros Missing
Hi Peter,
I am missing the Macro Options in build 52.06
Thank you
|
|
|
appengineer
Junior Member

Posts: 61
Registered: 8-4-2019
Member Is Offline
Mood: No Mood
|
|
Never mind, I figured it out.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Great, but use 52.08. There is a contracts bug in 52.06
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
April 23 2019 52.13
Bug fixes, especially important is fix to walk forward. The OOS periods were calculated on the total dates, not the dates that the WF was done on.
WF was still done on the correct dates though.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
April 24 2019 52.13
One more WF fixes and improved logic of sending WF to the GSB cloud.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
Note that wf uses the global dates range, not the "dates" field.
This was because if a user has multiple periods in dates, it screws the wf dates / runs calculation.
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
all users should read this post (subscribe to the thread too)
Methodology has been written up. Ive spent months on this and am very open to better ways to do this.
https://trademaid.info/forum/viewthread.php?tid=17&page=2#pi...
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
52.16 under testing. Much better allocation of WF jobs to the cloud. It also fixes the issues with cloud workers being killed and screwing up WF jobs.
Methodology updated today
https://trademaid.info/gsbhelp/
|
|
|
admin
Super Administrator
       
Posts: 5060
Registered: 7-4-2017
Member Is Offline
Mood: No Mood
|
|
April 29. 52.16 released.
Included is GSBResourceManager.20190428.1_updatedFilesOnly.zip
Put this in your existing RM folder. Only the updated files are included, it wont run by itself.
This is not a critical update of RM.
Has option to kill any worker with ram of 50gb (softcoded) and some other minor tweaks
|
|
|
jptann
Member
 
Posts: 101
Registered: 13-6-2017
Member Is Offline
Mood: No Mood
|
|
Peter, can't find the new release anywhere. I will send you an email with a tV to see if you can fix.
Thanks in advance
|
|
|
| Pages:
1
..
17
18
19
20
21
..
54 |