Difference between revisions of "CS382:Topics Matrix"

From Earlham CS Department
Jump to navigation Jump to search
(Course Structure - D R A F T)
Line 45: Line 45:
 
* Data collection: sensor nets, lasers
 
* Data collection: sensor nets, lasers
  
=== Course Structure - D R A F T ===
+
 
# What's a model (foundational material that isn't spread-out or requires more than one pass) - no lab (Sam)
+
<center>
# Using a dynamic model - fire (Fitz)
+
{| class="wikitable" border="1"
## Agent modeling with an existing model
+
|+ Course Structure - D R A F T
## Critical parameter
+
|-
## Parameter sweep
+
! Topic
# Building a static model - model area of parts of campus (, Philip)
+
! Unit(s)
# Visualizing data - mashup (Matt, Nate)
+
! Discipline(s)
# Structural modeling - bridge building (software and physical?) (Bryan)
+
! Skill(s)
# Equation modeling - water rockets and relationship between launch angle and distance traveled (Vlado)
+
! Tool(s)
# Agent modeling - social systems (Nate, Philip)
+
! Notes
 +
|-
 +
| What's a Model?
 +
| Foundations
 +
| Generic
 +
| TBD
 +
| TBD
 +
|
 +
|-
 +
| Using a Dynamic Model
 +
| Fire
 +
| Forestry
 +
| Critical parameter, parameter sweep
 +
| Agent modeling, NetLogo
 +
|
 +
|-
 +
| Building a Static Model
 +
| Area
 +
| Generic
 +
| Accuracy, precision, estimation
 +
| Mashup
 +
|
 +
|-
 +
| Visualizing Data
 +
| Mashup
 +
| TBD
 +
| TBD
 +
| Mashup
 +
|
 +
|-
 +
| Structural Modeling
 +
| Bridge
 +
| Physics
 +
| TBD
 +
| TBD
 +
| Software and physical?
 +
|-
 +
| Equation Modeling
 +
| Rocket
 +
| Physics
 +
| TBD
 +
| TBD
 +
| Software and physical?
 +
|-
 +
| Modeling Society
 +
| People
 +
| Sociology
 +
| TBD
 +
| Agent modeling, NetLogo
 +
|
 +
|}
 +
</center>
 +
 
 
# Systems dynamics - population dynamics or medical half-life modeling (Matt)
 
# Systems dynamics - population dynamics or medical half-life modeling (Matt)
 
# Chaotic systems - climate model (Mikio)
 
# Chaotic systems - climate model (Mikio)

Revision as of 08:06, 11 February 2009

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.

Initial "dimensions" of the matrix:

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 - D R A F T
Topic Unit(s) Discipline(s) Skill(s) Tool(s) Notes
What's a Model? Foundations Generic TBD TBD
Using a Dynamic Model Fire Forestry Critical parameter, parameter sweep Agent modeling, NetLogo
Building a Static Model Area Generic Accuracy, precision, estimation Mashup
Visualizing Data Mashup TBD TBD Mashup
Structural Modeling Bridge Physics TBD TBD Software and physical?
Equation Modeling Rocket Physics TBD TBD Software and physical?
Modeling Society People Sociology TBD Agent modeling, NetLogo
  1. Systems dynamics - population dynamics or medical half-life modeling (Matt)
  2. Chaotic systems - climate model (Mikio)


Some would be one week long, some two weeks. Make these into links to the units as they are identified. List the high-level attributes for each here as Using a simple dynamic model is.