Printable View
It's right. Imagine: (999*30+29)/1000 = 29.9990. This value gets rounded up 2 positions after decimal points, so you get 30 as average.
You see, it's very unlikely to get the minimum loss of 29 Caltrops, but it's possible. Even after 1000 simulations the results may vary, but that's not nameable. If you take a look at the theoretical losses, the losses are much worse than the sim shows you. But they are so unlikely that one must disregard it.
I'm curious, not argumentative, so please take this question in that context.Quote:
Originally Posted by Asipak
If I configure a 9 round battle and press the Simulate button 20 times, does it not calculate the battle 1000 times? If so, how is that different from configuring that same battle, entering "1000" for the iterations, and pressing Simulate once?
If it's not the same, please do elaborate on how it's different, as I've been operating under the assumption that repeatedly clicking Simulate does the same thing. I understand one method loads the server up sort of "all at once" vs. a more spread out method, but I've gotten pretty good at timing when each iteration completes & clicking Simulate again quickly. :)
It does the same and it would be also quicker to simulate 1000 times once than 20*50 times because you needn't to load the HTML 20 times and you also save database requests. But users have learned that the load time of a web page doesn't take many seconds in general, so, in my opinion, it would annoy them. Nobody likes slow web pages. Especially, if you don't know the reason exactly.Quote:
If I configure a 9 round battle and press the Simulate button 20 times, does it not calculate the battle 1000 times? If so, how is that different from configuring that same battle, entering "1000" for the iterations, and pressing Simulate once?
This is the main reason for me.
Another point might be: For many simulations it's not necessary to simulate them more than 50 times, when you already got too high losses. Of 100.000 Simulations there are about 75.000 Simulations with only 50 repetitions in the database. It would have been a waste of resources to simulate them 1000 times.
I've noticed that the link at the bottom for the current sim doesn't include the limit trigger for a 250 gen setup when you open the simulation from the hall of fame. If I hit simulate battle then it shows up.
Hmm, you're right. I'm pretty sure that I've added the parameter to the link some days ago. Strange. I'll fix it.
If I typed "1000" into an "Iterations" field, I would know why. :)Quote:
Nobody likes slow web pages. Especially, if you don't know the reason exactly.
And while one of my favorite sayings is: "You can't fix stupid," I think you could put a small disclaimer up saying something like, "Warning: A large Iterations value will take longer to calculate." That really SHOULD address other concerns. Default value for the field could still be 50. Heck, it could even reset to 50 after every simulation.
Totally agree on this - I don't want it to calculate 1000 iterations every time. I rarely trust the results from 50 iterations, but I'll use it quickly to see how things look. If they look reasonably promising, I'd probably reset it to 250 & see how that worked out, and only if I was still happy would I go to 1000.Quote:
Another point might be: For many simulations it's not necessary to simulate them more than 50 times, when you already got too high losses. Of 100.000 Simulations there are about 75.000 Simulations with only 50 repetitions in the database. It would have been a waste of resources to simulate them 1000 times.
Thank you for discussing it with me, I do appreciate it.
The multiple waves doesn't seem to be working right now.. when i click calculate and it shows me other's results and I click one that is using multiple waves then click on the 2nd wave it still shows me the first wave numbers and when i change it it changes only the first wave. Same if I create my own 2 waves. If I click 2nd wave will still be showing first wave and not 0.
I know the wave buttons don't work for me in chrome (it just stays on wave 1), but they do in firefox. Other people have said that doesn't happen for them in chrome though so I thought it was just me.
That's strange, because it works by me, also with chrome. Please try to delete your cache. If this doesn't help, perhaps you need to update the browser.
Many functions are realised with javascript and if they won't work some day, perhaps beacuse of an update, it would be always a good idea to refresh your cache.
I agree, but I think a better solution may be to set the iteration value to 100 after 200 simulations. I really don't like to add another input field to the form. The simulator shall stay simple and be easy to use.Quote:
If I typed "1000" into an "Iterations" field, I would know why.
And while one of my favorite sayings is: "You can't fix stupid," I think you could put a small disclaimer up saying something like, "Warning: A large Iterations value will take longer to calculate." That really SHOULD address other concerns. Default value for the field could still be 50. Heck, it could even reset to 50 after every simulation.
I have implemented an ajax-loader image to show the simulation process and the iteration value will be set to 100 after 200 simulations.
Would it be possible to add a drop-down to select from the camp setups for each adventure? I know you have the map that you can click on each camp to setup the simulator but having the camp setups on the simulator would be far more handy imo.