Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


1. Time record requirements: time + content
2. Team progress: sprint: semi-monthly synchronization + regular stand meeting/ "morning" meeting
3. Team:
1. Algorithms (Good mathematical foundation, especially linear algebra and mathematical analysis (calculus))
2. Architecture (code structure control, assist algorithm landing, solve difficult bugs)
3. Engineering (divided into large and small car groups, filled in code details, fine-tuned operation feel, assisted in mechanical structure testing)
4. (New team member: Read code, assist with documentation, unit testing and integration testing(future))
4. Personnel:
1. Algorithm: Renzo Li Yihe (secondary) Temirlan(secondary)
2. Structure: Li Yihe (primary) Zhang Tianyi Temirlan(primary)
3. Engineering: Yu Heng, Guo Ynuo, Song Yuchen, Tang Belong, Song Yuchen
5. Management: Li Yihe, Zhang Tianyi Reference: Agile development (notice: Simplify the process!!)
6. Development cooperation: git + *wiki*
1. Record experiences, bug debugging, cooperation records and usage methods
7. Code management: pros encapsulates pros twice and three times
1. Source code file management (.hpp.cpp), binary file management (.lib.exe) (code reusability)
2. Interface management and class management (code security)
3. Code comment specification (code readability)
4. review (Necessary?)
5. Unit testing and integration testing (1. Small project scale 2. Large learning cost -> *temporarily* abandoned)
6. Code space-time efficiency awareness (htusz says brain write often freezes)
8. *Code architecture*
1. Create a folder under /include to store the.hpp library files created by the team
2. /src stores the.cpp source file
3. Specific structure path: self-study + explanation
4. Learning the new architecture Maintain some maintenance of the old code
5. Reference: https://github.com/Tualatin-Robotics/VEX-69247A https://github.com/kekland/1737b-vex https://github.com/LouisAsanaka/VEX-Change-Up https://github.com/81208X/VRC2020
6. Overall structure: public version + vehicle crew (long-term planning)
9. Workflow
1. vscode (remember to update regularly to fit pros) + pros (Enable automatic update, pros updated to the latest version) (macos workflow will be give by Li Yihe)
2. wiki (duke wiki )
3. git + *github*

  • No labels