Gamestudio Links
Zorro Links
Newest Posts
optimize global parameters SOLVED
by dBc. 09/27/25 17:07
ZorroGPT
by TipmyPip. 09/27/25 10:05
Release 2.68 replacement of the .par format
by Martin_HH. 09/23/25 20:48
assetHistory one candle shift
by jcl. 09/21/25 11:36
Plugins update
by Grant. 09/17/25 16:28
AUM Magazine
Latest Screens
Rocker`s Revenge
Stug 3 Stormartillery
Iljuschin 2
Galactic Strike X
Who's Online Now
1 registered members (dBc), 17,982 guests, and 5 spiders.
Key: Admin, Global Mod, Mod
Newest Members
krishna, DrissB, James168, Ed_Love, xtns
19168 Registered Users
Previous Thread
Next Thread
Print Thread
Rate Thread
Need a way to distinguish the final factor and parameters runs #451954
05/28/15 06:19
05/28/15 06:19
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline OP
User
GPEngine  Offline OP
User
G

Joined: Sep 2013
Posts: 504
California
I kill my Training if the Cycles are too slow, measured via timer() from INITRUN to EXITRUN.

There is a final cycle or two at the end of the Training phase. These cycles are special. They take a long time compared to the individual Training Cycles. Anyway, I'm willing to wait for them. Most of the costs of Training have already been spent by then.

I don't see how to distinguish them. TRAINMODE is true in both cases. At first I thought it was just the FACTORS run. But apparently there is another run after that, where parameter choices are being resolved. In that run, FACTORS is not set. How can I identify it? Through guess-and-check, I find it is possibly identified by

(is(TRAINMODE) and not is(FACTORS) and not is(RULES))

Yikes.

Last edited by GPEngine; 05/28/15 06:21. Reason: smrt
Re: Need a way to distinguish the final factor and parameters runs [Re: GPEngine] #451960
05/28/15 09:12
05/28/15 09:12
Joined: Jul 2000
Posts: 28,022
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 28,022
Frankfurt
Training is done by a simple state machine, with the state stored in g->nState. It should be always in one of those states:

#define RULES (1<<12) // generate rules only
#define FACTORS (1<<13) // generate factors only
#define PARAMETERS (1<<14) // generate parameters only
#define PARRULES (1<<15) // generate rules with parameters, first rule run
#define PARFINAL (1<<16) // generate rules with parameters, parameter selection
#define RULFINAL (1<<17) // generate rules with parameters, final rule run
#define RULEXT (1<<18) // External training with no parameters or rules
#define FACTORS1 (1<<19) // first FACTORS run
#define FACTORS2 (1<<20) // second FACTORS run


Re: Need a way to distinguish the final factor and parameters runs [Re: jcl] #451971
05/28/15 14:31
05/28/15 14:31
Joined: Sep 2013
Posts: 504
California
G
GPEngine Offline OP
User
GPEngine  Offline OP
User
G

Joined: Sep 2013
Posts: 504
California
Thanks. I can work with that. laugh


Moderated by  Petra 

Gamestudio download | Zorro platform | shop | Data Protection Policy

oP group Germany GmbH | Birkenstr. 25-27 | 63549 Ronneburg / Germany | info (at) opgroup.de

Powered by UBB.threads™ PHP Forum Software 7.7.1