Great game of Turkey: Difference between revisions

Revision as of 17:21, 7 February 2016

Make today's decision

# This code is Op_en7421# on page [[Great game of Turkey]]

library(OpasnetUtils)

objects.latest("Op_en7421", code_name = "initiate")

ques <- question()

cat(as.character(ques$Description[1]), "\n")
cat(as.character(ques$Question[1]), "\n")

oprint(ques["Option"])

+ Show code - Hide code

# This is code Op_en7421/choices on page [[Great game of Turkey]]

library(OpasnetUtils)

objects.latest("Op_en7421", code_name = "initiate")

ques <- question()

dat <- data.frame(
	Question = ques$Question[1],
	User = wiki_username, 
	Result = ques$Option[option] # Option
)

opbase.upload(
	dat, 
	ident = "Op_en7421", 
	name = "Great game of Turkey", 
	subset = "Choices", 
	act_type = "append", 
	language = "eng", 
	who = wiki_username
)

oprint(dat)
cat("Your choice was successfully saved.\n")

Setup your profile

+ Show code - Hide code

# This is code Op_en7421/choices on page [[Great game of Turkey]]

library(OpasnetUtils)

dat <- data.frame(
	User = wiki_username, 
	Date = as.character(Sys.Date()),
	Result = group # Group
)

opbase.upload(
	dat, 
	ident = "Op_en7421", 
	name = "Great game of Turkey", 
	subset = "User", 
	act_type = "append", 
	language = "eng", 
	who = wiki_username
)

oprint(dat)
cat("Your group was successfully saved.\n")

Question

What is a good game to crowdsource citizen priorities about daily political decisions in such a way that

it can be done using a mobile app,
it characterises happiness of citizen groups of the decisions,
it characterises progress of important societal values,
it enables crowdsourcing the actual questions and options asked?

Answer

See the top of the page for the main questionnaire of the game. Here we present results from the game.

+ Show code - Hide code

#This is code Op_en7421/ on page [[Great game of Turkey]]

library(OpasnetUtils)
library(ggplot2)

objects.latest("Op_en7421", code_name = "initiate")
objects.latest("Op_en6007", code_name = "answer") # oggplot etc

BS <- 24

happindex <- EvalOutput(happindex)
oggplot(happindex, x = "Date", fill = "Group") + facet_wrap(~ User) + labs(title = "Happiness per day") +
	theme(axis.text.x = element_text(angle = 90, hjust = 1)) # Turn text and adjust to right

happmean <- oapply(happindex, cols = c("Date", "Question", "Option"), FUN = mean)
happequity <- oapply(happmean, cols = "Group", FUN = sd)

oggplot(mergeusers(happmean), x = "User", fill = "Group") + labs(title = "Mean happiness during the whole period")
oggplot(mergeusers(happequity), x = "User") + labs(title = "Deviation from the equity")

progindex <- EvalOutput(progindex)
oggplot(progindex, x = "Date", fill = "Issue") + facet_wrap(~ User)+ labs(title = "Progress per day") +
	theme(axis.text.x = element_text(angle = 90, hjust = 1)) # Turn text and adjust to right

progmean <- oapply(progindex, cols = c("Date", "Question", "Option"), FUN = mean)
progequity <- oapply(progmean, cols = "Issue", FUN = sd)

oggplot(mergeusers(progmean), x = "User", fill = "Issue") + labs(title = "Mean progress over time")
oggplot(mergeusers(progequity), x = "User") + labs(title = "Deviation from the policy balance")

Rationale

