Checking the answer for physical/logical adequacy

LVL: FREE

MODULE: Logic, Dimensions, and Modeling

[EXEC: MICRO_CORE]

āœ–ļø 1. Order-of-Magnitude Checks

šŸ” Order-of-Magnitude Checks

  • Compare your answer to real-world scales you already know.
  • If calculating a person's weight gives 50000 kg, something is wrong.
  • Round numbers to one significant figure for quick mental checks.
  • Ask: "Is this in the ballpark of what I expect?"
  • Powers of ten matter more than exact digits here.

Example: You calculate a car's speed as 5000 m/s. Highway speeds are around 30 m/s, so 5000 is impossibly high — likely a unit error.

šŸ’” Think: "Could I actually see/hold/measure this in real life?"

[EXEC: DEEP_COMPUTE]

1. Order-of-Magnitude Checks

Order-of-Magnitude Checks

An order-of-magnitude check estimates whether a computed result falls within a plausible range by comparing it to known reference values or physical constraints. This technique identifies catastrophic errors (such as misplaced decimal points or unit conversion mistakes) before detailed verification.

Intuition: If you calculate the mass of a car as 50000000 kg or 0.005 kg, both answers are immediately suspect because typical cars weigh around 1000–2000 kg.

Core Rules:

  • Compare the result to familiar benchmarks (e.g., human height is roughly 1–2 m, not 100 m or 0.01 m)
  • Check units and powers of ten separately; a factor of 1000 error often signals unit confusion
  • Reject answers that violate known physical bounds (e.g., speed exceeding light speed, negative absolute temperature)
  • Use rough mental arithmetic to verify the calculation's scale

Consequence: This method catches gross errors instantly, preventing propagation into downstream calculations.

Example: Computing Earth's radius as 6400000 m is reasonable (order 10610^6 m), but 64 m would be absurd.

TASK_1[0 / 3]
LVL_2
MOD: SANITY_CHECK

A student calculates the height of a standard classroom door. According to the principles of order-of-magnitude checks, which of the following results is the only plausible estimate?

DEEP_COMPUTE
ULTRA
[EXEC: MICRO_CORE]

āœ–ļø 2. Sign Checks

āž•āž– Sign Checks

  • A negative distance or negative time usually signals an error.
  • Check if the sign matches the physical direction (up vs down, profit vs loss).
  • Temperature can be negative, but absolute temperature in Kelvin cannot.
  • If velocity is negative, confirm your coordinate system allows it.
  • Profit should be positive; debt or loss should be negative.

Example: You calculate a bank account balance as -200 dollars after a deposit. The negative sign contradicts the deposit action — recheck your arithmetic.

šŸ’” Ask: "Does this sign match the story of the problem?"

[EXEC: DEEP_COMPUTE]

2. Sign Checks

Sign Checks

A sign check verifies whether the algebraic sign (positive or negative) of a computed quantity aligns with the physical or logical context of the problem. Many real-world variables have inherent sign constraints that must be respected.

Intuition: If you calculate a person's age as āˆ’5-5 years or a distance as āˆ’12-12 meters (when measuring separation), the negative sign signals an error in setup or computation.

Core Rules:

  • Identify physically non-negative quantities: mass, distance, absolute temperature, population count, time duration (in most contexts)
  • Recognize directional quantities: velocity, acceleration, force, profit/loss, where sign indicates direction or surplus/deficit
  • Verify that the sign matches the problem's stated conditions (e.g., "moving left" implies negative velocity if right is positive)
  • Check whether sign changes occur at expected transitions (e.g., profit turning to loss)

Consequence: Sign errors often reveal algebraic mistakes, incorrect coordinate system choices, or misapplied formulas.

Example: Calculating gravitational force as +500+500 N when it should attract (negative direction) indicates a sign error in the force law.

TASK_1[0 / 3]
LVL_2
MOD: SANITY_CHECK

A student solves a physics and economics problem set and calculates the following four values. Based on the rules of sign checks, which calculated value indicates a definite error in the setup or computation?

DEEP_COMPUTE
ULTRA
[EXEC: MICRO_CORE]

āœ–ļø 3. Boundary Condition Checks

