From assadn at yahoo.com Wed Jan 9 02:58:39 2013 From: assadn at yahoo.com (Asad Norouzi) Date: Tue, 8 Jan 2013 23:58:39 -0800 (PST) Subject: [robocup-small] 2nd Call For Participation: RoboCup IranOpen 2013 Message-ID: <1357718319.87543.YahooMailNeo@web122003.mail.ne1.yahoo.com> ******************************* Apologies for duplicate messages **************************** ########################### Call For Participation ########################## ??? ??? ??? ??? ??? ??? ??? ??? ? The 8th RoboCup IranOpen Competitions ??? ??? ??? ??? ??? ??? ??? ??? ????? ??? ??? ? ??03- 7 April 2013 ??? ??? ??? ??? ??? ??? ??? ??? ????? ??? ??? ??? ? Tehran, Iran ??? ??? ??? ??? ??? ??? ??? ??? ????? ??? ??? http://2013.iranopen.ir ##########################? RoboCup IranOpen 2013 ######################## The 8th RoboCup IranOpen competitions will be held in Tehran on April 3-7, 2013. Having had the experience of 7 years successful organization of these competitions, we look forward to an even more glorious event with more teams competing in this major robotics event from all over the world. Last year we, gladly, had 330 teams from China, Czech Republic, Germany, Greece, India, Iran, Mexico, The Netherlands, Pakistan, Portugal, Turkey, United Kingdom, and United States. ? RoboCup IranOpen is an attempt to further promote AI and Robotics research. These competitions will provide a chance for all researchers to present and share their experiences and achievements. The RoboCup IranOpen 2013 competitions leagues are as follows: - Humanoid - Middle Size - Small Size - Standard Platform - Soccer 3D Simulation - Soccer 2D Simulation - Rescue Robot - Rescue Simulation - RoboCup at Home - Junior Soccer A Open Weight - Junior Soccer B Open Weight - Junior Soccer B Light Weight - Junior Rescue A Primary - Junior Rescue A Secondary - Junior Rescue B - Junior CoSpace Rescue The RoboCup IranOpen 2013 competitions extra leagues which are not among the official RoboCup leagues: - Deminer Autonomous - Deminer Manual - Deminer Technical Challenge - Senior Demo - Junior Demo Primary - Junior Demo Secondary - IranOpenROV (Radio Operated Vehicles - underwater robots) - IranOpenUAV (Unmanned Aerial Vehicles) Participation: All teams are required to pre-register through the online form available in the website. The pre-registered teams should then submit the relevant qualification materials. Last year 367 teams were qualified from 1000 pre-registered teams. Important dates: Pre-Registration: November 06, 2012 - February 03, 2013 Submission of qualification materials: December 05, 2012 - February 03, 2013 Qualification: February 03 - 28, 2013 Registration: February 03 - March 18, 2013 Teams Setup: April 03 - 04, 2013 Competitions: April 05 - 07, 2013 For further information please visit our official website at http://2013.iranopen.ir For enquiries please contact us via the hereunder email addresses: General Enquiries: info at iranopen.ir Registration: registration at iranopen.ir Visa & International Affairs: visa at iranopen.ir Travel Support: asadollah_norouzi at sp.edu.sg Regards On behalf of, Iranian RoboCup National Committee RoboCup IranOpen 2013 Organizing Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Sun Jan 13 18:03:21 2013 From: chead at chead.ca (Christopher Head) Date: Sun, 13 Jan 2013 15:03:21 -0800 Subject: [robocup-small] Planned Rule Changes Message-ID: <20130113150321.4f324c08@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hello teams! Your technical committee (with some input from the OC as well) has just finished planning what rules we?ll be changing for RoboCup 2013. Here?s what we?re planning on doing: Yellow card rules are a little bit ambiguous as written in the rulebook. How we have always played at RoboCup has been that each yellow card reduces the maximum team size by one, no matter how many robots are on the field or how many robots a team has available to use. Which specific robot committed the violation was not important. We determined that given: (1) how interchangeable different robots from the same team are, (2) that teams have different levels of hardware reliability and resources and might want to bring different numbers of robots to the field for a game, and (3) that a team playing with fewer than the maximum number of robots is already at a disadvantage, the current rules are appropriate. While it is slightly unfair that a team voluntarily playing with fewer robots is not punished for receiving a yellow card, we feel that any other possible solution is even more unfair, so what we have is the best answer. We will be updating the wording in the rulebook to reflect this. Some teams asked for video review of referee calls. Because we do not yet have good, tested infrastructure, it would be too soon to put this in the rules. We would like to test out video review systems at RoboCup 2013 and may consider rule changes further in the future. For now, remember that use of tools to help with refereeing is at the referee?s discretion, so if a referee would like to check calls using a video review tool, (s)he is welcome to do that. Lots of teams also asked for ball speed measurement. We?d like to see this operational for RoboCup 2013, but again, this can be deployed via referee?s discretion. We don?t think there?s any need for it to go in the rules. The rules say what?s allowed (ball speed up to 8 m/s); how the referee enforces that should be up to them, as long as it?s fair. The chip goal rules are incredibly complicated, possibly contradictory, and probably ambiguous as written. Furthermore, while strict limits on chip goals probably made sense back when they were written, when chipping was a distinct technical advantage, today, with most teams having chippers, strict rules are probably not so necessary. We have not decided exactly what our rules around chip goals will be yet. We will probably have some limits, but they will be much simpler. We will announce the new rules as soon as possible. Some teams had complaints about the lack of progress in ten seconds rule. We believe the rule is appropriate and unambiguous, but we will reword it to be more clear. The rule is, was, and will be: if ten seconds pass with no progress, the REFEREE may call a stoppage in play for no progress and then order a force start. The opposing team may go for the ball after the force start, but NOT before. If the opposing team goes for the ball before the referee calls force start, even if ten seconds have passed with no apparent progress, that team is in violation. There were some problems with the two defenders rule. We feel the two defenders rule is too subjective and, because the punishment is quite severe, can result in a lot of arguments. We will be considering more objective metrics for when to make and when not to make a two defenders call; again, we will announce the new rules as soon as possible. Thanks! Chris (SSL TC chair) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEAREDAAYFAlDzPTkACgkQXUF6hOTGP7cbvACggxfB9hP8DVXXb8+IY0hOYVRD XWIAoJZ4FktiBKU8cBotdurp0lMUAV8H =J+RN -----END PGP SIGNATURE----- From jgurzoni at yahoo.com.br Wed Jan 23 09:12:53 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Wed, 23 Jan 2013 12:12:53 -0200 Subject: [robocup-small] Call for Papers - RoboCup International Symposium 2013 Message-ID: <019f01cdf973$bd52ae00$37f80a00$@yahoo.com.br> ******************************************************************** Call for Papers RoboCup International Symposium 2013 Eindhoven, The Netherlands July 1st, 2012 http://www.robocup2013.org/ ******************************************************************** OVERVIEW The 17th annual RoboCup International Symposium will be held in conjunction with RoboCup 2013 (June 24-30). The Symposium represents the core meeting for presentation and discussion of scientific contributions to a variety of research areas related to all RoboCup divisions (RoboCupSoccer, RoboCupRescue, RoboCup at Home, RoboCup at Work and RoboCupJunior). Its scope encompasses, but is not restricted to, research and educational activities within the fields of Robotics and Artificial Intelligence. Due to its interdisciplinary nature, the symposium offers a unique venue for exploring various and intimate connections of theory and practice across a wide spectrum of research fields. The experimental, interactive, and benchmark character of the RoboCup initiative presents the opportunity to disseminate novel ideas and promising technologies, which are rapidly adopted and field-tested by a large (and still growing) community. SUBMISSION We solicit submissions of papers reporting on high-quality, original research with relevance to the areas mentioned below. All researchers working in these areas, even if not actively participating in RoboCup teams, are urged to submit their work. Both papers describing real-world research and papers reporting theoretical results, as well as combinations thereof, are welcome. We also encourage the submission of high-quality overview articles for any field related to the general scope of RoboCup. The proceedings of the RoboCup International Symposium are published and archived within the Springer-Verlag Lecture Notes in Artificial Intelligence (LNAI) series. Submitted papers are limited to 12 pages formatted according to the LNAI requirements (http://www.springer.com/series/1244) and must be electronically submitted through the symposium web site: https://www.easychair.org/conferences/?conf=robocupsymposium2013 All contributions are peer-reviewed by at least three reviewers using a blind review process. NEW TRACK To encourage open-source releases of hard- and software components, a special track on open-source developments will be included in the 2013 RoboCup International Symposium. Contributions to this track are limited to eight pages, formatted according to LNAI requirements. They should include evidence of impact of the released component to the RoboCup community. Review of these contributions will be based on technical contribution and benefit for the RoboCup community. IMPORTANT DATES * Submission of full papers: March 1, 2013 * Notification to authors: April 14, 2013 * Submission of camera-ready copies: April 29, 2013 * RoboCup 2013 Symposium: July 1st, 2013 SYMPOSIUM CO-CHAIRS * Sven Behnke, University of Bonn * Manuela Veloso, Carnegie Mellon University * Arnoud Visser, Universiteit van Amsterdam * Rong Xiong, Zhejiang University AREAS OF INTEREST * Robot Hardware and Software - mobile and humanoid robots - sensors and actuators - embedded and mobile devices - robot construction and new materials - robotic system integration - robot software architectures - robot programming environments and languages - real-time and concurrent programming - robot simulators * Perception and Action - distributed sensor integration - sensor noise filtering - real-time image processing and pattern recognition - motion and sensor models - sensory-motor control - robot kinematics and dynamics - high-dimensional motion control * Robotic Cognition and Learning - world modeling - localization, navigation, and mapping - planning and reasoning - decision making under uncertainty - reinforcement learning - complex motor skill acquisition - motion and sensor model learning * Multi-Robot Systems - team coordination methods - communication protocols - learning and adaptive systems - teamwork and heterogeneous agents - dynamic resource allocation - adjustable autonomy * Human-Robot Interaction - human-robot interfaces - speech synthesis and natural language generation - visualization - emotion recognition - human's intent cognition - affect detection and synthesis - robot response to external disturbances - safety and dependability * Education and Edutainment - Robotics and Artificial Intelligence education - educational robotics - robot kits and programming tools - robotic entertainment * Applications - disaster rescue information systems - search and rescue robots - robotic surveillance - service and social robots - robots at home Regards on behalf of the symposium co-chairs Manuala Veloso, Rong Xiong, Sven Behnke and Arnoud Visser Email:robocupsymposium2013 at easychair.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Fri Jan 25 22:44:34 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Sat, 26 Jan 2013 01:44:34 -0200 Subject: [robocup-small] Reminder: Pre-Registration for RoboCup 2013 - deadline Jan 31 Message-ID: <000001cdfb77$7701a950$6504fbf0$@yahoo.com.br> Greetings to everybody ! We would like to remind teams of the approaching deadline to pre-register for RoboCup 2013 SSL competition. Pre-Registration Procedure - to be completed before January 31st, 23:59 GMT+1 Submit by email to organizing committee( rc-ssl-oc at lists.robocup.org ). The email should contain the following information: * Team Name * Country * University * Main contact & Email of main contact * Team Website( If you have one ) The email subject should be : 2013 Participation Intent( your team name ). The details of the qualification procedure is posted on the league wiki, http://robocupssl.cpe.ku.ac.th/robocup2013:qualification . The list of currently registered teams is also available, at http://robocupssl.cpe.ku.ac.th/robocup2013:teams Best Regards Angelo Gurzoni Jr On behalf of the SSL Committees for RoboCup Netherlands 2013. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dannyz at cs.cmu.edu Fri Feb 8 16:45:04 2013 From: dannyz at cs.cmu.edu (Danny Zhu) Date: Fri, 08 Feb 2013 16:45:04 -0500 Subject: [robocup-small] RoboCup 2012 SSL-Vision logs Message-ID: <511571E0.5020800@cs.cmu.edu> Hello all, I'm a graduate student and member of CMDragons, and I'm hoping to analyze the RoboCup 2012 games as part of my research. Is there anyone who could provide me with the SSL-Vision logs for those games? Thanks, Danny From jgurzoni at yahoo.com.br Tue Feb 12 21:27:25 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Wed, 13 Feb 2013 00:27:25 -0200 Subject: [robocup-small] FW: RoboCup 2013 Eindhoven, the Netherlands [Newsletter #1] Message-ID: <001701ce0991$aa69ee60$ff3dcb20$@yahoo.com.br> From: Roel Merry chair at robocup2013.org Sent: Tuesday, February 12, 2013 5:06 PM To: Info RoboCup 2013 Subject: [Rc-ssl-oc] RoboCup 2013 Eindhoven, the Netherlands [Newsletter #1] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 96826 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.emz Type: application/octet-stream Size: 48974 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.jpg Type: image/jpeg Size: 11534 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.emz Type: application/octet-stream Size: 48974 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 98349 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RoboCup 2013 Eindhoven, the Netherlands [Newsletter #1].pdf Type: application/pdf Size: 92788 bytes Desc: not available URL: From zhyaic at gmail.com Mon Feb 25 09:58:00 2013 From: zhyaic at gmail.com (Yue Zhao) Date: Mon, 25 Feb 2013 22:58:00 +0800 Subject: [robocup-small] 2013 Qualification Video (ZJUNlict) Message-ID: This is ZJUNlict's Qualification Video for RoboCup 2013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhyaic at gmail.com Mon Feb 25 10:00:06 2013 From: zhyaic at gmail.com (Yue Zhao) Date: Mon, 25 Feb 2013 23:00:06 +0800 Subject: [robocup-small] 2013 Qualification Video (ZJUNlict) Message-ID: This is ZJUNlict's Qualification Video for RobotCup 2013 Website:http://www.nlict.zju.edu.cn/ssl/WelcomePage.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From sugi at toyota-ct.ac.jp Wed Feb 27 01:30:09 2013 From: sugi at toyota-ct.ac.jp (Toko Sugiura) Date: Wed, 27 Feb 2013 15:30:09 +0900 Subject: [robocup-small] 2013 Qualification Video (KIKS) In-Reply-To: References: Message-ID: <201302271530.EIE69462.HJVT@toyota-ct.ac.jp> Dear all, Here is KIKS' qualification video for RobotCup 2013 URL:http://www.ee.toyota-ct.ac.jp/~sugi/KIKS2013Qualification. wmv or http://www.ee.toyota-ct.ac.jp/~sugi/RoboCup.html Best Regards, Toko Sugiura, KIKS _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ Toko Sugiura, Prof. Depart. of Electrical and Electronic Eng., Toyota National College of Technology 2-1 Eisei-cho, Toyota Aichi 471-8525, Japan Phone +81-565-36-5847 Fax. +81-565-36-5845 e-mail: sugi at toyota-ct.ac.jp _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ From liulisa at mit.edu Wed Feb 27 02:06:12 2013 From: liulisa at mit.edu (Lisa Liu) Date: Wed, 27 Feb 2013 02:06:12 -0500 Subject: [robocup-small] 2013 Qualification Video (RFC Cambridge) Message-ID: RFC Cambridge's 2013 Qualification Video: -- Dropbox: http://dl.dropbox.com/u/5319360/2013_TQV_RFC_Cambridge.mp4 -- Youtube: http://www.youtube.com/watch?v=GKZiTRdS2Gc -------------- next part -------------- An HTML attachment was scrubbed... URL: From andre at global-mainframe.com Wed Feb 27 08:54:34 2013 From: andre at global-mainframe.com (Andre Ryll) Date: Wed, 27 Feb 2013 14:54:34 +0100 Subject: [robocup-small] 2013 Qualification Video (TIGERS Mannheim) Message-ID: <512E101A.8070306@global-mainframe.com> Dear all, our qualification video, which is a mix of scenes from Robocup 2012 in Mexico, can be found online at: http://vimeo.com/44548363 Best regards, Andre Ryll, TIGERS Mannheim From saith_rodriguez at hotmail.com Wed Feb 27 12:07:20 2013 From: saith_rodriguez at hotmail.com (Carlos Saith Rodriguez) Date: Wed, 27 Feb 2013 12:07:20 -0500 Subject: [robocup-small] 2013 Qualification Video STOx's In-Reply-To: References: Message-ID: Dear all, Here is STOx's qualification video 2013. URL: http://www.stoxs.org/index.php/descargas Best Regards. Saith Rodr?guez Team Leader -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Wed Feb 27 21:51:57 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Wed, 27 Feb 2013 23:51:57 -0300 Subject: [robocup-small] FW: RoboCup International Symposium deadline extension Message-ID: <001701ce155e$94833920$bd89ab60$@yahoo.com.br> Dear all, The RoboCup Federation have decided to extend the deadline for submission to the RoboCup International Symposium 2013 in three weeks. Below the Call for papers with the new deadlines. ******************************************************************** Call for Papers RoboCup International Symposium 2013 Eindhoven, The Netherlands July 1st, 2012 http://www.robocup2013.org/ ******************************************************************** OVERVIEW The 17th annual RoboCup International Symposium will be held in conjunction with RoboCup 2013 (June 24-30). The Symposium represents the core meeting for presentation and discussion of scientific contributions to a variety of research areas related to all RoboCup divisions (RoboCupSoccer, RoboCupRescue, RoboCup at Home, RoboCup at Work and RoboCupJunior). Its scope encompasses, but is not restricted to, research and educational activities within the fields of Robotics and Artificial Intelligence. Due to its interdisciplinary nature, the symposium offers a unique venue for exploring various and intimate connections of theory and practice across a wide spectrum of research fields. The experimental, interactive, and benchmark character of the RoboCup initiative presents the opportunity to disseminate novel ideas and promising technologies, which are rapidly adopted and field-tested by a large (and still growing) community. SUBMISSION We solicit submissions of papers reporting on high-quality, original research with relevance to the areas mentioned below. All researchers working in these areas, even if not actively participating in RoboCup teams, are urged to submit their work. Both papers describing real-world research and papers reporting theoretical results, as well as combinations thereof, are welcome. We also encourage the submission of high-quality overview articles for any field related to the general scope of RoboCup. The proceedings of the RoboCup International Symposium are published and archived within the Springer-Verlag Lecture Notes in Artificial Intelligence (LNAI) series. Submitted papers are limited to 12 pages formatted according to the LNAI requirements (http://www.springer.com/series/1244) and must be electronically submitted through the symposium web site: https://www.easychair.org/conferences/?conf=robocupsymposium2013 All contributions are peer-reviewed by at least three reviewers using a blind review process. NEW TRACK To encourage open-source releases of hard- and software components, a special track on open-source developments will be included in the 2013 RoboCup International Symposium. Contributions to this track are limited to eight pages, formatted according to LNAI requirements. They should include evidence of impact of the released component to the RoboCup community. Review of these contributions will be based on technical contribution and benefit for the RoboCup community. We would like to have up to three open-source projects submission from each league. IMPORTANT DATES * Submission of full papers: March 22, 2013 * Notification to authors: April 28, 2013 * Submission of camera-ready copies: May 15, 2013 * RoboCup 2013 Symposium: July 1st, 2013 SYMPOSIUM CO-CHAIRS * Sven Behnke, University of Bonn * Manuela Veloso, Carnegie Mellon University * Arnoud Visser, Universiteit van Amsterdam * Rong Xiong, Zhejiang University AREAS OF INTEREST * Robot Hardware and Software - mobile and humanoid robots - sensors and actuators - embedded and mobile devices - robot construction and new materials - robotic system integration - robot software architectures - robot programming environments and languages - real-time and concurrent programming - robot simulators * Perception and Action - distributed sensor integration - sensor noise filtering - real-time image processing and pattern recognition - motion and sensor models - sensory-motor control - robot kinematics and dynamics - high-dimensional motion control * Robotic Cognition and Learning - world modeling - localization, navigation, and mapping - planning and reasoning - decision making under uncertainty - reinforcement learning - complex motor skill acquisition - motion and sensor model learning * Multi-Robot Systems - team coordination methods - communication protocols - learning and adaptive systems - teamwork and heterogeneous agents - dynamic resource allocation - adjustable autonomy * Human-Robot Interaction - human-robot interfaces - speech synthesis and natural language generation - visualization - emotion recognition - human's intent cognition - affect detection and synthesis - robot response to external disturbances - safety and dependability * Education and Edutainment - Robotics and Artificial Intelligence education - educational robotics - robot kits and programming tools - robotic entertainment * Applications - disaster rescue information systems - search and rescue robots - robotic surveillance - service and social robots - robots at home Regards on behalf of the symposium co-chairs Manuala Veloso, Rong Xiong, Sven Behnke and Arnoud Visser Email:robocupsymposium2013 at easychair.org _______________________________________________ rc-ssl-oc mailing list rc-ssl-oc at lists.robocup.org http://lists.robocup.org/listinfo.cgi/rc-ssl-oc-robocup.org From masutani at isc.osakac.ac.jp Wed Feb 27 23:08:09 2013 From: masutani at isc.osakac.ac.jp (MASUTANI Yasuhiro) Date: Thu, 28 Feb 2013 13:08:09 +0900 Subject: [robocup-small] 2013 Qualification Video (ODENS) Message-ID: <86txoxf5cm.wl%masutani@isc.osakac.ac.jp> Dear All, The following URL is the link to the qualification video of Team ODENS. http://www.youtube.com/watch?v=kAV2RzzftxU Sincerely yours, Yasuhiro Masutani Team ODENS Osaka Electro-Communication University Japan From k0tqr0_1116 at ybb.ne.jp Thu Feb 28 01:58:26 2013 From: k0tqr0_1116 at ybb.ne.jp (Kotaro Yasui) Date: Thu, 28 Feb 2013 15:58:26 +0900 Subject: [robocup-small] 2013 Qualification Video RoboDragons Message-ID: <001201ce1581$046e3920$0d4aab60$@ne.jp> Dear all, Here is the link to RoboDragons' 2013 qualification videos. http://www.ist.aichi-pu.ac.jp/lab/narulab/download_e.html Best regards, Kotaro Yasui -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikolausmitchell at gatech.edu Thu Feb 28 07:25:12 2013 From: nikolausmitchell at gatech.edu (Nikolaus Mitchell) Date: Thu, 28 Feb 2013 07:25:12 -0500 Subject: [robocup-small] RoboJackets Video Submission Message-ID: Our qualification video can seen at http://www.youtube.com/watch?v=F6CX9oOdbIg or at www.robojackets.org/~ehuang/Qualification_video.wmv . -- Nikolaus J. Mitchell RoboCup Project Manager | Robojackets - http://www.robojackets.org Georgia Institute of Technology George W. Woodruff School of Mechanical Engineering -------------- next part -------------- An HTML attachment was scrubbed... URL: From feyzavarol at gmail.com Thu Feb 28 09:38:39 2013 From: feyzavarol at gmail.com (Feyza Varol) Date: Thu, 28 Feb 2013 16:38:39 +0200 Subject: [robocup-small] 2013 Qualification Video (BRocks) Message-ID: Hi all, The link for our qualification video for Robocup 2013 can be found below: http://youtu.be/dTzEqtrri8A Yours sincerely, O. Feyza Varol On behalf of the BRocks team -------------- next part -------------- An HTML attachment was scrubbed... URL: From nurullah at nakkaya.com Thu Feb 28 11:18:37 2013 From: nurullah at nakkaya.com (Nurullah Akkaya) Date: Thu, 28 Feb 2013 18:18:37 +0200 Subject: [robocup-small] 2013 Qualification Video (NEUIslanders) Message-ID: Dear all, Here is NEUIslanders's qualification video for 2013. - https://dl.dropbox.com/u/11332353/neuislanders-2013.wmv - http://dropbox.nakkaya.com/neuislanders-2013.wmv Best, -- Nurullah Akkaya http://nakkaya.com From aras.adhami at gmail.com Thu Feb 28 11:23:59 2013 From: aras.adhami at gmail.com (aras adhami-mirhosseini) Date: Thu, 28 Feb 2013 19:53:59 +0330 Subject: [robocup-small] 2013 Qualification Video (MRL) Message-ID: Hi all, Here is the link to MRL 2013 qualification videos. http://mrl.ir/files/Laboratories/ssl/MRL-Qualification2013.mp4 Best regards, Aras Adhami-Mirhosseini -------------- next part -------------- An HTML attachment was scrubbed... URL: From s1203 at matsue-ct.jp Thu Feb 28 12:05:38 2013 From: s1203 at matsue-ct.jp (=?ISO-2022-JP?B?GyRCQFBBUkt8NHVFTRsoQg==?=) Date: Fri, 1 Mar 2013 02:05:38 +0900 Subject: [robocup-small] 2013 Qualification Video (MCT Susanoo Logics) Message-ID: Dear all, Here is MCT Susanoo Logics' qualification video for 2013. - http://youtu.be/M_mDZPoFxAc I am sending this email on behalf of Toshiyuki Beppu. Sincerely. --------------- Makito Ishikura MCT Susanoo Logics s1203 at matsue-ct.jp From mrniknejad at gmail.com Thu Feb 28 13:09:06 2013 From: mrniknejad at gmail.com (mohammad Reza niknejad) Date: Thu, 28 Feb 2013 21:39:06 +0330 Subject: [robocup-small] 2013 Qualification Video (Immortals) Message-ID: Dear all, here is the link to Immortals Qualification Video : http://immortals.iust.ac.ir/Immortals13(720p).mpg Regards Mohammad Reza Niknejad -------------- next part -------------- An HTML attachment was scrubbed... URL: From aandreapalmer at gmail.com Thu Feb 28 15:51:25 2013 From: aandreapalmer at gmail.com (Andrea Palmer) Date: Thu, 28 Feb 2013 12:51:25 -0800 Subject: [robocup-small] 2013 Qualification Video (UBC Thunderbots) Message-ID: Hi all, Here is the link to the UBC Thunderbots Qualification Video. http://youtu.be/GeXvmVlzjvs Best regards, Andrea Palmer UBC Thunderbots | Team Lead -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco.morales at itam.mx Thu Feb 28 16:19:22 2013 From: marco.morales at itam.mx (Marco Morales Aguirre) Date: Thu, 28 Feb 2013 15:19:22 -0600 Subject: [robocup-small] 2013 Qualification Video (Eagle Knights) Message-ID: <198EDC84-3D1B-48FA-A542-A240154501F9@itam.mx> Dear All, Here is the link to the qualification video of the Eagle Knights team for RoboCup 2013 http://youtu.be/DDUJYdTUnmA Best regards, _____________ Marco Morales Profesor Titular II, Depto. de Sistemas Digitales Instituto Tecnol?gico Aut?nomo de M?xico -ITAM R?o Hondo 1, Progreso Tizap?n, M?xico D.F. 01080, M?xico tel. +52 (55) 5628-4000 x. 3626 fax: +52 (55) 5490-4663 -------------- next part -------------- An HTML attachment was scrubbed... URL: From toorugoo at gmail.com Thu Feb 28 16:34:35 2013 From: toorugoo at gmail.com (Vitor Hugo Meneses Beck) Date: Thu, 28 Feb 2013 18:34:35 -0300 Subject: [robocup-small] 2013 Qualification Video (RoboFEI) Message-ID: Hi all, Here is the link to the RoboFEI Qualification Video http://youtu.be/DmuzUpSNmO4 Best regards, Vitor Hugo -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefanohenrique at gmail.com Thu Feb 28 17:29:08 2013 From: stefanohenrique at gmail.com (Stefano Henrique Rodrigues) Date: Thu, 28 Feb 2013 19:29:08 -0300 Subject: [robocup-small] 2013 Qualification Video (RoboIME) Message-ID: Hi all, Here is the link to the RoboIME Qualification Video. http://youtu.be/7RoejhgwAHM Best Regards, -- Stefano Henrique Rodrigues B.S. - Ci?ncia da Computa??o - Universidade Federal do Tocantins M.Sc - Sistemas e Computa??o - Instituto Militar de Engenharia [(em andamento)] +55 21 81660730 -------------- next part -------------- An HTML attachment was scrubbed... URL: From amiryan.j at robocyrus.ir Thu Feb 28 18:02:04 2013 From: amiryan.j at robocyrus.ir (javad amiryan) Date: Fri, 1 Mar 2013 02:32:04 +0330 Subject: [robocup-small] 2013 Qualification Video (Cyrus) Message-ID: Hi, this is the link to Cyrus Qualification Video : http://www.filehosting.org/file/details/332026/Cyrus-Video.wmv -- Regards, Javad Amiryan, On behalf of Cyrus Robotic Team. -------------- next part -------------- An HTML attachment was scrubbed... URL: From small-size at parsianrobotic.ir Thu Feb 28 18:16:33 2013 From: small-size at parsianrobotic.ir (Parsian Robotic) Date: Fri, 1 Mar 2013 02:46:33 +0330 Subject: [robocup-small] 2013 Qualification Video (Parsian) In-Reply-To: References: Message-ID: Dear all, Here's the link for Parsian SSL qualification video for RoboCup 2013 http://ele.aut.ac.ir/~parsian/13qualify/Parsian-SSL-2013-Qualification.mp4 Best Regards -- S.Mehdi Mohaimanian Pour ( Sepehr ) AmirKabir University Of Technology ( Tehran Polytechnic ) s.m.m at aut.ac.ir www.voidminded.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpmendoza at ri.cmu.edu Thu Feb 28 17:09:23 2013 From: jpmendoza at ri.cmu.edu (Juan Pablo Mendoza) Date: Thu, 28 Feb 2013 17:09:23 -0500 Subject: [robocup-small] 2013 Qualification Video (CMDragons) Message-ID: Hi all, Here is the link to CMDragon's qualification video: http://www.youtube.com/watch?v=zHmQhAzf_0M Regards, Juan Pablo Mendoza | Carnegie Mellon University -------------- next part -------------- An HTML attachment was scrubbed... URL: From shahzad31comp at gmail.com Fri Mar 1 08:47:47 2013 From: shahzad31comp at gmail.com (MUHAMMAD SHAHZAD) Date: Fri, 1 Mar 2013 18:47:47 +0500 Subject: [robocup-small] 2013 Qualification Video (EMEnents) Message-ID: Hi All,Here are links to Team EMEnents Qualification video. Link1: https://www.facebook.com/photo.php?v=451082231629464&l=949459642394465334 Link2: https://docs.google.com/file/d/0B0Xa0U3umDvIR1hna3ZnNzBOZjA/edit?usp=sharing Best Regards Team EMEnents -------------- next part -------------- An HTML attachment was scrubbed... URL: From robocupssl at ceme.nust.edu.pk Fri Mar 1 08:53:38 2013 From: robocupssl at ceme.nust.edu.pk (robocupssl at ceme.nust.edu.pk) Date: Fri, 1 Mar 2013 18:53:38 +0500 Subject: [robocup-small] 2013 Qualification Video (EMEnents) Message-ID: <37190586$361e116$361328a0$@com> Hi All,Here are links to Team EMEnents Qualification video. Link1: https://www.facebook.com/photo.php?v=451082231629464&l=949459642394465334 Link2: https://docs.google.com/file/d/0B0Xa0U3umDvIR1hna3ZnNzBOZjA/edit?usp=sharing Best Regards Team EMEnents -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Sat Mar 2 16:39:54 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Sat, 2 Mar 2013 18:39:54 -0300 Subject: [robocup-small] Team qualification material submission - status Message-ID: <000001ce178e$7c5bf800$7513e800$@yahoo.com.br> Dear SSL team members, greetings. As the period for submission of qualification material is over, the OC members have updated the League's wiki with all team's submission status. We ask that you please check your team's status and, if the information is not correct, forward the original email again to the OC's attention. http://robocupssl.cpe.ku.ac.th/robocup2013:teams Best Regards Angelo Gurzoni Jr On behalf of the SSL OC for RoboCup Netherlands 2013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From circuitben at gmail.com Mon Mar 4 05:36:22 2013 From: circuitben at gmail.com (Ben Johnson) Date: Mon, 4 Mar 2013 02:36:22 -0800 Subject: [robocup-small] 2013 Qualification Video Stanford Robotics Club Message-ID: Our qualification video is at: http://youtu.be/wugvb3zGie0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From circuitben at gmail.com Wed Mar 6 15:36:20 2013 From: circuitben at gmail.com (Ben Johnson) Date: Wed, 6 Mar 2013 12:36:20 -0800 Subject: [robocup-small] ssl-vision support for V4L2 Message-ID: I have added Video4Linux2 support to ssl-vision so it can be used with USB cameras and other non-Firewire devices. My branch with this support is located at: https://github.com/cktben/ssl-vision I have tested this with the Playstation 3 Eye, which is cheap and capable of 640x480 at 60FPS. The camera can be mostly configured inside ssl-vision, but there is currently no option to set resolution or framerate. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Wed Mar 13 11:03:56 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Wed, 13 Mar 2013 12:03:56 -0300 Subject: [robocup-small] RoboCup 2013 Eindhoven, the Netherlands [Newsletter #2] Message-ID: <000a01ce1ffb$fd82e770$f888b650$@yahoo.com.br> From: rc-ssl-oc-bounces at lists.robocup.org [mailto:rc-ssl-oc-bounces at lists.robocup.org] On Behalf Of Roel Merry Sent: Tuesday, March 12, 2013 6:07 PM To: Info RoboCup 2013 Subject: [Rc-ssl-oc] RoboCup 2013 Eindhoven, the Netherlands [Newsletter #2] cid:image001.jpg at 01CE1F67.BF4C6330 CONTENTS 1. Preface 2. Registration 3. VISA 4. Cargo 5. Accommodations 6. Important dates 7. Contact 1. Preface In this second newsletter from the local organization for the RoboCup World Championships 2013 we would like to give you somewhat more information regarding the registration, the updated website, the VISA procedure, shipment of your robots and the possibilities for accommodations during RoboCup 2013. The website for RoboCup 2013 ( www.robocup2013.org) got a major update. The biggest changes to the website are the accessibility and the addition of social media such as Facebook ( www.facebook.com/RoboCup2013) and Twitter (@RoboCup2013 twitter.com/robocup2013) With the new format we hope that you will find the required information easier and faster and that it allows you to stay up to date regarding the news and information of and related to RoboCup 2013. The preparations and organization is proceeding rapidly. We are working hard to make RoboCup 2013 an unforgettable and enjoyable event. Good luck with the preparations for the world championships. We hope that together with you we can make it an event to remember. 2. Registration Also for RoboCup 2013 a web-based system is used, regonline. Only qualified teams can register. Please wait until your league qualifies the teams, so your team will be available in regonline. There is a registration code necessary, which we will send to the team leaders of the qualified teams. Registration proceeds separately for each qualified team and for the team leader and team members. When registering a team, you need to include the information for a ?point of contact? for the team. Please note, though, that the person serving as point of contact is not registered at that time, but only the team is registered. In addition to registering your team, all team leaders and team members need to register as Faculty/Staff or Student participants. a. Payment Credit card payments are immediately validated, therefore we strongly recommend payment by credit card. The other available method of payment takes time. No registration is considered complete until full payment is received. b. Invitation letter The participants from the countries requiring visas will need an invitation letter. The invitation letter will be sent by email to the participants, at our very earliest convenience after the registration is complete. Please wait patiently for the payment to be complete. If you still have questions, please email to visa at robocup2013.org. c. Major Leagues registration Qualified teams are organized by league. No major team can register after May 31, 2013. Team members can only register after their team registration is complete. Early registration 1 March ? 30 April 2013 Team: 600 EUR Faculty/staff: 380 EUR Student: 270 EUR Individual*: 380 EUR Regular registration 1 May ? 31 May 2013 Team: 700 EUR Faculty/staff: 430 EUR Student: 320 EUR Individual*: 430 EUR Late/onsite registration 1 June 2013 ? 30 June 2013 Team: not available Faculty/staff: 480 EUR Student: 370 EUR Individual*: 480 EUR * Major Individual ? Faculty who do not have teams, but want to register for the competition can register as a non-participant. No prior registration of a team is required in these cases. These participants are invited to all social events, but may not enter team areas and do not receive a RoboCup-2013 certificate. We strongly encourage everyone to register as early as possible. Please avoid on-site registration, as we may be forced to reject on-site registrations due to space limitations. Nobody will be admitted to the site and to the team areas before being fully registered and all payments have been received. There will be no exceptions. Long waiting hours may be incurred at the on-site registration. d. Junior Leagues registration ? Before you can register your junior team, the team must be qualified. Please contact your RoboCupJunior national representative for all questions concerning qualification. ? Junior teams must have at least two team members in order to register. Junior teams must consist of minimum of two team members. ? We strongly recommend teams to register all team students at once. The system does not allow you to add only one team student to your existing registration. Adding more team student(s) later without two extra students will not be possible ? Parents or other mentors need to register as Junior Parent/Chaperone for permission to enter the site at any time, to be admitted to certain restricted areas, and to participate in social events. ? Parents accompanying their children, who want to visit the site only during hours for public access and only in areas open to the public, do not need to register. Early registration 1 March ? 31 May 2013 Team: 120 EUR Mentor: 120 EUR Student: 100 EUR Junior parent / Chaperone: 120 EUR Late/onsite registration 1 June 2013 ? RoboCup 2013 Team: not available Mentor: 220 EUR Student: 200 EUR Junior parent / Chaperone: 220 EUR We strongly encourage everyone to register as early as possible. Please avoid on-site registration, as we may be forced to reject on-site registrations due to space limitations. Nobody will be admitted to the site and to the team areas before being fully registered and all payments have been received. There will be no exceptions. Long waiting hours may be incurred at the on-site registration. e. Registration as Symposium Only participant It is possible for both faculty and students to register as Symposium Only participants. Invitation letters to Symposium Only participants are issued to those with accepted publications therein, only. On the registration web site, choose ?Symposium Only Faculty/Staff? or ?Symposium Only Student?. Fees Symposium Only: ? Faculty/staff: 250 EUR ? Student: 150 EUR All registered team members are automatically admitted to the Symposium. Team members do not need to register separately for the symposium. On the website ( www.robocup2013.org) you can find more information including the payment methods and visa and cancellation policy. More details regarding visa are also included further on in this newsletter. 3. VISA You can apply for a short stay visa at the Dutch embassy or consulate in your country 3 months before the competitions start. Make sure that you include the following documents in your application: * Valid passport (travel document) * Letter of invitation. RoboCup2013 only sends out a letter of invitation after your registration is complete, i.e. after you paid the registration fees. * Evidence showing that you have sufficient means of support for your stay in the Netherlands, transit journey, and/or return journey. This means showing you have at least ?34,- per person per day at your disposal for the duration of your visa (for example by means of bank statements, traveller?s cheques or cash). * Documents showing you have adequate medical travel insurance. * Proof of reservations for the journey. * Documents which make the return to your country of origin or country of continuous residence plausible. Such as an employer?s statement, records of children attending school, proof of ownership of your own house and/or other immovable property. * Two passport photographs. Please note: An embassy or consulate may always ask you for extra documents or items. Please note: To speed up the visa-requests, the Dutch embassies prefer teams to make a group appointment for all the team-members. For more information, see the brochure of the Immigration and Naturalisation service of the Dutch Government or the website of the Dutch government. An overview of the countries for which a visum is required is included on the website www.robocup2013.org/visa-information. 4. Cargo For RoboCup 2013, every team is free to select its own company for shipment of the robots. The 24th and 25th of June between 09.00 and 12.00, your goods can be delivered to the address below: RoboCup 2013 Theo Koomenlaan 1 5644 HZ Eindhoven The Netherlands Please note: Every team is responsible for receiving their own goods at the venue. RoboCup 2013 will not receive or store any goods. Please note: The RoboCup 2013 organization is not responsible for calamities, disputes or claims concerning direct agreements between competing teams in RoboCup 2013 and any shipper. The organization recommends MOL logistics as a possible shipment company. You can find more information regarding shipment through MOL logistics in this document ( link), which is also linked on the website. 5. Acommodations Below you can find an overview of accommodations in several price categories. The listed accommodations offer special prices during RoboCup 2013. Reservations have to be made by the teams themselves. For the RoboCupJunior teams there is besides the listed accommodations an additional option in the form of a Junior camping, of which you can find the details using this on the website under ?Participants? ? ?Junior Camping?. Name Travel distance Price range Van der Valk Hotel Eindhoven**** 1 km ??? Hampshire Hotel Parkzicht*** 2.3 km ?? 3BE Backpackers Bed & Breakfast Eindhoven 2.4 km ? Mercure Hotel Eindhoven**** 2.6 km ?? Sandton Hotel City Centre***? 2.7 km ?? Park Plaza Eindhoven****? 3 km ??? Hotel Auberge Nassau**? 3.8 km ?? Benno*? 3.8 km ? Hotel la Reine ? 3.8 km ?? Boutiquehotel Lumi?re Hampshire Classic***? 4 km ?? Crown Inn***? 4 km ?? Best Western Premier Art Hotel Eindhoven****? 4 km ??? Queen***? 4 km ?? Hampshire Eden Crown Hotel****? 4.5 km ??? Pullman Eindhoven Cocagne****? 4.5 km ??? Holiday Inn****? 5 km ??? Campanile*** 6.2 km ?? Novotel*** 8.5 km ?? NH Conference Centre Koningshof 8.5 km ?? NH Best 12.5 km ?? Carlton de Brug 13 km ?? Besides the above accommodations there are also a number of holiday parcs in the proximity of Eindhoven at which you can book a bungalow for a group of people. Using the following link you can find an overview of the bungalow parcs around Eindhoven in Google maps 6. Important dates In the tables below you can find the important dates of the senior competitions, the junior competitions and the symposium. a. Senior leagues Competitions June 27 ? 30 Demonstration games and setup June 26 Setup June 24 ? 25 Late registration June 1 ? 23 Regular registration(1) May 1 ? 31 Early registration deadline March 1 ? April 30 Deadline for completion of qualification in each RoboCup league(2) March 15 Team Pre-Registration Deadline(2) February 15 (1) No team registration accepted after May 31. (2) Pre-registration and qualification deadlines may vary for some leagues. b. Junior leagues Junior workshop at symposium July 1 Competitions June 27 ? 30 Setup June 26 Late registration June 1 ? 23 Registration(1) April 1 - May 31 Pre-registration by national or regional representatives March 1 - May 4 Release of team allocations (quota for each country/region) February 28 Submission of placeholder applications by regional representatives January 28 ? February 20 (1) No team registration accepted after May 31. c. Symposium ? Extended deadline! Symposium July 1 Submission of camera-ready copies May 15 Notification to authors April 28 Submission of full papers March 22 7. Contact For questions regarding RoboCup 2013, please contact one of the mail addresses below. General: info at robocup2013.org Chairs: chair at robocup2013.org Competitions: competitions at robocup2013.org Towards the 2013 competitions we will send regular newsletters to keep you informed regarding the organization and details that are important for the various leagues and teams. We hope to welcome you all at the Genneper Parcs in Eindhoven! On behalf of the RoboCup 2013 organization. Best regards, Roel Merry & Ren? van de Molengraft (co-chairs RoboCup 2013) cid:image002.jpg at 01CE1F67.BF4C6330 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 19261 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 10526 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RoboCup 2013 Eindhoven, the Netherlands [Newsletter #2].pdf Type: application/pdf Size: 248608 bytes Desc: not available URL: From chead at chead.ca Sun Mar 17 02:01:47 2013 From: chead at chead.ca (Christopher Head) Date: Sat, 16 Mar 2013 23:01:47 -0700 Subject: [robocup-small] New Rules Message-ID: <20130316230147.7c7b20d1@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear teams, I?m happy to announce that the technical committee, with some much-appreciated input from the organizing committee, has prepared the new rules for use at RoboCup 2013. As always, these rules are available on the league?s wiki, at . Other than small grammatical and formatting tidying, I?d like to bring your attention to the following major changes (I suggest following along in the ?Changes from 2012 to 2013? document, so you can see what was removed as well as what was added). In subsection 3.1.3, text is added indicating that goalie interchange requires the referee, and from there the teams (via the refbox), to be notified of the goalie?s pattern number (a new refbox including this feature is almost ready for release and will use the Protobuf packet format as discussed a while ago on this mailing list). Subsection 3.1.4 has been removed because the rules about card handling have been coalesced and rewritten later on. In subsection 9.3, the phrase ?other than due to a forced restart? has been added to the double touch rules. In my opinion, it makes no sense to apply the double touch rules to a forced restart because both teams, and multiple robots per team, can touch the ball at the same time; there is no specific ?kicker? who should not be allowed to double touch. The original occurrence of the phrase ?neutral restart? has been replaced by ?forced restart? for clarity, as that is what it is called in the referee box. In subsection 9.3 further down, a line has been added making it absolutely clear that a forced restart has only happened and teams may only approach the ball after the referee indicates the forced restart. In subsection 12.1, the broken robot rule has been removed (as it now awards an indirect, not a direct, free kick; this was intended all along but accidentally put in the wrong section). The two defenders rule was deleted from this section and placed in subsection 12.2 regarding penalty kicks; having it here was pointless as two defenders could never happen except inside the defense area. In subsection 12.2, a new two defenders rule was added that now only awards a penalty kick if the second defender and the ball are both in the defense area at the same time, or if the second defender touches the ball while inside the defense area (the defender might be straddling the line of the defense area, so the second defender could touch the ball while the ball itself is not actually in the defense area?this is still a penalty). This objective metric should reduce confusion about whether the second defender materially affected gameplay. In subsection 12.3, the broken robot rule removed from 12.1 has been inserted, and the chip goal rule has been updated. I have summarized the new chip goal rule in a separate paragraph below, as it affects many parts of the text. In subsection 12.4.1, the yellow card handling rule has been rewritten. As the rule was previously written, it would in theory have allowed a robot to be sent off with a yellow card but then be interchanged for some other robot immediately; of course, we never played that way, rather taking a yellow card to decrease the number of robots allowed on the field without affecting any specific robot. The new rule doesn?t actually change how we play, it just updates the text to reflect reality. Subsection 12.4.2 makes the same update for red cards. Decision of the Technical Committee #7 of Law 12 only applied to the old chip goal rules, so it is deleted. Subsection 13.2 updates the outcomes of direct free kicks for the new chip goal rule. Subsection 14.4 updates the outcomes of penalty kicks for the new chip goal rule. Law 15 indicates what happens if a throw-in is kicked directly into a goal. The previous rules simply stated that this was not permitted, without indicating what happened in result. This would mean that the ruling would degenerate to the ball crossing the goal line without scoring, which would grant a goal or corner kick to the opponent of the last team to touch the ball. However, there is a problem with this interpretation: throw-ins are signalled to the teams as indirect free kicks, but actual indirect free kicks award a goal kick to the kicking team if they get the ball directly into the goal. Therefore, with the rules as previously written, the same signal would sometimes make a direct kick into the goal a good thing (indirect free kick) but sometimes a bad thing (throw-in)! The two added clauses make the throw-in follow the same rules as the indirect free kick, thus removing this confusion. Subsections 16.1 and 17.1 update the outcomes of goal and corner kicks for the new chip goal rule. Subsection A.3 is added and explains the semantics of an abandoned (forfeit) match. Subsection A.4 is added and dictates that round-robin games shall end early if the score difference between the two teams reaches ten points. Throughout various sections, text has been updated for the new chip goal rules. The new chip goal rules are intended to simplify the rules and encourage more chipping. The fundamental principles of the new rules are as follows: (1) Chip goals are usually permitted. However, as a goalie in actual soccer would be allowed to catch a high-flying ball with his or her hands, so a goalie in SSL will be allowed to ?catch? a ball. Of course, the robot does not actually have any way to catch the ball. Therefore, the chip goal rule dictates that if the ball flies above 150?mm, touches the goalie, and then goes directly into the goal without touching any other robot, then the goalie is considered to have caught the ball; no goal is awarded, and instead the defending team is given an indirect free kick. This rule only applies if the last robot to touch the ball before the goalie is an attacker; it does not apply if the ball touches a defender, then touches the goalie, then enters the goal. (2) Chip goals directly from restarts of play (other than neutral restarts, i.e. Force Start) are not permitted; they are generally handled the same as a goal scored from an indirect free kick, but only for the kicker?s opponent?s goal?these rules do not apply to own goals. Specifically: (a) A direct chip goal from a direct free kick awards the kicker a goal kick (just like any direct goal on an indirect free kick). (b) A direct chip goal from an indirect free kick awards the kicker a goal kick (this is true for ANY direct goal from an indirect free kick, so no rule is needed). (c) A direct chip goal from a goal kick causes the goal kick to be retaken. (d) A direct chip goal from a corner kick awards the kicker a goal kick. (3) Chipping shall not be used for penalty kicks. If the kicker chips on a penalty kick and the ball rises above 150 mm before it touches the goalie or the goal structure, the penalty kick is forfeit?no goal is awarded if the ball goes in, and the kick is not retaken. Please feel free to contact this list with any questions or concerns or, for confidential matters, the Technical Committee (at ) or me personally (at ). Christopher Head RoboCup Small Size League Technical Committee Chair -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFFXE4ACgkQnfE3lq0v9Iw2EAD/WFeHlerMj6uNsdWe1RQ/ajCT 4Tg77VmhhrpFMA3tbPwA/jG87Ewo6HVJNEgsUbdH3fBfVYK0pml5C35628s8Dy8V =Yz6W -----END PGP SIGNATURE----- From jgurzoni at yahoo.com.br Thu Mar 21 15:35:14 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Thu, 21 Mar 2013 16:35:14 -0300 Subject: [robocup-small] ssl-vision support for V4L2 In-Reply-To: References: Message-ID: <000c01ce266b$395a2bd0$ac0e8370$@yahoo.com.br> Ben, hello. Very nice job ! I just had a moment to start testing your module, and it's working well with a couple USB cameras I have. Would be nice to get feedback/contributions about this new capture stack from more people so we can hopefully incorporate it in SSL-Vision. Cheers Angelo From: robocup-small-bounces at cc.gatech.edu [mailto:robocup-small-bounces at cc.gatech.edu] On Behalf Of Ben Johnson Sent: Wednesday, March 06, 2013 5:36 PM To: robocup-small at cc.gatech.edu Subject: [robocup-small] ssl-vision support for V4L2 I have added Video4Linux2 support to ssl-vision so it can be used with USB cameras and other non-Firewire devices. My branch with this support is located at: https://github.com/cktben/ssl-vision I have tested this with the Playstation 3 Eye, which is cheap and capable of 640x480 at 60FPS. The camera can be mostly configured inside ssl-vision, but there is currently no option to set resolution or framerate. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Fri Mar 22 21:54:59 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Fri, 22 Mar 2013 22:54:59 -0300 Subject: [robocup-small] FW: Robocup Symposium - Extended Submission Deadline Message-ID: <001701ce2769$6ef40be0$4cdc23a0$@yahoo.com.br> Dear all, To give a few more days to finalize submissions to the RoboCup Symposium after the extended IROS deadline, we set our submission deadline to Friday March 29th, midnight PST. Submitted papers are limited to 12 pages (regular papers) or 8 pages (new track papers) formatted according to the LNAI requirements (http://www.springer.com/series/1244) and must be electronically submitted through the symposium web site: https://www.easychair.org/conferences/?conf=robocupsymposium2013 All contributions are peer-reviewed by at least three reviewers using a blind review process. We would like to have submissions from each league. IMPORTANT DATES * Submission of full papers: March 29, 2013 * Notification to authors: May 3, 2013 * Submission of camera-ready copies: May 15, 2013 * RoboCup 2013 Symposium: July 1st, 2013 Regards on behalf of the symposium co-chairs Manuala Veloso, Rong Xiong, Sven Behnke and Arnoud Visser Email: robocupsymposium2013 at easychair.org _______________________________________________ _______________________________________________ rc-ssl-oc mailing list rc-ssl-oc at lists.robocup.org http://lists.robocup.org/listinfo.cgi/rc-ssl-oc-robocup.org From jgurzoni at yahoo.com.br Sat Mar 23 16:54:34 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Sat, 23 Mar 2013 17:54:34 -0300 Subject: [robocup-small] announce the qualification results ? In-Reply-To: <38D0CD43-9F94-4D81-B630-5701A4834812@yahoo.com> References: <000301ce27ec$78759520$6960bf60$@yahoo.com.br> <2B6A0FD4-7C4E-461B-932F-8A43455468D9@yahoo.com> <001d01ce27fc$26175bf0$724613d0$@yahoo.com.br> <62845B0D-0184-459D-970F-19B17756B3BA@yahoo.com> <002501ce27fe$76f1fd30$64d5f790$@yahoo.com.br> <7C475A7D-2BCC-4611-B42D-EA2AC1D55819@yahoo.com> <002e01ce2805$3e499400$badcbc00$@yahoo.com.br> <38D0CD43-9F94-4D81-B630-5701A4834812@yahoo.com> Message-ID: <003f01ce2808$a1c673b0$e5535b10$@yahoo.com.br> I think would be nice to add link to the wiki Just send to robocup-small at cc.gatech.edu and everybody will receive Cheers From: Mohammad Hosein [mailto:iliaiust at yahoo.com] Sent: Saturday, March 23, 2013 5:43 PM To: Angelo Gurzoni Jr Subject: Re: announce the qualification results ? Is it good to add link of wiki down of 1th topics? Pleas send it to me. Thx Mohammad Sent from my iPad On Mar 24, 2013, at 1:00 AM, "Angelo Gurzoni Jr" wrote: That?s good, I would only condense the topics and messages, like I did below. But it?s up to you, the message core is fine Tks for the help From: Mohammad Hosein [mailto:iliaiust at yahoo.com] Sent: Saturday, March 23, 2013 5:22 PM To: Angelo Gurzoni Jr Subject: Re: announce the qualification results ? Hi all Topics: 1) Qualified teams Qualification results have been upload on wiki page 2) TDP's Uploading TDP's will be finished next few days, and you can see and use all the TDP's 3) Conditionally qualified teams OC/TC will contact with conditionally qualified teams in the next days Cheers Mohammad hosein -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Sun Mar 24 15:58:27 2013 From: chead at chead.ca (Christopher Head) Date: Sun, 24 Mar 2013 12:58:27 -0700 Subject: [robocup-small] New Referee Box Message-ID: <20130324125827.3f96c73c@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello teams! I have just published release candidate 1 of the 2013 referee box on the wiki which offers the new Protobuf protocol (the old legacy protocol is still included for backwards compatibility). At this time, only a source tarball is available. I have tested the new referee box under Linux, but the instructions for building under Windows are out of date as I do not have a Windows development environment to test against. I appreciate any testing anyone can do?try running the new refbox and, if you have time, try updating your software to use the new Protobuf packets. If you find any bugs, please send them to me personally (no need to clutter the mailing list). If anyone gets the referee box working under Windows, I would be happy to take a patch to the documentation and Makefile explaining how to do this. Christopher Head SSL TC Chair -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFPWuMACgkQnfE3lq0v9IzYsQD/SyGLPBM0fdC9WmqEpUnmsDo3 X1OzIPlB9R92prms7YYA/izxWAiW3NSquzEv7Yf4o5CTbqSsz+kuAFww1w7ILcgy =H2Fd -----END PGP SIGNATURE----- From chead at chead.ca Sun Mar 24 19:39:59 2013 From: chead at chead.ca (Christopher Head) Date: Sun, 24 Mar 2013 16:39:59 -0700 Subject: [robocup-small] New Referee Box In-Reply-To: <20130324125827.3f96c73c@kruskal.chead> References: <20130324125827.3f96c73c@kruskal.chead> Message-ID: <20130324163959.7d56686b@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 By the way, if you prefer, you can also send bug reports or patches to . Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFPjs8ACgkQnfE3lq0v9Ixw2QD+O9WyZc1i9MpqO0+tr+D/hUmx 7gZtegA/PuJPkKlTl2EA/jX1hqt4yRzYNFAGhrQsFFdkGnubg49oxWDQqMQkXTaY =J14+ -----END PGP SIGNATURE----- From iliaiust at hotmail.se Mon Mar 25 04:42:19 2013 From: iliaiust at hotmail.se (mohammad hossein fazeli) Date: Mon, 25 Mar 2013 08:42:19 +0000 Subject: [robocup-small] Qualification Message-ID: Hi all Topics: 1) Qualified teams Qualification results have been upload on wiki page http://robocupssl.cpe.ku.ac.th/robocup2013:teams 2) TDP's Uploading TDP's will be finished next few days, and you can see and use all the TDP's 3) Conditionally qualified teams OC/TC will contact with conditionally qualified teams in the next days Cheers Mohammad hosein RC-SSL-OC Sent from my iPad -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Tue Mar 26 01:33:44 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Tue, 26 Mar 2013 02:33:44 -0300 Subject: [robocup-small] ETDP deadline extension - April 30 Message-ID: <002401ce29e3$7d57e3b0$7807ab10$@yahoo.com.br> Greetings Due to the extension of the paper submission deadline given by RoboCup Symposium and the proximity of RoboCup Iran Open, the OC and TC agreed to extend the ETDP submission date to April 30, 2013. We hope that this gives more time to the top 8 teams from last competition to prepare papers which contribute to the advancement of the League and help all teams. Best Regards Angelo Gurzoni Jr On behalf of the SSL OC for RoboCup 2013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From joydeep at cmu.edu Wed Mar 27 18:26:34 2013 From: joydeep at cmu.edu (Joydeep Biswas) Date: Wed, 27 Mar 2013 18:26:34 -0400 Subject: [robocup-small] New Rules In-Reply-To: <20130316230147.7c7b20d1@kruskal.chead> References: <20130316230147.7c7b20d1@kruskal.chead> Message-ID: Hi Chris, I would like to clarify the rule regarding "catching" chip kicks in the following scenario: Scenario: 1. Yellow robot 0 chip kicks the ball towards blue goal. 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces off its front. 3. The ball, bouncing off the front of blue goalie, hits the back of blue defender robot 1. 4. The ball, after hitting the back of blue defender robot 1, enters the blue goal. Would this scenario result in a goal for yellow team? -Joydeep On Sun, Mar 17, 2013 at 2:01 AM, Christopher Head wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Dear teams, > I?m happy to announce that the technical committee, with some > much-appreciated input from the organizing committee, has prepared the > new rules for use at RoboCup 2013. As always, these rules are available > on the league?s wiki, at . > Other than small grammatical and formatting tidying, I?d like to bring > your attention to the following major changes (I suggest following > along in the ?Changes from 2012 to 2013? document, so you can see what > was removed as well as what was added). > > In subsection 3.1.3, text is added indicating that goalie interchange > requires the referee, and from there the teams (via the refbox), to be > notified of the goalie?s pattern number (a new refbox including this > feature is almost ready for release and will use the Protobuf packet > format as discussed a while ago on this mailing list). > > Subsection 3.1.4 has been removed because the rules about card handling > have been coalesced and rewritten later on. > > In subsection 9.3, the phrase ?other than due to a forced restart? has > been added to the double touch rules. In my opinion, it makes no sense > to apply the double touch rules to a forced restart because both teams, > and multiple robots per team, can touch the ball at the same time; > there is no specific ?kicker? who should not be allowed to double > touch. The original occurrence of the phrase ?neutral restart? has been > replaced by ?forced restart? for clarity, as that is what it is called > in the referee box. > > In subsection 9.3 further down, a line has been added making it > absolutely clear that a forced restart has only happened and teams may > only approach the ball after the referee indicates the forced restart. > > In subsection 12.1, the broken robot rule has been removed (as it now > awards an indirect, not a direct, free kick; this was intended all > along but accidentally put in the wrong section). The two defenders > rule was deleted from this section and placed in subsection 12.2 > regarding penalty kicks; having it here was pointless as two defenders > could never happen except inside the defense area. > > In subsection 12.2, a new two defenders rule was added that now only > awards a penalty kick if the second defender and the ball are both in > the defense area at the same time, or if the second defender touches the > ball while inside the defense area (the defender might be straddling > the line of the defense area, so the second defender could touch the > ball while the ball itself is not actually in the defense area?this is > still a penalty). This objective metric should reduce confusion about > whether the second defender materially affected gameplay. > > In subsection 12.3, the broken robot rule removed from 12.1 has been > inserted, and the chip goal rule has been updated. I have summarized > the new chip goal rule in a separate paragraph below, as it affects many > parts of the text. > > In subsection 12.4.1, the yellow card handling rule has been rewritten. > As the rule was previously written, it would in theory have allowed a > robot to be sent off with a yellow card but then be interchanged for > some other robot immediately; of course, we never played that way, > rather taking a yellow card to decrease the number of robots allowed on > the field without affecting any specific robot. The new rule doesn?t > actually change how we play, it just updates the text to reflect > reality. > > Subsection 12.4.2 makes the same update for red cards. > > Decision of the Technical Committee #7 of Law 12 only applied to the > old chip goal rules, so it is deleted. > > Subsection 13.2 updates the outcomes of direct free kicks for the new > chip goal rule. > > Subsection 14.4 updates the outcomes of penalty kicks for the new chip > goal rule. > > Law 15 indicates what happens if a throw-in is kicked directly into a > goal. The previous rules simply stated that this was not permitted, > without indicating what happened in result. This would mean that the > ruling would degenerate to the ball crossing the goal line without > scoring, which would grant a goal or corner kick to the opponent of the > last team to touch the ball. However, there is a problem with this > interpretation: throw-ins are signalled to the teams as indirect free > kicks, but actual indirect free kicks award a goal kick to the kicking > team if they get the ball directly into the goal. Therefore, with the > rules as previously written, the same signal would sometimes make a > direct kick into the goal a good thing (indirect free kick) but > sometimes a bad thing (throw-in)! The two added clauses make the > throw-in follow the same rules as the indirect free kick, thus removing > this confusion. > > Subsections 16.1 and 17.1 update the outcomes of goal and corner kicks > for the new chip goal rule. > > Subsection A.3 is added and explains the semantics of an abandoned > (forfeit) match. > > Subsection A.4 is added and dictates that round-robin games shall end > early if the score difference between the two teams reaches ten points. > > Throughout various sections, text has been updated for the new chip > goal rules. The new chip goal rules are intended to simplify the rules > and encourage more chipping. The fundamental principles of the new > rules are as follows: > > (1) Chip goals are usually permitted. However, as a goalie in actual > soccer would be allowed to catch a high-flying ball with his or her > hands, so a goalie in SSL will be allowed to ?catch? a ball. Of course, > the robot does not actually have any way to catch the ball. Therefore, > the chip goal rule dictates that if the ball flies above 150 mm, touches > the goalie, and then goes directly into the goal without touching any > other robot, then the goalie is considered to have caught the ball; no > goal is awarded, and instead the defending team is given an indirect > free kick. This rule only applies if the last robot to touch the ball > before the goalie is an attacker; it does not apply if the ball touches > a defender, then touches the goalie, then enters the goal. > > (2) Chip goals directly from restarts of play (other than neutral > restarts, i.e. Force Start) are not permitted; they are generally > handled the same as a goal scored from an indirect free kick, but only > for the kicker?s opponent?s goal?these rules do not apply to own goals. > Specifically: > (a) A direct chip goal from a direct free kick awards the kicker a goal > kick (just like any direct goal on an indirect free kick). > (b) A direct chip goal from an indirect free kick awards the kicker a > goal kick (this is true for ANY direct goal from an indirect free kick, > so no rule is needed). > (c) A direct chip goal from a goal kick causes the goal kick to be > retaken. > (d) A direct chip goal from a corner kick awards the kicker a goal kick. > > (3) Chipping shall not be used for penalty kicks. If the kicker chips > on a penalty kick and the ball rises above 150 mm before it touches the > goalie or the goal structure, the penalty kick is forfeit?no goal is > awarded if the ball goes in, and the kick is not retaken. > > Please feel free to contact this list with any questions or concerns > or, for confidential matters, the Technical Committee (at > ) or me personally (at ). > > Christopher Head > RoboCup Small Size League Technical Committee Chair > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlFFXE4ACgkQnfE3lq0v9Iw2EAD/WFeHlerMj6uNsdWe1RQ/ajCT > 4Tg77VmhhrpFMA3tbPwA/jG87Ewo6HVJNEgsUbdH3fBfVYK0pml5C35628s8Dy8V > =Yz6W > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Thu Mar 28 00:19:47 2013 From: chead at chead.ca (Christopher Head) Date: Wed, 27 Mar 2013 21:19:47 -0700 Subject: [robocup-small] New Rules In-Reply-To: References: <20130316230147.7c7b20d1@kruskal.chead> Message-ID: <20130327211947.2a47e9fd@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Yes, this would be a goal for yellow. The only case when a chip goal is not a goal during normal play is if it touches the goalie then goes in the goal, WITHOUT touching any other robot in between?this includes another defender. We tried to strike a balance between encouraging teams to use chippers where it makes sense to do so, while still giving the goalie the power to defend effectively against chip goals, and the rule about the goalie catching chip kicks that go directly into the goal after touching the goalie was our way to (hopefully!) achieve that balance. Chris On Wed, 27 Mar 2013 18:26:34 -0400 Joydeep Biswas wrote: > Hi Chris, > > I would like to clarify the rule regarding "catching" chip kicks in > the following scenario: > > Scenario: > 1. Yellow robot 0 chip kicks the ball towards blue goal. > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces > off its front. > 3. The ball, bouncing off the front of blue goalie, hits the back of > blue defender robot 1. > 4. The ball, after hitting the back of blue defender robot 1, enters > the blue goal. > > Would this scenario result in a goal for yellow team? > > -Joydeep -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd =wBEU -----END PGP SIGNATURE----- From zhyaic at gmail.com Thu Mar 28 01:23:47 2013 From: zhyaic at gmail.com (Yue Zhao) Date: Thu, 28 Mar 2013 13:23:47 +0800 Subject: [robocup-small] New Rules In-Reply-To: <20130327211947.2a47e9fd@kruskal.chead> References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> Message-ID: Hello Chris, I also have a question: 1) yellow robot chip ball to blue's penalty area 2) blue's goalie touch the ball 3) blue's goalie then intentionally kick/touch the ball to blue's own goal to get a goal kick How about this scenario? You know, blue will get a goal kick in this way. That means kicking/touching the ball to the own goal is better than clearing the ball out of penalty area. 2013/3/28 Christopher Head > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hello, > Yes, this would be a goal for yellow. The only case when a chip goal is > not a goal during normal play is if it touches the goalie then goes in > the goal, WITHOUT touching any other robot in between?this includes > another defender. We tried to strike a balance between encouraging > teams to use chippers where it makes sense to do so, while still giving > the goalie the power to defend effectively against chip goals, and the > rule about the goalie catching chip kicks that go directly into the > goal after touching the goalie was our way to (hopefully!) achieve that > balance. > > Chris > > On Wed, 27 Mar 2013 18:26:34 -0400 > Joydeep Biswas wrote: > > > Hi Chris, > > > > I would like to clarify the rule regarding "catching" chip kicks in > > the following scenario: > > > > Scenario: > > 1. Yellow robot 0 chip kicks the ball towards blue goal. > > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces > > off its front. > > 3. The ball, bouncing off the front of blue goalie, hits the back of > > blue defender robot 1. > > 4. The ball, after hitting the back of blue defender robot 1, enters > > the blue goal. > > > > Would this scenario result in a goal for yellow team? > > > > -Joydeep > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 > mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd > =wBEU > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Thu Mar 28 04:15:32 2013 From: chead at chead.ca (Christopher Head) Date: Thu, 28 Mar 2013 01:15:32 -0700 Subject: [robocup-small] New Rules In-Reply-To: References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> Message-ID: <20130328011532.23429d1e@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Actually, subsection 12.3 states that, in this case, an indirect free kick, not a goal kick (or corner kick, as it would actually be since the last touch would be by a defender), is awarded. The free kick would obviously be awarded inside the defense area and would therefore (as per subsection 13.4) be taken 100?mm from the touch line and 600?mm from the goal line, which is very close to the 100/500 where a goal kick would be taken, but the kick would nevertheless be indirect. Remember also that it is illegal to interfere with the goalie inside the defense area, so the goalie would have lots of time to set up a chip or kick of its own if it preferred. Chris On Thu, 28 Mar 2013 13:23:47 +0800 Yue Zhao wrote: > Hello Chris, > I also have a question: > > 1) yellow robot chip ball to blue's penalty area > 2) blue's goalie touch the ball > 3) blue's goalie then intentionally kick/touch the ball to blue's own > goal to get a goal kick > > How about this scenario? You know, blue will get a goal kick in this > way. That means kicking/touching the ball to the own goal is better > than clearing the ball out of penalty area. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFT/CcACgkQnfE3lq0v9Iz6OwD/WHt5RfVfjgN3S1Xi3wDj3fWx C1Tov5qDHfFecfbwATEA/0/nN4jTNwY2uZ7ES1LNjj11o/+dNZkhcbfN0x8Lczqn =uhCW -----END PGP SIGNATURE----- From joydeep at cmu.edu Thu Mar 28 10:55:06 2013 From: joydeep at cmu.edu (Joydeep Biswas) Date: Thu, 28 Mar 2013 10:55:06 -0400 Subject: [robocup-small] New Rules In-Reply-To: <20130327211947.2a47e9fd@kruskal.chead> References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> Message-ID: Thanks for the clarification. I feel that allowing goals from chip kicks like in the scenario I mentioned will promote unintelligent behaviour where attacking robots will just keep on chipping at the goal in the hopes that scenarios like this happen, and that they will be awarded goals. For the goalie, however, it's reasonable to "catch" the chip kick, but entirely unreasonable to predict exactly how the ball will bounce off after hitting the goalie. Therefore, I feel if we are to allow goals from chipping, then if the goalie intercepts a chip shot in the defense area, the game should stop and the goalie should be awarded an indirect free kick from where it intercepted the ball. This is just like in real soccer where if the goalie actually catches the ball, he/she has full control of where he/she will pass the ball to, next. What are the views of the other participants of the small size league? -Joydeep On Thu, Mar 28, 2013 at 12:19 AM, Christopher Head wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hello, > Yes, this would be a goal for yellow. The only case when a chip goal is > not a goal during normal play is if it touches the goalie then goes in > the goal, WITHOUT touching any other robot in between?this includes > another defender. We tried to strike a balance between encouraging > teams to use chippers where it makes sense to do so, while still giving > the goalie the power to defend effectively against chip goals, and the > rule about the goalie catching chip kicks that go directly into the > goal after touching the goalie was our way to (hopefully!) achieve that > balance. > > Chris > > On Wed, 27 Mar 2013 18:26:34 -0400 > Joydeep Biswas wrote: > > > Hi Chris, > > > > I would like to clarify the rule regarding "catching" chip kicks in > > the following scenario: > > > > Scenario: > > 1. Yellow robot 0 chip kicks the ball towards blue goal. > > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces > > off its front. > > 3. The ball, bouncing off the front of blue goalie, hits the back of > > blue defender robot 1. > > 4. The ball, after hitting the back of blue defender robot 1, enters > > the blue goal. > > > > Would this scenario result in a goal for yellow team? > > > > -Joydeep > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 > mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd > =wBEU > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Thu Mar 28 11:10:36 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Thu, 28 Mar 2013 12:10:36 -0300 Subject: [robocup-small] New Rules In-Reply-To: References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> Message-ID: <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> Hello, everybody Wouldn't the scenario described by Joydeep result in a goal in the same way, if we use the current rules, where chip goals aren't allowed ? I'm not saying that Joydeep's line of thought isn't appropriate, as allowing chip goals may increase the occurrence of this otherwise rare event, just trying to put the scenario in the context of how would it be handled until now. The suggestion to stop the game when the goalie touches seem interesting, indeed. Cheers Angelo From: robocup-small-bounces at cc.gatech.edu [mailto:robocup-small-bounces at cc.gatech.edu] On Behalf Of Joydeep Biswas Sent: Thursday, March 28, 2013 11:55 AM To: Christopher Head Cc: robocup-small at cc.gatech.edu Subject: Re: [robocup-small] New Rules Thanks for the clarification. I feel that allowing goals from chip kicks like in the scenario I mentioned will promote unintelligent behaviour where attacking robots will just keep on chipping at the goal in the hopes that scenarios like this happen, and that they will be awarded goals. For the goalie, however, it's reasonable to "catch" the chip kick, but entirely unreasonable to predict exactly how the ball will bounce off after hitting the goalie. Therefore, I feel if we are to allow goals from chipping, then if the goalie intercepts a chip shot in the defense area, the game should stop and the goalie should be awarded an indirect free kick from where it intercepted the ball. This is just like in real soccer where if the goalie actually catches the ball, he/she has full control of where he/she will pass the ball to, next. What are the views of the other participants of the small size league? -Joydeep On Thu, Mar 28, 2013 at 12:19 AM, Christopher Head wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Yes, this would be a goal for yellow. The only case when a chip goal is not a goal during normal play is if it touches the goalie then goes in the goal, WITHOUT touching any other robot in between-this includes another defender. We tried to strike a balance between encouraging teams to use chippers where it makes sense to do so, while still giving the goalie the power to defend effectively against chip goals, and the rule about the goalie catching chip kicks that go directly into the goal after touching the goalie was our way to (hopefully!) achieve that balance. Chris On Wed, 27 Mar 2013 18:26:34 -0400 Joydeep Biswas wrote: > Hi Chris, > > I would like to clarify the rule regarding "catching" chip kicks in > the following scenario: > > Scenario: > 1. Yellow robot 0 chip kicks the ball towards blue goal. > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces > off its front. > 3. The ball, bouncing off the front of blue goalie, hits the back of > blue defender robot 1. > 4. The ball, after hitting the back of blue defender robot 1, enters > the blue goal. > > Would this scenario result in a goal for yellow team? > > -Joydeep -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd =wBEU -----END PGP SIGNATURE----- _______________________________________________ robocup-small mailing list robocup-small at cc.gatech.edu https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small -------------- next part -------------- An HTML attachment was scrubbed... URL: From joydeep at cmu.edu Thu Mar 28 12:33:23 2013 From: joydeep at cmu.edu (Joydeep Biswas) Date: Thu, 28 Mar 2013 12:33:23 -0400 Subject: [robocup-small] New Rules In-Reply-To: <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> Message-ID: Hi, Angelo, you pointed the problem out yourself: I believe that this otherwise rare scenario will become much more frequent as attackers keep chipping at the goal in the hopes of scoring a goal. If we're trying to imitate how a human goalie catches a flying ball, then the robot goalie should have just a fair chance of controlling how it wants to release the ball. Hence the suggestion of stopping the game with the indirect free kick. -Joydeep On Thu, Mar 28, 2013 at 11:10 AM, Angelo Gurzoni Jr wrote: > Hello, everybody**** > > Wouldn?t the scenario described by Joydeep result in a goal in the same > way, if we use the current rules, where chip goals aren?t allowed ?**** > > I?m not saying that Joydeep?s line of thought isn?t appropriate, as > allowing chip goals may increase the occurrence of this otherwise rare > event, just trying to put the scenario in the context of how would it be > handled until now. The suggestion to stop the game when the goalie touches > seem interesting, indeed.**** > > ** ** > > ** ** > > ** ** > > Cheers**** > > Angelo**** > > ** ** > > *From:* robocup-small-bounces at cc.gatech.edu [mailto: > robocup-small-bounces at cc.gatech.edu] *On Behalf Of *Joydeep Biswas > *Sent:* Thursday, March 28, 2013 11:55 AM > *To:* Christopher Head > *Cc:* robocup-small at cc.gatech.edu > *Subject:* Re: [robocup-small] New Rules**** > > ** ** > > Thanks for the clarification.**** > > ** ** > > I feel that allowing goals from chip kicks like in the scenario I > mentioned will promote unintelligent behaviour where attacking robots will > just keep on chipping at the goal in the hopes that scenarios like this > happen, and that they will be awarded goals. For the goalie, however, it's > reasonable to "catch" the chip kick, but entirely unreasonable to predict > exactly how the ball will bounce off after hitting the goalie. **** > > ** ** > > Therefore, I feel if we are to allow goals from chipping, then if the > goalie intercepts a chip shot in the defense area, the game should stop and > the goalie should be awarded an indirect free kick from where it > intercepted the ball. This is just like in real soccer where if the goalie > actually catches the ball, he/she has full control of where he/she will > pass the ball to, next.**** > > ** ** > > What are the views of the other participants of the small size league?**** > > ** ** > > -Joydeep**** > > On Thu, Mar 28, 2013 at 12:19 AM, Christopher Head wrote: > **** > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256**** > > Hello, > Yes, this would be a goal for yellow. The only case when a chip goal is > not a goal during normal play is if it touches the goalie then goes in > the goal, WITHOUT touching any other robot in between?this includes > another defender. We tried to strike a balance between encouraging > teams to use chippers where it makes sense to do so, while still giving > the goalie the power to defend effectively against chip goals, and the > rule about the goalie catching chip kicks that go directly into the > goal after touching the goalie was our way to (hopefully!) achieve that > balance. > > Chris**** > > > On Wed, 27 Mar 2013 18:26:34 -0400 > Joydeep Biswas wrote: > > > Hi Chris, > > > > I would like to clarify the rule regarding "catching" chip kicks in > > the following scenario: > > > > Scenario: > > 1. Yellow robot 0 chip kicks the ball towards blue goal. > > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces > > off its front. > > 3. The ball, bouncing off the front of blue goalie, hits the back of > > blue defender robot 1. > > 4. The ball, after hitting the back of blue defender robot 1, enters > > the blue goal. > > > > Would this scenario result in a goal for yellow team? > > > > -Joydeep**** > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux)**** > > iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 > mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd > =wBEU**** > > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small**** > > ** ** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joydeep at cmu.edu Thu Mar 28 12:53:36 2013 From: joydeep at cmu.edu (Joydeep Biswas) Date: Thu, 28 Mar 2013 12:53:36 -0400 Subject: [robocup-small] New Rules In-Reply-To: <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> Message-ID: Hi, Angelo, you pointed the problem out yourself: I believe that this otherwise rare scenario will become much more frequent as attackers keep chipping at the goal in the hopes of scoring a goal. If we're trying to imitate how a human goalie catches a flying ball, then the robot goalie should have just a fair chance of controlling how it wants to release the ball. Hence the suggestion of stopping the game with the indirect free kick. -Joydeep On Thu, Mar 28, 2013 at 11:10 AM, Angelo Gurzoni Jr wrote: > Hello, everybody**** > > Wouldn?t the scenario described by Joydeep result in a goal in the same > way, if we use the current rules, where chip goals aren?t allowed ?**** > > I?m not saying that Joydeep?s line of thought isn?t appropriate, as > allowing chip goals may increase the occurrence of this otherwise rare > event, just trying to put the scenario in the context of how would it be > handled until now. The suggestion to stop the game when the goalie touches > seem interesting, indeed.**** > > ** ** > > ** ** > > ** ** > > Cheers**** > > Angelo**** > > ** ** > > *From:* robocup-small-bounces at cc.gatech.edu [mailto: > robocup-small-bounces at cc.gatech.edu] *On Behalf Of *Joydeep Biswas > *Sent:* Thursday, March 28, 2013 11:55 AM > *To:* Christopher Head > *Cc:* robocup-small at cc.gatech.edu > *Subject:* Re: [robocup-small] New Rules**** > > ** ** > > Thanks for the clarification.**** > > ** ** > > I feel that allowing goals from chip kicks like in the scenario I > mentioned will promote unintelligent behaviour where attacking robots will > just keep on chipping at the goal in the hopes that scenarios like this > happen, and that they will be awarded goals. For the goalie, however, it's > reasonable to "catch" the chip kick, but entirely unreasonable to predict > exactly how the ball will bounce off after hitting the goalie. **** > > ** ** > > Therefore, I feel if we are to allow goals from chipping, then if the > goalie intercepts a chip shot in the defense area, the game should stop and > the goalie should be awarded an indirect free kick from where it > intercepted the ball. This is just like in real soccer where if the goalie > actually catches the ball, he/she has full control of where he/she will > pass the ball to, next.**** > > ** ** > > What are the views of the other participants of the small size league?**** > > ** ** > > -Joydeep**** > > On Thu, Mar 28, 2013 at 12:19 AM, Christopher Head wrote: > **** > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256**** > > Hello, > Yes, this would be a goal for yellow. The only case when a chip goal is > not a goal during normal play is if it touches the goalie then goes in > the goal, WITHOUT touching any other robot in between?this includes > another defender. We tried to strike a balance between encouraging > teams to use chippers where it makes sense to do so, while still giving > the goalie the power to defend effectively against chip goals, and the > rule about the goalie catching chip kicks that go directly into the > goal after touching the goalie was our way to (hopefully!) achieve that > balance. > > Chris**** > > > On Wed, 27 Mar 2013 18:26:34 -0400 > Joydeep Biswas wrote: > > > Hi Chris, > > > > I would like to clarify the rule regarding "catching" chip kicks in > > the following scenario: > > > > Scenario: > > 1. Yellow robot 0 chip kicks the ball towards blue goal. > > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces > > off its front. > > 3. The ball, bouncing off the front of blue goalie, hits the back of > > blue defender robot 1. > > 4. The ball, after hitting the back of blue defender robot 1, enters > > the blue goal. > > > > Would this scenario result in a goal for yellow team? > > > > -Joydeep**** > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux)**** > > iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 > mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd > =wBEU**** > > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small**** > > ** ** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpmendoza at ri.cmu.edu Thu Mar 28 14:29:04 2013 From: jpmendoza at ri.cmu.edu (Juan Pablo Mendoza) Date: Thu, 28 Mar 2013 14:29:04 -0400 Subject: [robocup-small] New Rules In-Reply-To: References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> Message-ID: Hi all, I think that trying to increase the teams' abilities to kick, track and defend against chip shots is a worthwhile scientific pursuit. However, I do agree with other comments here that we have to be careful to not detract from other aspects of game play by encouraging more chip shots. For example, it does seem like the rule change, as currently stated, would significantly increase the expected reward of unintelligently chipping into the opponent's defense area, in hopes for either a goal or a bounce off the goalkeeper that would leave attackers in a very advantageous position with respect to defenders who cannot enter the defense area. In that sense, I also find Joydeep's suggestion of stopping game play when the goalie touches the ball after a chip shot interesting. As slightly alternative suggestions, maybe the ball could be considered "caught" by the goalie in the defense area (and thus game play stops) only if it hits the top of the goalie, or only if it hits the goalie before the first bounce. It seems like this would encourage accurate chip shot tracking and a more active and intelligent goalkeeper, while discouraging random chip shots onto the goal. Finally, have you considered the option of first making the problem of defending against a chip shot a technical challenge, before incorporating it into the rules of the game? It seems like this would give all teams an opportunity to get up to date on this aspect of the game, thus providing a more even playing field for all teams. Juan Pablo On Thu, Mar 28, 2013 at 12:33 PM, Joydeep Biswas wrote: > Hi, > > Angelo, you pointed the problem out yourself: I believe that this > otherwise rare scenario will become much more frequent as attackers keep > chipping at the goal in the hopes of scoring a goal. > > If we're trying to imitate how a human goalie catches a flying ball, then > the robot goalie should have just a fair chance of controlling how it wants > to release the ball. Hence the suggestion of stopping the game with the > indirect free kick. > > -Joydeep > > On Thu, Mar 28, 2013 at 11:10 AM, Angelo Gurzoni Jr > wrote: > >> Hello, everybody**** >> >> Wouldn?t the scenario described by Joydeep result in a goal in the same >> way, if we use the current rules, where chip goals aren?t allowed ?**** >> >> I?m not saying that Joydeep?s line of thought isn?t appropriate, as >> allowing chip goals may increase the occurrence of this otherwise rare >> event, just trying to put the scenario in the context of how would it be >> handled until now. The suggestion to stop the game when the goalie touches >> seem interesting, indeed.**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> Cheers**** >> >> Angelo**** >> >> ** ** >> >> *From:* robocup-small-bounces at cc.gatech.edu [mailto: >> robocup-small-bounces at cc.gatech.edu] *On Behalf Of *Joydeep Biswas >> *Sent:* Thursday, March 28, 2013 11:55 AM >> *To:* Christopher Head >> *Cc:* robocup-small at cc.gatech.edu >> *Subject:* Re: [robocup-small] New Rules**** >> >> ** ** >> >> Thanks for the clarification.**** >> >> ** ** >> >> I feel that allowing goals from chip kicks like in the scenario I >> mentioned will promote unintelligent behaviour where attacking robots will >> just keep on chipping at the goal in the hopes that scenarios like this >> happen, and that they will be awarded goals. For the goalie, however, it's >> reasonable to "catch" the chip kick, but entirely unreasonable to predict >> exactly how the ball will bounce off after hitting the goalie. **** >> >> ** ** >> >> Therefore, I feel if we are to allow goals from chipping, then if the >> goalie intercepts a chip shot in the defense area, the game should stop and >> the goalie should be awarded an indirect free kick from where it >> intercepted the ball. This is just like in real soccer where if the goalie >> actually catches the ball, he/she has full control of where he/she will >> pass the ball to, next.**** >> >> ** ** >> >> What are the views of the other participants of the small size league?*** >> * >> >> ** ** >> >> -Joydeep**** >> >> On Thu, Mar 28, 2013 at 12:19 AM, Christopher Head >> wrote:**** >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256**** >> >> Hello, >> Yes, this would be a goal for yellow. The only case when a chip goal is >> not a goal during normal play is if it touches the goalie then goes in >> the goal, WITHOUT touching any other robot in between?this includes >> another defender. We tried to strike a balance between encouraging >> teams to use chippers where it makes sense to do so, while still giving >> the goalie the power to defend effectively against chip goals, and the >> rule about the goalie catching chip kicks that go directly into the >> goal after touching the goalie was our way to (hopefully!) achieve that >> balance. >> >> Chris**** >> >> >> On Wed, 27 Mar 2013 18:26:34 -0400 >> Joydeep Biswas wrote: >> >> > Hi Chris, >> > >> > I would like to clarify the rule regarding "catching" chip kicks in >> > the following scenario: >> > >> > Scenario: >> > 1. Yellow robot 0 chip kicks the ball towards blue goal. >> > 2. Blue goalie (blue robot 0) touches the ball, and the ball bounces >> > off its front. >> > 3. The ball, bouncing off the front of blue goalie, hits the back of >> > blue defender robot 1. >> > 4. The ball, after hitting the back of blue defender robot 1, enters >> > the blue goal. >> > >> > Would this scenario result in a goal for yellow team? >> > >> > -Joydeep**** >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.19 (GNU/Linux)**** >> >> iF4EAREIAAYFAlFTxOYACgkQnfE3lq0v9IzG3AD+KvnS0XMrPI9T1U1EW4TzL383 >> mONRcZ9UGRD3IeCGHqcA/Rh2Z0aqH66c8vL0as+TQBrvyAj0j1AJmcUsJboO1pTd >> =wBEU**** >> >> -----END PGP SIGNATURE----- >> _______________________________________________ >> robocup-small mailing list >> robocup-small at cc.gatech.edu >> https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small**** >> >> ** ** >> > > > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Sun Mar 31 15:25:40 2013 From: chead at chead.ca (Christopher Head) Date: Sun, 31 Mar 2013 12:25:40 -0700 Subject: [robocup-small] New Rules In-Reply-To: References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> Message-ID: <20130331122540.1cd74139@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi teams, It seems the new chip goal rule has stirred up quite a lot of discussion. This is a big change, and we expected it would be somewhat controversial. Please bear with us; we wanted to get the rules out in front of the teams as soon as they were ready, but because this is such a major change, and because a number of people have commented that they are not comfortable with it, we ARE still discussing the details and we are still open to changing things. We appreciate the input that has been given so far and we are weighing all the options that have been suggested on this list (as well as some others in the committees), so please continue to send your ideas to the list (and please do not assume the rules will stay exactly as written at this point). In the interests of time, though, I would like to have the discussion wrapped up by April 7 (one week), so please send your ideas to the list as soon as possible. Also, if you have specific concerns with the rules but you are not sure what rule change would solve those concerns, please just write them down in a mail to the list, as someone else may have an idea how to solve them. Thanks! Christopher Head SSL TC Chair -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFYjbcACgkQnfE3lq0v9IxSdwD+LOzD5od0F6rBMuI45N/lhD5B +f2dQz5UhvjocQ7ij2gA/0ml2ylJ/p3cWo6y2CgoCHSTNziFoCjzCfC9rfX8V+Xd =/gwR -----END PGP SIGNATURE----- From jgurzoni at yahoo.com.br Tue Apr 2 19:27:09 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Tue, 2 Apr 2013 20:27:09 -0300 Subject: [robocup-small] Registration codes and financial support confirmation reminder Message-ID: <001601ce2ff9$99d469c0$cd7d3d40$@yahoo.com.br> Greetings to everybody ! We would like to remind that early registration for RoboCup 2013 is already open and that the registration codes were sent today to all qualified teams. If your team did not receive it in the address provided during qualification, please check your mailbox's spam folder for the email from "RoboCup SSL Organization". If you do not receive it or have difficulties to use, please email the OC, rc-ssl-oc[at]lists.robocup.org We would like also to remind teams to send the financial support confirmation (details on the qualification page) by April 15th. Regards Angelo On behalf of the SSL OC for RoboCup 2013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From joydeepb at ri.cmu.edu Sat Apr 6 11:27:43 2013 From: joydeepb at ri.cmu.edu (Joydeep Biswas) Date: Sat, 6 Apr 2013 11:27:43 -0400 Subject: [robocup-small] Rules clarification: Goalie contact Message-ID: Hi, Section 12.1 says a direct free kick is awarded to the opposing team if a robot makes substantial contact with an opponent. In addition, 12.2 says that a penalty kick will be awarded to the opposing team if such contact occurs in the own defense area. This means that if the yellow goalie, in the yellow defense area, touches a blue robot in the yellow defense area while trying to defend against a goal, the blue team will be awarded a penalty kick. Did I read this correctly? If not, could the TC / OC please clarify? -Joydeep -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Sun Apr 7 02:56:44 2013 From: chead at chead.ca (Christopher Head) Date: Sat, 6 Apr 2013 23:56:44 -0700 Subject: [robocup-small] Rules clarification: Goalie contact In-Reply-To: References: Message-ID: <20130406235644.04631b79@kruskal.chead> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Joydeep, There are two reasons why this is not handled quite the way you read it. First, section 12.1 uses the phase ?substantial contact?; Law 12 Decisions of the Small Size League Technical Committee points out that ?substantial contact? is not just touching, it?s more serious contact where a moving robot hits a slow or stopped robot. Second, the above observation doesn?t even matter: section 12.3 states that ?an indirect free kick is awarded to the opposing team if a robot contacts the goalkeeper where the point of contact is in the defense area?. This is the usual interference with the goalie rule, and it has not been changed at all this year; therefore, in the situation you describe, assuming the point of contact is in the defense area, *yellow* would get an indirect free kick. This naturally takes precedence over any other rules regarding substantial contact in general, and this applies to any contact at all, not just substantial contact. Chris On Sat, 6 Apr 2013 11:27:43 -0400 Joydeep Biswas wrote: > Hi, > > Section 12.1 says a direct free kick is awarded to the opposing team > if a robot makes substantial contact with an opponent. In addition, > 12.2 says that a penalty kick will be awarded to the opposing team if > such contact occurs in the own defense area. > This means that if the yellow goalie, in the yellow defense area, > touches a blue robot in the yellow defense area while trying to > defend against a goal, the blue team will be awarded a penalty kick. > > Did I read this correctly? If not, could the TC / OC please clarify? > > -Joydeep -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFhGK8ACgkQnfE3lq0v9Iw4rQD/VUFfad61Ve1WkvcMmZbf4ZUT z5jvU76v8ZirvkpWxtwA/1PCfHtSLGUg+3zMejObN3214IlQnsFiMzFcQFlRrdw8 =B8oQ -----END PGP SIGNATURE----- From jpmendoza at ri.cmu.edu Mon Apr 8 15:15:03 2013 From: jpmendoza at ri.cmu.edu (Juan Pablo Mendoza) Date: Mon, 8 Apr 2013 15:15:03 -0400 Subject: [robocup-small] Rules clarification: Goalie contact In-Reply-To: <20130406235644.04631b79@kruskal.chead> References: <20130406235644.04631b79@kruskal.chead> Message-ID: Hi Chris, I have a followup question to this. Does *any* contact with the goalie in the defense area result in a free kick for the goalie's team? In particular, consider these situations: - The ball is in yellow's defense area. A blue robot and the yellow goalie are in it too. Yellow goalie then drives quickly into the ball (blue robot may be stopped), and in the process makes substantial contact with the blue robot. - The ball is in yellow's defense area. A blue robot and the yellow goalie are in it too. Yellow goalie then intentionally drives into the blue robot, not minding the location of the ball. - The ball is NOT in yellow's defense area. A blue robot and the yellow goalie are in yellow's defense area. Yellow goalie then intentionally (or unintentionally) drives into the blue robot. Would all of these result in an indirect free kick for yellow? Thank you, JP On Sun, Apr 7, 2013 at 2:56 AM, Christopher Head wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi Joydeep, > There are two reasons why this is not handled quite the way you read it. > > First, section 12.1 uses the phase ?substantial contact?; Law 12 > Decisions of the Small Size League Technical Committee points out that > ?substantial contact? is not just touching, it?s more serious contact > where a moving robot hits a slow or stopped robot. > > Second, the above observation doesn?t even matter: section 12.3 states > that ?an indirect free kick is awarded to the opposing team if a robot > contacts the goalkeeper where the point of contact is in the defense > area?. This is the usual interference with the goalie rule, and it has > not been changed at all this year; therefore, in the situation you > describe, assuming the point of contact is in the defense area, > *yellow* would get an indirect free kick. This naturally takes > precedence over any other rules regarding substantial contact in > general, and this applies to any contact at all, not just substantial > contact. > > Chris > > On Sat, 6 Apr 2013 11:27:43 -0400 > Joydeep Biswas wrote: > > > Hi, > > > > Section 12.1 says a direct free kick is awarded to the opposing team > > if a robot makes substantial contact with an opponent. In addition, > > 12.2 says that a penalty kick will be awarded to the opposing team if > > such contact occurs in the own defense area. > > This means that if the yellow goalie, in the yellow defense area, > > touches a blue robot in the yellow defense area while trying to > > defend against a goal, the blue team will be awarded a penalty kick. > > > > Did I read this correctly? If not, could the TC / OC please clarify? > > > > -Joydeep > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlFhGK8ACgkQnfE3lq0v9Iw4rQD/VUFfad61Ve1WkvcMmZbf4ZUT > z5jvU76v8ZirvkpWxtwA/1PCfHtSLGUg+3zMejObN3214IlQnsFiMzFcQFlRrdw8 > =B8oQ > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Mon Apr 8 15:55:04 2013 From: chead at chead.ca (Christopher Head) Date: Mon, 8 Apr 2013 12:55:04 -0700 Subject: [robocup-small] Rules clarification: Goalie contact In-Reply-To: References: <20130406235644.04631b79@kruskal.chead> Message-ID: <20130408125504.5955ec00@ritchie.cs.ubc.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 As written, yes, those all count as interference with the goalie?it doesn?t matter where the ball is. It is blue?s responsibility to get out of the way if yellow?s goalie wants to move, period. It?s therefore quite dangerous for a blue robot to go into yellow?s defense area, though legal if you?re careful. In all cases, though, remember that this only counts if the point of contact is within the defense area. The goalie cannot ram an opponent just outside the defense area?even if the goalie is partly inside the defense area, as long as the point of contact is outside, the rule doesn?t apply. While this may seem a bit extreme, this rule has been on the books since 2006 and, in my experience from attending the last few years of RoboCup, ?interference with the goalie? is called from time to time, but not excessively often. Chris On Mon, 8 Apr 2013 15:15:03 -0400 Juan Pablo Mendoza wrote: > Hi Chris, > > I have a followup question to this. Does *any* contact with the > goalie in the defense area result in a free kick for the goalie's > team? In particular, consider these situations: > - The ball is in yellow's defense area. A blue robot and the yellow > goalie are in it too. Yellow goalie then drives quickly into the ball > (blue robot may be stopped), and in the process makes substantial > contact with the blue robot. > - The ball is in yellow's defense area. A blue robot and the yellow > goalie are in it too. Yellow goalie then intentionally drives into > the blue robot, not minding the location of the ball. > - The ball is NOT in yellow's defense area. A blue robot and the > yellow goalie are in yellow's defense area. Yellow goalie then > intentionally (or unintentionally) drives into the blue robot. > > Would all of these result in an indirect free kick for yellow? > > Thank you, > JP -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlFjIJsACgkQMcVpqLZH/3zjbgD9EHmEMdcZ2XI06W3eF5y2Bmhi xyZ7K5UJr/65LhZDHS4A/RfdIsgjH19CbbNszTdN/chg6fTWoRp0EMQHd5BYyWJE =tAt7 -----END PGP SIGNATURE----- From chead at chead.ca Sun Apr 21 12:44:02 2013 From: chead at chead.ca (Christopher Head) Date: Sun, 21 Apr 2013 09:44:02 -0700 Subject: [robocup-small] New Rules In-Reply-To: <20130331122540.1cd74139@kruskal.chead> References: <20130316230147.7c7b20d1@kruskal.chead> <20130327211947.2a47e9fd@kruskal.chead> <003301ce2bc6$68d0dac0$3a729040$@yahoo.com.br> <20130331122540.1cd74139@kruskal.chead> Message-ID: <20130421094402.6ef385b3@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello again everyone, After some discussion and a vote from the six TC members, it was decided that the whole new chip goal rule will be discarded and RoboCup 2013 will be played with RoboCup 2012?s chip goal rules. The new rules have been published on the wiki. Christopher Head SSL TC Chair On Sun, 31 Mar 2013 12:25:40 -0700 Christopher Head wrote: > Hi teams, > It seems the new chip goal rule has stirred up quite a lot of > discussion. This is a big change, and we expected it would be somewhat > controversial. Please bear with us; we wanted to get the rules out in > front of the teams as soon as they were ready, but because this is > such a major change, and because a number of people have commented > that they are not comfortable with it, we ARE still discussing the > details and we are still open to changing things. We appreciate the > input that has been given so far and we are weighing all the options > that have been suggested on this list (as well as some others in the > committees), so please continue to send your ideas to the list (and > please do not assume the rules will stay exactly as written at this > point). > > In the interests of time, though, I would like to have the discussion > wrapped up by April 7 (one week), so please send your ideas to the > list as soon as possible. > > Also, if you have specific concerns with the rules but you are not > sure what rule change would solve those concerns, please just write > them down in a mail to the list, as someone else may have an idea how > to solve them. > > Thanks! > Christopher Head > SSL TC Chair -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlF0F1IACgkQnfE3lq0v9Iy7DwD/b3SuDzUg3vBTfwrF6Iw1qrDH wmVsUQsgZMgiRFITl6YA/if2h4juKrPOEUcUJ4IWnvn3O8LQJeqO6otz38osK0Ic =eio9 -----END PGP SIGNATURE----- From k0tqr0_1116 at ybb.ne.jp Tue Apr 23 03:00:58 2013 From: k0tqr0_1116 at ybb.ne.jp (Kotaro Yasui) Date: Tue, 23 Apr 2013 16:00:58 +0900 Subject: [robocup-small] About a bug of new Referee Box Message-ID: <002401ce3ff0$4fd6a110$ef83e330$@ne.jp> Dear RefBox developers, We tested the new Referee Box released in 2013 (candidate 2). Then, we found out the 'cmd_counter' value of the Legacy Packet is NOT incremented when any command is issued from the Referee Box. Isn't this a bug? legacypublisher.cc:60 is written as: packet[1] = counter; But we guess it should be as follows: packet[1] = static_cast(state.referee().command_counter()); Would you confirm (or check) if it's correct. Best regards, Kotaro Yasui -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Tue Apr 23 15:25:04 2013 From: chead at chead.ca (Christopher Head) Date: Tue, 23 Apr 2013 12:25:04 -0700 Subject: [robocup-small] About a bug of new Referee Box In-Reply-To: <002401ce3ff0$4fd6a110$ef83e330$@ne.jp> References: <002401ce3ff0$4fd6a110$ef83e330$@ne.jp> Message-ID: <20130423122504.2839cd68@ritchie.cs.ubc.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Thanks for testing and reporting, and you are absolutely correct that this is a bug and that this is the right way to fix it. I have fixed that, plus another bug that published the wrong value for Stage Time Left in the legacy protocol. I plan to put release candidate 3 on the wiki this evening with both bugs fixed. Chris On Tue, 23 Apr 2013 16:00:58 +0900 "Kotaro Yasui" wrote: > Dear RefBox developers, > > We tested the new Referee Box released in 2013 (candidate 2). > Then, we found out the 'cmd_counter' value of the Legacy Packet is > NOT incremented when any command is issued from the Referee Box. > Isn't this a bug? > > legacypublisher.cc:60 is written as: > packet[1] = counter; > > But we guess it should be as follows: > packet[1] = static_cast(state.referee().command_counter()); > > Would you confirm (or check) if it's correct. > > Best regards, > Kotaro Yasui > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlF24BAACgkQMcVpqLZH/3yOdgD/Q6SYEyOWO0OTaXuHtLF/OvIy gYfsqN8j7dEvAdL5hSEBAJKrLtKXSildh5zUH3Jfxh4g9TGqnC+8rEYIjScPSHeK =acq2 -----END PGP SIGNATURE----- From chead at chead.ca Tue Apr 23 22:01:34 2013 From: chead at chead.ca (Christopher Head) Date: Tue, 23 Apr 2013 19:01:34 -0700 Subject: [robocup-small] About a bug of new Referee Box In-Reply-To: <20130423122504.2839cd68@ritchie.cs.ubc.ca> References: <002401ce3ff0$4fd6a110$ef83e330$@ne.jp> <20130423122504.2839cd68@ritchie.cs.ubc.ca> Message-ID: <20130423190134.46c940e1@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Release candidate 3 is now up on the wiki. Chris On Tue, 23 Apr 2013 12:25:04 -0700 Christopher Head wrote: > Hello, > Thanks for testing and reporting, and you are absolutely correct that > this is a bug and that this is the right way to fix it. I have fixed > that, plus another bug that published the wrong value for Stage Time > Left in the legacy protocol. I plan to put release candidate 3 on the > wiki this evening with both bugs fixed. > > Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlF3PP4ACgkQnfE3lq0v9IwB+wD9E8UZZ+jHm9/GEqQ0GP/Wwq2N Mmai+ryHgulYxX88u8sA/1xNqzpTYT1D5JQmLPxWzEn6WvE5jJLDEEI0MsII1s07 =+snp -----END PGP SIGNATURE----- From chead at chead.ca Sun Apr 28 23:22:02 2013 From: chead at chead.ca (Christopher Head) Date: Sun, 28 Apr 2013 20:22:02 -0700 Subject: [robocup-small] Scoreboard Information Message-ID: <20130428202202.40fc8978@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, A new feature we plan to introduce at this year?s competition is scoreboards for the fields. The scoreboard will show the game clock and stage along with the two teams? scores. To identify the teams, the scoreboard will display the team names, and it is also optionally able to display a team logo and national flag. Therefore, I need two things: (1) Please check and ensure your team name is shown with proper spelling, punctuation, and capitals, the way you want it to appear on the scoreboard. If it?s wrong, please tell me the proper name. (2) If you want a logo and/or national flag shown on the scoreboard, please send those files to me personally (not to the list!). You can send one image (which will be shown below your name) or two images (a logo and a flag, to be shown side by side). Your images should be at least a few hundred pixels, so they scale nicely to the full screen. Also, the background of the scoreboard is black, so if your logo (or flag, for a few countries) is not rectangular, you should send me either an image with a black background or, better, an image with proper transparency information (transparent GIF or PNG with alpha channel), otherwise there will be a coloured rectangle behind your logo or flag. Preferably all images should be in PNG format as that is what the scoreboard uses. You can send me other formats, but it would be better if you convert to PNG so you can make sure the conversion comes out right. If you?re not sure whether your image is acceptable, I can put it in the scoreboard and send you a screenshot. Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlF952AACgkQnfE3lq0v9Izn1AD+L4BZghCenCmyfr3isMhn51I5 73sD9WGosC/1EiqaDOgA/3KG2ToynmfU9yGqRtGJkhAd/dN0oY0+AlBmaL8/CO/9 =ZyNp -----END PGP SIGNATURE----- From michael.bleier at robotics-erlangen.de Thu May 16 03:44:55 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Thu, 16 May 2013 09:44:55 +0200 Subject: [robocup-small] Announcement Mixed Team Tournament Message-ID: <51948E77.3070600@robotics-erlangen.de> Dear teams, I am happy to announce the Mixed Team Tournament at RoboCup 2013. The details are published on the leagues's wiki, at http://robocupssl.cpe.ku.ac.th/robocup2013:mixed_team_tournament. Please sign up for the Mixed Team Tournament by sending a confirmation e-mail to the Organizing Committee (rc-ssl-oc at lists.robocup.org) until May 31st. We will play 8 versus 8 robots (4 robots per sub-team). Goals only count if robots from both sub-teams have touched the ball. An extra goal is awarded if a goal is achieved by a pass between two different sub-teams. The big change this year is that the Mixed Team Tournament will be held on a large field (double the size of a standard SSL field). To provide vision data we will run SSL-Vision with four cameras. Hence, teams need to ensure that their software and tracking algorithms are capable of handling vision input originating from four different camera processing stacks. Logs from the large field demo at RoboCup 2011 are available for download at the SSL-Vision project page at https://code.google.com/p/ssl-vision/downloads/list. The logs can be played back with the log client available in the SSL-Vision repository for testing purposes. Tigers Mannheim have provided a much appreciated patch to run SSL-Vision with four cameras. Nevertheless, at the competitions we will probably run SSL-Vision on two separate PCs. Therefore, the vision packets might come from two different IPs and the timestamps are not necessarily synchronized. If this would prohibit your team from participating in the Mixed Team Tournament or you have any questions, please feel free to contact this list or the Technical Committee (rc-ssl-tc at lists.robocup.org). Cheers, Michael Bleier From michael.bleier at robotics-erlangen.de Fri May 17 06:49:58 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Fri, 17 May 2013 12:49:58 +0200 Subject: [robocup-small] SSL Radio Link Specifications Survey Message-ID: <51960B56.2070707@robotics-erlangen.de> Dear teams, If your team is qualified or even conditionally qualified for RoboCup 2013, please fill out the following survey: https://docs.google.com/forms/d/14SpxMjIsxt59dVeF4A7rKfc35qDLKP_ijSOin18YGVE/viewform This will help to determine if there is any interference between the radio modules used by SSL teams. In order to avoid interference with other leagues that use WLAN devices (SPL, MSL, Humanoid) please select your channels preferably outside the frequency range of 802.11b WLAN channels 1 - 11 (2.400 - 2.474 GHz). Cheers, Michael Bleier From michael.bleier at robotics-erlangen.de Tue May 21 02:17:08 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Tue, 21 May 2013 08:17:08 +0200 Subject: [robocup-small] Announcement Technical Challenges Message-ID: <519B1164.1050102@robotics-erlangen.de> Dear teams, This year two technical challenges will be held at RoboCup 2013. The details are published on the leagues's wiki, at http://robocupssl.cpe.ku.ac.th/robocup2013:technical_challenges. Please sign up for the technical challenges by sending a confirmation e-mail to the Organizing Committee (rc-ssl-oc at lists.robocup.org) until May 31st. If you have any questions, please feel free to contact this list or the Technical Committee (rc-ssl-tc at lists.robocup.org). Cheers, Michael Bleier From erdinc at neu.edu.tr Fri May 24 12:40:40 2013 From: erdinc at neu.edu.tr (Ali =?UTF-8?B?RXJkaW7DpyBLw7Zyb8SfbHU=?=) Date: Fri, 24 May 2013 19:40:40 +0300 Subject: [robocup-small] SSL-Monitor Message-ID: <20130524194040.46de09201bc4a1def18c222e@neu.edu.tr> Dear Friends, Since 2 or 3 months we have been working on a software project called ssl-monitor. It's a tool for broadcasting an ongoing game in 2D graphics to web, so people can watch it live. It supports broadcasting of both ongoing games in real-time or replays of pre-recorded games. In order to watch it, you just need a modern web browser. ssl-monitor consists of two components: * capturer * broadcaster Capturer component captures packets orginating from the vision server and refbox and then transmits them to broadcaster. Optionally it can record them as a pcap file, for replay purposes, or just play from a pcap file as well. Broadcaster component can be hosted on somewhere else and it receives the packets from capturer, processes them and then serves them over websockets. And client side code draws them on the Canvas. ssl-monitor is mostly written in Python, it uses Twisted, Tornado and Flask mainly. As you know its hard to make a live broadcast from field, we would like to record and broadcast (2D) the games. If you have pcap files and time we hope you can test and report bugs etc. http://robotics.neu.edu.tr/ssl-monitor/ -- N = R* ? fp ? ne ? fl ? fi ? fc ? L Ali Erdin? K?ro?lu < erdinc ? neu.edu.tr > CIO, Near East University Chairman, Near East University Advanced Research Center http://www.neu.edu.tr From jansegre at gmail.com Fri May 24 13:07:28 2013 From: jansegre at gmail.com (Jan) Date: Fri, 24 May 2013 14:07:28 -0300 Subject: [robocup-small] SSL-Monitor In-Reply-To: <20130524194040.46de09201bc4a1def18c222e@neu.edu.tr> References: <20130524194040.46de09201bc4a1def18c222e@neu.edu.tr> Message-ID: We (and probably more teams) have had very very similar ideas but hadn't had the time to implement anything. I'm keen to testing and contributing to it. It's very likely that we'll be able to host one or more broadcasters to help balancing in case it gets popular quickly, and lower delays for nearby locations. -- Cheers, Jan Segre RoboIME On Fri, May 24, 2013 at 1:40 PM, Ali Erdin? K?ro?lu wrote: > Dear Friends, > Since 2 or 3 months we have been working on a software project called > ssl-monitor. > > It's a tool for broadcasting an ongoing game in 2D graphics to web, so > people can watch it live. > It supports broadcasting of both ongoing games in real-time or replays of > pre-recorded games. > In order to watch it, you just need a modern web browser. > > ssl-monitor consists of two components: > * capturer > * broadcaster > > Capturer component captures packets orginating from the vision server and > refbox and then transmits > them to broadcaster. Optionally it can record them as a pcap file, for > replay purposes, or just play from > a pcap file as well. > > Broadcaster component can be hosted on somewhere else and it receives the > packets from capturer, > processes them and then serves them over websockets. And client side code > draws them on the Canvas. > ssl-monitor is mostly written in Python, it uses Twisted, Tornado and > Flask mainly. > > As you know its hard to make a live broadcast from field, we would like to > record and broadcast (2D) the games. > If you have pcap files and time we hope you can test and report bugs etc. > > http://robotics.neu.edu.tr/ssl-monitor/ > > -- > N = R* ? fp ? ne ? fl ? fi ? fc ? L > > Ali Erdin? K?ro?lu < erdinc ? neu.edu.tr > > CIO, Near East University > Chairman, Near East University Advanced Research Center > http://www.neu.edu.tr > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Wed May 29 15:18:28 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Wed, 29 May 2013 16:18:28 -0300 Subject: [robocup-small] FW: RoboCup 2013 Eindhoven, the Netherlands [Newsletter #4] Message-ID: <005101ce5ca1$4e1608c0$ea421a40$@yahoo.com.br> [cid:image002.jpg at 01CE5BFF.352999F0] CONTENTS 1. Preface 2. Update on cargo delivery 3. About Eindhoven 4. Introducing two RoboCup 2013 sponsors: a. ASML b. MathWorks 5. Important dates 6. Promote RoboCup 2013 7. RoboCup 2013 mascots 8. Contact 1. Preface Hopefully your final developments and preparations for RoboCup 2013 are well on its way and will allow you to play attractive and winning games, both from a scientific and competition perspective. We are looking forward to seeing your innovations and achievements. To help you to get the best result out of RoboCup 2013 we are working hard with a big team to prepare everything you need. In this fourth newsletter we would like to inform you about the updated schedule for cargo delivery, the city of Eindhoven, two of our main sponsors and ways you can promote RoboCup 2013 in your school, university or company. Finally, be aware that the deadline for team registration is approaching fast. 2. Update on cargo delivery To allow all teams to receive their robots as soon as possible after they arrive at the venue, we have enlarged the periods in which the cargo can be received on Monday and Tuesday to 9 ? 17 hr. Please note that every team is still responsible for receiving their own goods at the venue. RoboCup 2013 will not receive or store any goods. You can find the Major and Junior schedules on our website using the links below. On the website you can also download a PDF version of the schedule. Major schedule: http://www.robocup2013.org/major-leagues-schedule/ Junior schedule: http://www.robocup2013.org/junior-leagues-schedule/ 3. About Eindhoven Eindhoven is unmistakably the most adventurous city in the south of The Netherlands. The country?s fifth-largest city offers everything you need to make life enjoyable! A bustling city center with a huge variety of shops, numerous bars, pubs and restaurants, welcoming terraces, a lively nightlife, an overflowing events calendar and art and culture of the highest quality! But Eindhoven also has a rich historical background. Let Eindhoven surprise you Walking through the streets of Eindhoven you will see a young, modern city. But looks can be deceiving Eindhoven is in fact one of the oldest cities in The Netherlands and has a very interesting history! It received city rights back in 1232. A lively cigar and textile industry developed along the Dommel river. In the Villa park (city center) you can still see the imposing villas and mansions built by industrialists who settled here. The creation of the light-bulb in 1891 by Philips and the first DAF truck a little later was the beginning of the development and flourishing of the city. Traces of this industrial history can still be found when visiting Eindhoven. Since then Eindhoven has grown to become one of the most prominent cities of Europe in the fields of technology, knowledge and design. Many top-class international high-tech companies are now located in Eindhoven. The Technical University, Fontys High Schools and the Design Academy continue to attract students from all over the world. Modern architecture also found their place in Eindhoven. Some must-sees in Eindhoven: ? Stratumseind This 225 meter long street has the most bars and other nightlife possibilities from Eindhoven. The venue De Effenaar at the Dommelstraat is also worth your visit. ? Philips stadium The Philips stadium is the home base of soccer club PSV. ? Van Abbemuseum The Van Abbemuseum is one of the leading museums for modern and contemporary art. The impressive collection includes works of Picasso, Chagall, Kandinsky, El Lissitzky, Theo van Doesburg, Mondriaan and Appel. ? DAF-Museum You can see here the first cars developed by DAF. ? Sint Catharinakerk This church is designed by the famous architect Pierre Cuypers, he also designed the Rijksmuseum and the train station Centraal Station in Amsterdam. ? Evoluon The Evoluon is well known. This ?flying saucer? used to be a museum, but nowadays it is a convention center. ? Shopping in Eindhoven Besides the shopping streets in the inner city of Eindhoven, the indoor shopping centers De Heuvelgalerie and the Piazza Centre offer you the ultimate shopping experience. Source: www.vvveindhoven.nl 4. Introducing two RoboCup 2013 sponsors In this section we would like to introduce to you two of our sponsors for RoboCup 2013, ASML and MathWorks. These two sponsors will also be present at the event. If you want to find out more about job opportunities or technical possibilities, pay them a visit. a. ASML For engineers who think ahead ASML is a successful high-tech company headquartered in the Netherlands, which manufactures complex lithography machines that chip manufacturers use to produce integrated circuits. The steady progress of the world?s technological evolution through smaller, faster, smarter, more energy-efficient yet more affordable chips is to a large extent the result of technological breakthroughs at ASML. In the space of almost thirty years we have grown from nothing into a multinational with 55 locations in 16 countries and annual sales of 5.6 billion Euros in 2011. Behind ASML?s technological breakthroughs are engineers who think ahead. The people who work at ASML include some of the most creative minds in physics, mathematics, chemistry, mechatronics, optics, mechanical engineering, software engineering, and computer science. And, because ASML spends more than half a billion Euros per year on R&D, our people have the freedom and the resources to push the boundaries of known technology. They work in close-knit, multidisciplinary teams and each day they listen to, learn from and exchange ideas with each other. The ideal environment for growth With such a diverse technology culture, generous R&D budget, and a collective determination to create, develop and perfect entirely new technologies ASML represents the ideal environment for professional development and personal growth. If you have an unbridled passion for technology and want to be part of a team that tries out new ideas each day and constantly searches for better, more accurate, and faster ways of doing things, then visit www.asml.com/careers and send us your application. b. MathWorks MathWorks is the leading developer of mathematical computing software. MATLAB, the language of technical computing, is a programming environment for algorithm development, data analysis, visualization, and numeric computation. Simulink is a graphical environment for simulation and Model-Based Design of multi-domain dynamic and embedded systems. Engineers and scientists worldwide rely on these product families to accelerate the pace of discovery, innovation, and development in automotive, aerospace, electronics, financial services, biotech-pharmaceutical, and other industries. MathWorks products are also fundamental teaching and research tools in the world?s universities and learning institutions. Student competitions bridge classroom theory with hands-on learning of industry practices and technologies and are important vehicles for educating the engineers of tomorrow. RoboCup is an excellent example of project-based learning for which MATLAB and Simulink are already used extensively. MathWorks wants to show the student teams, the universities and the visitors the capabilities offered by its software and explore the possibility to apply them wider and more efficiently to the design of new robot technology. MathWorks also sees it as a social responsibility to contribute to society by stimulating our next generation to become interested in technology. The company mission is to accelerate the pace of science and technology. All RoboCup teams get complementary licenses for MATLAB, Simulink and other useful software that they offer and that you can use for preparing: http://www.mathworks.nl/academia/student-competitions/robocup/resources.html 5. Important dates In the tables below you can find the important dates of the major competitions, the junior competitions and the symposium. Team registration for both the major and junior leagues is possible until May 31. If you have not yet registered your team, make sure not to miss this deadline. a. Major leagues Competitions June 27 ? 30 Demonstration games and setup June 26 Setup June 24 ? 25 Late registration June 1 ? 23 Regular registration(1) May 1 ? 31 Early registration deadline March 1 ? April 30 Deadline for completion of qualification in each RoboCup league(2) March 15 Team Pre-Registration Deadline(2) February 15 (1) No team registration accepted after May 31. (2) Pre-registration and qualification deadlines may vary for some leagues. b. Junior leagues Junior workshop at symposium July 1 Competitions June 27 ? 30 Setup June 26 Late registration June 1 ? 23 Registration(1) April 1 - May 31 Pre-registration by national or regional representatives March 1 - May 4 Release of team allocations (quota for each country/region) February 28 Submission of placeholder applications by regional representatives January 28 ? February 20 (1) No team registration accepted after May 31. c. Symposium The symposium will take place on July 1 in the auditorium of the Eindhoven University of Technology ( www.tue.nl). Besides the oral and poster presentations, there will be two invited speakers, Raffaelo d'Andrea (ETH) and Chad Jenkins (Brown Univ). 6. Promote RoboCup 2013 Your help is crucial in promoting and maximizing public engagement for RoboCup 2013. You can do this by following us on twitter< https://twitter.com/robocup2013> and/or liking us on facebook< http://www.facebook.com/RoboCup2013>. Don't hesitate to share RoboCup-related content with us through these social media. Furthermore, we are looking for your stories to publish on the RoboCup 2013 website. How is your team preparing for the tournament? Did you participate in regional RoboCup events? Did you demonstrate your robots at a special occasion? Let us know! Send your story, if possible with some pictures or a video, to website at robocup2013.org Promoting RoboCup at your institution is another way to make more people aware of the upcoming event. We have created a short video< http://www.robocup2013.org/trailer-robocup-2013-2/?lang=en> that you can share on your website or show during classes. The video file, and some other materials to promote RoboCup, can be downloaded here< http://www.robocup2013.org/downloads/>. 7. RoboCup 2013 mascots With less than five weeks until RoboCup 2013 we would like to introduce all participants to a very special family of robot mascots. Most of you are familiar already with the yellow/orange robot that appears on our posters, website and in the header of this newsletter. Recently, it has been named Robot Robin in a Facebook poll< https://www.facebook.com/questions/461837863908880/>. A group of students of the St. Lucas College in Eindhoven now presents the rest of our robot mascots. You'll see more from them in the near future! [cid:image001.png at 01CE5BFF.F0227060] 8. Contact For questions regarding RoboCup 2013, please contact one of the mail addresses below. General: info at robocup2013.org Chairs: chair at robocup2013.org Competitions: competitions at robocup2013.org Good luck with the final preparations. We are looking forward to welcoming you all at the Genneper Parcs in Eindhoven for RoboCup 2013. On behalf of the RoboCup 2013 organization. Best regards, Roel Merry & Ren? van de Molengraft (co-chairs RoboCup 2013) [cid:image005.jpg at 01CE5BFF.352999F0] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 19261 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 10526 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 336109 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RoboCup 2013 Eindhoven, the Netherlands [Newsletter #4].pdf Type: application/pdf Size: 318009 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Untitled attachment 00041.sdx URL: From jgurzoni at yahoo.com.br Thu Jun 6 13:02:56 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Thu, 6 Jun 2013 14:02:56 -0300 Subject: [robocup-small] Mixed Teams and Technical Challenges sign-up - Reminder Message-ID: <001101ce62d7$b2b37880$181a6980$@yahoo.com.br> Hello to everybody As we approach the competition, the OC and TC need to finish the schedule, including the Mixed Team tournament and Technical Challenges. For this reason, we ask teams interested in participating, but that have not confirmed yet, to email the OC (rc-ssl-oc at lists.robocup.org) until this Sunday, June 9. The details of the events and teams already signed up are published on the leagues' wiki Mixed Team Tournament http://robocupssl.cpe.ku.ac.th/robocup2013:mixed_team_tournament. Technical Challenges http://robocupssl.cpe.ku.ac.th/robocup2013:technical_challenges. Best Regards Angelo -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Fri Jun 7 23:54:45 2013 From: chead at chead.ca (Christopher Head) Date: Fri, 7 Jun 2013 20:54:45 -0700 Subject: [robocup-small] Reminder: Flags and Logos Message-ID: <20130607205445.1448a431@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Just a reminder to please send in your national flags and team logos if you want them shown in the scoreboard! Currently, I have flags and logos from the following teams: KIKS RoboDragons RoboFEI RoboIME STOx?s Thunderbots TIGERS Mannheim That means I need files from the following teams: BRocks CMDragons Cyrus EMEnents ER-Force (TIGERS? flag file is good, tell me if you want to use it) Immortals MCT Susanoo Logics (KIKS and RoboDragons have good flag files, tell me if you want to use them) MRL NEUIslanders Odens (KIKS and RoboDragons have good flag files, tell me if you want to use them) Parsian RFC Cambridge RoboJackets Skuba ZJUNlict Thanks, Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlGyqwgACgkQnfE3lq0v9IxGVwD+LYzk903d1gx5V3zDzbpPhVjB NglI38bGUy/oVT1h08sA/2ccE1qwyg/uosh5VePRlpJLNoV1nwyHNOANQzuXSOSZ =F0ry -----END PGP SIGNATURE----- From ersin at aytac.me Sat Jun 8 03:46:37 2013 From: ersin at aytac.me (Ersin AYTAC) Date: Sat, 8 Jun 2013 10:46:37 +0300 Subject: [robocup-small] Reminder: Flags and Logos In-Reply-To: <20130607205445.1448a431@kruskal.home.chead.ca> References: <20130607205445.1448a431@kruskal.home.chead.ca> Message-ID: <98D3E6D1-E278-4B16-94F1-0347ABE3EF0D@aytac.me> Hi, Attached is the our team logo and national flag. Best, On Jun 8, 2013, at 6:54 AM, Christopher Head wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi everyone, > Just a reminder to please send in your national flags and team logos if > you want them shown in the scoreboard! Currently, I have flags and > logos from the following teams: > > KIKS > RoboDragons > RoboFEI > RoboIME > STOx?s > Thunderbots > TIGERS Mannheim > > That means I need files from the following teams: > > BRocks > CMDragons > Cyrus > EMEnents > ER-Force (TIGERS? flag file is good, tell me if you want to use it) > Immortals > MCT Susanoo Logics (KIKS and RoboDragons have good flag files, tell me > if you want to use them) > MRL > NEUIslanders > Odens (KIKS and RoboDragons have good flag files, tell me > if you want to use them) > Parsian > RFC Cambridge > RoboJackets > Skuba > ZJUNlict > > Thanks, > Chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (GNU/Linux) > > iF4EAREIAAYFAlGyqwgACgkQnfE3lq0v9IxGVwD+LYzk903d1gx5V3zDzbpPhVjB > NglI38bGUy/oVT1h08sA/2ccE1qwyg/uosh5VePRlpJLNoV1nwyHNOANQzuXSOSZ > =F0ry > -----END PGP SIGNATURE----- > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Flag.jpg Type: image/jpg Size: 66028 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Logo.png Type: image/png Size: 164846 bytes Desc: not available URL: From michael.bleier at robotics-erlangen.de Sat Jun 8 14:35:11 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Sat, 08 Jun 2013 20:35:11 +0200 Subject: [robocup-small] SSL Radio Link Specifications Survey In-Reply-To: <51960B56.2070707@robotics-erlangen.de> References: <51960B56.2070707@robotics-erlangen.de> Message-ID: <51B3795F.5020502@robotics-erlangen.de> Hi everyone, Just a friendly reminder to please send in your radio link information. https://docs.google.com/forms/d/14SpxMjIsxt59dVeF4A7rKfc35qDLKP_ijSOin18YGVE/viewform We are still missing information from the following teams: BRocks Cyrus EMEnents Immortals MRL Parsian Skuba ZJUNlict Thanks! Michael On 05/17/2013 12:49 PM, Michael Bleier wrote: > Dear teams, > > If your team is qualified or even conditionally qualified for RoboCup > 2013, please fill out the following survey: > > https://docs.google.com/forms/d/14SpxMjIsxt59dVeF4A7rKfc35qDLKP_ijSOin18YGVE/viewform > > > This will help to determine if there is any interference between the > radio modules used by SSL teams. > > In order to avoid interference with other leagues that use WLAN devices > (SPL, MSL, Humanoid) please select your channels preferably outside the > frequency range of 802.11b WLAN channels 1 - 11 (2.400 - 2.474 GHz). > > Cheers, > Michael Bleier From iliaiust at yahoo.com Sat Jun 8 17:07:34 2013 From: iliaiust at yahoo.com (mohammad hosein fazeli) Date: Sat, 8 Jun 2013 14:07:34 -0700 (PDT) Subject: [robocup-small] from: mohammad hosein fazeli subject: Message-ID: <1370725654.96298.YahooMailNeo@web122405.mail.ne1.yahoo.com> http://www.westerbrink.org/zo.php -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Mon Jun 10 23:13:45 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Tue, 11 Jun 2013 00:13:45 -0300 Subject: [robocup-small] RoboCup 2013 Eindhoven, the Netherlands [Newsletter #5] Message-ID: <001e01ce6651$b0f874a0$12e95de0$@yahoo.com.br> CONTENTS 1. Preface 2. Risk & damages and photograph & video release forms 3. Opening ceremonies 4. Route to the venue 5. Introducing sponsors 6. Contact 1. Preface This is the last newsletter before RoboCup 2013. The final preparations have started and the construction of the venue is also already in progress. We are really looking forward to the event and to welcome you all to RoboCup 2013 in Eindhoven, the Netherlands. In this newsletter we would like to inform you regarding the risk & damages and the photograph and video release forms that should be signed before entering the venue. Besides this, you can find information about the opening ceremony for RoboCupJunior and the way to get to the venue. Finally, we would like to introduce more of our sponsors to you. Did you know that next to the venue De Tongelreep, one of the largest swimming centers in Europe, is located? For all participants of RoboCup 2013 we arranged an entrance fee of only 2 euro?s. So if you like to swim, don?t forget your swimwear! 2. Risk & damages and photograph & video release forms On the RoboCup 2013 website you can find an important document regarding (1) a notice on the risk of bodily or personal injury and/or property loss or damage and (2) a photograph and videotape release form. This document should be signed by all major and junior participants before entering the venue. To avoid delays in the registration process we kindly ask you to print and sign the two documents before the event and to bring the signed documents while registering. Note: Participants that are under 18 years old should have both documents signed by a parent or guardian. You can download the form on http://www.robocup2013.org/notice-to-participants/ or directly using this link. 3. Opening ceremonies On the 26th of June RoboCup 2013 will be opened with a spectacular show with dance, music and (high) voltage. For the senior participants the opening ceremony will take place at 16:00 hr followed by a drink. This year we will also have an opening ceremony for RoboCupJunior. This ceremony will be held on June 26 at 21:00 hr after the RoboCupJunior venue closes. Make sure you don?t miss this festive start of RoboCup 2013! You can find the Major and Junior schedules on our website using the links below. On the website you can also download a PDF version of the schedules. Major schedule: http://www.robocup2013.org/major-leagues-schedule/ Junior schedule: http://www.robocup2013.org/junior-leagues-schedule/ 4. Route to the venue Below you can find various ways of transport to the venue: RoboCup 2013 Antoon Coolenlaan 3 5644 RX Eindhoven Public Transport You can plan your journey by public transport at http://9292.nl/en, also for the journey from and to the hotels. With this site you can find how late the busses and trains depart and the prices of the trips. If you want to use public transport during your stay you can consider the OV-chip card. It is possible to travel cheaper by putting credit on the card. More information about the OV-chip card can be found here: http://www.ov-chipkaart.nl/aanvragen/welkekaartpastbiju/toeristen/. Airport Schiphol Amsterdam You can go easily with the train from Airport Schiphol Amsterdam to Eindhoven central station. Tickets can be bought in the machines a floor above the platforms but it is also possible to use the OV-chipcard for this trip (same price). >From Schiphol Amsterdam direct trains to Eindhoven depart every 30 minutes (16 and 46 minutes past the hour). Also, every 30 minutes a train departs that requires 1 change (every hour and 30 minutes past the hour); first take the train to Nijmegen, change at Utrecht to the train to Maastricht. The travel time takes approximately 1:30 hours. PAY ATTENTION: If you arrive after the 27th of June and for your journey back, there is work scheduled on the track between Eindhoven and Amsterdam from June 27 till July 11. There are two options: travel via Breda or travel on the normal track and take a bus between ?s-Hertogenbosch and Zaltbommel. Look at http://9292.nl/en for your best option. Unlike the say on the website, travelling with Fyra is surcharge-free during the proceedings. Airport Eindhoven >From Airport Eindhoven you can travel by bus to train station Eindhoven. You can take bus 401, which departs every 10 minutes during the day. Get out at Eindhoven station, terminus of the bus line. Train station Eindhoven If you participate in the Junior competitions you have to take from Eindhoven central station bus 17 and get off at the bus stop ?Eindhoven, Zwemcentrum Tongelreep?. If you participate in the Major competitions you can take bus 7, 170, 171 or 172, 184 and get off at the bus stop ?Eindhoven, Theo Koomenlaan?. You can use the OV-chip card for this trip, or buy a ticket in the bus (this is more expensive). On both bus stops information will be provided for the walking routes. Car When coming from the A58, A2 or A67 get onto the N2 road. When on the N2, take exit 33 ?Waalre/Valkenswaard?. After taking the exit, keep following signs for ?Genneper Parken?. After about 500 meters go left at the first traffic lights. For the senior competition you go left again after the water tower (Willem Elsschotlaan) and at the T-junction again to the left. This will lead you to the Indoor Sports Centre. You can only use the parking space next to the Indoor Sport Centre on Monday and Thursday, the other days you have to use the parking space at the swimming Centre. For the junior competition you have to stay on the Antoon Coolenlaan. You will see a big parking lot on your left. Taxi It is also possible to book a taxi from the airport/station to the venue. Click here: http://www.schiphol.nl/Travellers/ToFromSchiphol.htm for more information about taxis at Schiphol and click here: http://www.eindhovenairport.com/en/accessibility/by-taxi/ for more information about taxis at Eindhoven airport. The taxis at the central station in Eindhoven can be found next to the busses or at the centrum side of the station. 5. Introducing sponsors Accenture With a Technology Lab at the High Tech Campus in Eindhoven and leading clients such as Philips and ASML, Accenture is an active member of this innovative hotspot. Accenture wants to fuel enthusiasm for robotics and stimulate high-tech initiatives to register for the Innovation Awards through www.innovation-awards.nl. Accenture is a global management consulting, technology services and outsourcing company, with more than 261,000 people serving clients in more than 120 countries, more info on www.accenture.nl. Aldebaran Robotics Founded in 2005 by Bruno Maisonnier and now established in France, the US and China, ALDEBARAN ROBOTICS designs, produces and sells humanoid robots in order to contribute to humankind's well-being. There are currently over 3,500 units of the first NAO robot operating within schools and universities in over 70 countries worldwide to serve teaching and research. ALDEBARAN ROBOTICS has a team of more than 280 people, 40% of whom are engineers and doctors, involved in developing and producing its robots." Festo Festo Didactic is the world-leading equipment and solution provider for industrial education. We design and implement learning laboratories, educational equipment and programs that train people to perform in highly dynamic and complex industrial environments. Our goal is to maximize the learning success in educational institutions and industrial companies around the globe. Focal Focal Meditech is manufacturer and supplier of healthcare robotics serving the autonomy of handicapped persons. This type of robotics make activities like object manipulation, independent eating or drinking possible or support weak human arm function when lifting objects. Prominent products are wheelchair born robotmanipulator Jaco, mealtime robot MySpoon and Focal's dynamic arm supports like Darwing or McArm (under development). A specific type of healthcare robotics is social robotics- robots that aim at social interaction and contact e.g. for persons with dementia. A well- known robot in this domain is robotseal Paro which also is distributed by Focal. All these applications will be shown at the booth of Focal. In addition, handicapped persons will demonstrate their use of Jaco and a Paro playground is present. High Tech Campus Turning technology into business. High Tech Campus Eindhoven is an R&D ecosystem of more than 120 companies and institutes, and some 8,000 researchers, developers and entrepreneurs, who together are working on developing the technologies and products of tomorrow. The preferred work approach at the Campus is Open Innovation; Campus companies share knowledge, skills and R&D facilities in order to achieve faster, better and more customer-oriented innovation. (www.hightechcampus.com) KMWE KMWE is a supplier for the Hightech Industry and Aerospace. KMWE is specialized in the High Mix, Low Volume and High Complexity machining of critical components and the assembly of mechatronic Systems. KMWE is a located in Eindhoven, Malaysia and Turkey. Almost 60 years of experience, an international supplier network, over 300 employees and a continuous drive for Excellence enable us to meet the high demands of our customers. Maxon Motor Maxon Motor is the world leading supplier of high-precision drives and systems and proud sponsor of RoboCup 2013! Robots are capable of performing tasks and assisting people that (other) people are incapable of, they are improving life and creating opportunities to new application areas which move mankind forward. Supporting innovation and future applications of robotics is important to society and to us. Nobleo Nobleo is a consultancy and engineering company providing high-end expertise and job opportunities. Nobleo stands for ?noblesse oblige?, which we translate to ?talent is an obligation?, an obligation to perform. The Nobleo employees belong to the top experts in their fields. Oc? Oc? is part of the Canon Group, one of the best known brands in the world. It is active in the areas of Graphic Arts and Document Services. By creating better digital printing systems for technical drawing offices, company printrooms and commercial printers. Or developing more effective ways for people to manage their business critical documents. Our R&D organization is internationally recognized for creating winning technologies, product concepts and software in digital printing and document management. It employs over 2,000 people on 9 global sites. For more information visit http://ocecareers.com. PhenomWorld Phenom: Engineered in Eindhoven, exported to China, Japan, etc. - Fast, Outstanding. SEM imaging and analysis. Phenom desktop SEM systems give direct access to high-resolution and high-quality imaging and analysis required in a large variety of applications. An affordable, flexible and fast tool enabling engineers, technicians and educational professionals to investigate micron and submicron structures. Phenom: See sharp, discover more. ROBOTIS ROBOTIS is the world?s leading supplier of modular robotic actuators and educational platforms. Since 1999, ROBOTIS has developed innovative products for academic research and STEM education. In 2013, ROBOTIS is launching the DYNANMIXEL PRO - targeted for the full-scale, professional service robot market. ROBOTIS is the co-developer of the open-source humanoid DARwIn-OP and a member of the DARPA Robotics Challenge Track A: Team THOR. Segula Technologies Nederland Segula is a strong player in the field of engineering, consulting and associated services. The company is a project organization working for industries (OEM) in amongst others automotive, healthcare and high-tech components & systems industry. Segula Technologies guides its clients throughout the full life cycle of the product, from initial design to operational maintenance. www.segula.nl. TURTLE-5k The TURTLE-5k is a low cost soccer robot similar to the 2012 world champion of TechUnited (TU/e). It was redesigned by a consortium of 4 (industrial) partners who mainly focused on getting the cost price as low as possible. The original world champion costs per robot approximately ?26.000,- (cost price). This new robot will make it easier for new teams to enter the competition of the Middle-size League. 6. Contact For questions regarding RoboCup 2013, please contact one of the mail addresses below. General: info at robocup2013.org Chairs: chair at robocup2013.org Competitions: competitions at robocup2013.org See you all in a couple of weeks at the Genneper Parcs in Eindhoven. On behalf of the RoboCup 2013 organization. Best regards, Roel Merry & Ren? van de Molengraft (co-chairs RoboCup 2013) -------------- next part -------------- A non-text attachment was scrubbed... Name: RoboCup 2013 Eindhoven, the Netherlands [Newsletter #5].pdf Type: application/pdf Size: 311484 bytes Desc: not available URL: From chead at chead.ca Tue Jun 11 00:43:19 2013 From: chead at chead.ca (Christopher Head) Date: Mon, 10 Jun 2013 21:43:19 -0700 Subject: [robocup-small] Field Selection Message-ID: <20130610214319.0513c268@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, To determine how teams are assigned to fields, the OC and TC use a program that randomizes the distribution of teams subject to certain constraints (avoiding placing too many very-high-level, very-low-level, or same-country teams on the same field). To allow independent verification of results, the program runs deterministically based on random seed numbers provided as input. Here is how we will select those seed numbers for RoboCup 2013, presenting the selection mechanism before the data is available to avoid any possible bias: The FIFA Confederation Cup is coming up soon, with the first game on June 15. We will take the first two goals scored in the Confederation Cup and use the time, in minutes, at which the goals were scored, from the match reports on the FIFA website. Based on this, we hopefully will be able to publish our field assignments this coming weekend. Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlG2qucACgkQnfE3lq0v9IwMxgD+OooWY63OLm+NIJtGba4NQpDb cSJrc+6/5kSf5EGx9msA/20pm6zVqhKqk7hVHZ+rswuLlaNTED1ti6v8ctYVfVFJ =Acxt -----END PGP SIGNATURE----- From shahzad31comp at gmail.com Sat Jun 15 08:32:58 2013 From: shahzad31comp at gmail.com (MUHAMMAD SHAHZAD) Date: Sat, 15 Jun 2013 17:32:58 +0500 Subject: [robocup-small] Bug in referee release 4 Message-ID: Hi is it only me or everyone is having problem with referee box release four it is sending garbage packet after every two packets . -------------- next part -------------- An HTML attachment was scrubbed... URL: From hadi.bmohammadi at gmail.com Sat Jun 15 12:18:10 2013 From: hadi.bmohammadi at gmail.com (Hadi beik mohammadi) Date: Sat, 15 Jun 2013 20:48:10 +0430 Subject: [robocup-small] MRL logo and national flag Message-ID: Hi , sorry for late response our team logo and national flag attached to this mail i hope see you soon -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MRL.jpg Type: image/jpeg Size: 242032 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Iran_Flag.gif Type: image/gif Size: 27644 bytes Desc: not available URL: From chead at chead.ca Sat Jun 15 16:14:12 2013 From: chead at chead.ca (Christopher Head) Date: Sat, 15 Jun 2013 13:14:12 -0700 Subject: [robocup-small] Bug in referee release 4 In-Reply-To: References: Message-ID: <20130615131412.5bf250a2@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi there, I haven't seen this problem myself. To help debug, can you tell me which protocol you are using (Protobuf or legacy)? Thanks, Chris MUHAMMAD SHAHZAD wrote: >Hi is it only me or everyone is having problem with referee box release >four it is sending garbage packet after every two packets . -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlG8yxQACgkQnfE3lq0v9Izz/AD/cJHyurqa3yE02iXIjkT/4WmO fkGK3AnB7Xzx+SiwJNgA/RZ3pYDQt/U0vptY4HshcNLh2tgTV3Y6bPjIBk1iDRGh =FHBk -----END PGP SIGNATURE----- From jgurzoni at yahoo.com.br Wed Jun 19 18:37:30 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Wed, 19 Jun 2013 19:37:30 -0300 Subject: [robocup-small] SSL Groups announcement Message-ID: <006601ce6d3d$96a87c60$c3f97520$@yahoo.com.br> Hello everybody On behalf of the OC and TC, I would like to announce that the groups for the SSL Competition 2013 is posted at the League's wiki, at http://robocupssl.cpe.ku.ac.th/robocup2013:schedule We wish a safe trip and good luck to all teams !! Best Regards Angelo On behalf of the SSL OC for RoboCup 2013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From feyzavarol at gmail.com Thu Jun 20 07:22:35 2013 From: feyzavarol at gmail.com (Feyza Varol) Date: Thu, 20 Jun 2013 14:22:35 +0300 Subject: [robocup-small] objection to the group drawing Message-ID: We have been attending competitions for 5 years. We wonder how come we are almost always in the same group with Skuba (4 times in 5 years) and Odens (3 times in 5 years). We do not complain being in the same group with these teams particularly. But we think that it is not random enough to be in the same group with the same teams. We guess that there is something more effective (e.g., the alphabetical order of teams) than randomness in the group drawing algorithm. We will appreciate if you clarify how the algorithm "exactly" works. On behalf of BRocks team -- ?. Feyza Varol Department of Electrical and Electronics Engineering Networked and Embedded Control Systems Laboratory Bogazici University 34342 Bebek Istanbul Turkey -------------- next part -------------- An HTML attachment was scrubbed... URL: From chead at chead.ca Thu Jun 20 17:42:48 2013 From: chead at chead.ca (Christopher Head) Date: Thu, 20 Jun 2013 23:42:48 +0200 Subject: [robocup-small] objection to the group drawing In-Reply-To: References: Message-ID: <20130620234248.7f20c7aa@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi there, I?m sorry to hear you?re not happy about this situation and that you?ve been assigned to tough fields. First, please understand that the field assignment is definitely random, with certain constraints. Those constraints are (1) the top four teams are distributed across the fields so they do not play each other during round robin, (2) the next four teams are distributed across the fields so they do not play each other during round robin, (3) weak teams may be distributed across the fields so they do not play each other during round robin, and (4) teams from the same country are distributed across the fields as evenly as possible. The field randomizer is available for anyone to download, build, and run from . Additionally, Michael Bleier and I have both audited the code in grouping.cpp, and we both agree that it is working properly: the random number generator is decent, and the algorithm used to construct random permutations has uniform probability distribution across all possible permutations (it is quite easy to accidentally construct a permutation generator that is not uniform by misusing array indices, but this code does not fall into that trap). Please feel free to look at the code yourself; if you find a bug that would have affected the results, we will be happy to look into it and decide where to go from there. As indicated by my June 10 e-mail, the two input integers needed to run the generator were provided as the minutes into the games of the first two goals scored in the FIFA Confederation Cup. According to the match overview at , this game had three goals, the first two scored at 3 and 48 minutes; thus, the generator was run as ?./grouping 3 48?. Pending certain other issues being sorted out which we still need to discuss further, I am not currently going to release the exact team list file that we used as teams.txt for the grouping program; however, I promise it *will* be released shortly, along with an explanation of how it was produced, *if* we decide that the field groupings will stand as currently published. Most importantly, though, I would like to apologize to all teams for NOT making sure that this random drawing process was done in a fully transparent manner that would have prevented any possible appearance of inappropriate activity. While I am personally convinced the drawing was fair, I should have made sure better procedures were followed, namely that the input team list should have been committed in public before the seed numbers were generated, the same way I *did* commit to the choice of seed numbers in my June 10 e-mail. Thanks for your patience in dealing with this, Christopher Head SSL TC chair On Thu, 20 Jun 2013 14:22:35 +0300 Feyza Varol wrote: > We have been attending competitions for 5 years. We wonder how come > we are almost always in the same group with Skuba (4 times in 5 > years) and Odens (3 times in 5 years). We do not complain being in > the same group with these teams particularly. But we think that it is > not random enough to be in the same group with the same teams. We > guess that there is something more effective (e.g., the alphabetical > order of teams) than randomness in the group drawing algorithm. We > will appreciate if you clarify how the algorithm "exactly" works. > > > On behalf of BRocks team -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlHDd1sACgkQnfE3lq0v9Iz3EwD+IA/8+cHcbcME0IIhU4JhcT0Y Ew4IQ97KcPSiXTiCYSMBAIHyHYeQGFS8Pu+L6YjYoJvkMyxpHlB5eAbgr2ZJ/aSp =N0EY -----END PGP SIGNATURE----- From chead at chead.ca Sat Jun 22 04:13:32 2013 From: chead at chead.ca (Christopher Head) Date: Sat, 22 Jun 2013 10:13:32 +0200 Subject: [robocup-small] New Field Drawings Message-ID: <20130622101332.14307ff3@kruskal.home.chead.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, Due to a number of problems, we are retracting the field assignments we previously published: (1) Immortals was included in the list of teams, even though we had been informed ahead of time that they would not be attending the competition. (2) The choice of which teams to seed was made improperly, not according to the published rules for seeding. (3) The process was not fully transparent?although the method for choosing random seed numbers was published ahead of time, the list of input teams for the generator and the source code to the generator itself were not published. (4) The way we chose seed numbers was not ideal. FIFA games are 90 minutes long, so using the number of minutes of goals allowed the seed numbers to be only between 1 and 90; using two numbers in that range provides only about 13 bits of entropy. The actual entropy would even be slightly lower (about 12 bits), because the first number will very often be smaller than the second. This is not enough entropy to ensure that all valid field assignments could potentially be generated. To address these issues, we will be rerunning the field assignment process tomorrow, Sunday, 2013-06-23. The source code to the generator program is published at . This program takes as input the list of teams, with each team assigned to a bin (1 for top four seeded, 2 for next four seeded, and 3 for all the others, in this case) and also a country. The program generates a random assignment of teams to fields, such that the bin 1 teams are spread across fields and the bin 2 teams are also spread across fields. Also, if the result has two teams from the same country in the same field, it will start over and generate a new assignment. The input file we will be using is attached to this e-mail. How that file was generated is as follows. First, the top four teams from last year (Skuba, ZJUNlict, KIKS, and Parsian) are listed from highest to lowest rank in bin 1, because the generator does not reorder these top teams?this ensures that Skuba will be on field A, ZJUNlict on field B, KIKS on field C, and Parsian on field D; we have extended this privilege to Skuba because, if there is any difference between the fields, then field A is likely the more desirable field (e.g. due to bleachers for spectators). Second, bin 2 has MRL and RoboDragons listed in alphabetical order, followed by two dummy entries to bring the bin up to four teams; normally this bin would finish the top eight teams, but that is not possible because Immortals will not be attending the competition and RoboFEI did not submit an ETDP. Finally, all the remaining teams are in bin 3, again in alphabetical order, with one dummy team to bring the count up to a multiple of four. You can see all the dummy teams in the input file are listed as the same country; this ensures that the fields will only have one team more or less than each other, because the program will not put two dummies on the same field. To select the two numbers the generator uses as seeds, we will be using a service called random.org. As described above (problem #4), most ways of choosing two numbers from things like soccer games or lotteries do not provide enough bits of entropy to perform a fully random assignment of teams. Random.org is a service that provides random data for many purposes, both free and commercial, based on radios tuned to pick up atmospheric noise. One of the services available on random.org is the ability to generate random integers based on a date; the site generates a list of numbers on that date, and from that time forward, anyone can go to the site and get the same numbers by entering the same parameters and date. To find this service, go to random.org, under Numbers choose Integers, click Switch to Advanced Mode, and choose the option to use a pregenerated randomization from a particular date. We will set the number of requested numbers to 2, the minimum value to 1, the maximum value to 1000000000 (1 billion), and the date to 2013-06-23. As an example, if we had used 2013-06-22 (today) instead, the two numbers would have been 415456377 and 424795746. We will publish the field grouping as soon as this is done; however, if you wish, as soon as midnight UTC 2013-06-23 has passed, you should be able to generate the grouping yourselves by using random.org and downloading and building the generator. Thanks, and sorry for the confusion! Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlHFXLYACgkQnfE3lq0v9IzaKwD+PHC0+uv/dkNou20OpRFLm6Rm dG8kqjLJqXPro/ySKs8BAICc3FP8Kj3CkdRG61j5HBOwGpA5VAvRXU9tZ1RYH2c6 =qLkz -----END PGP SIGNATURE----- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: teams.txt URL: From michael.bleier at robotics-erlangen.de Sat Jun 22 13:05:40 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Sat, 22 Jun 2013 19:05:40 +0200 Subject: [robocup-small] New Field Drawings In-Reply-To: <20130622101332.14307ff3@kruskal.home.chead.ca> References: <20130622101332.14307ff3@kruskal.home.chead.ca> Message-ID: <51C5D964.2070503@robotics-erlangen.de> Dear teams, We have been informed by the local organizer that the team Cyrus has not registered for RoboCup 2013. Therefore, we removed Cyrus from the team list for the group assignment. Find attached the updated official team file for the generation of the groups. Looking forward to seeing you all in Eindhoven. Cheers, Michael Bleier On behalf of the Technical Committee On 06/22/2013 10:13 AM, Christopher Head wrote: > Hi everyone, > Due to a number of problems, we are retracting the field assignments we > previously published: > > (1) Immortals was included in the list of teams, even though we had > been informed ahead of time that they would not be attending the > competition. > > (2) The choice of which teams to seed was made improperly, not > according to the published rules for seeding. > > (3) The process was not fully transparent?although the method for > choosing random seed numbers was published ahead of time, the list of > input teams for the generator and the source code to the generator > itself were not published. > > (4) The way we chose seed numbers was not ideal. FIFA games are 90 > minutes long, so using the number of minutes of goals allowed the seed > numbers to be only between 1 and 90; using two numbers in that range > provides only about 13 bits of entropy. The actual entropy would even > be slightly lower (about 12 bits), because the first number will very > often be smaller than the second. This is not enough entropy to ensure > that all valid field assignments could potentially be generated. > > To address these issues, we will be rerunning the field assignment > process tomorrow, Sunday, 2013-06-23. > > The source code to the generator program is published at > . This program takes as input > the list of teams, with each team assigned to a bin (1 for top four > seeded, 2 for next four seeded, and 3 for all the others, in this case) > and also a country. The program generates a random assignment of teams > to fields, such that the bin 1 teams are spread across fields and the > bin 2 teams are also spread across fields. Also, if the result has two > teams from the same country in the same field, it will start over and > generate a new assignment. > > The input file we will be using is attached to this e-mail. How that > file was generated is as follows. First, the top four teams from last > year (Skuba, ZJUNlict, KIKS, and Parsian) are listed from highest to > lowest rank in bin 1, because the generator does not reorder these top > teams?this ensures that Skuba will be on field A, ZJUNlict on field B, > KIKS on field C, and Parsian on field D; we have extended this > privilege to Skuba because, if there is any difference between the > fields, then field A is likely the more desirable field (e.g. due to > bleachers for spectators). Second, bin 2 has MRL and RoboDragons listed > in alphabetical order, followed by two dummy entries to bring the bin > up to four teams; normally this bin would finish the top eight teams, > but that is not possible because Immortals will not be attending the > competition and RoboFEI did not submit an ETDP. Finally, all the > remaining teams are in bin 3, again in alphabetical order, with one > dummy team to bring the count up to a multiple of four. You can see all > the dummy teams in the input file are listed as the same country; this > ensures that the fields will only have one team more or less than each > other, because the program will not put two dummies on the same field. > > To select the two numbers the generator uses as seeds, we will be using > a service called random.org. As described above (problem #4), most ways > of choosing two numbers from things like soccer games or lotteries do > not provide enough bits of entropy to perform a fully random assignment > of teams. Random.org is a service that provides random data for many > purposes, both free and commercial, based on radios tuned to pick up > atmospheric noise. One of the services available on random.org is the > ability to generate random integers based on a date; the site generates > a list of numbers on that date, and from that time forward, anyone can > go to the site and get the same numbers by entering the same parameters > and date. To find this service, go to random.org, under Numbers choose > Integers, click Switch to Advanced Mode, and choose the option to use a > pregenerated randomization from a particular date. We will set the > number of requested numbers to 2, the minimum value to 1, the maximum > value to 1000000000 (1 billion), and the date to 2013-06-23. As an > example, if we had used 2013-06-22 (today) instead, the two numbers > would have been 415456377 and 424795746. > > We will publish the field grouping as soon as this is done; however, if > you wish, as soon as midnight UTC 2013-06-23 has passed, you should be > able to generate the grouping yourselves by using random.org and > downloading and building the generator. > > Thanks, and sorry for the confusion! > Chris > > > > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- # Bin 1 (Top 4 of previous year who submitted ETDPs, in points order) #-------------------------------------------------------------------- 1 Thailand Skuba 1 China ZJUNlict 1 Japan KIKS 1 Iran Parsian # Bin 2 (Next 4 of previous year who submitted ETDPs, in alpha order) #-------------------------------------------------------------------- 2 Iran MRL 2 Japan RoboDragons 2 Dumm Dummy1 2 Dumm Dummy2 # Bin 3 (Normal teams, in alpha order) #------------------------------------- 3 Turkey BRocks 3 USA CMDragons 3 Pakistan EMEnents 3 Germany ER-Force 3 Japan MCT_Susanoo_Logics 3 Cyprus NEUIslanders 3 Japan ODENS 3 USA RFC_Cambridge 3 Brazil RoboFEI 3 Brazil RoboIME 3 USA RoboJackets 3 Colombia STOxs 3 Canada Thunderbots 3 Germany TIGERS_Mannheim 3 Dumm Dummy3 3 Dumm Dummy4 From jgurzoni at yahoo.com.br Sun Jun 23 10:54:53 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Sun, 23 Jun 2013 07:54:53 -0700 (PDT) Subject: [robocup-small] Final SSL-Grouping Message-ID: <1371999293.13096.YahooMailWin8@web164606.mail.gq1.yahoo.com>
Hello to all.
As communicated previously by Chris and Michael, we have drawn again the grouping for the SSL games of RoboCup 2013. The seeds used, from random.org, were 134721569 and 330511513, and the resultant grouping is below.

