New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added Architecture and Design Doc #1012
Added Architecture and Design Doc #1012
Conversation
…/Software into mathew/architecture_doc
Added robot status
Added design patterns
Combined the convention diagrams
done |
Made a bunch of changes, ready for re-review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 💯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we indicate on the coordinate_and_angle_convention_diagram
where (0,0)
is? Would also be helpful (but not necessary) to indicate which of {x,y} are positive/negative in each quadrant.
7305e74
Updated the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 🎉
@scveloso @matthewberends @jared-paul need re-review (and approval) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
@scveloso @jared-paul can you please take another look so we can wrap this up? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
informative, LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 👍
Please fill out the following before requesting review on this PR
Description
Added a big document that explains our architecture, system design, important components, and design patterns.
I also tweaked all the other docs to either fix links, or make minor updates.
I'm tagging more people than usual for review, since this will really benefit from more eyes and opinions. Please comment if anything isn't clear, if I missed anything, etc. We really want this documentation to be solid so it's useful to everyone.
The documentation focuses more on higher-level concepts and ideas, rather than any specific implementations since those can be read in the code, and we don't want to have to update the documentation often. That being said please let me know if you think sections need more detail.
HOW TO REVIEW
Reading raw markdown isn't easy. I'd recommend clicking "View file" for each changed file and just reading the nicely formatted markdown. If you have something to comment on, then go back and find the closest change and leave a comment there.
Testing Done
N/A. Manually made sure as many links work as possible.
Resolved Issues
resolves #878
resolves #879
resolves #880
Length Justification
The architecture doc is pretty big, and I wanted to do everything all at once to make linking easier.
Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
.h
file) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom
. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.TODO
(or similar) statements should either be completed or associated with a github issue