Questions(-)
Obs	Date	Question	Description	Option
1	2016-01-16	Should the scarf ban in the universities be abandoned?	Since Kemal Atatürk, scarfs have been banned in universities. Now this policy is being re-evaluated.	Yes
2	2016-01-16	Should the scarf ban in the universities be abandoned?		Partly
3	2016-01-16	Should the scarf ban in the universities be abandoned?		No
4	2016-01-17	Should the military budget be increased?	The political and military situation in Syria and areas nearby have become more difficult during the last 12 months.	Yes
5	2016-01-17	Should the military budget be increased?		No, keep the same
6	2016-01-17	Should the military budget be increased?		No, reduce
7	2016-01-17	Should the education budget be increased?		Yes
8	2016-01-17	Should the education budget be increased?	X % of the young people in Turkey do not receive any education except the primary school. Education is a known determinant of social improvement, but it is also expensive.	No, keep the same
9	2016-01-17	Should the education budget be increased?		No, reduce
10	2016-01-18	Should the presidential palace be made to a public place?	President Erdogan built a presidential palace with more than a thousand rooms. Should it be opened up to the public instead of being in president's private use?	Yes
11	2016-01-18	Should the presidential palace be made to a public place?		No
12	2016-01-18	What should be done to the immigration situation near the Syrian border?	The was in Syria has made millions of people to flee from the area.	Increase refugee camps and ask for money from the EU.
13	2016-01-18	What should be done to the immigration situation near the Syrian border?		Force people from Syria to go back.
14	2016-01-18	What should be done to the immigration situation near the Syrian border?		Ask military help from the US and Nato.
15	2016-01-18	What should be done to the immigration situation near the Syrian border?		Fight the illegal refugee transport from Turkey across the Mediterranean.
16	2016-01-18	What should be done to the immigration situation near the Syrian border?		Attack Russia verbally because it helps the Syrian government and prolongs the war.
17	2016-01-18	What should be done to the immigration situation near the Syrian border?		Fight the Kurds in Syria but silently so that western allies do not get mad.
18	2016-01-19	How should terrorist attack be prevented?	Homeland security may be compromised in touristic areas because of terrorist attacks.	Increase guards in tourist areas.
19	2016-01-19	How should terrorist attack be prevented?		Increase guards on the streets.
20	2016-01-19	How should terrorist attack be prevented?		Increase international collaboration.
21	2016-01-19	How should terrorist attack be prevented?		Do as before.

Calculations

+ Show code - Hide code

# This is code Op_en7421/happiness on page [[Great game of Turkey]]

library(OpasnetUtils)

objects.latest("Op_en7421", code_name = "initiate")

ques <- question()

cat(as.character(ques$Question[1]), "\n")

oprint(ques["Option"])

dat <- data.frame(
	Question = ques$Question[1],
	Option = ques$Option[option],
	Group = group,
	User = wiki_username, 
	Result = hscore # Hscore
)

opbase.upload(
	dat, 
	ident = "Op_en7421", 
	name = "Great game of Turkey", 
	subset = "Happiness", 
	act_type = "append", 
	language = "eng", 
	who = wiki_username
)

oprint(dat)
cat("Your happiness score was successfully saved.\n")

+ Show code - Hide code

# This is code Op_en7421/progress on page [[Great game of Turkey]]

library(OpasnetUtils)

objects.latest("Op_en7421", code_name = "initiate")

ques <- question()

cat(as.character(ques$Question[1]), "\n")

oprint(ques["Option"])

dat <- data.frame(
	Question = ques$Question[1],
	Option = ques$Option[option],
	Issue = issue,
	User = wiki_username, 
	Result = pscore # Pscore
)

if(!is.na(pscore)) {
	opbase.upload(
		dat, 
		ident = "Op_en7421", 
		name = "Great game of Turkey", 
		subset = "Progress", 
		act_type = "append", 
		language = "eng", 
		who = wiki_username
	)
	oprint(dat)
	cat("Your progress score was successfully saved.\n")
} else {
	cat("Choose your score first.\n")
}

+ Show code - Hide code

# This code is Op_en7421/ on page [[Great game of Turkey]]

library(OpasnetUtils)

ques <- opbase.data("Op_en7421.questions")
colnames(ques)[colnames(ques) == "Result"] <- "Option"

questions <- unique(as.character(ques$Question[ques$Date == as.character(Sys.Date())]))

for(i in questions) {
  cat(as.character(ques$Description[ques$Question == i][1]), "\n\n")
  cat(as.character(ques$Obs[ques$Question == i][1]), ": ", i, "\n")
  oprint(ques[ques$Question == i , "Option", drop = FALSE])
}

