To be clear (since many people are unaware of the "Disable until ticks
start option"), the way you would do this is to open your model in the
desktop version of NetLogo, open the menu to edit your "go" button, and
check the "Disable until ticks start" checkbox.
"Disable until ticks start" demo
I've definitely seen it before in NLW where someone clicking "go" before
"setup" leads to the model page being entirely borked until refreshed,
so that might be related to the problem you're seeing in classes, but I
can't really say for sure without more information.
Robert's other suggestions are also very good.
On 09/01/2015 11:07 AM, Robert Grider wrote:
Thanks for reporting! We tried to reproduce the error, but have been
unable to do so. We do have a few ideas for things that may be helpful:
* If this happens again, have students open Chrome's development
tools <https://developer.chrome.com/devtools#access>, flip to the
console tab, and copy the contents. This will be extremely helpful
for us in figuring out what has gone awry.
* Plots tend to take up a lot of memory, so you may find that you
get a better-performing model by eliminating some of the smaller
plots. Note that you can turn individual plot lines in the model
on and off by clicking on their name just below the plot.
* While running your model, I found that if I switched back and
forth between clicking the setup and go buttons very quickly, I
could sometimes get the model into a strange state. While it
wasn't exactly the behavior you described, I think it might be
related. In order to prevent this from happening, it would be best
to disable the |go| button (and probably the invade button) until
after ticks start. I'm going to open a ticket for NetLogo Web to
investigate whether these strange goings-on are an engine issue or
something else.
Hope that helps! Please follow-up if you come across more information
or are able to resolve the issue.
On Monday, August 31, 2015 at 8:21:42 PM UTC-5, David Quigley wrote:
Hey folks, wanted to start off a thread for a bug I discovered
today. I'll try to update as I track it down, but if y'all have
similar experiences or ideas on where the problem may lay, I
thought this might be helpful.
The Problem: Occasionally, a simulation running in NLW does not
complete the process of generating agents on setup.
The Evidence: My environment view does not include any turtles.
The simulation will not run.
The Solution: Refresh the page (perhaps more than once).
Details: We developed and deployed a custom NetLogo Web
application (found here
<http://inquiryhub.dls.ucar.edu/bio/InvasiveSpeciesMidwest.html>)
to support our Biology curriculum. We had ~20 users hit the page
at approximately the same time (and perhaps several times each).
The workflow is similar to other NL sims, the users simply hit
"Setup" to get the environment to populate. Certain users (~10%)
did not have the environment populate when they hit "Setup". As
far as I noticed, the simulation does not function after this
error (so re-clicking "setup" does not fix it, clicking "go" does
not start any interactions (i.e. no ticks), etc.). The first go-to
triage step I used was having users hit refresh on their browsers,
and it fixed the problem. The other users (~90%) had no issues.
Users with errors were using Dell Latitude laptops, running
windows, browsing in Chrome. Users with nearly identical setups
(e.g. me) do not have this issue.
I wish I had more detailed reports, but it was a live test session
and I was doing triage on the spot. Updates to come, if I can find
any. If you have thoughts, questions, etc, just let me know!
--
You received this message because you are subscribed to the Google
Groups "netlogo-devel" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"netlogo-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
