I suggest to keep the number of variations at one for each subtype.
That will make it easier also for spectators.

Greetings
Klaus

Am 13.06.2013 11:15, schrieb Hedayat Vatankhah:
That's fine with me, I can do that if there are no objections. We might create several variations of each type too. There are two limits for using heterogeneous players for each team now: teams can use up to 3 players of a single hetero type, and up to 9 hetero players in total. The limits can be configured too.


Klaus Dorer <klaus.dorer@hs-offenburg.de> wrote on Thu, 13 Jun 2013 06:04:49 +0200:
Yes, it would be good if you, Hedayat, could throw the dice to create values in the range I have sent and copied below and publish the files as soon as possible. That way no team has the advantage of knowing the values before the other. Thank you!

My suggestions for the value areas (min change, max change) are as follows:
Type1 LongLeg (2cm, 6cm) (split in half at the hip, half at the Ankle)
Type2 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.

Greetings
Klaus

Am 13.06.2013 00:06, schrieb Patrick MacAlpine:
OK.  I thought it was decided that the robot types would be released 2 weeks before the competition (which we're now within) and that it would be by someone not on a team (Hedayat for example).  This is based on the email exchanges from a different email thread which I have pasted below.
- Patrick

-----------------------------
Agree on both points.
No new foul rules applied, just visualization.
Two weeks announcement is also fine with me.

Greetings
Klaus

Am 23.05.2013 08:44, schrieb Patrick MacAlpine:

The penalty detection stuff I put together was a quick prototype of the system that Klaus had suggested and should probably be looked at a little and tuned before using it in a competition.  While I think it's fine to show possible fouls, I might be hesitant to have referees acting on them -- as a likely referee at this year's competition I'd rather not have to be making such judgment calls myself:)

I like the suggestions for new Nao types.  I doubt many teams will use them however if only given them a week in advance.  I think it might be better to give them out closer to two weeks before the competition in order to give teams more time to experiment with them and possibly integrate them into their teams.

Regards,
Patrick


On Thu, May 23, 2013 at 12:52 AM, Klaus Dorer <klaus.dorer@hs-offenburg.de> wrote:
Hello Sander,

good to see things develop :-)

The TC has decided to postpone the rule changes to next year, since they had not been tested early enough.
But as you say, we could add the changes to only display how the rules would be applied, at least in the early rounds of the tournament. This will give a good impression as to whether the current implementation is too rigid or too loose or just fitting.

Of course this makes me greedy. Since you are in that matter now: would it be easy to make an extension that allows us to distinguish heterogeneous players in roboviz. E.g. by changing the leg or feet colors slightly?

Hedayat is right that we have not finally decided on the number of heterogeneous players. I suggest to allow at most 3 players of each new type and at most 11 standard Naos as has been the case. Also I suggest to have no more than 3 new types, so that at least 2 standard Naos have to be used. So far I know of only two suggestions for alternate types, the two we tested at the German Open. One with faster ankle pitch, but slower ankle roll. The other with longer upper leg and, as a result from the test at German Open, also longer upper arms. Any other type suggestions?
We should announce the final types roughly one week ahead of the competition say the 17th of June?
Since our team is planning to use them I further suggest that this is done by someone else. Hedayat? I think the types should be used as suggested, but the actual values for the deviations should be randomly generated. The values should be generated so that they are at least x% higher than standard but at most y%. I can specify reasonable x and y values for the two types above, but am happy to have your suggestions.

Greetings
Klaus

 
----------------------------------



On Wed, Jun 12, 2013 at 4:33 PM, Hedayat Vatankhah <hedayatv@gmail.com> wrote:
Thanks for testing the packages. But I can't answer your questions. Justin will probably update RoboViz soon, and the latter should be announced by OC. But it is not going to be part of 0.6.7 release. They will release a naorobottypes.rb for RoboCup 2013 separately.

Good luck,
Hedayat


Patrick MacAlpine <patmac@gmail.com> wrote on Wed, 12 Jun 2013 15:27:00 -0500:
I am able to compile, install, and run the packages successfully on Ubuntu 12.04.� Has RoboViz been updated to show the reported fouls yet?� Also when will naorobottypes.rb be updated with the models for this year's competition?

- Patrick


On Wed, Jun 12, 2013 at 3:01 PM, Hedayat Vatankhah <hedayatv@gmail.com> wrote:
Hi,
Please test the following packages and let me know if there are any problems compiling, installing or running the packages:
http://hedayat.fedorapeople.org/misc/simspark-0.2.4.tar.gz
http://hedayat.fedorapeople.org/misc/rcssserver3d-0.6.7.tar.gz

Regards,
Hedayat

Dear all,
I'm preparing the release and Sander's commit was just on time ;). Actually, I've put a test release of simspark at [1], and I'll put rcssserver3d release there too soon. It'd be nice if you test the release file to see if they work fine. I prefer to release them ASAP, since we are already late.

Thanks a lot Sander. I'll try to test.

Regards,
Hedayat

[1] http://hedayat.fedorapeople.org/misc/

Sander van Dijk <sgvandijk@gmail.com> wrote on Wed, 12 Jun 2013 12:31:58 +0200:
I have integrated and committed them. Did some tests, but please test as well. If you run it, plus roboviz with the attached patch (note this is slightly different than the earlier one, because there is a new foul), you will see a lot of yellow cards come by. I foresee we will turn it off soon in the competition :) but at least there is some feedback, and bit easier to configure and tweak.

Sander



On 9 June 2013 20:44, Hedayat Vatankhah <hedayatv@gmail.com> wrote:
Hi Sander,


Sander van Dijk <sgvandijk@gmail.com> wrote on Sun, 9 Jun 2013 18:55:44 +0100:
Hi Hedayat,

My idea was indeed to have the yellow/red selection made in RoboViz, where non-penalized fouls are shown with yellow, penalized with red. If you think it's easier, I can integrate them; would be able to do that tomorrow.
Yes, it'd be great if you integrate them. :)

Regards,
Hedayat




I don't have any further pending changes.

Sander


On 8 June 2013 20:37, Hedayat Vatankhah <hedayatv@gmail.com> wrote:
Hi Sander,



Sander van Dijk <sgvandijk@gmail.com> 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.
I had a quick look to your changes in rcssserver3d, but I don't know how the color of the card is determined. How should we do it in rcssserver3d? Do you propose to decide about the color inside the monitor (e.g. Roboviz) by sending foul type but not adding an agent's foul counter?
I wanted to integrate Patrick's implementation but I'm not sure about the details.

P.S. I'd like to prepare the release in a few days (hopefully 2-3). Please let me know if there are any pending changes.


Regards,
Hedayat



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-ss3d-tc@lists.robocup.org
http://lists.robocup.org/listinfo.cgi/rc-ss3d-tc-robocup.org




--
Adaptive Systems Research Group
Department of Computer Science
University of Hertfordshire
United Kingdom




--
Adaptive Systems Research Group
Department of Computer Science
University of Hertfordshire
United Kingdom



------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Simspark Generic Physical MAS Simulator
simspark-devel mailing list
simspark-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/simspark-devel