+ Show code - Hide code

# This is code Op_en7421/ on page [[Great game of Turkey]]

library(OpasnetUtils)

ques <- opbase.data("Op_en7421.questions")
question <- as.character(ques$Question[ques$Obs == question])

dat <- data.frame(
	Date = as.character(Sys.Date()),
	User = wiki_username, 
	Result = question # Question
)

opbase.upload(
	dat, 
	ident = "Op_en7421", 
	name = "Great game of Turkey", 
	subset = "Question_vote",  # You MUST spell it with _
	act_type = "append", 
	language = "eng", 
	who = wiki_username
)

oprint(dat)

cat("Your question vote was successfully saved.\n")

+ Show code - Hide code

# This is code Op_en7421/ on page [[Great game of Turkey]]

library(OpasnetUtils)

ovote <- opbase.data("Op_en7421.questions")
ovote$Obs <- as.character(ovote$Obs)

dat <- data.frame(
  Question = ovote$Question[ovote$Obs == option],
  User = wiki_username, 
  Result = ovote$Result[ovote$Obs == option] # Option
)

opbase.upload(
	dat, 
	ident = "Op_en7421", 
	name = "Great game of Turkey", 
	subset = "Option_vote", 
	act_type = "append", 
	language = "eng", 
	who = wiki_username
)

oprint(dat)

cat("Your option vote was successfully saved.\n")

+ Show code - Hide code

# This is code Op_en7421/initiate on page [[Great game of Turkey]]

library(OpasnetUtils)

question <- function() {
  if(!exists("today")) today <- as.character(Sys.Date())
  ques <- opbase.data("Op_en7421.questions")
  
  qvote <- opbase.data("Op_en7421.question_vote")
  colnames(qvote)[colnames(qvote) == "Result"] <- "Question"
  qvote <- unique(qvote[qvote$Date == today , ]) # Remove double votes
  qvote <- aggregate(qvote["User"], by = qvote["Question"], FUN = length)
  qvote <- qvote[order(qvote$User, decreasing = TRUE) , ][1,] # Choose the row with most votes
  
  temp <- merge(ques, qvote)[1 , c("Question", "Description")]

  # Find the most popular options
  
  ovote <- opbase.data("Op_en7421.option_vote")
  colnames(ovote)[colnames(ovote) == "Result"] <- "Option"
  ovote <- ovote[nrow(ovote):1 , ] #Turn newest first
  #ovote <- ovote[!duplicated(ovote[c("Date", "User") , ]) , ] # Only keep the last vote
  out <- merge(temp, ovote)
  out <- aggregate(out["User"], by = out[c("Question", "Description", "Option")], FUN = length)
  out <- out[order(out$User, decreasing = TRUE) , ][1:4,] # Choose the 4 rows with most votes
  out <- out[!is.na(out$User) , ]
  out$User <- NULL
  
  return(out)
}

mergeusers <- function(happ) {
  if(length(happ$User) != length(happ$User[happ$User == wiki_username])) {
    test1 <- happ[happ$User == wiki_username , ]
    test1$User <- "You"
    test2 <- happ[happ$User != wiki_username , ]
    test2$User <- "Others"
    happ <- combine(test1, test2)
  }
  return(happ)
}

happiness <- Ovariable("happiness", ddata = "Op_en7421.happiness", getddata = FALSE)
progress <- Ovariable("progress", ddata = "Op_en7421.progress", getddata = FALSE)

choices <- Ovariable("choices", 
 dependencies = data.frame(Name = "happiness"),
 formula = function(...) {
   dat <- opbase.data("Op_en7421.choices")
   colnames(dat)[colnames(dat) == "Result"] <- "Option"
   dat$Obs <- NULL
   dat$Result <- 1
   return(dat)
 }
)

questions <- Ovariable("questions", 
 dependencies = data.frame(Name = "happiness"),
 formula = function(...) {
   dat <- opbase.data("Op_en7421.questions")
   colnames(dat)[colnames(dat) == "Result"] <- "Option"
   dat$Obs <- NULL
   dat$Result <- 1
   return(dat)
 }
)

