1. Problem Statement
Combine weather, rainfall, and historical event data to warn of extreme conditions.
In many academic AI projects, students begin directly with a dataset and a model. That approach is not enough for this project. The student must first understand the real-world situation in which this system would be used, the type of user who would depend on it, the nature of the input data, and the consequences of a wrong or unclear output. This project is therefore framed as a complete applied AI system, not only as an algorithmic exercise.
The central challenge in Climate Event Early Warning System is to convert raw or semi-structured input into a reliable decision-support output. The system should be able to accept realistic input, process it through a documented pipeline, and produce an output that can be inspected by a student, trainer, or domain expert. The result should not be treated as a final authority. It should be presented with enough evidence, confidence, limitations, and examples so that a human reviewer can understand how the output was produced.
This project belongs to the broader area of Simulation AI: Hardware, Weather and Systems and uses the core AI approach of AI for Simulation. Typical application directions include scenario planning, hardware monitoring, weather risk analysis. Students should therefore think about the project as a bridge between classroom learning and a real deployment scenario. The final prototype should show a working model or AI workflow, but it should also show the surrounding engineering: data preparation, validation, model comparison, error analysis, interface design, and responsible communication of limitations.
A successful project will answer four practical questions: What problem is being solved? What data or source material is needed? Which AI method is appropriate and why? How will the student prove that the system is useful, safe enough for demonstration, and better than a simple baseline? These questions should guide the entire implementation and final report.
2. Background
Simulation projects teach students how AI can approximate, accelerate, or analyze complex real-world systems such as weather, climate events, hardware signals, power usage, thermal behavior, and sensor failures.
The background of this project should be understood from two angles: the domain problem and the AI method. The domain problem explains why the project matters in the real world. The AI method explains how a computational system can assist with the task. Students should not treat these as separate topics. A technically strong model that does not fit the domain workflow is not useful, and a good domain idea without measurable AI performance is not complete.
AI for Simulation: The system must define variables, run scenarios, compare outputs, and explain how AI supports simulation or forecasting.
Historically, many student projects focused on training one model and reporting a single metric. Modern AI projects require a broader system view. Students must consider how data is collected, how it is cleaned, how labels or source documents are verified, how the model output is interpreted, and how mistakes are communicated. This is especially important in projects involving finance, healthcare, education, cybersecurity, public safety, or any domain where users may over-trust automated output.
The background study for this project should include a review of similar systems, available datasets, common baseline methods, and current limitations. Students should identify at least three existing approaches or tools before implementation. The final report should explain why the selected method is suitable for the problem and what trade-offs were accepted, such as speed versus accuracy, local deployment versus cloud APIs, interpretability versus model complexity, or simple baselines versus advanced architectures.
Example use cases
- scenario planning
- hardware monitoring
- weather risk analysis
These use cases are examples only. Students may adapt the project to a local institutional, industry, or regional context as long as the dataset, evaluation method, and limitations are clearly documented.
3. Project Objectives
- Understand the real-world problem and its intended users.
- Prepare the required dataset or source material.
- Build a baseline AI model or pipeline using LightGBM, SHAP, Streamlit.
- Evaluate the system with suitable metrics and example outputs.
- Create a simple demo application for presentation.
- Document limitations and possible future improvements.
4. Learning Outcomes
After completing this project, students should be able to explain the core AI concept, implement a working prototype, evaluate it honestly, and communicate its limitations.
- Define variables, assumptions, and scenario boundaries.
- Use AI as a surrogate, forecaster, or analyzer for simulated systems.
- Compare normal, edge, and extreme scenarios.
Internal Scope and Delivery Notes
This block is hidden on the public page. It is meant for trainers, reviewers, and curriculum coordinators.
- Suggested delivery level: Best for 2-4 student teams over 2-6 weeks. Teach the baseline first; add advanced extensions only after the demo works.
- In scope for training: student prototype, dataset preparation, baseline model, evaluation, visual workflow, report, and demo app.
- Keep out of student claims: production deployment, legal certification, medical/financial final decision-making, or autonomous action without human review.
- Implementation rule: students should complete the baseline before attempting advanced extensions.
5. Visual System Architecture
The architecture diagram shows how input moves from the user or dataset into processing, storage, AI inference, review, and final output. Students should explain this diagram before coding so that implementation does not become random trial and error.
6. Workflow and Flowchart
The flowchart is the project execution plan. It includes validation, data preparation, model execution, decision points, feedback loops, and final reporting. Students should map each flowchart block to code modules in their notebook or application.
7. Methodology Overview
The project should be developed in phases: data preparation, baseline model, improved AI pipeline, evaluation, and demo application. Students should show how data enters the system, how the model processes it, how output is generated, and how the result is evaluated.
7.1 System Modules
- Input module: accepts files, text, images, audio, sensor data, or forms depending on the project.
- Data preparation module: converts raw input into model-ready format.
- AI inference module: runs the baseline and improved model or AI pipeline.
- Evaluation module: calculates metrics and stores example success and failure cases.
- User interface module: presents output in a way that a non-expert can understand.
7.2 Core AI Pipeline
- Define the variables and assumptions of the simulated system.
- Generate or ingest scenario data.
- Train a model or run a simulation loop.
- Visualize scenario outcomes and sensitivity.
7.3 Application Layer
- Build a simple interface with sample inputs and clear outputs.
- Show confidence, evidence, visual overlays, recommendations, or warnings depending on the project type.
- Include graceful error messages for invalid or unsupported input.
Detailed Implementation Guide
Dataset and Source Links
Use one of these sources. If a source needs login, download once and share a small approved sample with students.
- NOAA climate data: https://www.ncei.noaa.gov/
- NASA POWER weather data: https://power.larc.nasa.gov/data-access-viewer/
- OpenAQ air quality data: https://openaq.org/
What Data Preparation Means Here
- List all scenario variables and units before generating data.
- Create baseline, normal, and extreme scenarios.
- Keep simulation assumptions in a separate table.
- Compare model outputs across scenarios.
- Document where the simulation is unrealistic.
Baseline and Improved Model
- Build a simple baseline first. Examples include TF-IDF plus logistic regression, a pretrained image classifier, a simple retrieval pipeline, or a shallow regression model.
- Build one improved version using the recommended project stack.
- Compare both versions and explain whether the added complexity is justified.
Advanced Extension
- Add one advanced extension only after the baseline works: agent workflow, RAG citations, local model deployment, edge inference, simulation scenarios, monitoring, or graph-based analysis.
- Compare the advanced extension with the baseline using the evaluation plan.
Project-Specific Study Notes
- Define the baseline before building the improved system.
- Keep a small demo dataset for reliable presentations.
- Report at least ten failure cases and what they teach.
8. Experimental Design and Evaluation Measures
The experimental design must show whether the system is useful, reliable, and understandable. Students should not report only one metric.
8.1 Project-specific evaluation focus
- Scenario error against known or simulated ground truth.
- Sensitivity to input assumptions.
- Behavior under extreme scenarios.
| Area | Measure |
|---|---|
| Model quality | Accuracy, precision, recall, F1-score, RMSE, MAE, mAP, IoU, retrieval precision, or task success rate depending on the project. |
| Baseline comparison | Compare the simplest baseline with the improved model or pipeline. |
| Error analysis | At least 10 failure cases with screenshots or examples, likely causes, and proposed fixes. |
| Usability | A new user should understand the input, output, and limitation of the app in under 3 minutes. |
| Robustness | Behavior on missing, noisy, ambiguous, low-quality, or out-of-distribution inputs. |
| Ethics and safety | Privacy, bias, misuse risk, human review, and limitation statements. |
9. Software and Hardware Requirements
9.1 Software
- Python 3.10 or newer
- Jupyter Notebook or Google Colab
- LightGBM, SHAP, Streamlit
9.2 Hardware
- Minimum: laptop with 8 GB RAM for most baseline implementations.
- Recommended: Google Colab GPU for vision, audio, micro-LLM, or deep learning projects.
10. Expected Deliverables
- Problem understanding document with objective, users, and limitations.
- Dataset folder or source-material folder with data dictionary.
- Notebook covering data preparation, baseline, improved model, evaluation, and conclusion.
- Working demo app suitable for a 3-minute presentation.
- Architecture diagram and flowchart explanation.
- Evaluation report with metrics, screenshots, failure cases, and ethical considerations.
- Final project report and presentation slides.
Suggested Student Work Plan
- Week 1: understand the problem, collect data, build the data dictionary, and reproduce the baseline.
- Week 2: improve the model or AI pipeline and run proper evaluation.
- Week 3: build the demo app, add visual explanations, and document failure cases.
- Week 4: complete the report, presentation, references, and final mentor review.
Common trainer mistakes to prevent
- Not documenting assumptions.
- Treating synthetic results as real-world proof.
- Testing only normal scenarios and no edge cases.
Assessment rubric
| Component | Suggested weight |
|---|---|
| Problem understanding and dataset documentation | 15% |
| Baseline implementation | 20% |
| Improved AI pipeline | 20% |
| Evaluation and error analysis | 20% |
| Demo app and presentation | 15% |
| Ethics, limitations, and future work | 10% |