HubNet Guide

NetLogo

NetLogo is a programmable modeling environment. It comes with a large library of existing simulations, both participatory and traditional, that you can use and modify. Content areas include social science and economics, biology and medicine, physics and chemistry, and mathematics and computer science. You and your students can also use it to build your own simulations.

In traditional NetLogo simulations, the simulation runs according to rules that the simulation author specifies. HubNet adds a new dimension to NetLogo by letting simulations run not just according to rules, but by direct human participation.

Since HubNet builds upon NetLogo, we recommend that before trying HubNet for the first time, you become familiar with the basics of NetLogo. To get started using NetLogo models, see Tutorial #1: Running Models in the NetLogo Users Manual.

HubNet Architecture

HubNet simulations are based on a client/server architecture. The activity leader uses the NetLogo application to run a HubNet activity. When NetLogo is running a HubNet activity, we refer to it as a HubNet server. Participants use a client application to log in and interact with the HubNet server.

There are two types of HubNet available. With Computer HubNet, participants run the HubNet Client application on computers connected by a regular computer network. In Calculator HubNet, created in conjunction with Texas Instruments, participants use Texas Instruments graphing calculators as clients which communicate via the TI-Navigator system.

We hope to add support for other types of clients such as tablets and phones.

Activities

The following activities are available in the Models Library, in the HubNet Activities folder. Information on how to run the models and activities can be found in the Info tab of each model. Additional discussion of educational goals and ways to incorporate many of the activities into your classroom in the Participatory Simulations Guide on the Participatory Simulations Project web site.

• Bug Hunters Camouflage - students hunt bugs and camouflaging emerges.
• Dice Stalagmite HubNet - students roll dice and explore the space of dependent and independent events.
• Disease - A disease spreads through the simulated population of students.
• Disease Doctors - A slight modification to the Disease activity where some students can recover from the disease.
• Gridlock - Students use traffic lights to control the flow of traffic through a city.
• Polling - Ask students questions and plot their answers.
• Root Beer Game - An adaptation of a popular game created at MIT in the early 1960s that shows how small delays in a distribution system can create big problems.
• Sampler - Students engage in statistical analysis as individuals and as a classroom. Through these activities, students discover the meaning and use of basic concepts in statistics.
• Tragedy of the Commons - Students work as farmers sharing a common resource.

Clients

To use the client application you simply need to launch the HubNet client application that is bundled with NetLogo.

Requirements

To use Computer HubNet, you need a networked computer with NetLogo installed for the server. When using the client application you will also need a networked computer with NetLogo installed for each participant. When using in classroom settings we also suggest an attached projector for the leader to project the entire simulation to the participants.

Starting an activity

You'll find the HubNet activities in NetLogo's Models Library, in the HubNet Activities folder. We suggest doing a few practice runs of an activity before trying it in front of a class.

Open a Computer HubNet model. NetLogo will prompt you to enter the name of your new HubNet session. This is the name that participants will use to identify this activity. Enter a name and press Start.

NetLogo will open the HubNet Control Center, which lets you interact with the HubNet server.

You, as the leader, should then notify everyone that they may join. To join the activity, participants launch the HubNet Client application and enter their name. They should see your activity listed and can join your activity by selecting it and pressing Enter. If the activity you started is not listed the student can enter the server address manually which can be found in the HubNet Control Center.

HubNet Control Center

The HubNet Control Center lets you interact with the HubNet server. It displays the name, activity, address and port number of your server. The "Mirror 2D View on clients" checkbox controls whether the HubNet participants can see the view on their clients, assuming there is a view in the client setup. The "Mirror plots on clients" checkbox controls whether participants will receive plot information.

The client list on the right displays the names of clients that are currently connected to you activity. To remove a participant from the activity, select their name in the list and press the Kick button. To launch your own HubNet client press the Local button, this is particularly useful when you are debugging an activity. The "Reset" button kicks out all currently logged in clients and reloads the client interface.

The lower part of the Control Center displays messages when a participant joins or leaves the activity. To broadcast a message to all the participants, click on the field at the bottom, type your message and press Broadcast Message.

Troubleshooting

I started a HubNet activity, but when participants open a HubNet Client, my activity isn't listed.

On some networks, the HubNet Client cannot automatically detect a HubNet server. Tell your participants to manually enter the server address and port of your HubNet server, which appear in the HubNet Control Center.

Note: The technical details on this are as follows. In order for the client to detect the server, multicast routing must be available between them. Not all networks support multicast routing. In particular, networks that use the IPsec protocol typically do not support multicast. The IPsec protocol is used on many virtual private networks (VPNs).

When a participant tries to connect to an activity, nothing happens (the client appears to hang or gives an error saying that no server was found).

If your computer or network has a firewall, it may be impeding the HubNet server from communicating. Make sure that your computer and network are not blocking ports used by the HubNet server (ports 9173-9180).

The view on the HubNet client is gray.

• Verify that the "Mirror 2D view on clients" checkbox in the HubNet Control Center is selected.
• Make sure that the display switch in the model is on.
• If you have made changes to the size of the view on the server you may need to press the "Reset" button in the Control Center to ensure the clients get the new size.

There is no view on the HubNet client.

Some activities don't have a view on the client. If you want to add a view simply select "HubNet Client Editor" from the Tools Menu and add a view like any other widget. Make sure to press the "Reset" button before having clients log in.

I can't quit a HubNet client.

You will have to force the client to quit. On OS X, force quit the application by selecting Force Quit... in the Apple menu. On Windows, press Ctrl-Alt-Delete to open the Task Manager, select HubNet Client and press End Task.

My computer went to sleep while running a HubNet activity. When I woke the computer up, I got an error and HubNet wouldn't work anymore.

The HubNet server may stop working if the computer goes to sleep. If this happens, quit the NetLogo application and start over. Change the settings on your computer so it won't sleep again.

My problem is not addressed on this page.

See Contacting Us.

Known Limitations

If HubNet malfunctions, see the bug reporting information at Contacting Us.

Please note that:

• HubNet has not yet been extensively tested with large numbers of clients (i.e. more than about 25). Unexpected results may occur with more clients.
• Out-of-memory conditions are not handled gracefully
• Sending large amounts of plotting messages to the clients can take a long time.
• NetLogo does not handle malicious clients in a robust manner (in other words, it is likely vulnerable to denial-of-service type attacks).
• Performance does not degrade gracefully over slow or unreliable network connections.
• If you are on a wireless network or sub-LAN, the IP address in the HubNet Control Center is not always the entire IP address of the server.
• Computer HubNet has only been tested on LANs, and not on dial-up connections or WANs.