Skip to content

Commit df312f8

Browse files
Clean up README by removing old sections
Removed outdated submission checklist and final notes sections.
1 parent fbabe51 commit df312f8

File tree

1 file changed

+0
-32
lines changed

1 file changed

+0
-32
lines changed

README.md

Lines changed: 0 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -103,35 +103,3 @@ This table doubles as a progress tracker; each module will produce intermediate
103103
4. Montiel, J., Read, J., Bifet, A., & Abdessalem, T. (2021). *River: Machine learning for streaming data in Python*. JMLR.
104104

105105
---
106-
107-
> This README will evolve alongside the project. Upcoming additions include experiment trackers, visual dashboards, and links to evaluation reports once submitted.
108-
109-
---
110-
111-
## 8. Submission Checklist & Final Notes
112-
113-
### Completion Snapshot
114-
- **Innovation documented** – Sections 2 and 4 capture the novelty, architectural flow, and justification for fusing iCaRL with ADWIN.
115-
- **Execution evidence** – Sections 3 and 5 outline the semester roadmap and technical modules delivered, demonstrating sustained work across the term.
116-
- **Evaluation coverage** – Section 6 itemises mid- and end-semester artefacts so reviewers can trace how outcomes map to assessment criteria.
117-
118-
### Self-Audit Before Marking Complete
119-
| Item | Status | Evidence & Next Actions |
120-
| --- | --- | --- |
121-
| Innovation statement & literature synthesis | ✅ Complete | Sections 2 & 7 summarise the novelty and references backing the hybrid approach. |
122-
| Architecture & workflow documentation | ✅ Complete | Section 4 diagrams the adaptive rehearsal flow used in code proofs. |
123-
| Implementation roadmap & progress log | ✅ Complete | Section 5 lists each module with planned completion windows to show semester-long effort. |
124-
| Experimental artefacts (metrics, plots, energy logs) | ⚠️ Attach | Ensure the final notebooks, tables, and detector alarm statistics are included in the repo/report bundle. |
125-
| Final report & presentation package | ⚠️ Attach | Link the polished PDF/slide deck once uploaded so evaluators can access them directly. |
126-
127-
Once the ⚠️ items are uploaded, you can confidently mark the project as completed with clear evidence of originality and sustained semester work.
128-
129-
---
130-
131-
## 9. Final Review & Submission Plan
132-
133-
- **Authenticity cross-check** – Revisit notebooks and experiment logs to ensure they reflect the adaptive rehearsal workflow (detector alarms → rehearsal bursts → evaluation) described in Sections 4 and 5. Capture screenshots or metadata hashes where appropriate for the appendix.
134-
- **Evidence packaging** – Bundle the energy/compute summaries, alarm statistics, and comparison plots referenced in Section 6 so evaluators can validate the claimed efficiency gains without rerunning experiments.
135-
- **Narrative alignment** – In the written report, mirror the README structure (innovation → roadmap → evaluation) so reviewers immediately see the semester-long progression and novel contribution.
136-
- **Repository hygiene** – Finalise README links, clean temporary notebooks, and update the submission checklist table once the ⚠️ items are addressed to avoid confusion during marking.
137-

0 commit comments

Comments
 (0)