

- #Netlogo if else how to
- #Netlogo if else update
- #Netlogo if else Patch
- #Netlogo if else code
- #Netlogo if else series
Green sticky notes when you get this to work. Switch back to the Interface, click “setup” and “go”, and watch your turtles graze! Let’s create a structured environemnt through which they will move. Now we’ve got 100 turtles aimlessly moving around, completely unaware of anything else around them. We’d like to keep go as simple as possible, so that it is easy to understand.Įventually, it will include many other things you want to have happen as the model runs, such as calculating something or plotting the results.Įach of these things to do will have its own procedure and each procedure will have its own unique name. We could have, but during the course of building your model, it’s likely that you’ll add many other parts. Why couldn’t we have just written all of these commands in go instead of in a separate procedure? Green sticky notes when you’ve gotten this to work. Once finished adding the code, go back to the Interface, click setup to initialize and go to make your agents move. The “-“ combines “move” and “turtles” into a single name. Earlier, we used red - 2, with spaces, in order to subtract two numbers, but here we want move-turtles, without spaces. Note there are no spaces around the hyphen in move-turtles. The “Disable until ticks start” prevents you from pressing go before setup. The “Forever” checkbox makes the button stay down once pressed, so its commands run over and over again, not just once.

For Commands enter go instead of setup.Follow the same steps you used to make the setup button, except: It’s above the view and by default says “continuous”.
#Netlogo if else update
Now that we’re using the tick counter (automatically created with reset-ticks), we should tell NetLogo that it only needs to update the view once per tick, instead of continuously updating it. Repeat to see the effects of the random initialization. Switch to the Interface tab and press the setup button you made before. end completes the definition of the “setup” procedure.reset-ticks starts the tick counter, now that setup is otherwise complete.That makes the turtle move to the point with those coordinates. Finally each turtle runs the setxy command with those two numbers as inputs. Then each turtle runs the reporter random-ycor, same for the Y axis. First each turtle runs the reporter random-xcor which will report a random number from the allowable range of turtle coordinates along the X axis. A reporter, as opposed to a command, reports a result. setxy random-xcor random-ycor is a command using “reporters”.After create-turtles we can put commands for the new turtles to run, enclosed by square brackets.
#Netlogo if else Patch
They start out standing at the origin, that is, the center of patch 0,0.

A procedure is a sequence of NetLogo commands that we assign a new name. Pressing the button runs a procedure called “setup”. Red sticky notes if this didn’t work for you.
#Netlogo if else series
A procedure combines a series of NetLogo commands into a single new command that you define. The way to make patches and turtles do more complex things is by creating procedures.
#Netlogo if else code
Now it is time to learn the heart of NetLogo: the Code tab.
#Netlogo if else how to
Thus far, we have covered how to access, modify, and direct all entities in NetLogo.
