MASON-INTEREST-L Archives

August 2011

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Proportional Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Sean Luke <[log in to unmask]>
Reply To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:
Mon, 22 Aug 2011 13:26:52 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
I'll right, guirandom it is.  Will include it in the next SVN update.

The generators likely won't couple.  In fact I suspect the vast  
majority of people
won't even know about the existence of the second one unless they've  
read the manual.  :-)

Sean

On Aug 22, 2011, at 12:31 PM, glen e. p. ropella wrote:

> My only worry is that the two generators may couple and make the  
> period
> shorter.  As long as they remain separate (no model code uses the
> guirandom and no gui code uses the model random), it seems OK.
>
> Sean Luke wrote circa 11-08-20 02:31 PM:
>> 1. The random number generator is presently called "guirandom".  I  
>> could
>> call it "random", which would be consistent with state.random, but  
>> I'm
>> worried it'd confuse people.  Should I not be worried?  Or can anyone
>> think of a better name?  These variable names last forever.
>
> I think it's useful to use a different name and "guirandom" is nice.
>
>> 2. The generator is created at GUIState construction time and is  
>> never
>> recreated thereafter (unless you want to do so yourself).  I think
>> that's the proper strategy.
>
> FWIW, I like that.  The guirandom lives as long as the gui lives.
>
> -- 
> glen e. p. ropella, 971-222-9095, http://tempusdictum.com

ATOM RSS1 RSS2