Using default param values in optimize()

Gamestudio Links

Zorro Links

Data from CSV not parsed correctly
by dr_panther. 05/06/24 18:50

Help with plotting multiple ZigZag
by degenerate_762. 04/30/24 23:23

M1 Oversampling
by 11honza11. 04/30/24 08:16

AUM Magazine

Latest Screens

3 registered members (AndrewAMD, dr_panther, 1 invisible), 1,043 guests, and 0 spiders.

Key: Admin, Global Mod, Mod

Newest Members

Print Thread

Rate Thread

Using default param values in optimize() #481608 10/06/20 14:47 10/06/20 14:47
Joined: Jul 2017 Posts: 784 Z Zheka OP User
Zheka OP User Z Joined: Jul 2017 Posts: 784	When optimizing a parameter in ASCENT mode, Zorro uses "min" values of other parameters. It would be better/more productive to use the "default" values - which is normally a "best known estimate", 'reasonably good' value, which is often chosen as the "center of the range'. And for a parameter already optimized - its "best" value should since be used when training the others in the same TrainCycle.

Re: Using default param values in optimize() [Re: Zheka] #481686 10/19/20 12:55 10/19/20 12:55
Joined: Jul 2000 Posts: 27,986 Frankfurt jcl Chief Engineer
jcl Chief Engineer Joined: Jul 2000 Posts: 27,986 Frankfurt	That's what it does.

Re: Using default param values in optimize() [Re: Zheka] #481707 10/20/20 13:36 10/20/20 13:36
Joined: Jul 2017 Posts: 784 Z Zheka OP User
Zheka OP User Z Joined: Jul 2017 Posts: 784	Indeed, in v2.33, in TrainCycle=1 Zorro uses default param values (rather than mins), but it wasn't in 2.25 to 2.30.

Re: Using default param values in optimize() [Re: Zheka] #481773 10/30/20 10:51 10/30/20 10:51
Joined: Jul 2000 Posts: 27,986 Frankfurt jcl Chief Engineer
jcl Chief Engineer Joined: Jul 2000 Posts: 27,986 Frankfurt	It certainly was.

Moderated by Petra