<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: [LOA] Hypothesis #3: Test Your Abstractions	</title>
	<atom:link href="/2012/loa-hypothesis-3-test-your-abstractions/feed/" rel="self" type="application/rss+xml" />
	<link>/2012/loa-hypothesis-3-test-your-abstractions/</link>
	<description>less helpful</description>
	<lastBuildDate>Thu, 20 Sep 2012 15:23:38 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>
		By: Max		</title>
		<link>/2012/loa-hypothesis-3-test-your-abstractions/#comment-515219</link>

		<dc:creator><![CDATA[Max]]></dc:creator>
		<pubDate>Thu, 20 Sep 2012 15:23:38 +0000</pubDate>
		<guid isPermaLink="false">/?p=14942#comment-515219</guid>

					<description><![CDATA[I have a challenge for the team: when testing measurable phenomenon (shooting baskets, counting Facebook users) it&#039;s easy to see what testing the abstraction means. But some of the abstractions we hope students learn and use in math class refer only internally, to other mathematical objects.

So... I wonder what some good examples of those abstractions are, and what it means when you test them? Is defining a quadrilateral with 4 congruent sides as a special type of quadrilateral an abstraction? Clearly testing that abstraction wouldn&#039;t just be looking up the definition of rhombus in the back of the book... What makes that definition robust, useful, etc.?]]></description>
			<content:encoded><![CDATA[<p>I have a challenge for the team: when testing measurable phenomenon (shooting baskets, counting Facebook users) it&#8217;s easy to see what testing the abstraction means. But some of the abstractions we hope students learn and use in math class refer only internally, to other mathematical objects.</p>
<p>So&#8230; I wonder what some good examples of those abstractions are, and what it means when you test them? Is defining a quadrilateral with 4 congruent sides as a special type of quadrilateral an abstraction? Clearly testing that abstraction wouldn&#8217;t just be looking up the definition of rhombus in the back of the book&#8230; What makes that definition robust, useful, etc.?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Santosh		</title>
		<link>/2012/loa-hypothesis-3-test-your-abstractions/#comment-515112</link>

		<dc:creator><![CDATA[Santosh]]></dc:creator>
		<pubDate>Thu, 20 Sep 2012 12:35:33 +0000</pubDate>
		<guid isPermaLink="false">/?p=14942#comment-515112</guid>

					<description><![CDATA[At this point you have reached a very specific abstraction - a *model*.  I prefer to gradually switch to calling it that.

We are no longer just talking about which are the extraneous details that can be dropped in describing the attributes of a given situation. i.e &quot;Which are the efficient abstractions?&quot;

we are now  talking about making a prediction about the *behavior* of a system.  Instead of a building a full- or reduced-scale model, we replace parts of the system with equations (an abstraction, yes), that describe the behavior of specific components.  If we get this right, our model has predictive ability; a necessary feature for a model to be valid.

Models-with-predictive-ability is such a powerful concept, some of them acquire the status of a theory in physics. (e.g. The Standard Model)

This aspect, the predictive ability of models, is sufficiently key, that I feel our students ought to become familiar with that term - model - used in appropriate context.  

So I vote for &quot;Test your model&quot;]]></description>
			<content:encoded><![CDATA[<p>At this point you have reached a very specific abstraction &#8211; a *model*.  I prefer to gradually switch to calling it that.</p>
<p>We are no longer just talking about which are the extraneous details that can be dropped in describing the attributes of a given situation. i.e &#8220;Which are the efficient abstractions?&#8221;</p>
<p>we are now  talking about making a prediction about the *behavior* of a system.  Instead of a building a full- or reduced-scale model, we replace parts of the system with equations (an abstraction, yes), that describe the behavior of specific components.  If we get this right, our model has predictive ability; a necessary feature for a model to be valid.</p>
<p>Models-with-predictive-ability is such a powerful concept, some of them acquire the status of a theory in physics. (e.g. The Standard Model)</p>
<p>This aspect, the predictive ability of models, is sufficiently key, that I feel our students ought to become familiar with that term &#8211; model &#8211; used in appropriate context.  </p>
<p>So I vote for &#8220;Test your model&#8221;</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