happindex <- Ovariable("happindex", 
  dependencies = data.frame(Name = c(
    "happiness",
    "choices",
    "questions"
    )),
  formula = function(...) {

    happiness <- oapply(happiness, cols = "User", FUN = mean)
    happindex <- choices * happiness * questions
    return(happindex)
  }
)

progindex <- Ovariable("progindex", 
 dependencies = data.frame(Name = c(
   "progress",
   "choices",
   "questions"
 )),
 formula = function(...) {

   progress <- oapply(progress, cols = "User", FUN = mean)
   progindex <- choices * progress * questions
   return(progindex)
 }
)

objects.store(list = ls())

Structure and functionalities

The content of and use of the data tables is the following:

Issues: List of decisions to be made. A user can suggest only one issue per day. For each day, the most popular issue is taken to the game.
Actions: List of decision options to be made. A user can suggest only one action per issue. For each time point, two most popular actions are taken to the game. However, the actions in the game may change during the day, if the rank of the issues changes.
Issue vote: List of votes for each issue. Each user can cast a single vote either for or against an issue. The number of votes a user has equals their bonuses.
Action vote: List of votes for each action under issues. The voting system is the same as for issues.
Decisions: List of decisions each user makes from the actions and issues on the game.
Bonuses: List of bonuses the users have earned during the game. In the beginning, each user has 1 bonus. You can earn bonuses if your actions suggestions gets to be played (+1) or if your issues gets to be played (+5). Every time a user makes a decision, they get +0.1 bonus.
Happiness: Users' opinions about how much happiness an action brings to their own group.
Values: Users' opinions about how much value an action brings to a selected group.
Users: List of users' groups (i.e. to which group each user identifies themselves).

The functions needed are the following.

Upload data: Take the data provided by the user or calculated. Add automatic fields, e.g. ts, user and date. Upload data to the respective table.
Create ovariable: Download data from a table. From the data, find the unique rows with a given condition (e.g. discard previous decisions made by a user previously on the same day). Then create an ovariable with the structure needed.
Firstuser: Check's whether user's wiki_username is found from Bonuses. If not, it is added there and 1 bonus given.

The interface codes used are the following:

Suggest issues: Ask date, issue and description from user. Date means the date when this issue will be played. Default is today, but user can change that and suggest future issues. Timestamp (ts) come automatically. User is the wiki_username. Upload data to Issues table. No need to check previous entries. Upload user's bonus to Issue vote as number of votes.
Show issues: Ask date (today by default) and show all issues and each one's actions listed from the most to least popular. This is necessary for suggesting actions.
Show today's issue: Ask nothing. Show today's top-ranked issue and its two top-ranked actions. [Calculate the sum of results over all users. Show these popularity sums as the result of object popularity? Select the most popular row among a group defined by an index; use oapply to integrate over the index using which.max and pick that row only. Should this be a function or ovariable?]
Suggest actions: Ask date, issue, action and description from user. Date is today by default. Ts and user come as previously. If the date-issue pair does not exist in Issues table, give error message. Upload data to Actions and user's bonus to Action vote.
Vote for issue: Ask the rank number of the issue as a number. The user can check the numbers with Show issues. Date, user, and ts come automatically. Do firstuser. Votes is the number of user's bonuses and comes from Bonuses. Upload data to Issue vote. Store information about the rank before voting somewhere (as an ovariable or a technical data table?). If the information has changed from the last time, give bonus to the user whose information is now on the top.
Vote for action: Similar to vote for issue, except that the action number is asked and data is uploaded to Action vote.
Make decision: Ask the action from the two top choices of the most popular issue using a drop-down list. The options can be seen with show today's issue. Upload data to Decisions. However, if an issue was the most popular at some point during the day, it is still kept in the issue list. ----#: . Is it? How? --Jouni (talk) 17:21, 7 February 2016 (UTC) (type: truth; paradigms: science: comment)
Evaluate happiness: Ask date (today is the default), action number from show issues for that date, and hscore for happiness score in the user's own group. Ts, user as previously. Check if user has a group in Users and if not, give an error message to sign up to a group first. Upload data to Happiness.
Evaluate values: As evaluate happiness, except that unlike group, the value is asked from the user and nothing is checked. Upload data to Values.
Manage profile: Ask the group to which user identifies themselves. Take user and ts as previously. Add data to Users.
Show results: This code is divided into several parts:
- Show happiness performance: Ask nothing. From Decisions, take the action of each day; do this separately for You, the user's own decisions, and Crowd, i.e. the most popular action of each day. Combine that with the happiness scores from Happiness. Show cumulative happiness across time for both decision makers.
- Show value performance: Similar to show happiness performance, but for values from Values. It is imprtant to notice that value scores for each action are only partly a matter of opinion and partly a matter of research. Therefore, ideas should be developed how this research is gathered and used.
- Show situation': Show the situation of the current issue: the issue and description, and the two actions and their votes.
- Show all issues: Show all issues and actions and their votes for today.

