Gamestudio Links
Zorro Links
Newest Posts
Blobsculptor tools and objects download here
by NeoDumont. 03/28/24 03:01
Issue with Multi-Core WFO Training
by aliswee. 03/24/24 20:20
Why Zorro supports up to 72 cores?
by Edgar_Herrera. 03/23/24 21:41
Zorro Trader GPT
by TipmyPip. 03/06/24 09:27
VSCode instead of SED
by 3run. 03/01/24 19:06
AUM Magazine
Latest Screens
The Bible Game
A psychological thriller game
SHADOW (2014)
DEAD TASTE
Who's Online Now
5 registered members (AndrewAMD, monk12, TipmyPip, Quad, aliswee), 1,031 guests, and 6 spiders.
Key: Admin, Global Mod, Mod
Newest Members
sakolin, rajesh7827, juergen_wue, NITRO_FOREVER, jack0roses
19043 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: 27,977
Frankfurt
jcl Offline

Chief Engineer
jcl  Offline

Chief Engineer

Joined: Jul 2000
Posts: 27,977
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 | chip programmers | 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