\[ \begin{align}\begin{aligned}\newcommand\blank{~\underline{\hspace{1.2cm}}~}\\% Bold symbols (vectors) \newcommand\bs[1]{\mathbf{#1}}\\% Differential \newcommand\dd[2][]{\mathrm{d}^{#1}{#2}} % use as \dd, \dd{x}, or \dd[2]{x}\\% Poor man's siunitx \newcommand\unit[1]{\mathrm{#1}} \newcommand\num[1]{#1} \newcommand\qty[2]{#1~\unit{#2}}\\\newcommand\per{/} \newcommand\squared{{}^2} \newcommand\cubed{{}^3} % % Scale \newcommand\milli{\unit{m}} \newcommand\centi{\unit{c}} \newcommand\kilo{\unit{k}} \newcommand\mega{\unit{M}} % % Percent \newcommand\percent{\unit{{\kern-4mu}\%}} % % Angle \newcommand\radian{\unit{rad}} \newcommand\degree{\unit{{\kern-4mu}^\circ}} % % Time \newcommand\second{\unit{s}} \newcommand\s{\second} \newcommand\minute{\unit{min}} \newcommand\hour{\unit{h}} % % Distance \newcommand\meter{\unit{m}} \newcommand\m{\meter} \newcommand\inch{\unit{in}} \newcommand\foot{\unit{ft}} % % Force \newcommand\newton{\unit{N}} \newcommand\kip{\unit{kip}} % kilopound in "freedom" units - edit made by Sri % % Mass \newcommand\gram{\unit{g}} \newcommand\g{\gram} \newcommand\kilogram{\unit{kg}} \newcommand\kg{\kilogram} \newcommand\grain{\unit{grain}} \newcommand\ounce{\unit{oz}} % % Temperature \newcommand\kelvin{\unit{K}} \newcommand\K{\kelvin} \newcommand\celsius{\unit{{}^\circ C}} \newcommand\C{\celsius} \newcommand\fahrenheit{\unit{{}^\circ F}} \newcommand\F{\fahrenheit} % % Area \newcommand\sqft{\unit{sq\,\foot}} % square foot % % Volume \newcommand\liter{\unit{L}} \newcommand\gallon{\unit{gal}} % % Frequency \newcommand\hertz{\unit{Hz}} \newcommand\rpm{\unit{rpm}} % % Voltage \newcommand\volt{\unit{V}} \newcommand\V{\volt} \newcommand\millivolt{\milli\volt} \newcommand\mV{\milli\volt} \newcommand\kilovolt{\kilo\volt} \newcommand\kV{\kilo\volt} % % Current \newcommand\ampere{\unit{A}} \newcommand\A{\ampere} \newcommand\milliampereA{\milli\ampere} \newcommand\mA{\milli\ampere} \newcommand\kiloampereA{\kilo\ampere} \newcommand\kA{\kilo\ampere} % % Resistance \newcommand\ohm{\Omega} \newcommand\milliohm{\milli\ohm} \newcommand\kiloohm{\kilo\ohm} % correct SI spelling \newcommand\kilohm{\kilo\ohm} % "American" spelling used in siunitx \newcommand\megaohm{\mega\ohm} % correct SI spelling \newcommand\megohm{\mega\ohm} % "American" spelling used in siunitx % % Capacitance \newcommand\farad{\unit{F}} \newcommand\F{\farad} \newcommand\microfarad{\micro\farad} \newcommand\muF{\micro\farad} % % Inductance \newcommand\henry{\unit{H}} \newcommand\H{\henry} \newcommand\millihenry{\milli\henry} \newcommand\mH{\milli\henry} % % Power \newcommand\watt{\unit{W}} \newcommand\W{\watt} \newcommand\milliwatt{\milli\watt} \newcommand\mW{\milli\watt} \newcommand\kilowatt{\kilo\watt} \newcommand\kW{\kilo\watt} % % Energy \newcommand\joule{\unit{J}} \newcommand\J{\joule} % % Composite units % % Torque \newcommand\ozin{\unit{\ounce}\,\unit{in}} \newcommand\newtonmeter{\unit{\newton\,\meter}} % % Pressure \newcommand\psf{\unit{psf}} % pounds per square foot \newcommand\pcf{\unit{pcf}} % pounds per cubic foot \newcommand\pascal{\unit{Pa}} \newcommand\Pa{\pascal} \newcommand\ksi{\unit{ksi}} % kilopound per square inch % NOTE: do NOT define \bar -- it is the built-in LaTeX accent used by \bar{x}, % \bar{y} (sample means). Redefining it made those render as the word "bar". \newcommand\barunit{\unit{bar}} \end{aligned}\end{align} \]

Nov 16, 2026 | 1100 words | 11 min read

17.5. Milestone 2 - Failure Investigation (Team)#

At a Glance

What you will do: Analyze GHU-1’s recovered telemetry in Excel and determine, with evidence, what killed the crop.

What you will submit: Per team, one Failure Investigation memo (PDF) and your Excel workbook.

17.5.1. Memorandum#

To:

Environmental Controls Engineering Team

From:

Dr. Imani Okafor, Crew Systems Lead, Ares Program Mission Control

Re:

GHU-1 Telemetry: Failure Investigation

As promised, attached is the complete telemetry log recovered from GHU-1, from deployment until loss of crop. It contains every sensor reading and every actuator command, once per minute.

Before we accept a design for GHU-2’s controller, we need your engineering assessment of what went wrong on GHU-1. Program leadership wants every conclusion supported by the data. Answer these three questions.

  1. What was the immediate cause of the crop loss, and when did it occur?

  2. What other failures or risks does the log show, even if they did not directly kill the crop?

  3. What must GHU-2’s controller do differently? State these as measurable design requirements.

Dr. Okafor


17.5.2. GHU-1 Data#

Download the telemetry log, ghu1_telemetry_log.csv. It has about 9,100 rows, one per minute of the mission.

Column

Meaning

time_s, sol

Mission elapsed time (seconds; Martian sols)

t_out_c, tau

Outside temperature (\(^\circ\text{C}\)); atmospheric dust opacity

t_in_c

Greenhouse air temperature (\(^\circ\text{C}\))

rh_pct

Relative humidity (%)

soil_vwc

Soil moisture (volumetric water content, 0 to 1)

par_umol

Light at the canopy (umol/m^2/s)

heater_pct, led_pct, co2_valve_pct, pump_pct

Actuator commands (%)

co2_k30_ppm

CO2, primary sensor (K30)

co2_scd41_ppm

CO2, backup sensor (SCD41)

Important

The log contains raw telemetry only. You must find the evidence of what caused GHU-1’s failure in the data yourself.

17.5.3. Required Analysis#

Work in Excel, using the skills from the Excel modules. Your workbook is part of the submission. Organize it in a professional format, with one labeled analysis per sheet.

Assign Parts A through D across your members, with one lead per part, and label each sheet with its lead’s name. The team writes the memo (Part E) jointly, and the memo cites each member’s sheet. You may analyze the data together, but every sheet must name its lead.

A. Describe the Mission (Summary Statistics)#

The mission ends in a loss-of-control event, which you will pinpoint in Part D. To prevent this event from skewing your description of normal operation, restrict Parts A and B to data before sol 6.0.

Over that period, compute the mean, median, standard deviation, minimum, and maximum of t_in_c, rh_pct, and co2_scd41_ppm. Compare each variable against the crop requirements in the Mission Brief. Which variables, if any, did GHU-1’s controller hold well? Which variables failed the whole time?

B. Time in Specification (Conditional Counting)#

Use COUNTIFS (or an equivalent method) to compute the percentage of mission time that each of the following variables stayed within specification. Use the same period, before sol 6.0.

  • t_in_c within \(\pm 2\ ^\circ\text{C}\) of the day/night setpoints

  • co2_scd41_ppm within \([800, 1000]\ \text{ppm}\)

  • rh_pct within \([40, 60]\%\)

The log has no day/night column. The sun is up during the middle half of each sol, so use the day setpoint when the fractional part of sol is between 0.25 and 0.75 and the night setpoint otherwise.

C. The Two CO2 Sensors (Regression)#

GHU-2 carries two CO2 sensors because the program expects one of them to be faulty or noisy. Find out what the K30 was doing on GHU-1.

  1. Add a computed column: divergence = ABS(co2_k30_ppm - co2_scd41_ppm).

  2. Plot a histogram of the divergence column and describe its shape. A healthy pair of redundant sensors should disagree only by noise. Is that what you see?

  3. Make a scatter plot of co2_k30_ppm (y) against co2_scd41_ppm (x) for the full log. Use linear regression to fit a trendline to the data. Record the model equation and \(r^2\), and include them in the plot legend.

  4. Filter to rows where divergence <= 200 and repeat step 3. Record the new equation and \(r^2\), and include them in the plot legend.

  5. Explain what the two linear fits tell you by answering these questions.

    • When the sensors agreed, how strong was the relationship?

    • What were the off-line points doing? Which sensor was malfunctioning, and what value was it stuck at?

    • What did the controller’s CO2 valve do during those windows, and what did the real CO2 concentration reach?

D. The Final Hours (Timeline)#

Plot t_in_c and heater_pct against sol from sol 5.5 to the end of the log. Use professionally formatted line charts. Late in this window, the actuator commands change abruptly. Find when this change happens. Describe what the greenhouse temperature did next, and determine how long the crop lasted after that moment. Use the Mission Brief annex to explain why it happened that fast.

E. Failure Investigation Memo#

As a team, write a memo for Dr. Okafor (2 to 3 pages plus figures) with these elements:

  • The immediate cause of the crop loss, with the timeline evidence from Part D.

  • Contributing failures and risks. At minimum, include your findings from Parts B and C: the CO2 sensor fault, the controller’s response to it, and the humidity findings. Every claim cites a number or figure from your analysis.

  • Requirements for GHU-2. Write one requirement for every finding that implies a design requirement. State each one measurably and trace it to its finding (“Because GHU-1’s log shows X, GHU-2’s controller shall Y”). These requirements feed into your Milestone 3 design memo.

  • The process-level root cause, in one short paragraph. The log records what the controller did, and the client’s memo indicates why it was built that way. Name the process failure behind the technical failure, and name one design-process safeguard from this course that would have caught it.

  • Figures formatted to the course’s professional standards, with titles, labeled axes with units, legends, and captions.

17.5.4. Submission#

  • Submit one PDF (the memo), named m2_failure_investigation_memo_team_#.pdf, and one Excel workbook, named m2_failure_investigation_analysis_team_#.xlsx, per team to 17.4 Milestone 2 - Failure Investigation (Team) in Gradescope, with all members added.

  • Submit before the deadline on the Course Schedule.

Learning Objectives

DV01:

Table and Plot Formatting - Prepare tables and plots for technical presentation with proper formatting. Include descriptive titles, axis labels with units, appropriately scaled axes, and visible legends.

DV02:

Summary Statistics - Describe the central tendency (mean, median, mode) and variability (standard deviation, variance) of data using appropriate tools or methods.

DV03:

Graphical Comparison of Data - Select, interpret, and justify appropriate graphical representations of data based on data type and structure. Use plots to compare distributions and identify patterns.

DV04:

Regression Model Construction - Construct regression models that describe relationships between variables and support prediction.

DV05:

Regression Model Evaluation - Evaluate and compare regression models using quantitative metrics (SSE, SST, and R²) and contextual reasoning.

EB03:

Data-Supported Justification - Justify decisions or comparisons using explicit reference to data.

PC03:

Captioning Visuals - Include professional captions for all figures, tables, and plots that describe what is shown and why it is relevant.

PA02:

Identify Limitations in Process - Identify limitations, challenges, or inefficiencies in the problem-solving or design approach.

PA03:

Plan for Process Improvement - Identify concrete behaviors or strategies to improve future problem-solving or design efforts.

PC01:

Written Communication Standards - Use professional tone, clear sentence structure, and correct spelling and grammar in all written work.

PS03:

Constraints and Criteria - Define key criteria and constraints that address client and user needs.

TM02:

Document Contributions - Provide clear evidence of individual contributions to the team’s work, including technical, written, or supportive tasks.