From: Hedayat V. <hed...@gm...> - 2013-05-22 18:48:35
|
Hi Sander, I'll add Patrick's code, and a small code to check the rules for heterogeneous players. However, what are the rules for 2013? Is there a limitation on the number of hetero agents of each type? What about the total number of hetero players for a team? About the release, sure I'll do it. Regards, Hedayat /*Sander van Dijk <sgv...@gm...>*/ wrote on Wed, 22 May 2013 16:25:20 +0100: > Hey all, > > With just over a month to go, I guess it's time to put a release > together for the simulator version for Eindhoven. I just committed > something I wanted in there: the ability to send foul information to > the monitor. Attached is a quick (and a bit dirty) patch to make this > information visible in RoboViz; you should get a list underneath the > top bar showing fouls for 10 seconds. > > With this, my suggestion is to put Patrick's rule implementations into > the new version, but have no automatic penalization on them. Instead, > the foul is shown in the monitor (with a yellow card instead of a red > card), and the human referee can decide on the action to take. Even if > we ignore them in the end, it should still give us an idea of how > reasonable the calls are in a tournament. > > Looking forward to your opinins. > > @Hedayat: you have the most experience putting a release together, > would you have time to do this in the near future? > > Sander > > > -- > Adaptive Systems Research Group > Department of Computer Science > University of Hertfordshire > United Kingdom > > > _______________________________________________ > rc-ss3d-tc mailing list > rc-...@li... > http://lists.robocup.org/listinfo.cgi/rc-ss3d-tc-robocup.org |
From: Klaus D. <kla...@hs...> - 2013-05-31 05:42:53
|
Hello all, I have committet two Nao type suggestions to the sourceforge repository. Type1 (LongLeg) is a slightly changed type compared to what has been committed steming from observations at the German Open. The enlengthment of the legs is now split into two parts at the hip (as has been) and at the ankle. This should make sure that inverse kinematics based walks should work more easily with this type. In addition, now also the arms are longer, simplifying e.g. getup behaviors. Type2 (FastFoot) is unchanged a Nao with faster ankle pitch, but slower ankle roll. My suggestions for the value areas (min change, max change) are as follows: LongLeg (2cm, 6cm) (split in half at the hip, half at the Ankle) FastFoot (1 deg/s, 3 deg/s), meaning instead of a value of 6.1395 at least 7.13 and at most 9.13 for pitch and 5.13 to 3.13 for roll. Below the naorobottypes.rb # Type 0 (Standard Nao) {'ThighRelHip2_Z' => -0.04, 'AnkleRelShank_Z' => -0.055, 'lj5_max_abs_speed' => 6.1395, 'lj6_max_abs_speed' => 6.1395, 'ElbowRelUpperArm_Y' => 0.07}, # Type 1 {'ThighRelHip2_Z' => -0.06, 'AnkleRelShank_Z' => -0.075, 'lj5_max_abs_speed' => 6.1395, 'lj6_max_abs_speed' => 6.1395, 'ElbowRelUpperArm_Y' => 0.11}, # Type 2 {'ThighRelHip2_Z' => -0.04, 'AnkleRelShank_Z' => -0.055, 'lj5_max_abs_speed' => 9.21, 'lj6_max_abs_speed' => 4.605, 'ElbowRelUpperArm_Y' => 0.07} Other type suggestions are still welcome. Greetings Klaus Am 22.05.2013 20:48, schrieb Hedayat Vatankhah: > Hi Sander, > I'll add Patrick's code, and a small code to check the rules for > heterogeneous players. However, what are the rules for 2013? Is there > a limitation on the number of hetero agents of each type? What about > the total number of hetero players for a team? > > About the release, sure I'll do it. > > Regards, > Hedayat > > > /*Sander van Dijk <sgv...@gm...>*/ wrote on Wed, 22 May 2013 > 16:25:20 +0100: >> Hey all, >> >> With just over a month to go, I guess it's time to put a release >> together for the simulator version for Eindhoven. I just committed >> something I wanted in there: the ability to send foul information to >> the monitor. Attached is a quick (and a bit dirty) patch to make this >> information visible in RoboViz; you should get a list underneath the >> top bar showing fouls for 10 seconds. >> >> With this, my suggestion is to put Patrick's rule implementations >> into the new version, but have no automatic penalization on them. >> Instead, the foul is shown in the monitor (with a yellow card instead >> of a red card), and the human referee can decide on the action to >> take. Even if we ignore them in the end, it should still give us an >> idea of how reasonable the calls are in a tournament. >> >> Looking forward to your opinins. >> >> @Hedayat: you have the most experience putting a release together, >> would you have time to do this in the near future? >> >> Sander >> >> >> -- >> Adaptive Systems Research Group >> Department of Computer Science >> University of Hertfordshire >> United Kingdom >> >> >> _______________________________________________ >> rc-ss3d-tc mailing list >> rc-...@li... >> http://lists.robocup.org/listinfo.cgi/rc-ss3d-tc-robocup.org > > > > _______________________________________________ > rc-ss3d-tc mailing list > rc-...@li... > http://lists.robocup.org/listinfo.cgi/rc-ss3d-tc-robocup.org |