CS382:Topics Matrix

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
• Scientific tools
• Skill sets from the attribute guidelines

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

1. What's a model (foundational material that isn't spread-out or requires more than one pass) - no lab
2. Using a dynamic model - fire
   1. Agent modeling with an existing model
   2. Critical parameter
   3. Parameter sweep
3. Building a static model - model area of parts of campus
4. Structural modeling - bridge building (software and physical?)
5. Equation modeling - water rockets and relationship between launch angle and distance traveled
6. Agent modeling - social systems
7. Chaotic systems - climate model
8. Systems dynamics - viral spread or population dynamics
9. Visualizing data - mashup

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.