Loading...
Community presentation
Yes. You want a **short, simple PPT**, mainly with space to insert your actual plots and Excel tables—not a long explanation-heavy presentation. Use this prompt in Gamma/Slidesg…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
Yes. You want a **short, simple PPT**, mainly with space to insert your actual plots and Excel tables—not a long explanation-heavy presentation. Use this prompt in Gamma/Slidesgo: ```text Create a simple, professional scientific presentation about my IMD internship work on EHF (Excess Heat Factor) forecast verification. IMPORTANT: - Keep the presentation concise. - Do NOT create unnecessary slides. - Use a clean scientific/meteorological style. - Do not generate fake graphs, fake numerical results, or fake maps. - Leave clearly marked empty spaces/placeholders where I will upload my actual images, plots, and Excel tables. - I will upload the actual plots and Excel files separately. - Use short bullet points, not paragraphs. - The presentation should look like a technical internship progress/verification presentation. SLIDE 1 — TITLE Title: "EHF Forecast Verification and Validation" Subtitle: "Monitoring and Forecast Data Processing and Verification" Include: - IMD Internship - EHF (Excess Heat Factor) - Forecast Day-1 and Day-2 Verification SLIDE 2 — DATA PROCESSING AND FILE STRUCTURE Explain briefly with a simple flow diagram: Original Data Folder ↓ Date-wise folders/files ↓ Extract Monitoring + Forecast Day-1 + Forecast Day-2 ↓ Combine date-wise data ↓ Monitoring_Common.nc Forecast_Day1_Common.nc Forecast_Day2_Common.nc ↓ Find common dates ↓ Common-date datasets used for verification Mention briefly: - Monitoring data were combined into one NetCDF dataset. - Forecast Day-1 data were combined separately. - Forecast Day-2 data were combined separately. - Common dates were identified between monitoring and forecast datasets. - These common-date datasets were then used for spatial visualization and verification. SLIDE 3 — BIAS VERIFICATION Give a very short explanation of bias: Bias = Forecast − Monitoring Explain: - Positive bias → Forecast overestimates Monitoring - Negative bias → Forecast underestimates Monitoring - Near zero → Forecast and Monitoring are similar Mention that two approaches were investigated: 1. EHF > 0 in both Monitoring and Forecast 2. EHF > 0 in either Monitoring or Forecast Then leave a large placeholder: "[INSERT BIAS PLOT HERE]" SLIDE 4 — BIAS RESULT 1 Title: "Bias: EHF > 0 in Monitoring and Forecast" Leave most of the slide blank for me to upload my actual bias spatial plot. Add only a small caption area: "Spatial bias between forecast and monitoring where EHF > 0." SLIDE 5 — BIAS RESULT 2 Title: "Bias: EHF > 0 in Either Monitoring or Forecast" Leave a large placeholder for my actual plot. SLIDE 6 — BIAS COMPARISON Title: "Bias Comparison" Leave space for me to upload another actual comparison/result image. SLIDES 7–11 — RMSE VERIFICATION Use FIVE slides for RMSE. SLIDE 7: Title: "RMSE Verification — Overview" Briefly explain: RMSE = √[mean((Forecast − Monitoring)²)] Mention: - RMSE measures the magnitude of forecast error. - Lower RMSE indicates better forecast agreement. - RMSE was calculated spatially and temporally. Leave space for an RMSE overview/result image. SLIDE 8: Title: "Whole-Period Spatial RMSE" Leave a large placeholder for my whole-period spatial RMSE map. SLIDE 9: Title: "Monthly Spatial RMSE" Leave a large placeholder for my multi-panel monthly RMSE plot. SLIDE 10: Title: "RMSE for EHF Events" Briefly mention: - RMSE was also evaluated for EHF event conditions. - Event-based verification helps assess forecast error specifically during EHF conditions. Leave space for my EHF-event RMSE plot. SLIDE 11: Title: "RMSE Time-Series / Monthly Verification" Leave a large placeholder for my actual RMSE time-series/monthly result. SLIDE 12 — POD AND FAR: BASIC EVENT VERIFICATION Title: "POD and FAR — Event-Based Verification" Briefly explain the contingency table: Forecast Event No Forecast Event Observed Event HIT MISS No Observed Event FALSE ALARM CORRECT NEGATIVE POD: POD = Hits / (Hits + Misses) POD measures how many observed EHF events were successfully forecast. FAR: FAR = False Alarms / (Hits + False Alarms) FAR measures how many forecast EHF events did not actually occur. Keep the explanation very short. SLIDE 13 — INITIAL GRID-BASED POD/FAR Title: "Grid-Based EHF Event Verification" Explain briefly: - EHF threshold was applied at individual grid points. - Monitoring and Forecast data were compared grid-by-grid. - Hit, Miss, False Alarm and Correct Negative events were identified. - POD and FAR were calculated from these event classifications. Leave space for my actual POD/FAR plot or table. SLIDE 14 — POD/FAR RESULTS Title: "Overall and Monthly POD/FAR Results" Leave TWO large placeholders: - Placeholder 1: Overall POD/FAR result - Placeholder 2: Monthly POD/FAR result Do not create fake values. SLIDE 15 — SUBDIVISION-WISE VERIFICATION Title: "Subdivision-Wise EHF Verification" I will upload an Excel file containing subdivision-wise results. Create a clean placeholder for the Excel-derived table. The table contains information such as: - Name of Subdivision - Total Days - Forecast EHF Days - Observed EHF Days - Hits - Correct Negatives - Misses - False Alarms - FAR % - POD % Do not invent or modify the numerical results. SLIDE 16 — GRID COVERAGE THRESHOLD APPROACH Title: "Subdivision Event Definition — Grid Coverage" Explain the motivation briefly: "A single grid point exceeding the EHF threshold may not represent an event across an entire subdivision." Therefore, different spatial coverage thresholds were investigated: 25% grid coverage 50% grid coverage 75% grid coverage Explain: - 25% → subdivision considered an event when at least 25% of valid grid points exceed the EHF threshold. - 50% → at least half of the valid grid points exceed the threshold. - 75% → at least three-fourths of the valid grid points exceed the threshold. Keep this slide conceptual and simple. SLIDE 17 — 25%, 50%, 75% COMPARISON Title: "Comparison of Grid Coverage Thresholds" Leave space for me to upload the Excel results/table. Show three clearly separated sections: 25% Coverage 50% Coverage 75% Coverage Mention: "The final threshold will be selected after discussion and validation with the supervisor." FINAL DESIGN: - Keep slides uncluttered. - Use scientific blue/white styling with subtle red/orange accents for EHF. - Use large headings. - Use minimal text. - Leave enough blank space for actual plots and tables. - Do not generate artificial data. - Do not create fake maps. - Do not add unnecessary conclusion/references slides. - The total presentation should be approximately 17 slides. ```
Presentation overview
This community presentation was shared by Punyam Shah as a complete 17-slide example. Yes. You want a **short, simple PPT**, mainly with space to insert your actual plots and Excel tables—not a long explanation-heavy presentation. Use this prompt in Gamma/Slidesg… The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