The OC and TC wish good luck to all teams and that we all enjoy our next days together !

Angelo
On behalf of the SSL Committees for RoboCup 2013

==== Grouping ====
Group A:
Skuba (Thailand)
MRL (Iran)
RoboJackets (USA)
MCT_Susanoo_Logics (Japan)
ER-Force (Germany)

Group B:
ZJUNlict (China)
TIGERS_Mannheim (Germany)
RoboIME (Brazil)
ODENS (Japan)
NEUIslanders (N. Cyprus)

Group C:
KIKS (Japan)
Thunderbots (Canada)
STOxs (Colombia)
RoboFEI (Brazil)
RFC_Cambridge (USA)

Group D:
Parsian (Iran)
RoboDragons (Japan)
CMDragons (USA)
BRocks (Turkey)
EMEnents (Pakistan)
 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jbbalanko at gmail.com Wed Jun 26 09:20:34 2013 From: jbbalanko at gmail.com (Jordan Balanko) Date: Wed, 26 Jun 2013 15:20:34 +0200 Subject: [robocup-small] Live Stream, Field C Message-ID: Hi all, I have a camera installed on field C (Thunderbots field) and will do my best to stream as many games as I can, both Thunderbots and others. The stream will be live at: http://www.ustream.tv/channel/ubcthunderbots I will also be recording all games to my computer and will be happy to share with anyone who would like a copy (they will also be uploaded to YouTube after the competition). Best of luck to everyone! Cheers, Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: From sborissov3 at gatech.edu Fri Jun 28 03:57:40 2013 From: sborissov3 at gatech.edu (Stoian Borissov) Date: Fri, 28 Jun 2013 09:57:40 +0200 Subject: [robocup-small] 2013SSLRules+InfractionTable Message-ID: Hello All, After reading through the SSL rulebook several times, I compiled a simple table that summarizes the different conditions when direct, indirect, and penalty kicks are awarded. It also references sections in the rulebook. I think it would be a good idea to include such a table in the rulebook, along with possibly a second table which presents the same information, but the columns organized by infraction instead of by freekick type. Thanks, -- Stoian Borissov Georgia Tech Robojackets -------------- next part -------------- A non-text attachment was scrubbed... Name: SSL2013Rules+InfractionsTable.xls Type: application/vnd.ms-excel Size: 7680 bytes Desc: not available URL: From mehmet.akar at boun.edu.tr Sat Jun 29 05:36:51 2013 From: mehmet.akar at boun.edu.tr (Mehmet Akar) Date: Sat, 29 Jun 2013 12:36:51 +0300 Subject: [robocup-small] Fwd: [robocup-exec] Symposium July 1th In-Reply-To: <0963669047ECDE4B9EF137DF26A5E2502F7FF653@MBX04.uva.nl> References: <0963669047ECDE4B9EF137DF26A5E2502F7FF653@MBX04.uva.nl> Message-ID: Dear all, below is the info regarding the Robocup Symposium to be held on the July 1st. MA ---------- Forwarded message ---------- From: Visser, A. Date: Sat, Jun 29, 2013 at 11:53 AM Subject: [robocup-exec] Symposium July 1th To: "robocup-exec at cc.gatech.edu" Dear Execs, could you distribute the following information inside your league? The RoboCup 2013 Symposium will be on Monday, July 1th. The location will be Auditorium of the Eindhoven University of Technology, next to the train station. The Auditorium is located on the following address: Eindhoven University of Technology Den Dolech 2 5612 AZ Eindhoven Inside the Auditorium signs will guide you to the "Blauwe Zaal" (Blue Room). The distance from the venue is 4.4 km (see attached route). The symposium co-chairs have tried to make an attractive program, with two renowed researchers as key-note speakers: 9:00-10:00 Raffaello d?Andrea: Why RoboCup Matters 14:00 ? 15:00 Chad Jenkins: Towards a World Wide Web for Robotics The abstracts of those talks, the schedule the oral presentations and poster sessions you could find on: http://staff.science.uva.nl/~arnoud/activities/robocup/RoboCup2013/Symposium/schedule.html There is also a parallel workshop organized by Junior League: http://staff.science.uva.nl/~arnoud/activities/robocup/RoboCup2013/Symposium/junior_track.html The program of the poster session can be found at http://staff.science.uva.nl/~arnoud/activities/robocup/RoboCup2013/Symposium/poster_sessions.html Note that the proceedings of the symposium will be distributed at the registration desk. Please wear your RoboCup badge at the symposium: it is your entrance pass to the symposium. Regards, Arnoud Visser (on behalf of the co-chairs) _______________________________________________ robocup-exec mailing list robocup-exec at cc.gatech.edu https://mailman.cc.gatech.edu/mailman/listinfo/robocup-exec -- Assoc. Prof. Mehmet Akar Dept. of Electrical and Electronic Eng. Bogazici University 34342 Bebek/Istanbul Turkey Phone: +90 212 359 6854 Fax: +90 212 287 2465 E-mail: mehmet.akar at boun.edu.tr http://www.necs.ee.boun.edu.tr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: RouteSymposium.png Type: image/png Size: 1429543 bytes Desc: not available URL: From andre at global-mainframe.com Sat Jul 6 18:01:36 2013 From: andre at global-mainframe.com (Andre Ryll) Date: Sun, 07 Jul 2013 00:01:36 +0200 Subject: [robocup-small] TIGERS Mannheim - Software/Hardware Release 2013 Message-ID: <51D893C0.5050701@global-mainframe.com> Dear SSL-Robocuppers, we, the TIGERS Mannheim, have decided to completely publish this years software and hardware. This includes mechanics (Inventor CAD), electronics (CadSoft EAGLE), robot and base station firmware (C) and our central software (written in Java). We do this to further advance the league and lower the entry level for new teams. Please forward this information to everybody who might be interested. A big link on the robocup SSL website would also be of great help for new teams who might be interested in joining the SSL. We provide our data free of any charge. You may use it for educational purpose or any other non-commercial purpose (including joining the SSL). We strictly forbid to use this data for any commercial purpose. We do not give any warrenties with this release, nor do we promise everything works out of the box. You should still know what you do! We hope that we can initiate a process of more information exchange in the SSL as there are a lot of problems which are re-occuring to every new team. Any release of other teams is highly appreciated. You can download our release, tagged after Eindhoven (2./3.7.) here: http://tigers-mannheim.de/download/release2013/ If you have any problems with the download, contact TIGERS at: management at tigers-mannheim.de Kind regards, Andre Ryll TIGERS Mannheim PS: Feedback welcome! From miguel.solis at usm.cl Sun Oct 6 16:01:15 2013 From: miguel.solis at usm.cl (miguel.solis at usm.cl) Date: Sun, 06 Oct 2013 16:01:15 -0400 Subject: [robocup-small] Unique patterns - SSL Vision Message-ID: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> Hi everyone, i'm from a new team excited for finishing our current work and looking to participate in the next robocup competition. For different reasons, we have a very very reduced space for making tests (the current area of the field we have is of 1.6 mts x 3 mts) and the camera is at a height of 2 mts, and we have some issues with ssl-vision and we'd like to know your opinions about what possibly is going wrong... we're able to identify blue and yellow team (verifying it on the graphical client), but when we check the box of "unique patterns" the robots suddenly disappear and we aren't able to identify the id of each robot. Is it possible to fail because the field test is too small ?, because the distortion set at calibration ? (distortion = 0.25) ... we are working with the standard pattern, the pattern image is ok and its path is correctly defined (no error at loading the pattern image is shown)... we'd appreciate any help or advise, Thank you, Best regards, Miguel Solis IRSS Deluxe Team From joydeepb at ri.cmu.edu Tue Oct 8 11:12:01 2013 From: joydeepb at ri.cmu.edu (Joydeep Biswas) Date: Tue, 8 Oct 2013 11:12:01 -0400 Subject: [robocup-small] Unique patterns - SSL Vision In-Reply-To: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> References: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> Message-ID: Hi Miguel, Good to hear about your entrance to the SSL! :) To help debug this issue, please send me two images captured by your cameras, one with no robots on the field (so that I can use it for geometry calibration), and the second with some robots on the field. For instructions on how to capture these images, see the section named "Recording Images to Files" on the wiki: https://code.google.com/p/ssl-vision/wiki/CapturingImages Regards, Joydeep On Sun, Oct 6, 2013 at 4:01 PM, wrote: > Hi everyone, > > i'm from a new team excited for finishing our current work and looking to > participate in the next robocup competition. For different reasons, we have > a very very reduced space for making tests (the current area of the field we > have is of 1.6 mts x 3 mts) and the camera is at a height of 2 mts, and we > have some issues with ssl-vision and we'd like to know your opinions about > what possibly is going wrong... > > we're able to identify blue and yellow team (verifying it on the graphical > client), but when we check the box of "unique patterns" the robots suddenly > disappear and we aren't able to identify the id of each robot. > > Is it possible to fail because the field test is too small ?, because the > distortion set at calibration ? (distortion = 0.25) ... > > we are working with the standard pattern, the pattern image is ok and its > path is correctly defined (no error at loading the pattern image is > shown)... we'd appreciate any help or advise, > > Thank you, > > Best regards, > > Miguel Solis > IRSS Deluxe Team > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small From michael.bleier at robotics-erlangen.de Tue Oct 8 11:50:11 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Tue, 08 Oct 2013 17:50:11 +0200 Subject: [robocup-small] Unique patterns - SSL Vision In-Reply-To: References: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> Message-ID: <525429B3.6010107@robotics-erlangen.de> Hi Miguel and Joydeep, We also had troubles with this kind of setup a couple times. The parameters of SSL-Vision are optimized for around 4m camera height. The software has thresholds that rejects Blobs that are too big in the camera frame. Here are a few ideas, which might cause the problem: (1) There are a couple of threshold for the maximum size of the color blobs and also the distance between the different blobs. You can find them in the settings tree Global > Team Config > Teams > Standard2010 > Pattern Fitting or Center/Other Marker Settings (2) There is a magic constant in the code for the distance in the search tree for the green/pink color patches. Maybe this distance is too restrictive. file: src/shared/cmpattern/cmpattern_teamdetector.cpp code line: reg_tree.startQuery(*reg,20.0); Best regards, Michael On 10/08/2013 05:12 PM, Joydeep Biswas wrote: > Hi Miguel, > > Good to hear about your entrance to the SSL! :) > > To help debug this issue, please send me two images captured by your > cameras, one with no robots on the field (so that I can use it for > geometry calibration), and the second with some robots on the field. > For instructions on how to capture these images, see the section named > "Recording Images to Files" on the wiki: > https://code.google.com/p/ssl-vision/wiki/CapturingImages > > Regards, > Joydeep > > On Sun, Oct 6, 2013 at 4:01 PM, wrote: >> Hi everyone, >> >> i'm from a new team excited for finishing our current work and looking to >> participate in the next robocup competition. For different reasons, we have >> a very very reduced space for making tests (the current area of the field we >> have is of 1.6 mts x 3 mts) and the camera is at a height of 2 mts, and we >> have some issues with ssl-vision and we'd like to know your opinions about >> what possibly is going wrong... >> >> we're able to identify blue and yellow team (verifying it on the graphical >> client), but when we check the box of "unique patterns" the robots suddenly >> disappear and we aren't able to identify the id of each robot. >> >> Is it possible to fail because the field test is too small ?, because the >> distortion set at calibration ? (distortion = 0.25) ... >> >> we are working with the standard pattern, the pattern image is ok and its >> path is correctly defined (no error at loading the pattern image is >> shown)... we'd appreciate any help or advise, >> >> Thank you, >> >> Best regards, >> >> Miguel Solis >> IRSS Deluxe Team >> _______________________________________________ >> robocup-small mailing list >> robocup-small at cc.gatech.edu >> https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From joydeepb at ri.cmu.edu Tue Oct 8 11:58:22 2013 From: joydeepb at ri.cmu.edu (Joydeep Biswas) Date: Tue, 8 Oct 2013 11:58:22 -0400 Subject: [robocup-small] Unique patterns - SSL Vision In-Reply-To: <525429B3.6010107@robotics-erlangen.de> References: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> <525429B3.6010107@robotics-erlangen.de> Message-ID: Hi, > (2) There is a magic constant in the code for the distance in the search > tree for the green/pink color patches. Maybe this distance is too > restrictive. Yes, I've had issues with this as well, and is my primary suspect. I think we should just add another entry to the VarXML tree for this parameter and document it. -Joydeep From jansegre at gmail.com Tue Oct 8 12:22:37 2013 From: jansegre at gmail.com (Jan) Date: Tue, 8 Oct 2013 13:22:37 -0300 Subject: [robocup-small] Unique patterns - SSL Vision In-Reply-To: References: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> <525429B3.6010107@robotics-erlangen.de> Message-ID: Hi, We've had this kind of issue on our lab, to temporarily solve it we assembled smaller patterns. We know it's a hack and we'd largely appreciate if that magic parameter was configurable. On Tue, Oct 8, 2013 at 12:58 PM, Joydeep Biswas wrote: > Hi, > > > (2) There is a magic constant in the code for the distance in the search > > tree for the green/pink color patches. Maybe this distance is too > > restrictive. > > Yes, I've had issues with this as well, and is my primary suspect. I > think we should just add another entry to the VarXML tree for this > parameter and document it. > > -Joydeep > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -- Att, Jan Segre RoboIME -------------- next part -------------- An HTML attachment was scrubbed... URL: From joydeepb at ri.cmu.edu Sat Oct 12 07:37:15 2013 From: joydeepb at ri.cmu.edu (Joydeep Biswas) Date: Sat, 12 Oct 2013 07:37:15 -0400 Subject: [robocup-small] Unique patterns - SSL Vision In-Reply-To: References: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> <525429B3.6010107@robotics-erlangen.de> Message-ID: Hi Jan, Miguel, Michael, Attached is a patch (reference: revision 205 of trunk) that makes the magic constants configurable. This patch adds two configuration numbers, "Max Num Markers To Detect" and "Max Query Distance" to the following configuration subtree in ssl-vision: "Global" -> "Team Config" -> "Teams" -> -> "Other Marker Settings". Please try it out and verify that it solves the problem by twiddling the magic numbers. If someone facing this problem could send me some sample captured pngs, I could test it out at my end as well. The patch will be pushed to trunk once verified. Thanks, Joydeep On Tue, Oct 8, 2013 at 12:22 PM, Jan wrote: > Hi, > > We've had this kind of issue on our lab, to temporarily solve it we > assembled smaller patterns. We know it's a hack and we'd largely appreciate > if that magic parameter was configurable. > > > On Tue, Oct 8, 2013 at 12:58 PM, Joydeep Biswas wrote: >> >> Hi, >> >> > (2) There is a magic constant in the code for the distance in the search >> > tree for the green/pink color patches. Maybe this distance is too >> > restrictive. >> >> Yes, I've had issues with this as well, and is my primary suspect. I >> think we should just add another entry to the VarXML tree for this >> parameter and document it. >> >> -Joydeep >> _______________________________________________ >> robocup-small mailing list >> robocup-small at cc.gatech.edu >> https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > > > > > -- > Att, > Jan Segre > RoboIME > > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > -------------- next part -------------- Index: src/shared/cmpattern/cmpattern_team.h =================================================================== --- src/shared/cmpattern/cmpattern_team.h (revision 207) +++ src/shared/cmpattern/cmpattern_team.h (working copy) @@ -79,6 +79,8 @@ VarInt * _other_markers_max_height; VarInt * _other_markers_min_area; VarInt * _other_markers_max_area; + VarInt * _other_markers_max_detections; + VarDouble * _other_markers_max_query_distance; VarList * _histogram_settings; VarBool * _histogram_enable; Index: src/shared/cmpattern/cmpattern_teamdetector.cpp =================================================================== --- src/shared/cmpattern/cmpattern_teamdetector.cpp (revision 207) +++ src/shared/cmpattern/cmpattern_teamdetector.cpp (working copy) @@ -109,6 +109,9 @@ _center_marker_uniform=_team->_center_marker_uniform->getDouble(); _center_marker_duplicate_distance=_team->_center_marker_duplicate_distance->getDouble(); + _other_markers_max_detections=_team->_other_markers_max_detections->getInt(); + _other_markers_max_query_distance=_team->_other_markers_max_query_distance->getDouble(); + filter_team.setWidth(_team->_center_marker_min_width->getInt(),team->_center_marker_max_width->getInt()); filter_team.setHeight(_team->_center_marker_min_height->getInt(),team->_center_marker_max_height->getInt()); filter_team.setArea(_team->_center_marker_min_area->getInt(),team->_center_marker_max_area->getInt()); @@ -411,16 +414,16 @@ { (void)image; - const int MaxMarkers = 16; + const int MaxDetections = _other_markers_max_detections; Marker cen; // center marker - Marker markers[MaxMarkers]; + Marker markers[MaxDetections]; + const float marker_max_query_dist = _other_markers_max_query_distance; + const float marker_max_dist = _pattern_max_dist; - float marker_max_dist = _pattern_max_dist; - // partially forget old detections //decaySeen(); - filter_team.init( colorlist->getRegionList(team_color_id).getInitialElement() ); + filter_team.init( colorlist->getRegionList(team_color_id).getInitialElement()); const CMVision::Region * reg=0; SSL_DetectionRobot * robot=0; @@ -437,10 +440,10 @@ cen.set(reg,reg_center3d,getRegionArea(reg,_robot_height)); int num_markers = 0; - reg_tree.startQuery(*reg,20.0); + reg_tree.startQuery(*reg,marker_max_query_dist); double sd=0.0; CMVision::Region *mreg; - while((mreg=reg_tree.getNextNearest(sd))!=0 && num_markerscen_x,mreg->cen_y)>=0.5 Index: src/shared/cmpattern/cmpattern_teamdetector.h =================================================================== --- src/shared/cmpattern/cmpattern_teamdetector.h (revision 207) +++ src/shared/cmpattern/cmpattern_teamdetector.h (working copy) @@ -184,6 +184,8 @@ double _center_marker_area_stddev; double _center_marker_uniform; double _center_marker_duplicate_distance; + int _other_markers_max_detections; + double _other_markers_max_query_distance; bool _histogram_enable; int _histogram_pixel_scan_radius; Index: src/shared/cmpattern/cmpattern_team.cpp =================================================================== --- src/shared/cmpattern/cmpattern_team.cpp (revision 207) +++ src/shared/cmpattern/cmpattern_team.cpp (working copy) @@ -71,6 +71,8 @@ _other_markers_max_height = _other_markers_filter->findChildOrReplace(new VarInt("Max Height (pixels)",40)); _other_markers_min_area = _other_markers_filter->findChildOrReplace(new VarInt("Min Area (sq-pixels)",15)); _other_markers_max_area = _other_markers_filter->findChildOrReplace(new VarInt("Max Area (sq-pixels)",600)); + _other_markers_max_detections = _other_markers_filter->findChildOrReplace(new VarInt("Max Num Markers To Detect", 16)); + _other_markers_max_query_distance = _other_markers_filter->findChildOrReplace(new VarDouble("Max Query Distance", 20.0)); _histogram_settings = _settings->findChildOrReplace(new VarList("Histogram Settings")); _histogram_enable = _histogram_settings->findChildOrReplace(new VarBool("Enable",true)); Index: robocup-ssl-teams.xml =================================================================== --- robocup-ssl-teams.xml (revision 207) +++ robocup-ssl-teams.xml (working copy) @@ -116,6 +116,12 @@ 600 + + 16 + + + 20.000000 + @@ -288,6 +294,12 @@ 600 + + 16 + + + 20.000000 + @@ -461,6 +473,12 @@ 600 + + 16 + + + 20.000000 + @@ -634,6 +652,12 @@ 600 + + 16 + + + 20.000000 + @@ -807,6 +831,12 @@ 600 + + 16 + + + 20.000000 + @@ -980,6 +1010,12 @@ 600 + + 16 + + + 20.000000 + @@ -1153,6 +1189,12 @@ 600 + + 16 + + + 20.000000 + @@ -1326,6 +1368,12 @@ 600 + + 16 + + + 20.000000 + @@ -1499,6 +1547,12 @@ 600 + + 16 + + + 20.000000 + @@ -1672,6 +1726,12 @@ 600 + + 16 + + + 20.000000 + @@ -1845,6 +1905,12 @@ 25000 + + 16 + + + 20.000000 + @@ -2018,6 +2084,12 @@ 600 + + 16 + + + 20.000000 + @@ -2191,6 +2263,12 @@ 600 + + 16 + + + 20.000000 + @@ -2364,6 +2442,12 @@ 600 + + 16 + + + 20.000000 + From miguel.solis at usm.cl Thu Oct 10 17:01:07 2013 From: miguel.solis at usm.cl (miguel.solis at usm.cl) Date: Thu, 10 Oct 2013 17:01:07 -0400 Subject: [robocup-small] Unique patterns - SSL Vision In-Reply-To: References: <20131006160115.Horde.UjTMN1dzdO9SUcGLe4EUxYA@webmail.utfsm.cl> <525429B3.6010107@robotics-erlangen.de> Message-ID: <20131010170107.Horde.jmgsT1dzdO9SVxWTzZLneGA@webmail.utfsm.cl> Thank you so much for all your tips, i finally got it (don't really know if it's the correct setup, but at least it's working haha). In Team Config -> Pattern Fitting, i changed Max Marker Center Dist, MaxError and Expected StdDev... that showed the id of each robot, but i also changed the magic parameter you mentioned and then the id started to blink slower than it was without any changes on this file. Appreciate your help, Miguel Solis Jan escribi?: > Hi, > > We've had this kind of issue on our lab, to temporarily solve it we > assembled smaller patterns. We know it's a hack and we'd largely appreciate > if that magic parameter was configurable. > > > On Tue, Oct 8, 2013 at 12:58 PM, Joydeep Biswas wrote: > >> Hi, >> >> > (2) There is a magic constant in the code for the distance in the search >> > tree for the green/pink color patches. Maybe this distance is too >> > restrictive. >> >> Yes, I've had issues with this as well, and is my primary suspect. I >> think we should just add another entry to the VarXML tree for this >> parameter and document it. >> >> -Joydeep >> _______________________________________________ >> robocup-small mailing list >> robocup-small at cc.gatech.edu >> https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small >> > > > > -- > Att, > Jan Segre > RoboIME From arsalan_akhter at ymail.com Tue Oct 22 14:43:18 2013 From: arsalan_akhter at ymail.com (Arsalan Akhter) Date: Tue, 22 Oct 2013 11:43:18 -0700 (PDT) Subject: [robocup-small] Log files of Robocup SSL Matches Message-ID: <1382467398.58478.YahooMailNeo@web164502.mail.gq1.yahoo.com> Hi, Do we have a repository (or a collection) of the log files of the matches which have been played in Robocup Small Size League? Also if they are individually held at the moment, can they be shared? ? ________________________________ Arsalan Akhter College of Electrical and Mechanical Engineering, National University of Sciences and Technology, Rawalpindi, Pakistan ________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.bleier at robotics-erlangen.de Tue Oct 22 15:20:48 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Tue, 22 Oct 2013 21:20:48 +0200 Subject: [robocup-small] Log files of Robocup SSL Matches In-Reply-To: <1382467398.58478.YahooMailNeo@web164502.mail.gq1.yahoo.com> References: <1382467398.58478.YahooMailNeo@web164502.mail.gq1.yahoo.com> Message-ID: <5266D010.7040602@robotics-erlangen.de> Hi Arsalan, > Do we have a repository (or a collection) of the log files of the > matches which have been played in Robocup Small Size League? I started working on some code to automatically create log files of Small Size games. During RoboCup 2013 I recorded pretty much all matches (vision + referee). From previous RoboCup competitions we might be able to get some data logged by individual teams. I will try to make the code and log files available asap. Cheers, Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From arsalan_akhter at ymail.com Tue Oct 22 15:58:19 2013 From: arsalan_akhter at ymail.com (Arsalan Akhter) Date: Tue, 22 Oct 2013 12:58:19 -0700 (PDT) Subject: [robocup-small] Log files of Robocup SSL Matches In-Reply-To: <5266D010.7040602@robotics-erlangen.de> References: <1382467398.58478.YahooMailNeo@web164502.mail.gq1.yahoo.com> <5266D010.7040602@robotics-erlangen.de> Message-ID: <1382471899.66830.YahooMailNeo@web164503.mail.gq1.yahoo.com> Thanks Michael for the effort :-) Looking forward to it. ? ________________________________ Arsalan Akhter College of Electrical and Mechanical Engineering, National University of Sciences and Technology, Rawalpindi, Pakistan ________________________________ On Wednesday, October 23, 2013 12:21 AM, Michael Bleier wrote: Hi Arsalan, > > >> Do we have a repository (or a collection) of the log files of the >> matches which have been played in Robocup Small Size League? > >I started working on some code to automatically create log files of >Small Size games. During RoboCup 2013 I recorded pretty much all matches >(vision + referee). From previous RoboCup competitions we might be able >to get some data logged by individual teams. > >I will try to make the code and log files available asap. > >Cheers, >Michael > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan.posey at gatech.edu Wed Oct 23 13:41:19 2013 From: stefan.posey at gatech.edu (Stefan P) Date: Wed, 23 Oct 2013 13:41:19 -0400 Subject: [robocup-small] Log files of Robocup SSL Matches In-Reply-To: <1382471899.66830.YahooMailNeo@web164503.mail.gq1.yahoo.com> References: <1382467398.58478.YahooMailNeo@web164502.mail.gq1.yahoo.com> <5266D010.7040602@robotics-erlangen.de> <1382471899.66830.YahooMailNeo@web164503.mail.gq1.yahoo.com> Message-ID: Angelo and I had talked about this on and off after Mexico City. Never had time. I know I personally logged most of the elimination and finals that year. A few other team members did to. I think we managed to get every match in the play offs / finals. They should be somewhere on the robojackets server. There is probably a good bit of the playoffs / finals logged from this year too. If people are really into older stuff possibly some from Istanbul as well (though I am not sure what happened to those). Try talking to a current member as I finally managed to graduate last Dec. I know there is a viewer / log generator. Only thing to do really would be extracting it from the rj software package and integrating it into the ref box or vision and add some recording automation. If people wanted to go that route. Though integrating things is never as simple as it sounds. -- Stefan Posey On Tue, Oct 22, 2013 at 3:58 PM, Arsalan Akhter wrote: > Thanks Michael for the effort :-) > > Looking forward to it. > > ** > ------------------------------ > *Arsalan Akhter* > *College of Electrical and Mechanical Engineering,* > *National University of Sciences and Technology,* > *Rawalpindi, Pakistan* > ------------------------------ > > > On Wednesday, October 23, 2013 12:21 AM, Michael Bleier < > michael.bleier at robotics-erlangen.de> wrote: > > Hi Arsalan, > > > > Do we have a repository (or a collection) of the log files of the > > matches which have been played in Robocup Small Size League? > > > I started working on some code to automatically create log files of > Small Size games. During RoboCup 2013 I recorded pretty much all matches > (vision + referee). From previous RoboCup competitions we might be able > to get some data logged by individual teams. > > I will try to make the code and log files available asap. > > Cheers, > Michael > > > > > _______________________________________________ > robocup-small mailing list > robocup-small at cc.gatech.edu > https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.bleier at robotics-erlangen.de Sat Oct 26 13:45:30 2013 From: michael.bleier at robotics-erlangen.de (Michael Bleier) Date: Sat, 26 Oct 2013 19:45:30 +0200 Subject: [robocup-small] Log files of Robocup SSL Matches In-Reply-To: <1382471899.66830.YahooMailNeo@web164503.mail.gq1.yahoo.com> References: <1382467398.58478.YahooMailNeo@web164502.mail.gq1.yahoo.com> <5266D010.7040602@robotics-erlangen.de> <1382471899.66830.YahooMailNeo@web164503.mail.gq1.yahoo.com> Message-ID: <526BFFBA.5000801@robotics-erlangen.de> Hi all, I would like to start a common database of Small Size game logs. Since we also want to push forward autonomous referee software in future years, log files will become an important tool for testing and training. As an effort to start this database I uploaded log files of all games at RoboCup 2013 after Round Robin. I will add the remaining logs as soon as I find the time to convert my data. A database with links to game logs can be found on the Small Size wiki: http://sslrobocup.com/gamelogs In discussion with members of the TC/OC I came up with the log file format described on the wiki page. It can be easily read in plain C++ and protobuf. The file format should be able to support future changes. More information and experimental software for recording and playback of the log files can be found on github (https://github.com/michael-bleier/ssl-logtools). The software binds to all network interfaces and currently uses the offical SSL-Vision / RefBox multicast addresses. The log player can also handle gzip compressed log files by decompressing the complete data to memory. Call for Help: (1) If you have interesting log files form previous RoboCup competitions that could be converted to the common file format, please contact me. (2) If you have have good log player or analysis code that might be useful to others, please share. I am happy about any kind of feedback on the log file format or software. If you have any questions, feel free to ask. Cheers, Michael Team ER-Force http://www.er-force.de/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From opfer at vs.uni-kassel.de Thu Nov 7 03:45:11 2013 From: opfer at vs.uni-kassel.de (Stephan Opfer) Date: Thu, 07 Nov 2013 09:45:11 +0100 Subject: [robocup-small] Buying a SSL Robot Message-ID: <527B5317.6040103@vs.uni-kassel.de> Hello SSL Community, I have a simple question: Is somewhere a SSL-Like robot available to buy? Anything < 1000? is welcome. SSL-Like means: - Omnidrive - Approximately as large as a SSL-Robot - Odometry, Velocity > 2 m/s - Further actuation attachable (e.g. it should be possible to solder some additional servos to the control board) Best Regards, Stephan -- Distributed Systems Research Group Stephan Opfer T. +49 561 804-6283 F. +49 561 804-6277 Univ. Kassel, FB 16, Wilhelmsh?her Allee 73, D-34121 Kassel WWW: http://www.uni-kassel.de/go/vs_stephan-opfer From assadn at yahoo.com Sat Dec 7 06:42:51 2013 From: assadn at yahoo.com (Asad Norouzi) Date: Sat, 7 Dec 2013 03:42:51 -0800 (PST) Subject: [robocup-small] RoboCup IranOpen 2014: Call For Participation Message-ID: <1386416571.39418.YahooMailNeo@web122006.mail.ne1.yahoo.com> ++++++++++++++++++++++ Apologies for duplicate messages ++++++++++++++++++++ ###########################? Call For Participation ########################## ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? The 9th RoboCup IranOpen Competitions?????????? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? April 07-11, 2014?????????????????? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ???? Tehran, Iran?????????????????? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ? http://2014.iranopen.ir ##########################? RoboCup IranOpen 2014 ######################## The 9th RoboCup IranOpen competitions will be held in April 07-11, 2014. Having had the experience of 8 years successful organization of these competitions, we look forward to an even more glorious event with more teams competing in this major robotics event from all over the world. Last year we, gladly, had 301 teams from China, Colombia, Germany, Greece, India, Iran, Italy, Mexico, Netherlands, Pakistan, Turkey,and United States. ? RoboCup IranOpen is an attempt to further promote AI and Robotics research. These competitions will provide a chance for all researchers to present and share their experiences and achievements. The RoboCup IranOpen 2014 competitions leagues are as follows: * RoboCup Soccer * Humanoid * Middle Size * Small Size * Standard Platform * Soccer 3D Simulation * Soccer 2D Simulation * RoboCupRescue * Rescue Robot * Rescue Simulation * RoboCup at Home * RoboCupJunior * Soccer A Open Weight * Soccer B Open Weight * Soccer B Light Weight * Rescue A Primary * Rescue A Secondary * Rescue B * CoSpace Rescue The RoboCup IranOpen 2014 competitions extra leagues which are not among the official RoboCup leagues: * Deminer Autonomous * Deminer Manual * Deminer Technical Challenge * Senior Demo * Junior Demo Primary * Junior Demo Secondary * IranOpenROV (Radio Operated Vehicles - underwater robots) * IranOpenUAV (Unmanned Aerial Vehicles) Participation: All teams are required to pre-register through the online form available in the website. The pre-registered teams should then submit the relevant qualification materials. Last year 301 teams were qualified from 653 pre-registered teams. Important dates: * Pre-Registration: November 25, 2013 - January 06, 2014 * Submission of qualification materials: December 02, 2013 - January 06, 2014 * Qualification: January 06 - 20, 2014 * Registration: January 06 - 27, 2014 For further information please visit our official website at http://2014.iranopen.ir For inquiries please contact us via the hereunder email addresses: * General Inquiries: info at iranopen.ir * Registration: registration at iranopen.ir * Visa & International Affairs: visa at iranopen.ir * Travel Support: asadollah_norouzi at sp.edu.sg We are now on Google Plus! Please follow us here: https://plus.google.com/113211996972561870891 Regards On behalf of, Iranian RoboCup National Committee RoboCup IranOpen 2014 Organizing Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgurzoni at yahoo.com.br Thu Dec 12 14:30:45 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Thu, 12 Dec 2013 17:30:45 -0200 Subject: [robocup-small] =?iso-8859-1?q?CFP=3A_RoboCup_Symposium_2014_-_Jo?= =?iso-8859-1?q?=E3o_Pessoa=2C_Brazil=2E?= Message-ID: <003e01cef770$a8fd6660$faf83320$@yahoo.com.br> ******************************************************************** Call for Papers RoboCup International Symposium 2014 Jo?o Pessoa, Brazil July 25th, 2014 http://www.robocup2014.org/ ******************************************************************** OVERVIEW The 18th annual RoboCup International Symposium will be held in conjunction with RoboCup 2014 (July 19-24). The Symposium represents the core meeting for presentation and discussion of scientific contributions to a variety of research areas related to all RoboCup divisions (RoboCupSoccer, RoboCupRescue, RoboCup at Home, RoboCup at Work and RoboCupJunior). Its scope encompasses, but is not restricted to, research and educational activities within the fields of Robotics and Artificial Intelligence. Due to its interdisciplinary nature, the symposium offers a unique venue for exploring various and intimate connections of theory and practice across a wide spectrum of research fields. The experimental, interactive, and benchmark character of the RoboCup initiative presents the opportunity to disseminate novel ideas and promising technologies, which are rapidly adopted and field-tested by a large (and still growing) community. SUBMISSION We solicit submissions of papers reporting on high-quality, original research with relevance to the areas mentioned below. All researchers working in these areas, even if not actively participating in RoboCup teams, are urged to submit their work. Both papers describing real-world research and papers reporting theoretical results, as well as combinations thereof, are welcome. We also encourage the submission of high-quality overview articles for any field related to the general scope of RoboCup. The proceedings of the RoboCup International Symposium are published and archived within the Springer-Verlag Lecture Notes in Artificial Intelligence (LNAI) series. Submitted papers are limited to 12 pages formatted according to the LNAI requirements (http://www.springer.com/series/1244) and must be electronically submitted through the symposium web site: https://www.easychair.org/conferences/?conf=robocupsymposium2014 All contributions are peer-reviewed by at least three reviewers using a blind review process. DEVELOPMENT TRACK To encourage open-source releases of hard and software components, a special track on open-source developments will be included in the 2014 RoboCup International Symposium. Contributions to this track are limited to eight pages, formatted according to LNAI requirements. They should include evidence of impact of the released component to the RoboCup community. Review of these contributions will be based on technical contribution and benefit for the RoboCup community. IMPORTANT DATES * Submission of full papers: April 11th, 2014. * Notification to authors: May 23rd, 2014. * Submission of camera-ready copies: June 6th, 2014. * RoboCup 2014 Symposium: July 25th, 2014. SYMPOSIUM CO-CHAIRS * H. Levent Akin, Bogazi?i University * Reinaldo A. C. Bianchi, FEI University * Subramanian Ramamoorthy, University of Edinburgh * Komei Sugiura, National Institute of Information and Communications Technology AREAS OF INTEREST * Robot Hardware and Software - mobile and humanoid robots - sensors and actuators - embedded and mobile devices - robot construction and new materials - robotic system integration - robot software architectures - robot programming environments and languages - real-time and concurrent programming - robot simulators * Perception and Action - distributed sensor integration - sensor noise filtering - real-time image processing and pattern recognition - motion and sensor models - sensory-motor control - robot kinematics and dynamics - high-dimensional motion control * Robotic Cognition and Learning - world modeling - localization, navigation, and mapping - planning and reasoning - decision making under uncertainty - reinforcement learning - complex motor skill acquisition - motion and sensor model learning * Multi-Robot Systems - team coordination methods - communication protocols - learning and adaptive systems - teamwork and heterogeneous agents - dynamic resource allocation - adjustable autonomy * Human-Robot Interaction - human-robot interfaces - speech synthesis and natural language generation - visualization - emotion recognition - human's intent cognition - affect detection and synthesis - robot response to external disturbances - safety and dependability * Education and Edutainment - Robotics and Artificial Intelligence education - educational robotics - robot kits and programming tools - robotic entertainment * Applications - disaster rescue information systems - search and rescue robots - robotic surveillance - service and social robots - robots at home Regards on behalf of the symposium co-chairs. Email: symposium at robocup2014.org From joydeepb at ri.cmu.edu Tue Dec 17 14:50:21 2013 From: joydeepb at ri.cmu.edu (Joydeep Biswas) Date: Tue, 17 Dec 2013 14:50:21 -0500 Subject: [robocup-small] Updates to SSL-Vision for 4-Camera, double-field setup Message-ID: Hi Everyone, I just pushed changes to the 4cam_experimental branch of ssl-vision that change the calibration and field markings specification method. If you have a 4-camera setup in your lab, I would request you to try out the new system. I would also appreciate it if teams with 4-cam setups could share captured images with me directly (joydeepb at ri.cmu.edu) for additional testing. Some initial instructions on how to use the new calibration procedure: https://code.google.com/p/ssl-vision/wiki/4CameraSetup?ts=1387308766&updated=4CameraSetup Instructions on how to capture images to share for testing: https://code.google.com/p/ssl-vision/wiki/CapturingImages Checking out a copy of the 4cam_experimental branch: svn checkout https://ssl-vision.googlecode.com/svn/branches/4cam_experimental Thanks, Joydeep From jgurzoni at yahoo.com.br Fri Dec 27 22:17:50 2013 From: jgurzoni at yahoo.com.br (Angelo Gurzoni Jr) Date: Sat, 28 Dec 2013 01:17:50 -0200 Subject: [robocup-small] RoboCup 2014 Small Size League - Call for Participation Message-ID: <003901cf037b$879148e0$96b3daa0$@yahoo.com.br> ******************************************************************** Call for Participation RoboCup Small Size League Competition 2014 July 19-25, 2014 (Joao Pessoa, Brazil) http://www.robocup2014.org/ Small Size League Wiki http://wiki.robocup.org/wiki/Small_Size_League http://robocupssl.cpe.ku.ac.th/ ******************************************************************** Robocup is a competition domain designed to advance Robotics and AI research through a friendly competition. Small Size robot soccer is one of the Robocup league divisions, focused on the problem of intelligent multi-agent cooperation and control in a highly dynamic environment with a hybrid centralized/distributed system. Researchers and students are invited to participate in the RoboCup Small Size League competition 2014, in Brazil. To participate, teams must complete the qualification process, available on the League's Wiki, at http://robocupssl.cpe.ku.ac.th/robocup2014:qualification, and summarized in this e-mail. IMPORTANT DATES . Pre-Registration Deadline : January 31, 2014 . Qualification Deadline : February 28, 2014 . Qualification Announcement : March 15, 2014 . Financial Support Confirmation Deadline : April 15, 2014 The qualification process consists of: 1. Pre-Registration Indicate participation intent by sending an email to the organizing committee(rc-ssl-oc at lists.robocup.org), containing the following: . Team Name . Country . University . Main contact name and Email . Team Website (optional) The email subject should be: 2014 Participation Intent . 2. Submission of the Qualification Material: Teams are required to send the following qualification material to the organizing committee (rc-ssl-oc at lists.robocup.org): . A Team Description Paper (TDP) in LNAI format (http://www.springer.com/series/1244) . A Team Video demonstrating the team capabilities The detailed requirements of the qualification material are posted on the League's wiki, at http://robocupssl.cpe.ku.ac.th/robocup2014:qualification * (Special requirement for Top 8 teams from Robocup 2013) - Top 8 teams have to submit also an Extended Team Description Paper (ETDP) by April 15, 2014. Hope to see you at Robocup 2014. Best Regards, 2014 Robocup Small Size League Organizing and Technical Committees -------------- next part -------------- An HTML attachment was scrubbed... URL: From joydeep at cmu.edu Sun Dec 29 08:45:07 2013 From: joydeep at cmu.edu (Joydeep Biswas) Date: Sun, 29 Dec 2013 08:45:07 -0500 Subject: [robocup-small] Moving to Double-Sized Field Message-ID: Dear Fellow-RoboCuppers of the Small Size League, We, the Technical, Organizing and Executive committees of the SSL, write to you today regarding the much-awaited, much-debated, much-anticipated move to the double-sized field. We have extensively discussed the pros and cons regarding this big change, and to summarize the views of the committees, if you, the members of the SSL, agree to the change to the double-sized field today, we will switch to the double-sized field in RoboCup 2014, with every assistance from the TC and OC necessary to make this change happen. Understanding that some teams might need some more time, we have also discussed the lesser alternative of voluntary adoption of the double-sized field in RC2014, with compulsory change in RC2015. However, we believe and hope that the SSL community will embrace the change of field size this year, thus opening up many avenues for development in the SSL for the years ahead. The collected views (considering pros and cons) of the TC, OC, and the Executive committee, regarding this matter are available in the following shared document: https://docs.google.com/document/d/1mip36bZCGtwGX2Sw1QIm35ixyoFGuMWVSPl91kFCCTI/pub We request all the teams to go through the document, and respond with their views regarding the following two questions, to be answered by filling out the survey form: https://docs.google.com/forms/d/1dRb6ltDaYu9y_0jGcb86Tnknr10SIg8TqWdyNQim4hc/viewform We request the teams to respond as soon as possible, by January 10th 2014 in the interest of preparation for RoboCup 2014. Q: When, does your team feel should the SSL move to the larger, double-sized field? Option 1: This year, at RoboCup 2014. Option 2: Voluntarily for RoboCup 2014, Compulsorily for 2015. Option 3: At some unknown future RoboCup. Option 4: Never Q: What can the TC and OC do, to make the transition easier to the larger field? Regards, The Technical, Organization, and Executive committees of the RoboCup SSL, 2014. -------------- next part -------------- An HTML attachment was scrubbed... URL: From raul at roboticspot.com Sun Dec 29 17:18:16 2013 From: raul at roboticspot.com (raul at roboticspot.com) Date: Sun, 29 Dec 2013 17:18:16 -0500 (EST) Subject: [robocup-small] Moving to Double-Sized Field In-Reply-To: References: Message-ID: <11685.80.37.169.250.1388355496.squirrel@www.roboticspot.com> We don't have a team since 2006, but as long time spectators believe this double-sized field would be a good idea. From an spectator point of view "robot crowding" is usually the most used strategy in defense and that usually has a big impact in strategy for counter-attack and leads to volley shots. The final of the Robocup 2014 was a good example of that. http://www.youtube.com/watch?v=hZE1YQCghLk Regards. > Dear Fellow-RoboCuppers of the Small Size League, > > We, the Technical, Organizing and Executive committees of the SSL, write > to you today regarding the much-awaited, much-debated, much-anticipated > move to the double-sized field. > > We have extensively discussed the pros and cons regarding this big > change, and to summarize the views of the committees, if you, the > members of the SSL, agree to the change to the double-sized field today, > we will switch to the double-sized field in RoboCup 2014, with every > assistance from the TC and OC necessary to make this change happen. > > Understanding that some teams might need some more time, we have also > discussed the lesser alternative of voluntary adoption of the > double-sized field in RC2014, with compulsory change in RC2015. However, > we believe and hope that the SSL community will embrace the change of > field size this year, thus opening up many avenues for development in > the SSL for the years ahead. > > The collected views (considering pros and cons) of the TC, OC, and the > Executive committee, regarding this matter are available in the > following shared document: > > https://docs.google.com/document/d/1mip36bZCGtwGX2Sw1QIm35ixyoFGuMWVSPl91kFCCTI/pub > > > We request all the teams to go through the document, and respond with > their views regarding the following two questions, to be answered by > filling out the survey form: > > https://docs.google.com/forms/d/1dRb6ltDaYu9y_0jGcb86Tnknr10SIg8TqWdyNQim4hc/viewform > > We request the teams to respond as soon as possible, by January 10th > 2014 in the interest of preparation for RoboCup 2014. > > Q: When, does your team feel should the SSL move to the larger, > double-sized field? > > Option 1: This year, at RoboCup 2014. > > Option 2: Voluntarily for RoboCup 2014, Compulsorily for 2015. > > Option 3: At some unknown future RoboCup. > > Option 4: Never > > Q: What can the TC and OC do, to make the transition easier to the > larger field? > > Regards, > > The Technical, Organization, and Executive committees of the RoboCup > SSL, 2014.