Difference between revisions of "CS382:Topics Matrix"

From Earlham CS Department
Jump to navigation Jump to search
Line 1: Line 1:
−
This is meant to be a rough draft of an idea Charlie and I talked about: that we should have a n-by-n matrix of different ideas that we want to make sure we hit.  Since an n-by-n matrix is hard to display (especially on a wiki!) it turned into a list instead.  Once this is finished, we should make sure that at least one unit addresses each one of these topics.
+
__NOTOC__
  
−
Initial "dimensions" of the matrix:
+
=== Course Structure ===
−
* [[#Scientific Disciplines|Scientific disciplines]]
+
When your unit(s) are in a stable location change the Topic column to an actual link.  When it's ready to be reviewed put a "Y" in the Ready to Review column.  This is the signal that the reviewers will look for; no Y, no review.
−
* [[#Scientific Tools|Scientific tools]]
 
−
* [[#Guideline Skill Sets|Skill sets]] from the [[CS382:attributes-guidelines|attribute guidelines]]
 
−
 
 
−
In Silico is designed to meet Earlham's Analytical Reasoning general education requirement, specifically the Quantitative Reasoning component.  The full description is here: http://www.earlham.edu/curriculumguide/academics/analytical.html
 
−
 
 
−
There are a number of themes that run through the units:
 
−
* Quantitative reasoning
 
−
* Using models, modifying models, developing models
 
−
* Validation and verification
 
−
* Using tools, broadly defined
 
−
* Data -> information -> knowledge
 
−
* Algorithmic thinking
 
−
* Abstraction
 
−
* Computational thinking
 
−
 
 
−
The units should have the following attributes, for the pedagogical ones all units should try to adhere to them, for the others we just need to make sure at least one unit covers them.
 
−
* Pedagogical
 
−
** Inquiry based learning
 
−
** Scaffolded
 
−
** Open-ended to a degree
 
−
** Using science to illustrate the diversity and complexity of the world around us
 
  
−
* Structural
 
−
** Metric system
 
−
** OSX, Windows, Linux whenever possible (lab sizes and locations)
 
−
** Classroom response system - questions for each unit, participation/attendance measured by response rate?
 
−
 
−
Mechanical and structural stuff:
 
−
* Scales well, say 20-80 students
 
−
** Automated assessment tools
 
−
** Effective use of TAs
 
−
 
−
 
−
=== Scientific Disciplines ===
 
−
* Biology
 
−
* Chemistry
 
−
* Physics
 
−
* Geology (earthquakes)
 
−
* Environmental science
 
−
* One of the social sciences
 
−
 
−
Potentially:
 
−
* Astronomy
 
−
 
−
=== Scientific Tools ===
 
−
* Equation-based modeling
 
−
* Agent-based modeling: Netlogo or AgentSheets
 
−
* Systems-based modeling: Vensim
 
−
* Visualization/visual modeling
 
−
* Mashups and Google Earth
 
−
 
−
Potentially
 
−
* SecondLife or OpenSim
 
−
 
−
=== Foundation Skills ===
 
−
* Creating a graph
 
−
* Interpreting a graph
 
−
* Basic statistics
 
−
* Estimation
 
−
* Parameter sweep
 
−
* Data collection
 
−
 
−
Potentially
 
−
* Building a physical model
 
−
 
−
=== Thoughts ===
 
−
Some of these should go somewhere, and some of these should be in every unit.
 
−
 
−
* What data do I need to collect, how do I collect it accurately, and then how do I build it
 
−
** Perhaps one unit where they have to go out and collect data to see how hard it really is, how about modeling campus (rectangle and heart)
 
−
* Data collection: sensor nets, lasers
 
−
 
−
=== Course Structure ===
 
−
When your unit(s) are ready to be reviewed change these placeholders to actual links.  This is the signal that the reviewers will look for; no link, no review.
 
 
<center>
 
<center>
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
Line 89: Line 16:
 
! Tool(s)
 
! Tool(s)
 
! Notes
 
! Notes
 +
! Ready to Review?
 
|-
 
|-
 
| 1
 
| 1
Line 97: Line 25:
 
| TBD
 
| TBD
 
| TBD
 
| TBD
 +
|
 
|  
 
|  
 
|-
 
|-
Line 106: Line 35:
 
| Critical parameter, parameter sweep
 
| Critical parameter, parameter sweep
 
| Agent modeling, NetLogo
 
| Agent modeling, NetLogo
 +
|
 
|  
 
|  
 
|-
 
|-
Line 116: Line 46:
 
| Mashup
 
| Mashup
 
| Software and physical
 
| Software and physical
 +
|
 
|-
 
|-
 
| 4
 
| 4
Line 125: Line 56:
 
| Mashup
 
| Mashup
 
| Tufte based approach?   
 
| Tufte based approach?   
 +
|
 
|-
 
|-
 
| 5-6
 
| 5-6
Line 134: Line 66:
 
| TBD
 
| TBD
 
| Software and physical?
 
| Software and physical?
 +
|
 
|-
 
|-
 
| 7-8
 
| 7-8
Line 143: Line 76:
 
| TBD
 
| TBD
 
| Software and physical?
 
| Software and physical?
 +
|
 
|-
 
|-
 
| 9  
 
| 9  
Line 151: Line 85:
 
| TBD
 
| TBD
 
| Agent modeling, NetLogo
 
| Agent modeling, NetLogo
 +
|
 
|  
 
|  
 
|-
 
|-
Line 160: Line 95:
 
| TBD
 
| TBD
 
| TBD
 
| TBD
 +
|
 
|  
 
|  
 
|-
 
|-
Line 169: Line 105:
 
| TBD
 
| TBD
 
| TBD
 
| TBD
 +
|
 
|  
 
|  
 
|}
 
|}
 
</center>
 
</center>
  
−
Some would be one week long, some two weeks. Make Topic entry into a link when the unit is in "First Draft" form and ready to be reviewed.
+
=== Context ===
 +
There are a number of themes that run through the units:
 +
* Quantitative reasoning
 +
* Using models, modifying models, developing models
 +
* Validation and verification
 +
* Using tools, broadly defined
 +
* Data -> information -> knowledge
 +
* Algorithmic thinking
 +
* Abstraction
 +
* Computational thinking
 +
 
 +
The units should have the following attributes, for the pedagogical ones all units should try to adhere to them, for the others we just need to make sure at least one unit covers them.
 +
* Pedagogical
 +
** Inquiry based learning
 +
** Scaffolded
 +
** Open-ended to a degree
 +
** Using science to illustrate the diversity and complexity of the world around us
 +
 
 +
* Structural
 +
** Metric system
 +
** OSX, Windows, Linux whenever possible (lab sizes and locations)
 +
** Classroom response system - questions for each unit, participation/attendance measured by response rate?
 +
 
 +
Mechanical and structural stuff:
 +
* Scales well, say 20-80 students
 +
** Automated assessment tools
 +
** Effective use of TAs
 +
 
 +
==== Scientific Tools ====
 +
* Equation-based modeling
 +
* Agent-based modeling: Netlogo or AgentSheets
 +
* Systems-based modeling: Vensim
 +
* Visualization/visual modeling
 +
* Mashups and Google Earth
 +
 
 +
Potentially
 +
* SecondLife or OpenSim
 +
 
 +
==== Foundation Skills ====
 +
* Creating a graph
 +
* Interpreting a graph
 +
* Basic statistics
 +
* Estimation
 +
* Parameter sweep
 +
* Data collection
 +
 
 +
Potentially
 +
* Building a physical model
 +
 
 +
==== Thoughts ====
 +
Some of these should go somewhere, and some of these should be in every unit.
 +
 
 +
* What data do I need to collect, how do I collect it accurately, and then how do I build it
 +
** Perhaps one unit where they have to go out and collect data to see how hard it really is, how about modeling campus (rectangle and heart)
 +
* Data collection: sensor nets, lasers

Revision as of 10:01, 16 February 2009


Course Structure

When your unit(s) are in a stable location change the Topic column to an actual link. When it's ready to be reviewed put a "Y" in the Ready to Review column. This is the signal that the reviewers will look for; no Y, no review.

D R A F T
Week Topic Unit(s) Who Discipline(s) Skill(s) Tool(s) Notes Ready to Review?
1 What's a Model? Foundations Sam, Mikio Generic TBD TBD
2 Using a Dynamic Model Fire Fitz, Vlado Forestry Critical parameter, parameter sweep Agent modeling, NetLogo
3 Building a Static Model Area Philip, Bryan Generic Accuracy, precision, estimation Mashup Software and physical
4 Visualizing Data Mashup Matt, Nate TBD TBD Mashup Tufte based approach?
5-6 Structural Modeling Bridge Bryan, Dylan Physics TBD TBD Software and physical?
7-8 Equation Modeling Rocket Vlado, Dylan Math, Physics TBD TBD Software and physical?
9 Modeling Society People Nate, Philip Sociology TBD Agent modeling, NetLogo
10-11 Systems Dynamics Models Systems Dynamics Placeholder Matt, Sam Sociology TBD TBD
12-13 Chaotic Systems Climate Mikio, Fitz Lots TBD TBD

Context

There are a number of themes that run through the units:

  • Quantitative reasoning
  • Using models, modifying models, developing models
  • Validation and verification
  • Using tools, broadly defined
  • Data -> information -> knowledge
  • Algorithmic thinking
  • Abstraction
  • Computational thinking

The units should have the following attributes, for the pedagogical ones all units should try to adhere to them, for the others we just need to make sure at least one unit covers them.

  • Pedagogical
    • Inquiry based learning
    • Scaffolded
    • Open-ended to a degree
    • Using science to illustrate the diversity and complexity of the world around us
  • Structural
    • Metric system
    • OSX, Windows, Linux whenever possible (lab sizes and locations)
    • Classroom response system - questions for each unit, participation/attendance measured by response rate?

Mechanical and structural stuff:

  • Scales well, say 20-80 students
    • Automated assessment tools
    • Effective use of TAs

Scientific Tools

  • Equation-based modeling
  • Agent-based modeling: Netlogo or AgentSheets
  • Systems-based modeling: Vensim
  • Visualization/visual modeling
  • Mashups and Google Earth

Potentially

  • SecondLife or OpenSim

Foundation Skills

  • Creating a graph
  • Interpreting a graph
  • Basic statistics
  • Estimation
  • Parameter sweep
  • Data collection

Potentially

  • Building a physical model

Thoughts

Some of these should go somewhere, and some of these should be in every unit.

  • What data do I need to collect, how do I collect it accurately, and then how do I build it
    • Perhaps one unit where they have to go out and collect data to see how hard it really is, how about modeling campus (rectangle and heart)
  • Data collection: sensor nets, lasers
Retrieved from "https://wiki.cs.earlham.edu/index.php?title=CS382:Topics_Matrix&oldid=7568"