I need to count ticks each car takes from start of trip till end of trip. I am working on showing road bloackade simulation in netlogo. For this trip time of cars is needed to be calculated.
For this I have made following code:
to-report start-journey-time
report min-pxcor
end
to-report end-journey-time
report max-pxcor
end
The current value of the tick counter is access with the reporter ticks. Note that this is different from tick, which is used to increment the counter.
So, assuming each car has a variable called journey-time, you can do something like this. When the journey starts: set journey-time ticks, and when the journey finishes set journey-time ticks - journey-time. This is not great code since you are using the same variable for both the start time and the duration, but it saves a variable. If you want more readable code, use separate variables.
Related
I'm trying to run experiments for a model of mine. I need it to output certain variable values for every tick but when I run the experiment I only get the values of either tick = 0 or the values at the end of the simulation. I need the values for every tick, anyone knows how this can be done in the NetLogo behaviour space experiments? Thanks in advance!
When you setup an experiment, there is a checkbox for saving the "reports" of a reporter at every step:
When I setup this experiment for the Wolf Sheep Predation Model from the Models Library, it outputs the count turtles for every tick.
Looking for a way to store a turtle length of stay in the model after they have left the model. My model runs for several months and a few thousand turtles enter, undergo process then leave the area. It's complicate model (it's a hybrid DES and ABM) so I've tried to reproduce the simple bit below.
Turtles will be created at every tick and given a random length of stay but will only be able to begin process when they move to the right area (area-name) and when their time is up they leave the area. Their time-in-system reflects the wait for the area and the length-of-stay which I want to save once they're complete. If I leave them in the model it starts to break down after a couple of months and I suspect this is because the model has too many turtles still in the system for calculation and is inefficient.
go
create turtles 2
[
set time-in-system 0
set length-of-stay ceiling ((random-normal 48 4) + ticks)]
set shape "person"
if any? area-name with [not any? turtles-here]
[move-to one-of area-name]
]
undergo-process
end
to-undergo-process
ask turtles with [shape = "person"]
[
set time-in-system time-in-system + 1
]
ask turtles-on area-name
[if ticks = length-of-stay
[set shape "dot"
move-to exit-door]
end
I can then plot and see in realtime to make sure it is working
histogram time-in-system of turtles with [shape = "dot"]
but can't seem to figure out how to store them as unique values for plotting after the model has run and I have a dataset of outcomes without keeping them alive in the model. The real-time plot isn't necessary as long as I can store the unique values after they have left
If I ask them to die then I lose the unique values in the histogram. I don't want a tally of all values but each turtle's unique value at the end of the process after they left - at the moment the only solution I have to storing them is as an agent-set that stays alive in the exit-door patch but this takes up a lot of calculation power as the model progresses for months...
There may be a really simple command for this but I've been going round in circles through the programming manual trying to find it. Any tips appreciated
You should create a list storing the values of turtles that left.
Isolating only the code that is relevant for this purpose, it would be something like:
globals [
times
]
to setup
set times (list)
end
to leave-simulation ; This being executed by turtles.
set times lput (time-in-system times)
die
end
If your program is going to run for actual months, I recommend you use the file-write command to store your data. This way the data is preserved if the program halts for any reason; it gives you much more freedom to do the analysis you want without running the full simulation again.
If you write to a .csv (comma separated value) file, you can use almost any program (excel, R, matlab, python, C# or back to netlogo) to plot a histogram.
I'm working with a NetLogo model on EV charging behaviour. All (500) agents monitor their my-charging-demand per tick and I want to find out what happens to this emergent behaviour when I change the policy intervention that is active (costs of electricity in this case). I am trying to show changes in charging characteristics such as charging-duration, charging power etc.
What is the best way to create data on the agents' my-charging-demand in time?
Right now I am plotting all their data in one graph using the following code:
ask adopters
[ create-temporary-plot-pen (word-who)
set-plot-pen-color color
plotxy ticks my-charging-demand
]
It works, but unfortunately it also made the model incredibly slow, as 500 pens are to be updated every tick. The model needs 105120 ticks before a whole year/run is completed, as each tick in the model represents 5 minutes. Therefore, speed does matter :-)
Is there a more efficient way to keep track / create data of one variable all agents have?
If I have understood this correctly, you want each agent to remember the value of its variable my-charging-demand across all time. If so, the easiest way (but I don't know if it's more efficient) is to have the list as a turtle variable. So, modify your turtles-own to add another variable:
adopters-own
[ ....
my-charging-demand
my-charging-demand-series
]
And wherever you have the code for calculating demand, add the result to the list
ask adopters
[ ...
set my-charging-demand ...
set my-charging-demand lput my-charging-demand my-charging-demand-series
...
]
I can't imagine a plot with 500 lines is readable. The plot should do something like the average of my-charging-demand or the proportion of turtles with my-charging-demand greater than some threshold.
I would like to use the BehaviorSpace's "Measure runs using reporters" to compile the number of turtles dead number-dead for each ticks ticks, ID information on living turtle who for each ticks, and information on the number of counters count-up that the living turtle has for each ticks. I am beginner of Netlogo. I do not know how to set it to "Measure runs using reporters". Already, I was referring to "Netlogo's BehaviorSpace Guide" https://ccl.northwestern.edu/netlogo/docs/behaviorspace.html , and then count turtles are successful. The following is an example of the input screen of "Measure runs using reporters". However this was a syntax error except count turtles.
count turtles
count number-dead
count count-up
count who
If number-dead and count-up are breeds that you have defined, then those parts are fine. If they are instead global variables that contain the number of something, then you want to show them rather than count them. However, who is an internal variable that belongs to each turtle so that piece of code doesn't make any sense.
What I suggest you do is create a monitor on the interface for each of the variables that you want in your BehaviorSpace output. So create one monitor for count turtles and another for show number-dead and so on. When all of those are working for a normal run, then you can do a BehaviourSpace run.
I've made a population model in Netlogo where the simulation stops when all my turtles have died OR the number of 300 ticks is reached. I need to report (or write to a file) the mean state of my turtles (turtle-own variables) one tick before the simulation ends. It would be easy if all simulations will run to 300 ticks, but in most cases the simulation ends before this happens (all turtles die). How can I achieve this? The death of the turtles is conditioned to either their "lifetime" runs out or to a stochastic probability of dying, so I can't predict when will this happen, and I need to know whether the last turtle died due to their lifetime running out or due to the probability worked against the turtle. Thanks!
Have you played around with BehaviorSpace at all? It works pretty well for means and sums etc. You can easily make BehaviorSpace experiments to export whatever reporters you set up to a .csv spreadsheet or table, whether you want reports at the end of your simulation or at each tick. For a simple example, if I want to know the mean x-coordinate of my turtles, I can set up the reporter using to-report:
to-report mean-xcor
let xlist ( [xcor] of turtles )
report mean xlist
end
Then, I can use Behavior Space (Tools > Behaviour Space) to set up an experiment that writes that mean xcor for all turtles at either each tick or only at the end of a run. The tool also allows you to set up multiple parameterizations of your simulation and compare results with different treatments- it's really handy! You can get creative with what you report in order to have the output be what you need. For your specific case, you could just make sure that your experiment is recorded at each tick.
You could also do this manually and with a little more control if you prefer. You can create a file and header during your setup using something like:
to setup-turtle-reporting
file-open "turtle_details_out.csv"
file-type (word "tick, who, xcor, ycor \n")
file-close
end
That sets up a .csv file in your model folder that has the column headers tick, who, xcor, and ycor. Then, during each tick you can have turtles write the appropriate variables to that same file:
to turtle-report
file-open "turtle_details_out.csv"
ask turtles [
file-type (word ticks ", " who ", " xcor ", " ycor "\n" )
]
file-close
end
This option gives you a bit more control in some ways, but is fiddlier. You will have to also play around with file-delete or manually delete/rename the file as you complete different simulations, as file-type will append to the existing file rather than overwriting it.