14 KiB
Daily Checklist - Master's Thesis Completion
Deadline: February 15, 2026
📅 Week 1: January 16-22 - PERFORMANCE DATA COLLECTION
Friday, January 16 (Day 1) - PASSED
- Install/verify NVIDIA Nsight Graphics
- Document test hardware specs (run
./scripts/get_hardware_specs.sh) - Review test scenario document (
./scripts/test_scenarios.md)
Saturday, January 17 (Day 2) - PASSED
- Work on Unreal game implementation
Sunday, January 18 (Day 3) - PASSED
- Finish Unreal game implementation 🎉
Achievement unlocked: Both Unity and Unreal games ready for testing!
Monday, January 19 (Day 4) - PASSED (incomplete)
- Install/verify NVIDIA Nsight Systems
- Document test hardware specs (run
./scripts/get_hardware_specs.sh) - Review test scenario document (
./scripts/test_scenarios.md) Run→ moved./scripts/close_background_apps.shbefore testingComplete ALL Unity testing (3 full 90-second runs)→ movedSave captures as→ movedunity_run_1.nsight-rep,unity_run_2.nsight-rep,unity_run_3.nsight-repTake screenshots of Nsight timeline for each run→ moved
Goal: All Unity performance data captured ❌ NOT ACHIEVED Target hours: 4 hours
Tuesday, January 20 (Day 5) - PASSED (skipped)
Run→ moved./scripts/close_background_apps.shbefore testingComplete ALL Unreal testing (3 full 90-second runs)→ movedSave captures as→ movedunreal_run_1.nsight-rep,unreal_run_2.nsight-rep,unreal_run_3.nsight-repTake screenshots of Nsight timeline for each run→ movedDocument any differences observed between engines→ moved
Goal: All Unreal performance data captured ❌ NOT ACHIEVED Target hours: 4 hours
Wednesday, January 21 (Day 6) - PASSED (skipped)
Export key metrics from Nsight (frame time, draw calls, memory)→ movedTake screenshots of important Nsight views→ movedOrganize all captured data in spreadsheet/CSV→ movedCreate comparison tables (Unity vs Unreal)→ movedIdentify key findings from raw data→ moved
Goal: Data organized, initial analysis done ❌ NOT ACHIEVED Target hours: 4 hours
Thursday, January 22 (Day 7) - PASSED (skipped)
Create graph 1: Frame time comparison→ movedCreate graph 2: GPU utilization comparison→ movedCreate graph 3: Memory usage comparison→ movedCreate graph 4: Draw calls efficiency→ movedSave all figures to latex/tex/img/→ moved
❌ WEEK 1 MILESTONE MISSED: Performance data NOT collected Target hours: 4 hours
📅 Week 2: January 23-29 - WRITING & ANALYSIS
Friday, January 23 (Day 8) ✅ TODAY - CATCH-UP DAY
⚠️ BEHIND SCHEDULE - Need to catch up on performance testing
PRIORITY: Complete Unity Testing (from Day 4)
- Run
./scripts/close_background_apps.shbefore testing - Complete Unity stationary test run
- Complete Unity dynamic test run
- Save captures as
unity_stationary.nsight-rep,unity_dynamic.nsight-rep - Take screenshots of Nsight timeline for each run
If time permits: Start Unreal Testing (from Day 5)
- Complete Unreal stationary test run
- Complete Unreal dynamic test run
- Save captures as
unreal_stationary.nsight-rep,unreal_dynamic.nsight-rep
Goal: Get back on track - complete Unity testing minimum Target hours: 8 hours
Saturday, January 24 (Day 9) - CATCH-UP
Complete Unreal Testing + Start Data Analysis
- Run
./scripts/close_background_apps.shbefore testing - Complete Unreal stationary test run (if not done Friday)
- Complete Unreal dynamic test run (if not done Friday)
- Save captures as
unreal_stationary.nsight-rep,unreal_dynamic.nsight-rep - Take screenshots of Nsight timeline for each run
- Document any differences observed between engines
- Export key metrics from Nsight (frame time, draw calls, memory)
Goal: All performance data captured (both engines) Target hours: 8 hours
Sunday, January 25 (Day 10) - CATCH-UP
Data Analysis & Visualization
- Take screenshots of important Nsight views
- Organize all captured data in spreadsheet/CSV
- Create comparison tables (Unity vs Unreal)
- Identify key findings from raw data
- Create graph 1: Frame time comparison
- Create graph 2: GPU utilization comparison
- Create graph 3: Memory usage comparison
- Create graph 4: Draw calls efficiency
- Save all figures to latex/tex/img/
✅ DELAYED WEEK 1 MILESTONE: All performance data collected and visualized Target hours: 8 hours
Monday, January 26 (Day 11)
Chapter 4 & 5 - Methodology and Results
- Write Chapter 4 methodology section (test setup, tools used)
- Write Chapter 5 Section 5.1 (Test methodology)
- Write Chapter 5 Section 5.2 (Test scenarios)
- Write Chapter 5 Section 5.3 (Results - Unity)
- Create LaTeX tables for results
Goal: Chapter 4 done, Chapter 5 half done Target hours: 4 hours
Tuesday, January 27 (Day 12)
Finish Chapter 5 + Start Chapter 6
- Write Chapter 5 Section 5.4 (Results - Unreal)
- Write Chapter 5 Section 5.5 (Comparative analysis)
- Insert all figures and tables with proper references
- Chapter 6 Section 6.1: Graphics capabilities (Unity URP vs Unreal)
- Chapter 6 Section 6.2: Shader systems comparison
Goal: Chapter 5 complete, Chapter 6 started Target hours: 4 hours
Wednesday, January 28 (Day 13)
Finish Chapter 6
- Chapter 6 Section 6.3: Lighting and post-processing
- Chapter 6 Section 6.4: Physics engine comparison
- Chapter 6 Section 6.5: Audio systems
- Chapter 6 Section 6.6: Animation systems
- Chapter 6 Section 6.7: Scripting and workflow
- Integrate interview quotes where relevant
Goal: Chapter 6 complete Target hours: 4 hours
Thursday, January 29 (Day 14)
Chapter 7 - Results Comparison
- Chapter 7 Section 7.1: Synthesis of performance results
- Create master comparison table (all metrics)
- Chapter 7 Section 7.2: Multi-criteria analysis
- Create comparison matrix (performance vs features vs usability)
- Chapter 7 Section 7.3: Use case recommendations
- Chapter 7 Section 7.4: Research limitations
Goal: Chapter 7 complete Target hours: 4 hours
📅 Week 3: January 30 - February 5 - POLISH & INTEGRATION
Friday, January 30 (Day 15)
Chapter 8 - Conclusions
- Chapter 8 Section 8.1: Main research findings
- Answer all research questions from introduction
- Verify hypotheses (state which confirmed/rejected)
- Chapter 8 Section 8.2: Practical recommendations
- Chapter 8 Section 8.3: Scientific contribution
- Chapter 8 Section 8.4: Limitations and future work
✅ DELAYED WEEK 2 MILESTONE: All core chapters complete (first draft) Target hours: 8 hours
Saturday, January 31 (Day 16)
Bibliography & Figures
- Review all citations in bibliografia.bib
- Add missing references (Unity/Unreal docs, tools)
- Verify citation format consistency
- Verify all figures are in tex/img/ directory
- Check that all figures have proper captions
- Ensure all tables have captions above them
- Polish graph aesthetics (fonts, colors, labels)
Goal: Bibliography done, figures publication-ready Target hours: 8 hours
Sunday, February 01 (Day 17)
Appendices & Cross-references
- Create Appendix A: Interview question template
- Create Appendix B: Detailed performance data tables
- Create Appendix C: Test environment specifications
- Create Appendix D: Nsight configuration details
- Update appendices list in main.tex
- Update list of figures, tables, table of contents
- Check acronyms list (add any missing)
- Verify all cross-references work
Goal: Appendices created, all lists correct Target hours: 8 hours
Monday, February 02 (Day 18)
First Complete Review
- Compile complete thesis
- Read entire thesis start to finish
- Make notes of sections needing improvement
- Check logical flow between chapters
- Create prioritized list of issues to fix
Goal: Complete PDF generated, issue list created Target hours: 4 hours
Tuesday, February 03 (Day 19)
Fix Issues & Polish
- Fix top 15 issues from review list
- Improve transitions between chapters
- Ensure terminology consistency
- Polish introduction
- Polish abstract
Goal: Major issues addressed Target hours: 4 hours
Wednesday, February 04 (Day 20)
Final Polish & Send to Advisor
- Fix remaining issues from review list
- Final polish pass on all chapters
- Recompile thesis
- Read abstract and conclusions again
- Send thesis PDF to advisor (dr inż. Michał Chwesiuk)
✅ DELAYED WEEK 3 MILESTONE: Complete thesis sent for feedback Target hours: 4 hours
Thursday, February 05 (Day 21)
Proofreading Pass 1
- Proofread abstract (Polish + English)
- Check Polish grammar and style
- Proofread Chapters 1-3
- Check for typos and grammar errors
- Verify technical terminology is correct
Goal: First half proofread Target hours: 4 hours
📅 Week 4: February 6-15 - FINAL POLISH & SUBMISSION
Friday, February 06 (Day 22)
Proofreading Pass 2 + Advisor Feedback
- Incorporate advisor feedback (if received)
- Proofread Chapters 4-6
- Check all code listings format correctly
- Verify all URLs in bibliography work
- Check footnotes
Goal: More proofreading, feedback addressed Target hours: 8 hours
Saturday, February 07 (Day 23)
Final Proofreading + Formatting Check
- Proofread Chapters 7-8
- Check formatting requirements:
- Margins correct
- Font sizes correct
- Line spacing correct
- Page numbers correct
- Headers/footers correct
- Verify title page information
- Verify formatting against WUT requirements
Goal: Complete proofreading, formatting verified Target hours: 8 hours
Sunday, February 08 (Day 24)
Final Compilation & Verification
- Compile final PDF
- Verify all citations compile without errors
- Check all figures render correctly
- Verify all cross-references point to correct pages
- Run spell-check on Polish sections
- Run spell-check on English sections
- Create backup of everything (thesis, source, data)
Goal: Final, clean PDF generated Target hours: 8 hours
Monday, February 09 (Day 25)
Submission Preparation
- Check WUT submission requirements (digital/print)
- Print required number of copies (if needed)
- Bind thesis at print shop (if needed)
- Prepare digital submission files
- Prepare any additional documents needed
Goal: Physical copies ready (if required) Target hours: 4 hours
Tuesday, February 10 (Day 26)
Buffer Day - Final Fixes
- Address any last-minute issues
- Final review of submission requirements
- Triple-check deadline and submission process
- Test upload process if possible
- Rest and prepare mentally
Goal: Everything ready, peace of mind Target hours: 4 hours
Wednesday, February 11 (Day 27)
Buffer Day
- Handle any unexpected issues
- Final verification of all materials
- Ensure submission files are ready
- Have submission checklist ready
Goal: Buffer for emergencies Target hours: 4 hours
Thursday, February 12 (Day 28)
Buffer Day
- Final review of everything
- Address any last issues
- Prepare thesis files for upload
- Rest before submission
Goal: Ready for submission Target hours: 4 hours
Friday, February 13 (Day 29)
- Final review of submission requirements
- Prepare any additional documents needed
- Triple-check deadline and submission process
- Have submission checklist ready
- Prepare thesis files for upload
Goal: All submission materials ready Target hours: 8 hours
Saturday, February 14 (Day 30)
- Final final review of thesis PDF
- Check all links and references work
- Verify file sizes and formats
- Test upload process if possible
- Rest and prepare mentally
Goal: Everything verified and ready Target hours: 8 hours
Sunday, February 15 (Day 31) - SUBMISSION DAY 🎯
- Submit thesis via required channels
- Confirm submission received
- Save confirmation email/receipt
- Backup final submitted version
- CELEBRATE! 🎉🎓
✅ FINAL MILESTONE: THESIS SUBMITTED ON TIME!
🔥 Daily Routine Recommendation
Morning (9:00-13:00): 4 hours
- This is prime writing/analysis time
- Focus on hardest task of the day
- Minimize distractions
Afternoon (14:00-17:00): 3 hours
- Technical work (LaTeX, figures, data)
- Less intensive tasks
- Take a proper lunch break!
Evening (19:00-21:00): 2 hours (optional)
- Light editing and review
- Planning for next day
- Only if you have energy
Rest:
- Get 7-8 hours of sleep
- Take short breaks (5 min every 25 min)
- Exercise/walk daily
- Eat properly!
✅ Quick Daily Log Template
Date: ___/___/2026
Hours: ___
Mood: 😊 😐 😟
Done today:
1. ________________
2. ________________
3. ________________
Tomorrow's top 3:
1. ________________
2. ________________
3. ________________
Remember: Progress over perfection. Every day counts. You've got this! 💪