Check it out here: http://nsrivast.github.io/data-viz-nairobi/
I'll be posting the student projects tomorrow after the presentations!
453 karma · joined November 14, 2007
Check it out here: http://nsrivast.github.io/data-viz-nairobi/
I'll be posting the student projects tomorrow after the presentations!
[1] http://www.amazon.com/Fluid-Concepts-And-Creative-Analogies/...
Love geoguessr! Thank you for making it, I am officially addicted.
I think there are lots of interesting things one could do with the gameplay and data. I would classify it as a Game with a Purpose[1], and I wonder if you have considered using the data you gather to answer some interesting questions:
1) Can we re-map the world according to the similarity measure measured by your game rather than the geographic measure? If so, what does the map look like?
2) How much additional information do you get by exploring? (What is the relationship between distance explored and subgame score?) Is there a way to add this as a feature of the game, i.e. require players to "invest" points to explore a larger area?
3) What are the salient features of a landscape that place it geographically? Language on stores/signs, architecture, landscape geography, prominent flora/fauna, type of cars/roads. Can we identify and classify these features?
Having built a few games with a purpose before (e.g. Wikiwarp [2]), I would love to help if I can. I would be happy to contribute to development to get access to your very interesting data!
Thanks, and best of luck!
[1] http://en.wikipedia.org/wiki/Game_with_a_purpose [2] https://github.com/nsrivast/wikiwarp
1) medium of exchange
2) store of value
3) unit of account
4) common ground for rumor and speculation!
For this example, let's assume our queueing environment is a grocery store checkout line: our customers enter, line up in order, and are checked out by one or more registers. The basic way to think about these problems is to classify them across three parameters:
- arrival time: do customers enter the line in a way that is Deterministic (events happen over fixed intervals), randoM (events are distributed exponentially and described by Poisson process), or General (events fall from an arbitrary probability distribution)?
- checkout time: same question for customers getting checked out, is that process D or M or G?
- N = # of registers
So the simplest example would be D/D/1, where - for example - every 3 seconds a customer enters the line and every 1.5 seconds a customer is checked out by a single register. Not very exciting. At a higher level of complexity, M/M/1, we have a single register where customers arrive at rate _L and are checked out at rate _U (in units of # per time interval), where both _L and _U obey Poisson distributions. (You can also model this as an infinite Markov chain where your current node is the # of people in the queue, you transition to a higher node with rate _L and to a lower node with rate _U.) For this system, a customer's average total time spent in the queue is 1/(_U - _L) - 1/_U.
The intelligent routing system routes each customer to the next available checkout counter; equivalently, each checkout counter grabs the first person in line as soon as it frees up. So we have a system of type M/G/R, where our checkout time is Generally distributed and we have R>1 servers. Unfortunately, this type of problem is analytically intractable, as of now. There are approximations for waiting times, but they depend on all sorts of thorny higher moments of the general distribution of checkout times. But if instead we assume the checkout times are randomly distributed, we have a M/M/R system. In this system, the total time spent in queue per customer is C(R, _L/_U)/(R _U - _L), where C(a,b) is an involved function called the Erlang C formula [2].
How can we use our framework to analyze the naive routing system? I think the naive system is equivalent to an M/M/1 case with arrival rate _L_dumb = _L/R. The insight here is that in a system where customers are instantaneously and randomly assigned to one of R registers, each register should have the same queue characteristics and wait times as the system as a whole. And each register has an arrival rate of 1/R times the global arrival rate. So our average queue time per customer in the dumb routing system is 1/(_U - _L/R) - 1/_U.
In OP's example, we have on average 9000 customers arriving per minute, or _L = 150 customers/second. Our mean checkout time is 306ms, or _U ~= 3. Evaluating for different R values gives the following queue times (in ms):
# Registers 51 60 75 100 150 200 500 1000 2000 4000
dumb routing 16,667 1,667 667 333 167 111 37 18 9 4
smart routing 333 33 13 7 3 2 1 0 0 0
which are reasonably close to the simulated values. In fact, we would expect the dumb router to be comparatively even worse for the longer-tailed Weibull distribution they use to model request times, because you make bad outcomes (e.g. where two consecutive requests at 99% request times are routed to the same register) even more costly. This observation seems to agree with some of the comments as well [3].
[1] http://en.wikipedia.org/wiki/Queueing_theory
[2] http://en.wikipedia.org/wiki/Erlang%27s_C_formula#Erlang_C_f...
If the voting policy is unknown (and PG is committed to keeping it unknown), perhaps fewer people will worry about it's functional form, fewer people will care about what their vote multiplier happens to be, and more people would get on with the incredibly simple business of submitting interesting links and voting up what they find interesting. Perhaps.
You should leave if the quality of the content deteriorates, not based on some background metric for an arbitrary scrip!
Yet Company B does not necessarily look less attractive - a high amount of short sales might mean a rise in the price when people cover (buy back) their shorts.
Label each with a tiny sticker that says "Private: Do NOT Read!"
Place each in a random public location.