Home Download Help Resources Extensions FAQ NetLogo Publications Contact Us Donate Models: Library Community Modeling Commons Beginners Interactive NetLogo Dictionary (BIND) NetLogo Dictionary User Manuals: Web Printable Chinese Czech Farsi / Persian Japanese Spanish

NetLogo Models Library: 
If you download the NetLogo application, this model is included. You can also Try running it in NetLogo Web 
Random Basic is the simplest of all the ProbLab models. It can either be used first or as a detour from a more complex model to explain randomness. This model introduces the user to the random generator in NetLogo. Randomness means that in the short term you cannot guess a value but in the long term all possible values will have occurred more or less equally often.
Here we see a bar chart grow reflecting a realtime succession of random events. You can think of the bar chart as a competition between the columns and ask whether one of the columns wins more often than others. Or you can think of it as some goodies being given out and think about whether the goodies are being given out fairly. Or think about it some other way  that's fine.
You can set the size of the sample space. Also, you can split the bar chart into two subregions (red and green) and track the convergence of the distribution on proportion values that you have set.
This model is a part of the ProbLab curriculum. The ProbLab Curriculum is currently under development at the CCL. For more information about the ProbLab Curriculum please refer to http://ccl.northwestern.edu/curriculum/ProbLab/.
At every tick, the computer selects a random number between 1 and "samplespace" (a slider in the interface tab). For instance, if the slider reads 100, then the random number will be between 1 and 100, inclusive. This random number piggybacks on a virtual dart. In this program the dart is called the 'messenger' because it carries the number from the top of the view to the appropriate column. Each column is associated with one number. Once the messenger gets to its column, the messenger vanishes but the column becomes taller by one square (the squares are called 'frames' in this and other models in ProbLab). The columns grow until one of them reaches the brown half of the view, which stops the run.
Choose a samplespace (you can leave it at the default value of '100') and press Setup. Now press Go. The messenger (the dart) will obtain a random number and carry it to the correct column. The redgreen slider changes which columns are red and which are green. If it's set at 50% and if the sample space is 100 then patches up to 50 will be red and the rest will be green. If it's set at 50% and the sample space is 30 then patches up to 15 will be red. There are cases where this might be confusing: for instance, if it's set at 50% and if the sample space is 5 then patches up to 2 will be red. The '3'column will be green because it goes further than 50% of 5. That is, all columns up to and including the 3column are more than 50% of the columns in the samplespace of 5  they are actually 60% because each of the 5 columns makes up 20% (and 5 * 20% is 100%). (See the section EXTENDING THE MODEL, below.)
These are the widgets in order of appearance from top to bottom: SAMPLESPACE is a slider for setting how many columns you want to be filling up. Also, it sets the range of numbers that will be randomly selected. If you set the slider to 3 then you will have 3 columns and the values will always be either 1, 2, or 3. SETUP  prepares the model for running with your samplespace parameter setting. GO  runs the model with the current settings. BIGGEST GAP  shows the biggest vertical difference between all columns. For instance, if the highest column is 10 squares high and the lowest is at 3 squares high then this monitor will show '7'. %RED  shows what percentage of the squares are red out of all the squares. COLORS?  when this switch is on the patches get painted either red or green depending on the redgreen slider value and their position. REDGREEN  sets the cutoff line for which patches are painted red and which green. When your samplespace is 100 then the position of the little handle on the slider (what you grab and move) is exactly at the cutoff line. For sample spaces other than 100 it will be under the cutoff line only when it is set at 50. This is because currently this slider works according to percentage of events and not column value. %FULL  the proportion of the yellow area that has been filled up by squares.
What happens to the biggest gap as the model runs. Does it change? Does it get consistently bigger? Smaller? Is this connected to the size of the sample space or not? Come up with an explanation for this. Also, if you keep running the model with the same sample space until it stops, are you getting the same biggest gap each time? Is it "kind of the same"?
How does the size of the SampleSpace affect your sense of "fairness?" Is it more "fair" when the samplespace is small (narrow) or when it is big (wide)? Try changing the samplespace slider and see if you feel that the events are being equally distributed across the bar chart. You can set the redgreen slider at 50%, then at other values, and, looking at the %red monitor, evaluate how long it takes for the redgreen and the %red values to be more or less the same. Perhaps a good way to go about this is by using a samplespace of size 2. This is much like flipping a coin. Now set it to a samplespace of 6. This is kind of like rolling a die.
Actually, what is fairness? Is the difference between two columns of heights 0 and 3 the same as the difference between two columns of heights 20 and 23?
How does the passage of time  more and more events  affect how close the redgreen slider and the %red are?
Currently, the redgreen slider shows you how many patches there are that are smaller than a cutoff value. But you may want to know, for instance, how often the value '1' appeared and compare it to how many times the value '2' appeared. You could just count, but you may want to compare the ratio between these accumulations and see what happens to it as the program runs.
Another idea is to keep track of how many times, on average, a certain value, for instance '1' occurs out of every 10 trials. Partitioning the events into groups of 10 is called "sampling."
Keep track of how long it takes, on average, to get a certain value (for instance, '1'). That's called "waiting time".
Even another thing to check is how often you get a "double," that is, how often you get the same value back to back. How would the sample size affect that?
Build plots of your extensions to the model.
Implement a monitor that shows the smallest gap. There is currently a monitor which shows the biggest gap.
The redgreen slider could work differently. For instance, instead of indexing the percentage, it could index the column number. If the redgreen were set to 7 then it could index all the columns from 1 through 7.
What would happen if you added more messengers? Perhaps you could sprout them at different locations and have them execute the same code. Would this change the way the type of experimental outcomes?
Add a slider that allows you to choose specific columns and find out how many squares have accumulated in it.
Perhaps you noticed that each time you setup and run the model (each experiment) the random numbers come in a different order. But you may want to explore the same set of random numbers in several experiments where you modify some parameters. To do this, you should try working with the NetLogo primitive "randomseed" (see the NetLogo User Manual for details). If you keep samplespace constant, you should get the same numbers in the same order.
We use the random
primitive a great deal in NetLogo and especially in ProbLab, where we care about probability. But how does NetLogo produce random numbers? Does it roll a die or flip a coin? Actually, NetLogo uses the "Mersenne Twister" random generator. This generator is sometimes called a “pseudorandom” number generator because it uses a certain mathematical algorithm to produce numbers that appear random, but are actually predictable given enough time to figure out the pattern.
All of the ProbLab models use randomness. Having worked with this model, you may now have a better sense of where these random numbers are coming from and what to expect when the random
primitive is used. In particular, note how other ProbLab models use randomness to control the movement of agents.
This model is a part of the ProbLab curriculum. The ProbLab Curriculum is currently under development at Northwestern's Center for Connected Learning and ComputerBased Modeling. . For more information about the ProbLab Curriculum please refer to http://ccl.northwestern.edu/curriculum/ProbLab/.
If you mention this model or the NetLogo software in a publication, we ask that you include the citations below.
For the model itself:
Please cite the NetLogo software as:
Copyright 2004 Uri Wilensky.
This work is licensed under the Creative Commons AttributionNonCommercialShareAlike 3.0 License. To view a copy of this license, visit https://creativecommons.org/licenses/byncsa/3.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
Commercial licenses are also available. To inquire about commercial licenses, please contact Uri Wilensky at uri@northwestern.edu.
This model was created as part of the projects: PARTICIPATORY SIMULATIONS: NETWORKBASED DESIGN FOR SYSTEMS LEARNING IN CLASSROOMS and/or INTEGRATED SIMULATION AND MODELING ENVIRONMENT. The project gratefully acknowledges the support of the National Science Foundation (REPP & ROLE programs)  grant numbers REC #9814682 and REC0126227.
(back to the NetLogo Models Library)