Finding Information Inside a Conceptual Model (EMI 201)

A scientist's paragraph counts as a model the moment it connects a cause to a result. If Scientist 1 writes that sea-surface temperature above a threshold for a number of days drives algae out of coral tissue, that sentence is a complete causal chain: condition, then mechanism, then outcome. No diagram required. The diagram is just one way to draw a chain that already exists in the words.

To pull information out of a written model, read it as a sequence and label each link: trigger, mechanism, result. Underline the numbers and conditions, since questions often hinge on exact values like a temperature threshold or a nutrient concentration. The key discipline is staying inside one viewpoint at a time. If two scientists disagree, Scientist 1's chain and Scientist 2's chain are separate systems, each with its own trigger, and the question will specify whose model you're reading. Borrowing a cause from the wrong scientist is the single most common error.

This skill sits right before evaluating whether a model holds up against evidence or whether a prototype succeeded, so get the retrieval step right first: you cannot judge a claim you have misread. When the model shows up as a flowchart instead of prose, the task gets easier rather than harder. The arrows do the labeling for you, so the cause of any box is simply whatever box an arrow leads from. Reading prose demands that you build the chain yourself; reading a flowchart only demands that you trace an arrow backward.