Choose your reading route
eduKateSG · Why Mathematics? · Crack-Growth Reliability with the Paris Law: Stress Intensity, First Passage, Inspection Intervals and Uncertainty
Start with the question, audit the worked example, or jump to the assumptions and practice. Every chapter stays open for uninterrupted reading.
Understand the question
Define the quantity and follow the mechanism.Route 2 · Chapters 6–10
Reproduce the example
Audit the numbers one step at a time.Route 3 · Chapters 11–15
Check assumptions
See where design and calibration matter.Route 4 · Chapters 16–20
Explore applications
Connect the method to a concrete investigation.Route 5 · Chapters 21–25
Study and verify
Practise, inspect failure cases and read further.
Full chapter index · Practice and checking · Mathematics Learning Hub
Why mathematics is important in engineering becomes vivid when a crack that is harmless today may grow under repeated loading. Fracture mechanics connects crack size, stress intensity and material resistance. The Paris law describes a middle regime of fatigue-crack growth, while reliability analysis represents uncertain initial flaws, loads, material parameters, inspection performance and the first time a crack reaches a critical state.
This guide develops stress-intensity range, the Paris equation, integration over cycles, first-passage probability and inspection planning. It also explains the model’s boundaries: the Paris law does not cover every growth regime, variable-amplitude histories are not interchangeable, and a calculated inspection interval must be supported by material data, structural analysis and validated nondestructive evaluation.
Full chapter index
Chapters 1–5 · Understand the question
Chapters 6–10 · Reproduce the example
Chapters 11–15 · Check assumptions
Chapters 16–20 · Explore applications
Chapters 21–25 · Study and verify
Repeated stress cycles can extend a flaw until residual strength is inadequate. A millimetre-scale crack may grow over many flights or machine cycles. This is the central mathematical mechanism in why a small crack matters. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Not every detected mark is a fatigue crack and growth depends on geometry and environment. Define component, loading and flaw type. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind crack size as a state variable. Let a denote a consistent crack dimension that evolves with cycle count N. In the illustrative case, A(N) can be plotted against accumulated cycles. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Complex three-dimensional fronts cannot always be represented by one length. State the crack geometry convention.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat stress intensity factor as a model-checking problem rather than a vocabulary exercise. For a simple mode-I geometry, K=Y sigma sqrt(pi a), where Y represents geometry. If Y=1, sigma=100 MPa and a=0.005 m, K is about 12.53 MPa sqrt(m). Recompute the example from the raw values and label every unit. Y can change as the crack grows and handbook solutions have domains. Use a validated geometry solution.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
The mathematics of stress-intensity range becomes useful only when its mechanism is explicit. Under cyclic loading, delta K=K_max-K_min drives many fatigue-growth descriptions. Consider the worked illustration: With constant Y and stress range delta sigma, delta K=Y delta sigma sqrt(pi a). Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Crack closure and load ratio can alter effective driving force. Record R ratio and load sequence.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Primary source: https://doi.org/10.1115/1.3656900. Read it for the method and its assumptions; do not transfer its performance claims automatically to another model.
Use the paris law to practise sensitivity analysis. In its usual middle-regime form, da/dN=C(delta K)^m. C sets scale and m controls sensitivity to delta K. Before accepting the result, identify the quantity that would change the conclusion most. C units depend on m and the chosen unit system. Keep one unit system through the calculation.
A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.
Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.
Build a small counterexample for a growth-rate calculation. With C=10^-10 in compatible SI units, m=3, Y=1, delta sigma=100 MPa and a=0.005 m, delta K≈12.53 and da/dN≈1.97×10^-7 m/cycle. The initial example is: That is about 0.197 micrometres per cycle in this illustration. Then create a nearby case where the usual shortcut becomes unreliable. The constants are fictional and not design data. Check powers and units independently.
Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.
When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.
Connect integrating crack growth to a real decision while protecting the boundary between calculation and judgement. Cycles from a0 to a1 follow N=integral from a0 to a1 of da/[C(delta K(a))^m] when the model and loading are fixed. For m=2 and constant Y delta sigma, the integral becomes logarithmic in a. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. Numerical integration may be needed when Y or load changes. Compare analytic and numerical results.
The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.
A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.
A critical size can be defined when applied K reaches a validated fracture-resistance condition under declared loads. Solve K(a_c)=K_allowable for a simple geometry. This is the central mathematical mechanism in critical crack size. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Toughness, constraint, residual stress and plasticity limit a simple equation. Use certified resistance data and safety rules. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind three growth regimes. Near-threshold, Paris-regime and rapid-growth behaviour have different characteristics. In the illustrative case, The Paris straight line occupies only part of a log(da/dN)-log(delta K) plot. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Extrapolating it to zero growth or final fracture is unsafe. Mark the calibrated delta K range.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat load ratio and mean stress as a model-checking problem rather than a vocabulary exercise. The ratio R=K_min/K_max can affect crack closure and measured growth rates. Two cycles with equal delta K but different R may not grow identically. Recompute the example from the raw values and label every unit. A single C,m pair may not transfer across R. Use data matched to load ratio.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
The mathematics of variable-amplitude loading becomes useful only when its mechanism is explicit. Real histories contain overloads, underloads and sequences that can accelerate or retard growth. Consider the worked illustration: An overload may create temporary retardation rather than simple linear damage. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Reordering cycles can change crack growth. Preserve the load sequence.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Use random initial flaws to practise sensitivity analysis. Manufacturing and service flaws vary, so a0 can be represented by a justified distribution or conservative bound. Monte Carlo samples different initial crack sizes and growth parameters. Before accepting the result, identify the quantity that would change the conclusion most. Unobserved flaws are shaped by inspection and sampling, not a raw population alone. Condition on detection history.
A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.
Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.
A second primary source is https://standards.nasa.gov/standard/NASA/NASA-HDBK-5010-VOLUME_1. Compare the problem definition, estimator and validation rather than quoting one result in isolation.
Build a small counterexample for uncertain paris parameters. C and m are estimated from test data and often strongly correlated. The initial example is: Sampling them independently can create implausible growth curves. Then create a nearby case where the usual shortcut becomes unreliable. Log transformation and specimen variability affect estimates. Preserve joint parameter uncertainty.
Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.
When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.
Connect first-passage probability to a real decision while protecting the boundary between calculation and judgement. Failure by cycle n is the probability that the crack process first reaches a critical boundary by n. Simulated paths can be checked for the first crossing of a_c. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. Checking only the final cycle can miss an earlier crossing in nonmonotone models. Record first-crossing time explicitly.
The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.
A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.
Sample initial flaw, load history and material parameters, propagate a(N), and count paths crossing the limit. A rare crossing needs many credible paths or specialised rare-event methods. This is the central mathematical mechanism in monte carlo path simulation. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. A smooth simulator can still use wrong input tails. Validate each input distribution. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind reliability over time. The survival function S(N)=P(T>N) describes the chance the first-passage cycle T exceeds N. In the illustrative case, Failure probability by N is 1-S(N). Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. It is conditional on model, inspection and operating assumptions. Date the load and inspection baseline.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat inspection probability of detection as a model-checking problem rather than a vocabulary exercise. An inspection detects a crack probabilistically as a function of crack size and procedure. A simulated path may survive an inspection only if the crack is missed or below removal criteria. Recompute the example from the raw values and label every unit. Treating detection as a hard threshold overstates certainty. Use a validated POD model.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
The mathematics of bayesian updating after inspection becomes useful only when its mechanism is explicit. A no-find inspection changes the crack-size distribution but does not prove no crack exists. Consider the worked illustration: Posterior weights favour paths that were less likely to be detected. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. The update depends on false calls and POD assumptions. Show prior, likelihood and posterior.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Use choosing repeat intervals to practise sensitivity analysis. An interval should leave adequate opportunity to detect growth before the critical condition under approved rules. FAA guidance links intervals to crack-growth data, detectable size and critical size. Before accepting the result, identify the quantity that would change the conclusion most. Dividing one deterministic life by a factor is not a complete reliability argument. Combine growth, POD and consequence checks.
A simple baseline is essential. It reveals whether the advanced method is improving accuracy or only adding complexity. Compare model calls, wall time, uncertainty and failure-mode coverage under one declared budget. Repeat stochastic calculations with several seeds; a favourable single run is not evidence of dependable efficiency.
Students can extend the example by adding correlation, a second failure mode or a modest measurement error. Explain which part of the formula changes and which remains fixed. This exercise shows how mathematics transfers from a clean textbook case to engineering and computing without pretending that the classroom model is a certified design tool.
Build a small counterexample for practice activity. Integrate a simplified Paris model from 2 mm to 5 mm under constant loading, then vary C by a factor of two. The initial example is: Predict that doubling C halves the calculated cycles in this fixed model. Then create a nearby case where the usual shortcut becomes unreliable. The classroom geometry and constants are illustrative. Plot a against N and verify units.
Counterexamples are positive learning tools. They reveal the conditions that make a method work and help students recognise when a software output deserves a pause. Keep the counterexample small enough to plot or enumerate. Check sign, support, bounds and conservation of probability before adding complexity.
When writing the conclusion, separate a documented fact from an interpretation and from an illustrative scenario. Cite the primary method paper for the factual mechanism, use the local calculation for the illustration, and label any recommendation as conditional on the stated model. This keeps career and engineering advice age-appropriate and honest.
Connect parent and educator guidance to a real decision while protecting the boundary between calculation and judgement. Crack growth connects square roots, powers, calculus, probability, graphs and material science. Ask why growth accelerates as a becomes larger in the simple model. First verify the arithmetic, then translate it into an allowed action and an action the evidence does not support. A numerical answer should never be used to assess real hardware without qualified engineers. Use fictional data and clear boundaries.
The audit should include the original question, input provenance, failure convention, algorithm settings, convergence or stopping rule, and a sensitivity result. For an adaptive method, also preserve the sequence of choices. For an optimisation, preserve every constraint. For Bayesian updating, preserve the prior and observation model. These records turn a result into something another person can challenge and improve.
A final transfer question is useful: where else would the same mathematical idea appear? Density ratios appear in survey correction and machine learning, probabilistic constraints in planning, and conditional probability in medical testing. The context changes, but transparent assumptions and reproducible checks remain valuable.
The Paris law is not valid from crack initiation to final fracture, and a no-find inspection is not proof of zero damage. More decimal places do not compensate for uncertain C, m or loads. This is the central mathematical mechanism in common misconceptions. Write the quantities and assumptions before using software, then reproduce the calculation or geometric argument in a small example. Critical size is not universal across geometry and load. Separate model regime, data and decision. The useful habit is to keep the physical question, the probability model and the numerical method in separate columns so that a correct computation is not mistaken for complete evidence.
Did You Know? A result can be numerically stable and still answer the wrong question if the failure event, denominator or transformation changes. Test one nearby case and predict the direction of change before recalculating. Save inputs, intermediate values and units so a second reader can audit the path.
For practice, turn the example into a sensitivity check. Change one defensible input while holding the others fixed, compare the new result with the original and explain why it moved. Then construct a counterexample in which the shortcut fails. End with two sentences: what the mathematics supports, and what remains uncertain.
Start with the operational question behind when the model needs extension. Short cracks, corrosion, creep, mixed modes, plasticity and complex spectra may require other laws or experiments. In the illustrative case, A chemically assisted crack may grow while cyclic delta K is small. Draw the relevant graph, density, boundary or timeline before calculating; the picture should use the same variables and sign convention as the equations. Forcing Paris behaviour can miss the dominant mechanism. Select the model from physics and evidence.
A student should be able to rebuild the result without hidden settings. Record the sampling rule or optimisation criterion, the exact failure definition, and the evidence used for every distribution or parameter. Compare a transparent baseline with the advanced method. If they disagree, investigate the mechanism before deciding which answer is more credible.
This chapter belongs to a larger decision, so translate the number carefully. State one action the evidence permits and one action it does not. A parent or educator can ask which school ideas are doing the work: algebra organises relationships, probability represents uncertainty, calculus describes local change, and computing repeats the documented rules at scale.
Treat research and next reading as a model-checking problem rather than a vocabulary exercise. Paris and Erdogan’s 1963 paper established the influential power-law discussion, while NASA’s active fracture-control handbook gives current implementation guidance. Read the original equation beside modern fracture-control requirements. Recompute the example from the raw values and label every unit. Neither source supplies application-specific parameters automatically. Benchmark software against a known integral.
The strongest check uses evidence the model did not choose for itself. Hold out later observations, an independent simulation set or a known-answer benchmark. Report errors where decisions are sensitive, especially near the failure boundary, instead of relying on one global accuracy score. A method that performs well on easy safe cases can still fail at the rare cases that motivated the analysis.
Now change one assumption and make a directional prediction before running the calculation. If the result moves the opposite way, inspect the sign convention, transformation, density ratio or constraint. This prediction-first routine develops transferable problem-solving skills because it connects symbolic work to a testable expectation.
Continue with the Mathematics Learning Hub and the previous reliability article. These links own broader probability ideas and the immediately preceding rare-event geometry.
The mathematics of frequently asked questions becomes useful only when its mechanism is explicit. FAQs should cover K, delta K, C and m, integration, first passage, critical size, POD and inspection intervals. Consider the worked illustration: Each answer should state model regime and units. Preserve the original inputs, calculate step by step and compare with a second method whenever an analytic or high-budget reference exists. Avoid turning illustrative crack growth into operational advice. Publish equations, data provenance and checks.
There are three uncertainties to keep apart. Sampling or numerical uncertainty comes from finite computation. Parameter uncertainty comes from estimating inputs. Model-form uncertainty comes from simplified physics, distributions or dependence. Reducing the first does not automatically reduce the other two. A credible report names all three and shows which one drives the decision.
For a practical investigation, create a small reproducible notebook or spreadsheet with a frozen data sheet, formula sheet, diagnostics sheet and decision note. Another student should be able to change one input and obtain the same update without guessing what the model meant.
Quick answers
What should I calculate first? Start with the estimand or failure event, then a simple baseline.
Does the advanced method guarantee accuracy? No. It needs input, numerical and model checks.
Which school mathematics matters? Algebra, graphs, probability, functions and careful units all contribute.
How can a student practise safely? Use fictional or open benchmark data and preserve every intermediate value.
What makes a career claim responsible? Describe how the mathematics is used without promising admission, salary or employment.
Extended practice laboratory
Practice case 1: Why a small crack matters
Setup: Use this chapter’s illustrative case: A millimetre-scale crack may grow over many flights or machine cycles.
Task: Define component, loading and flaw type.
Checking target: Not every detected mark is a fatigue crack and growth depends on geometry and environment.
Practice case 2: Crack size as a state variable
Setup: Use this chapter’s illustrative case: A(N) can be plotted against accumulated cycles.
Task: State the crack geometry convention.
Checking target: Complex three-dimensional fronts cannot always be represented by one length.
Practice case 3: Stress intensity factor
Setup: Use this chapter’s illustrative case: If Y=1, sigma=100 MPa and a=0.005 m, K is about 12.53 MPa sqrt(m).
Task: Use a validated geometry solution.
Checking target: Y can change as the crack grows and handbook solutions have domains.
Practice case 4: Stress-intensity range
Setup: Use this chapter’s illustrative case: With constant Y and stress range delta sigma, delta K=Y delta sigma sqrt(pi a).
Task: Record R ratio and load sequence.
Checking target: Crack closure and load ratio can alter effective driving force.
Practice case 5: The Paris law
Setup: Use this chapter’s illustrative case: C sets scale and m controls sensitivity to delta K.
Task: Keep one unit system through the calculation.
Checking target: C units depend on m and the chosen unit system.
Practice case 6: A growth-rate calculation
Setup: Use this chapter’s illustrative case: That is about 0.197 micrometres per cycle in this illustration.
Task: Check powers and units independently.
Checking target: The constants are fictional and not design data.
Practice case 7: Integrating crack growth
Setup: Use this chapter’s illustrative case: For m=2 and constant Y delta sigma, the integral becomes logarithmic in a.
Task: Compare analytic and numerical results.
Checking target: Numerical integration may be needed when Y or load changes.
Practice case 8: Critical crack size
Setup: Use this chapter’s illustrative case: Solve K(a_c)=K_allowable for a simple geometry.
Task: Use certified resistance data and safety rules.
Checking target: Toughness, constraint, residual stress and plasticity limit a simple equation.
Practice case 9: Three growth regimes
Setup: Use this chapter’s illustrative case: The Paris straight line occupies only part of a log(da/dN)-log(delta K) plot.
Task: Mark the calibrated delta K range.
Checking target: Extrapolating it to zero growth or final fracture is unsafe.
Practice case 10: Load ratio and mean stress
Setup: Use this chapter’s illustrative case: Two cycles with equal delta K but different R may not grow identically.
Task: Use data matched to load ratio.
Checking target: A single C,m pair may not transfer across R.