This page was automatically generated by NetLogo 4.0.4. Questions, problems? Contact email@example.com.
The applet requires Java 1.4.1 or higher. It will not run on Windows 95 or Mac OS 8 or 9. Mac users must have OS X 10.2.6 or higher and use a browser that supports Java 1.4. (Safari works, IE does not. Mac OS X comes with Safari. Open Safari and set it as your default web browser under Safari/Preferences/General.) On other operating systems, you may obtain the latest Java plugin from Sun's Java site.
In order for this to work, this file, your model file (Disease_Solo_SysRef.nlogo), and the file NetLogoLite.jar must all be in the same directory. (You can copy NetLogoLite.jar from the directory where you installed NetLogo.)
On some systems, you can test the applet locally on your computer before uploading it to a web server. It doesn't work on all systems, though, so if it doesn't work from your hard drive, please try uploading it to a web server.
You don't need to include everything in this file in your page. If you want, you can just take the HTML code beginning with <applet> and ending with </applet>, and paste it into any HTML file you want. It's even OK to put multiple <applet> tags on a single page.
If NetLogoLite.jar and your model are in different directories, you must modify the archive= and value= lines in the HTML code to point to their actual locations. (For example, if you have multiple applets in different directories on the same web server, you may want to put a single copy of NetLogoLite.jar in one central place and change the archive= lines of all the HTML files to point to that one central copy. This will save disk space for you and download time for your users.)
powered by NetLogo
view/download model file: Disease_Solo_SysRef.nlogo
Disease Solo is a one-player version of the HubNet activity Disease. It simulates the spread of a disease through a population. One agent in the population is a person controlled by the user; the others are "androids" controlled by the computer.
The user controls the blue agent via the buttons and slider on the right side of the view. The infection is started by pressing the "infect" button.
Sick agents are indicated by a red circle.
Androids can move using a few different simple strategies. By default they simply move randomly, however, using the AVOID? and CHASE? switches you can indicate that uninfected androids should run from infected ones or infected androids should chase uninfected ones.
The person may also catch the infection.
Healthy "agents" on the same patch as sick agents have an INFECTION-CHANCE chance of becoming ill.
SETUP/CLEAR - sets up the world and clears plots.
SETUP/KEEP - sets up the world without clearing the plot; this lets you compare results from different runs.
GO - runs the simulation.
INFECT - infects one of the androids
NUM-ANDROIDS - determines how many androids are created at setup
INFECTION-CHANCE - a healthy agent's chance at every time step to become sick if it is on the same patch as an infected agent
NUMBER SICK - the number of sick agents
NUMBER SICK - the number of sick agents versus time
AVOID? - when this switch is on each uninfected android checks all four directions to see if it can move to a patch that is safe from infected agents.
CHASE? - when this switch is on each infected androids checks all four directions to see if it can infect another agent.
UP, DOWN, LEFT, and RIGHT - move the person around the world, STEP-SIZE determines how far the person moves each time one of the control buttons is pressed.
Think about how the plot will change if you alter a parameter. Altering the infection chance will have different effects on the plot.
Do several runs of the model and record a data set for each one by using the setup/keep button. Compare the different resulting plots.
What happens to the plot as you do runs with more and more androids?
Currently, the agents remain sick once they're infected. How would the shape of the plot change if agents eventually healed? If, after healing, they were immune to the disease, or could still spread the disease, how would the dynamics be altered?
The user has a distinct advantage in this version of the model (assuming that the goal is either not to become infected, or to infect others), as the user can see the entire world and the androids can only see one patch ahead of them. Try to even out the playing field by giving the androids a larger field of vision.
Determining the first agent who is infected may impact the way disease spreads through the population. Try changing the target of the first infection so it can be determined by the user.
You can use the keyboard to control the person. To activate the keyboard shortcuts for the movement button, either hide the command center or click in the white background.
The plot uses temporary plot pens, rather than a fixed set of permanent plot pens, so you can use the setup/keep button to overlay as many runs as you want.
Disease (HubNet version)
This model is a one player version of the HubNet activity Disease. In the HubNet version, multiple users can participate at once.
To refer to this model in academic publications, please use: Wilensky, U. (2005). NetLogo Disease Solo model. http://ccl.northwestern.edu/netlogo/models/DiseaseSolo. Center for Connected Learning and Computer-Based Modeling, Northwestern University, Evanston, IL.