šŸŽÆ Boundary Condition Checks

  • Plug in extreme values like zero or infinity to test your formula.
  • At time = 0, position should match the starting point.
  • When speed = 0, kinetic energy must equal zero.
  • If input is zero, output should make physical sense (often zero or a constant).
  • Boundary tests catch formula mistakes before you use them.

Example: Your distance formula gives d=5t+3d = 5t + 3. At t=0t = 0, d=3d = 3 meters — this means you started 3 meters from the origin, which should match the problem setup.

šŸ’” Test the edges: "What happens when I turn the dial to zero or max?"

[EXEC: DEEP_COMPUTE]

3. Boundary Condition Checks

Boundary Condition Checks

A boundary condition check tests a mathematical model or formula by substituting extreme or limiting input values (e.g., zero, infinity, maximum capacity) and verifying that the output behaves as physically or logically expected. This exposes formula errors and domain violations.

Intuition: If a population growth model predicts negative population when time t=0t = 0 (initial condition), the model is fundamentally flawed.

Core Rules:

  • Test t=0t = 0 (initial time): verify the model returns known starting values
  • Test limits as variables approach infinity or zero: ensure asymptotic behavior matches reality (e.g., friction force vanishes when velocity is zero)
  • Check maximum/minimum physical constraints (e.g., tank volume at full capacity, temperature at absolute zero)
  • Confirm the model does not produce undefined operations (division by zero, negative square roots in real contexts)

Consequence: Boundary failures reveal incorrect assumptions, missing terms, or inapplicable formulas.

Example: For v(t)=v0+atv(t) = v_0 + at, setting t=0t = 0 gives v(0)=v0v(0) = v_0, confirming initial velocity is preserved.

TASK_1[0 / 3]
LVL_2
MOD: SANITY_CHECK

A student proposes a model for a plant's height h(t)=5tāˆ’2h(t) = 5t - 2, where tt is the number of days since the seed was planted. The seed has a physical height of 0 at the start. What height does this mathematical model predict at the initial time boundary condition (t=0t = 0)?

DEEP_COMPUTE
ULTRA
[EXEC: MICRO_CORE]

āœ–ļø 4. Applications in Engineering and Finance

šŸ› ļø Real-World Applications

  • Engineers check if stress calculations exceed material limits (steel breaks above 400 MPa).
  • Financial analysts reject models predicting negative stock prices or 1000 percent annual returns.
  • A bridge design claiming 1 mm deflection under 100 tons needs verification.
  • Sanity checks prevent catastrophic failures and bad investments.
  • Always compare results to industry standards or historical data.

Example: A financial model projects 500 percent profit next year. Historical average is 8 percent — the model likely has a compounding error or unrealistic assumptions.

šŸ’” Reality-test everything: "Would an expert laugh at this number?"

[EXEC: DEEP_COMPUTE]

4. Applications in Engineering and Finance

Applications in Engineering and Finance

In engineering stress analysis and financial modeling, adequacy checks prevent catastrophic design failures and absurd forecasts by filtering computationally correct but physically/economically impossible results.

Intuition: A bridge design predicting tensile stress of 100000000 Pa in a steel cable (far exceeding material strength) must be recalculated, even if the math is algebraically correct.

Core Rules in Engineering:

  • Verify stresses remain below material yield limits (e.g., steel yields near 250000000 Pa)
  • Check that deflections, temperatures, and loads fall within operational ranges
  • Ensure safety factors are positive and greater than 1

Core Rules in Finance:

  • Reject negative prices, interest rates below -100%, or probabilities outside [0, 1]
  • Test revenue projections against market size (e.g., claiming 200% market share is impossible)
  • Verify exponential growth models do not predict infinite wealth in finite time

Consequence: These checks act as sanity filters, catching unit errors, formula misapplications, and unrealistic assumptions before implementation.

Example: A loan model yielding monthly payment of -500 dollars signals a sign error in the amortization formula.

TASK_1[0 / 3]
LVL_2
MOD: SANITY_CHECK

A financial analyst calculates the probability of a stock market crash next year as 1.5, and the company's projected market share as 150 percent. According to the core rules in finance, why must these results be rejected?

DEEP_COMPUTE
ULTRA

AWAITING_CONFIRMATION

CONFIRM KNOWLEDGE ACQUISITION TO UPDATE SYSTEM ANALYTICS.