{"action":"created","issue":{"url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/issues/112","labels_url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/issues/112/labels{/name}","comments_url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/issues/112/comments","events_url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/issues/112/events","html_url":"https://github.com/RoboCupAtHome/RuleBook/issues/112","id":95346111,"number":112,"title":"Idea: make all/some challenges GPSR","user":{"login":"LoyVanBeek","id":709259,"avatar_url":"https://avatars.githubusercontent.com/u/709259?v=3","gravatar_id":"","url":"https://api.github.com/users/LoyVanBeek","html_url":"https://github.com/LoyVanBeek","followers_url":"https://api.github.com/users/LoyVanBeek/followers","following_url":"https://api.github.com/users/LoyVanBeek/following{/other_user}","gists_url":"https://api.github.com/users/LoyVanBeek/gists{/gist_id}","starred_url":"https://api.github.com/users/LoyVanBeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LoyVanBeek/subscriptions","organizations_url":"https://api.github.com/users/LoyVanBeek/orgs","repos_url":"https://api.github.com/users/LoyVanBeek/repos","events_url":"https://api.github.com/users/LoyVanBeek/events{/privacy}","received_events_url":"https://api.github.com/users/LoyVanBeek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/labels/General%20Rules","name":"General Rules","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/milestones/3","html_url":"https://github.com/RoboCupAtHome/RuleBook/milestones/Leipzig%202016","labels_url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/milestones/3/labels","id":1080397,"number":3,"title":"Leipzig 2016","description":"TC MUST have a draft ready before November 1st, 2015 so it can be tested on the Japanese Camp in december.","creator":{"login":"LoyVanBeek","id":709259,"avatar_url":"https://avatars.githubusercontent.com/u/709259?v=3","gravatar_id":"","url":"https://api.github.com/users/LoyVanBeek","html_url":"https://github.com/LoyVanBeek","followers_url":"https://api.github.com/users/LoyVanBeek/followers","following_url":"https://api.github.com/users/LoyVanBeek/following{/other_user}","gists_url":"https://api.github.com/users/LoyVanBeek/gists{/gist_id}","starred_url":"https://api.github.com/users/LoyVanBeek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/LoyVanBeek/subscriptions","organizations_url":"https://api.github.com/users/LoyVanBeek/orgs","repos_url":"https://api.github.com/users/LoyVanBeek/repos","events_url":"https://api.github.com/users/LoyVanBeek/events{/privacy}","received_events_url":"https://api.github.com/users/LoyVanBeek/received_events","type":"User","site_admin":false},"open_issues":12,"closed_issues":0,"state":"open","created_at":"2015-04-23T10:51:59Z","updated_at":"2015-07-16T04:12:34Z","due_on":"2015-10-31T23:00:00Z","closed_at":null},"comments":1,"created_at":"2015-07-16T04:12:24Z","updated_at":"2015-07-19T18:11:47Z","closed_at":null,"body":"For stage 1, this should be simple, because GPSR is all stage-1 abilities integrated. \r\nStage-2 challenges can be defined as a spoken command to the robot. \r\nFor example, the restaurant-challenge can be commanded to the robot as:\r\n- \"Follow me\"\r\n- \"Stop\"\r\n- \"Remember that this location is table N\"\r\n- \"Follow me\" \r\n- repeat\r\n- \"Remember that this location is the kitchen\r\n- \"Go to table 1 and ask for an order\"\r\n- \"Bring me a coke and hamburger\" (the robot should know that food and beverages can be obtained from a kitchen and look there)\r\n- repeat"},"comment":{"url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/issues/comments/122689588","html_url":"https://github.com/RoboCupAtHome/RuleBook/issues/112#issuecomment-122689588","issue_url":"https://api.github.com/repos/RoboCupAtHome/RuleBook/issues/112","id":122689588,"user":{"login":"balkce","id":7661882,"avatar_url":"https://avatars.githubusercontent.com/u/7661882?v=3","gravatar_id":"","url":"https://api.github.com/users/balkce","html_url":"https://github.com/balkce","followers_url":"https://api.github.com/users/balkce/followers","following_url":"https://api.github.com/users/balkce/following{/other_user}","gists_url":"https://api.github.com/users/balkce/gists{/gist_id}","starred_url":"https://api.github.com/users/balkce/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/balkce/subscriptions","organizations_url":"https://api.github.com/users/balkce/orgs","repos_url":"https://api.github.com/users/balkce/repos","events_url":"https://api.github.com/users/balkce/events{/privacy}","received_events_url":"https://api.github.com/users/balkce/received_events","type":"User","site_admin":false},"created_at":"2015-07-19T18:11:47Z","updated_at":"2015-07-19T18:11:47Z","body":"@LoyVanBeek idea of an audience member giving commands has been considered in past years as \"non-expert users\" in pretty much that same line of thought (even to the point of testing natural interaction). However, if I remember correctly, the main issues were that:\r\n\r\n1.- The audience member may end up being as fluent as a team member, providing unfair extra points.\r\n2.- The audience selection process adds complexity to an already complex logistic.\r\n3.- The randomness may end up providing non-uniformity to the grading to teams.\r\n\r\nHaving said all this, I do agree with the arguments of good PR (with good TC/team supervision) and the fact that audience will be engaged to a \"boring\" test. I welcome this discussion.\r\n\r\nAs for the original comment, I thought about it and my primary issue with it would be that every test would require ASR to be carried out, which, when considering past performances, may end up hindering teams (to the point of not getting to the parts of the test we're interested in benchmarking). However, I would agree to this idea only if we see a good ASR performance in the vast majority of the teams this year, such that ASR is considered an essential functionality for next year to the point of not even warranting its evaluation."}}