BOM Nowcasting 🌦️

Welcome. This repository is the central hub for the BOM Nowcasting team. We use this space to organize the project, manage documentation, and track progress.

---

Project Vision

BOM Nowcasting is focused on building practical short-term forecasting workflows end to end.

The team's work moves through a practical pipeline:

• Collect & Organize: Work with observational, historical, and derived weather data.
• Prepare & Validate: Clean inputs, align time windows, and validate data quality.
• Model & Evaluate: Develop nowcasting models and assess forecast accuracy against operational needs.

The goal is to build reliable nowcasting workflows while understanding how data quality, infrastructure, and modeling choices affect forecast performance.

---

🛑 The "Stay in GitHub" Rule

Keep all project work inside GitHub. GitHub already provides everything we need for documentation, planning, and task tracking.

⛔ Important: You may receive suggestions from tutors, lecturers, or others to use different third-party tools (like Notion, Jira, or Trello) for planning or documentation. Those are only suggestions. For this project, keep everything inside this repository and the GitHub platform so our work stays organized, consolidated, and easy to review.

---

🚦 Start Here

Use these links first:

1. roadmap/ProjectGoal.md
2. knowledge-base/compute-infrastructure/Wireguard.md
3. team-members/README.md
4. management/weekly-reports/README.md
5. team-members/README.md 📓
6. management/weekly-todos/README.md ✅

---

🚀 Where to Start

If you are a new team member, please read these documents first to get oriented:

1. roadmap/ProjectGoal.md
2. knowledge-base/compute-infrastructure/Wireguard.md
3. team-members/README.md
4. management/weekly-reports/README.md
5. team-members/README.md 📓
6. management/weekly-todos/README.md ✅

---

🗂️ Repository Structure

This repository is strictly for documentation and project management (no code!). Here is how our knowledge base is organized:

Folder	Purpose
knowledge-base/	Combined compute infrastructure, data, models, learning resources, Q&A, papers, and repository/platform references.
management/ 🚦	Weekly reports, weekly TODOs, and team coordination docs.
roadmap/	Project goals, planning docs, and semester overviews.
team-members/	Combined member profiles and notebook progress tracking.

---

📊 Project Tracking & Usage

📦 What This Repository Is For

• Project documentation and architecture rules
• Planning and task tracking
• Combined weekly meeting notes and progress reports
• Team organization

📋 The GitHub Project Board We use a GitHub Project Kanban board called BOM Nowcasting Team to manage tasks and track progress. All tasks, issues, and progress updates should be recorded on this board so the work remains visible and organized for everyone.

---

📚 Documentation Guidelines

All documentation here should be written so it is easy to read directly in GitHub's web interface. When adding or editing files, please follow these rules:

✍️ Format

• Use standard Markdown (.md) files.
• Write documents so they are clear and highly scannable.
• Use headers, bullet points, and lists to break up walls of text.
• Keep files structured and logically organized within their folders.

✂️ Keep It Short

• Try not to let documentation pages grow too massive.
• Keep documents short, punchy, and concise.
• If a document becomes too long, split it into a new, separate file.
• Each document should ideally focus on one main topic.

This makes the documentation easier to read, maintain, and navigate for the whole team! 🙂