MASON-INTEREST-L Archives

May 2014

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Monospaced 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:
Wed, 14 May 2014 09:45:51 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (15 lines)
On May 14, 2014, at 9:39 AM, Ernesto Carrella <[log in to unmask]> wrote:

> 1) Do you think it's a good idea as long as we are still using an older version of MASON to pulse the MersenneTwisterFast ourselves? Should we do so by calling getNewInt() 1249 times?

It's a very minor thing: the chance that it'll effect your simulation results is extremely small.  But for a library I want to be extra conservative.  I wouldn't worry about it.


> 2) I don't know how common it is for other modellers but I often give each agent its own mersenne twister fast randomizer to decouple their random behavior from the activation time (and potentially from the rest of the model as well). These randomizers wouldn't be touched by state.start().

This is unwise.  You'd have to be *extremely* careful, making sure that each of these random number generators have their own seed.  Generally speaking you should *never* use more than one random number generator, ever, unless you have certain multithreading issues.

I don't know what you mean by "decoupling" from "activation time" -- a random number generator is supposed to produce *random* numbers.  Its sequence shouldn't be coupled to anything.

Sean

ATOM RSS1 RSS2