arthurhjorth / collective_action_models Goto Github PK

I'm still not sure how to do this, but there are a few different ways we could. the problem is that a week (= tick) would need to run a bunch of movements for each farmer, but asynchronous from the tick counter, and we would have to do them all at the same time or it might be too easy to see who does what. (Although students might not pick up on that.)

We have a long list of player actions (each a list too) now. We need to use clever of reporting filtered version of the list so we only get the ones that we want. The list looks like this:

[ [ user-id week action-type value] [ user-id week action-type value] ... ]

We want to be able to show:

1. how many people did what at what times
2. a time line per person
3. how many people said they would do something (how many defected)

similar to fine-them, but just reversed

they used to start with three cows, so maybe three times the price of a cow. then they can either fix fences, sow grass, or buy more cows

This is what should happen:

• People who survey the fields should have an 75% chance of seeing people who sow grass and who shepherd their cows.
• People who survey the fence should have a 100% chance of seeing people who repair fences.

This should happen as part of their do-weekly sub-procedure.