How to make ovariables from the data tables? Dependencies: user, todate. In the ovariable formula, do the following.

issues <- Ovariable("issues", 
	dependencies = data.frame(Name = c("user", "todate")),
	formula = function(...) {
		out <- createova(dat = "Op_en7421.issues", addindex = "Issues")
		return(out)
	}
)

The function createova does something like this:

Create a temporary ovariable temp and fetch the respective table with ddata.
indices that are used to find unique rows: uncolumns <- c("Date", "Issue", "Action", "User", "Value", "Group", "Reason")
However, take away the index that is being added: Issue (for Issue vote and Issues); Action (for Action vote and Actions). None for other tables.
uncolumns <- uncolumns[!uncolumns %in% addindex]
indices that are transformed to Result: rescolumns <- c("Ivotes", "Avotes", "Bonus", "Vscore", "Hscore")
Do oapply(temp, INDEX = uncolumns, FUN = which.max) to find unique rows. Bring Description and other columns back.
Do colnames(temp@output)[colnames(temp@output) %in% rescolumns] <- "Result" to make the right result column.
if(!"Result" %in% colnames(temp@output)) temp$Result <- 1
return(temp)

**Important categories**
Groups for Turkey	Value categories
Nationalists Conservatives Minorities Liberals Kemalists	Civil Rights Women's Rights Religion National Values Democracy

Keywords

References

Related files

@@ Line 344: / Line 344: @@
 </rcode>
