<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hi,</p>
<p>I like this proposal, especially as the random component from my proposal may be less fair.</p>
<p>The kick positions sound good, I had similar ones in mind. I would not consider the third kick as the easiest however,</p>
<p>as the ball might go out of camera sight at a certain height.</p>
<p>With 4 participating teams, we have 48 kicks which would be reasonable to do in 90 minutes.</p>
<p>Just to be clear, the robot does not change the direction significantly before the kick so that the intercepting robot</p>
<p>has a chance to choose a reasonable starting position.</p>
<p>Best,</p>
<p>Alex</p>
<p><br /></p>
<p>On 2017-07-24 19:41, Andre Ryll wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --> <!-- head ignored --><!-- meta ignored -->
<p>I recommend to use three different positions for the chip kick. As I have implemented our chip kick detection I am well aware of the difficulties of detecting such kicks. I suggest the following positions:<br /> - From a corner to the center of the field. This is most difficult to detect as the ball goes through the camera axis and does not show a parabola in the images.<br /> - From a corner along the long side of the field. Here, a single camera is available as well but the ball shows a significant parabola. The ball may vanish from the images at its high points.<br /> - From the center to the goal or vice versa. This is most simple as the ball is visible on multiple cameras, basically providing you stereo vision.<br /> <br /> We used these exact position at IranOpen. Furthermore, we used distances from 2 - 3.5m. Basically, we had 2m, 2.5m, 3m, and 3.5m in the bucket. Then we drew them in random order. Thereby, each team gets the same chips, but cannot predict the order they were executed. To speed up the challenge, this can certainly be reduced to two distances. The technical difficulties of the different positions might be used to weight scores.</p>
<p>Cheers,<br /> <br /> Andre Ryll<br /> <span>Project Leader & Founder of<br /> TIGERs Mannheim<br /> </span></p>
<br />
<div class="moz-cite-prefix">Am 24.07.2017 um 19:26 schrieb Danny Zhu:</div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">That sounds reasonable to me, though I think we'll need to see it in practice. If the range needs to be wider, we can always add variation in the commanded distance as well. The exact distribution within the range shouldn't matter much, as long as the same thing is done for all competitors, right? <br /> <br /> Danny <br /> <br /> On 07/24/2017 07:18 PM, Alexander Danzer wrote: <br /> > That's a good point. <br /> > <br /> > However, when I investigated the possibilities of chip kick estimation, <br /> > I found that only considering a robot's orientation does not provide enough <br /> > precision for determining the kick's direction precise enough <br /> > for a distance of more than 3 meters. <br /> > <br /> > But we certainly should have some variety in the distance. When I wrote <br /> > 3.5 meters, I had in mind that the kick was performed with an ER-Force <br /> > robot, which has significant variations in the actual kick distance. <br /> > I would estimate deviations of around 20 centimeters for said distance, <br /> > but I have to check our current hardware tomorrow. <br /> > <br /> > So, what do you think of a distance in the range of 3.0 to 3.5 meters? <br /> > (with an ER-Force robot, this is quite hard to guarantee however with <br /> > an equal probability distribution). <br /> > <br /> > <br /> > On 2017-07-24 18:55, Joydeep Biswas wrote: <br /> >>> On Jul 24, 2017, at 6:22 PM, Alexander Danzer <a class="moz-txt-link-rfc2396E" href="mailto:alex@dnzr.name"><alex@dnzr.name></a> wrote: <br /> >>> <br /> >>> The ball touches ground after 3.5 meters in field plane. <br /> >> <br /> >> If the chip kick distance is fixed, then the intercepting robot only <br /> >> needs to know the kicking robots orientation when the ball is kicked - <br /> >> it does not really need to do chip kick estimation. <br /> >> <br /> >> -Joydeep <br /> > _______________________________________________ <br /> > rc-ssl-tc mailing list <br /> > <a class="moz-txt-link-abbreviated" href="mailto:rc-ssl-tc@lists.robocup.org">rc-ssl-tc@lists.robocup.org</a> <br /> > <a class="moz-txt-link-freetext" href="http://lists.robocup.org/cgi-bin/mailman/listinfo/rc-ssl-tc">http://lists.robocup.org/cgi-bin/mailman/listinfo/rc-ssl-tc</a> <br /> _______________________________________________ <br /> Management mailing list <br /> <a class="moz-txt-link-abbreviated" href="mailto:Management@tigers-mannheim.de">Management@tigers-mannheim.de</a> <br /> <a class="moz-txt-link-freetext" href="http://tigers-mannheim.de/cgi-bin/mailman/listinfo/management">http://tigers-mannheim.de/cgi-bin/mailman/listinfo/management</a> </blockquote>
<br /><!-- html ignored --><br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br /> robocup-small mailing list<br /> <a href="mailto:robocup-small@cc.gatech.edu">robocup-small@cc.gatech.edu</a><br /> <a href="https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small">https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small</a></div>
</blockquote>
<p><br /></p>
</body></html>