![]() |
Quote:
Again, if the throw-in rule said "The throw-in ends when the ball is LEGALLY touched inbounds," the situation would be different. But it doesn't. :p |
Quote:
|
Why do you presume that what's said
Quote:
|
Re: Why do you presume that what's said
Quote:
|
Quote:
|
What are the rules that we are mindful of them?
The following refers to forward-chaining logic - logic which is data-driven. The opposite, backward-chaining is so-called goal-driven logic. The 'rules' of basketball apply both systems willy-nilly. I am sympathetic towards those who would like there to be an answer to every 'situation' - but, unsurprisingly, there isn't.
---------------- A number of conflict resolution strategies are typically used to decide which rule to fire. These include: Don't fire a rule twice on the same data. We don't want to keep on adding to working memory. Fire rules on more recent working memory elements before older ones. This allows the system to follow through a single chain of reasoning, rather than keeping on drawing new conclusions from old data. Fire rules with more specific preconditions before ones with more general preconditions. This allows us to deal with non-standard cases. If, for example, we have a rule ``IF (bird X) THEN ADD (flies X)'' and another rule ``IF (bird X) AND (penguin X) THEN ADD (swims X)'' and a penguin called tweety, then we would fire the second rule first and start to draw conclusions from the fact that tweety swims. These strategies may help in getting reasonable behaviour from a forward chaining system, but the most important thing is how we write the rules. They should be carefully constructed, with the preconditions specifying as precisely as possible when different rules should fire. Otherwise we will have little idea or control of what will happen. Thanks, Alison . . . |
Re: Re: Why do you presume that what's said
Quote:
A is not going to get an 'extra' possession. They never finished the one they had, due to B's violation - so they'll get to finish it later, if in fact the chance comes again. If it doesn't, would that be unfair? It would take some serious backward-chaining, 'goal-oriented' rules to decide that! It's probably not very decidable. |
Re: Why do you presume that what's said
Quote:
|
Quote:
Deflecting the ball OOB <b>isn't</b> illegal? It isn't a violation? Rule 9-3-1 seems to say something completely different. That's a basic, Juulie. You're over-thinking this one. "What-ifs" and rationalizations won't work when you have clear rules language. The relevant rules being discussed aren't in any way ambiguous. |
Re: What are the rules that we are mindful of them?
Quote:
Sheer freaking bafflegab! |
Quote:
|
Re: Re: Why do you presume that what's said
Quote:
I'm not saying the ball can be kicked without being touched. I'm saying that, if you have two events occur simultaneously, you can resolve the situation, in the absence of a rule for doing so, this by concluding that: 1) Event A occurred before event B; Kick before touch - ball is dead, touch didn't happen. 2) B occurred before A (Touch before kick, throw-in ended, arrow to Team B, ball back to Team A for a spot throw-in) Precedent for concluding that one event occurred before another as a way of resolving an apparently simultaneous situation exists in the recently addressed matter of catching the tap. Stupid? Nice talk. |
Quote:
http://www.sodamnfunny.com/Animation...guinsdance.gif |
Re: Re: Re: Why do you presume that what's said
Quote:
tia. |
Quote:
[/B][/QUOTE]Tsk, tsk, tsk..... He's already explained that. The Laws of Physics don't apply to penguins named Tweety. |
All times are GMT -5. The time now is 07:19pm. |