-=== Structure and functionalities ===
-[[File:Great game data structure.png|thumb|450px|Data structure of the great game. Each blue box is a data table. Arrows show the information flows. Happiness and value performances are calculated based on decisions and scores estimated by the players (or researchers?). ''Upload data'' and ''select newest'' are generic functions needed to operate with the data.]]
-The content of and use of the data tables is the following:
-* '''Issues''': List of decisions to be made. A user can suggest only one issue per day. For each day, the most popular issue is taken to the game.
-* '''Actions''': List of decision options to be made. A user can suggest only one action per issue. For each time point, two most popular actions are taken to the game. However, the actions in the game may change during the day, if the rank of the issues changes.
-* '''Issue vote''': List of votes for each issue. Each user can cast a single vote either for or against an issue. The number of votes a user has equals their bonuses.
-* '''Action vote''': List of votes for each action under issues. The voting system is the same as for issues.
-* '''Decisions''': List of decisions each user makes from the actions and issues on the game.
-* '''Bonuses''': List of bonuses the users have earned during the game. In the beginning, each user has 1 bonus. You can earn bonuses if your actions suggestions gets to be played (+1) or if your issues gets to be played (+5). Every time a user makes a decision, they get +0.1 bonus.
-* '''Happiness''': Users' opinions about how much happiness an action brings to their own group.
-* '''Values''': Users' opinions about how much value an action brings to a selected group.
-* '''Users''': List of users' groups (i.e. to which group each user identifies themselves).
-The functions needed are the following.
-* '''Upload data''': Take the data provided by the user or calculated. Add automatic fields, e.g. ts, user and date. Upload data to the respective table.
-* '''Create ovariable''': Download data from a table. Find unique entries (e.g. if the user can make only one decision per day, find the user's newest decision and discard older ones. Then create an ovariable with the structure needed.
-* '''Uniques''': From a data.frame, find the unique rows with a given condition (e.g. discard previous decisions made by a user previously on the same day).
-* '''Firstuser''': Check's whether user's wiki_username is found from ''Bonuses''. If not, it is added there and 1 bonus given.
-The interface codes used are the following:
-* '''Suggest issues''': Ask date, issue and description from user. Date means the date when this issue will be played. Default is today, but user can change that and suggest future issues. Timestamp (ts) come automatically. User is the wiki_username. Upload data to Issues table. No need to check previous entries.
-* '''Show issues''': Ask date (today by default) and show all issues and each one's actions listed from the most to least popular. This is necessary for suggesting actions.
-* '''Show today's issue''': Ask nothing. Show today's top-ranked issue and its two top-ranked actions. Store this information somewhere (as an ovariable or a technical data table?). If the information has changed from the last time. give bonus to the user's whose information is now on the top. {{comment|# |Or should this be done after a vote?|--[[User:Jouni|Jouni]] ([[User talk:Jouni|talk]]) 12:18, 7 February 2016 (UTC)}}
-* '''Suggest actions''': Ask date, issue, action and description from user. Date is today by default. Ts and user come as previously. If the date-issue pair does not exist in Issues table, give error message. Upload data to Actions.
-* '''Vote for issue''': Ask the rank number of the issue as a number. The user can check the numbers with ''Show issues''. Date, user, and ts come automatically. Do ''firstuser''. Votes is the number of user's bonuses and comes from ''Bonuses''. Upload data to ''Issue vote''.
-* '''Vote for action''': Similar to ''vote for issue'', except that the action number is asked and data is uploaded to ''Action vote''.
-* '''Make decision''': Ask the action from the two top choices using a drop-down list. The options can be seen with ''show today's issue''. Upload data to ''Decisions''.
-* '''Evaluate happiness''': Ask date (today is the default), action number from ''show issues'' for that date, and hscore for happiness score in the user's own group. Ts, user as previously. Check if user has a group in ''Users'' and if not, give an error message to sign up to a group first. Upload data to ''Happiness''.
-* '''Evaluate values''': As evaluate happiness, except that unlike group, the value is asked from the user and nothing is checked. Upload data to ''Values''.
-* '''Show results''': This code is divided into several parts:
-** '''Show happiness performance''': Ask nothing. From ''Decisions'', take the action of each day; do this separately for the user's own decisions, and the Group, i.e. the most popular action of each day. Combine that with the happiness scores from ''Happiness''. Show cumulative happiness across time for both decision makers.
-** '''Show value performance''': Similar to show happiness performance, but for values from ''Values''.
-* '''Manage profile''': Ask the group to which user identifies themselves. Take user and ts as previously. Add data to ''Users''.
-You want to find the most popular choice. First, take the last vote of each person. Then calculate the sum of results over all users. Show these popularity sums as the result of object popularity? Select the most popular row among a group defined by an index; use oapply to integrate over the index using which.max and pick that row only. Should this be a function or ovariable?
-* Make a new index where You contains your answers and Crowd contains the most popular vote of everyone.
-* Show cumulative scores for happiness and values along time.
-** What the scores for each action are, is only partly a matter of opinion and partly a matter of research.
-* Rename terms: problem -> issue, option -> action, progress -> value
-* Only pick the most popular issue for decision. However, if an issue was the most popular at some point during the day, it is still kept in the issue list.
-* Only pick two main actions for decision.
-* Interface for both issue and action, where the latter depends on the former.
-** Show current issues in the order of popularity.
-** Ask for new issues. Fields: issue, description, date (automatic). Keep it simple.
-** Show current issues and their actions in order of popularity.
-** Ask for new actions. Fields: action, description, date.(?) Issue is ovariable with formula issue * action. (?)
-* How Bonus accumulates
-** Bonus is gathered when action is selected (1 bonus) to be voted. 5 bonus is gathered when your issue is selected.
-** This goes to Points table. The amount of points is your starting vote for your issue or action. When someone votes your issue or action you get points.
-** Person's bonus points are used as the starting point for votes.
-Add a table about person's points.
-Add Iscore to Question vote and Ascore to Option score. When a person votes, their bonus score is used.
-Interface for both issues and actions.
@@ Line 505: / Line 446: @@
 </rcode>
-{| {{prettytable}}
+=== Structure and functionalities ===
-|+'''Structures of the tables.
-! Issues || Actions || Happiness || Values || Issue vote || Action vote || User || Bonus
+[[File:Great game data structure.png|thumb|450px|Data structure of the great game. Each blue box is a data table. Arrows show the information flows. Happiness and value performances are calculated based on decisions and scores estimated by the players (or researchers?). ''Upload data'' and ''select newest'' are generic functions needed to operate with the data.]]
-|- style="vertical-align:top;"
+The content of and use of the data tables is the following:
-|
+* '''Issues''': List of decisions to be made. A user can suggest only one issue per day. For each day, the most popular issue is taken to the game.
-* Date
+* '''Actions''': List of decision options to be made. A user can suggest only one action per issue. For each time point, two most popular actions are taken to the game. However, the actions in the game may change during the day, if the rank of the issues changes.
-* Issue
+* '''Issue vote''': List of votes for each issue. Each user can cast a single vote either for or against an issue. The number of votes a user has equals their bonuses.
-* Description
+* '''Action vote''': List of votes for each action under issues. The voting system is the same as for issues.
-* Option(?)
+* '''Decisions''': List of decisions each user makes from the actions and issues on the game.
-|
+* '''Bonuses''': List of bonuses the users have earned during the game. In the beginning, each user has 1 bonus. You can earn bonuses if your actions suggestions gets to be played (+1) or if your issues gets to be played (+5). Every time a user makes a decision, they get +0.1 bonus.
-* Issue
+* '''Happiness''': Users' opinions about how much happiness an action brings to their own group.
-* User
+* '''Values''': Users' opinions about how much value an action brings to a selected group.
-* Action
+* '''Users''': List of users' groups (i.e. to which group each user identifies themselves).
-|
-* Issue
+The functions needed are the following.
-* Action
+* '''Upload data''': Take the data provided by the user or calculated. Add automatic fields, e.g. ts, user and date. Upload data to the respective table.
-* Group
+* '''Create ovariable''': Download data from a table.  From the data, find the unique rows with a given condition (e.g. discard previous decisions made by a user previously on the same day). Then create an ovariable with the structure needed.
-* User
+* '''Firstuser''': Check's whether user's wiki_username is found from ''Bonuses''. If not, it is added there and 1 bonus given.
-* Hscore
-|
+The interface codes used are the following:
-* Issue
+* '''Suggest issues''': Ask date, issue and description from user. Date means the date when this issue will be played. Default is today, but user can change that and suggest future issues. Timestamp (ts) come automatically. User is the wiki_username. Upload data to ''Issues table''. No need to check previous entries. Upload user's bonus to ''Issue vote'' as number of votes.
-* Action
+* '''Show issues''': Ask date (today by default) and show all issues and each one's actions listed from the most to least popular. This is necessary for suggesting actions.
-* Value
+* '''Show today's issue''': Ask nothing. Show today's top-ranked issue and its two top-ranked actions. [Calculate the sum of results over all users. Show these popularity sums as the result of object popularity? Select the most popular row among a group defined by an index; use oapply to integrate over the index using which.max and pick that row only. Should this be a function or ovariable?]
-* User
+* '''Suggest actions''': Ask date, issue, action and description from user. Date is today by default. Ts and user come as previously. If the date-issue pair does not exist in Issues table, give error message. Upload data to ''Actions'' and user's bonus to ''Action vote''.
-* Vscore
+* '''Vote for issue''': Ask the rank number of the issue as a number. The user can check the numbers with ''Show issues''. Date, user, and ts come automatically. Do ''firstuser''. Votes is the number of user's bonuses and comes from ''Bonuses''. Upload data to ''Issue vote''. Store information about the rank before voting somewhere (as an ovariable or a technical data table?). If the information has changed from the last time, give bonus to the user whose information is now on the top.
-|
+* '''Vote for action''': Similar to ''vote for issue'', except that the action number is asked and data is uploaded to ''Action vote''.
-* Date
+* '''Make decision''': Ask the action from the two top choices of the most popular issue using a drop-down list. The options can be seen with ''show today's issue''. Upload data to ''Decisions''.  However, if an issue was the most popular at some point during the day, it is still kept in the issue list. {{comment|# |Is it? How?|--[[User:Jouni|Jouni]] ([[User talk:Jouni|talk]]) 17:21, 7 February 2016 (UTC)}}
-* User
+* '''Evaluate happiness''': Ask date (today is the default), action number from ''show issues'' for that date, and hscore for happiness score in the user's own group. Ts, user as previously. Check if user has a group in ''Users'' and if not, give an error message to sign up to a group first. Upload data to ''Happiness''.
-* Issue
+* '''Evaluate values''': As evaluate happiness, except that unlike group, the value is asked from the user and nothing is checked. Upload data to ''Values''.
-|
+* '''Manage profile''': Ask the group to which user identifies themselves. Take user and ts as previously. Add data to ''Users''.
-* Issue
+* '''Show results''': This code is divided into several parts:
-* User
+** '''Show happiness performance''': Ask nothing. From ''Decisions'', take the action of each day; do this separately for ''You'', the user's own decisions, and ''Crowd'', i.e. the most popular action of each day. Combine that with the happiness scores from ''Happiness''. Show cumulative happiness across time for both decision makers.
-* Action
+** '''Show value performance''': Similar to show happiness performance, but for values from ''Values''. It is imprtant to notice that value scores for each action are only partly a matter of opinion and partly a matter of research. Therefore, ideas should be developed how this research is gathered and used.
-|
+** ''Show situation''': Show the situation of the current issue: the issue and description, and the two actions and their votes.
-* User
+** '''Show all issues''': Show all issues and actions and their votes for today.
-* Date
-* Group
+How to make ovariables from the data tables? Dependencies: user, todate. In the ovariable formula, do the following.
-|
+ issues <- Ovariable("issues",
-* Date
+ 	dependencies = data.frame(Name = c("user", "todate")),
-* User
+ 	formula = function(...) {
-* Reason
+ 		out <- createova(dat = "Op_en7421.issues", addindex = "Issues")
-* Bonus
+ 		return(out)
-|}
+ 	}
+ )
+The function createova does something like this:
+ Create a temporary ovariable temp and fetch the respective table with ddata.
+ indices that are used to find unique rows: uncolumns <- c("Date", "Issue", "Action", "User", "Value", "Group", "Reason")
+ However, take away the index that is being added: Issue (for Issue vote and Issues); Action (for Action vote and Actions). None for other tables.
+ uncolumns <- uncolumns[!uncolumns %in% addindex]
+ indices that are transformed to Result: rescolumns <- c("Ivotes", "Avotes", "Bonus", "Vscore", "Hscore")
+ Do oapply(temp, INDEX = uncolumns, FUN = which.max) to find unique rows. Bring Description and other columns back.
+ Do colnames(temp@output)[colnames(temp@output) %in% rescolumns] <- "Result" to make the right result column.
+ if(!"Result" %in% colnames(temp@output)) temp$Result <- 1
+ return(temp)
 {| {{prettytable}}

Great game of Turkey: Difference between revisions

Revision as of 17:21, 7 February 2016

Contents

Question

Answer

Rationale

Calculations

Structure and functionalities

See also

Keywords

References

Related files

Navigation menu

This page is a knowledge crystal of subtype assessment. The page identifier is Op_en7421
Moderator:Jouni (see all)

Upload data {{#opasnet_base_link:Op_en7421}}